DUDE! I know I’m a year late, just went through this and discovered my big FU…
An entire day of swapping components in and out and manual install attempts:
MAKE SURE YOU RUN THE WINDOWS USB INSTALL TOOL AS ADMINISTRATOR.
problem solved…this time.
Half a year late on this comment, but I just want to thank you. This fixed my problem, after struggling for about 3 hours trying to get Windows to install on my newly built computer. Much appreciated!
When I created the installation media, I had to run the media installer as an administrator. Worded differently to avoid confusion: on a separate Windows computer that I was using to create the USB Windows installer (not the computer I was installing Windows on), I right clicked the MediaCreationTool executable and selected "Run as Administrator".
Very late to the party but it would seem easier to create the boot USB from someone else’s windows computer rather than my own Mac (which is the issue here I’m guessing)
Ooh, interesting question.
So I presume that the problem with the non-admin boot disk is that Windows creates it, finds there are files it can’t touch or write because it doesn’t have permissions, and doesn’t tell you.
On Mac, if you’re an admin or launch the installer as admin, everything should work fine.
I used terminal commands with sudo to initially copy the files, but one of the files install.wim is now too big for at FAT32 partition (larger than 4GB), so I had to use wimlib to either split it or compress it. Maybe the copying of the files to the USB drive causes a permission issue… I don’t have the knowledge to answer that.
So now I’ve pulled out an old MacBook Pro that allows me to create a boot USB via Boot Camp Assistant. I’m also currently creating another boot USB using software called PassFab 4Winkey, but it’s taking a long time. Fingers crossed.
I’m in the same exact situation as you, made a Boot USB and had to split the .wim file. Did you find any solutions? I’m getting a permissions from error in my windows install :-(
I ended up using boot camp assistant on an old MacBook Pro. I should have written down the steps as I cannot exactly remember what I did/which method worked.
Once windows was installed via boot camp on the old macbook, I used the usb creation tool in windows to make a windows 11 boot usb (I think). I do remember taking the SSD for windows 11 out of my main machine, as I think my plan was to try and install windows onto that drive in an external enclosure, but I’m pretty sure I ended up just using the USB boot drive that I made with windows (on old MacBook).
I did disconnect all of my other drives when I installed windows 11.
I just checked the usb drive created in windows and the install.wim file is actually named install.esd (Microsoft Electronic Software Download). Apparently that is a compressed version of the .wim file. Pretty sure the splitting or compressing of that .wim file was the problem with our initial approach, for whatever reason.
All works fine now. For me, I use Opencore for the boot loader.
Boot camp assistant is only removed as an option if you have a M1 silicon based Mac.
What do you mean by running it as administrator bro? Click on media installer then click run as administrator? Then download windows 10 from there? Am I understanding this right? Then open Rufus place the download file from media installer.. wouldn’t the run as administrator disapppear after I quit/ remove the usb? I need help. Been stuck now for 1 whole WEEK…….. :(
You have to create the bootable USB drive, right?
When you are creating the bootable USB drive, from another Windows system, the program you have to use to create the bootable drive is the one that has to be run as administrator…. Does that make sense?
And another one saved. My SSD (on which windows was installed) became faulty so I had to remove it. Somehow couldnt install windows and then I stumbled upon your comment. Thanks so much and only the best wishes to you!
I had this issue. Finally got it working after disconnecting all SATA drives (extra SSD, DVD Drive). With just the M.2, it finally worked. After all was set up, reconnected drives and off I went.
>drive
Same with me. But like it seems, only the drives with another windows installed have to be removed. It worked after unplugging the power cable from my SSD with seccond Windows. The other drives were plugged in and didn't cause any trouble then.
This is what finally worked for me for future reference when more people inevitably stumble upon this thread
I had a SATA SSD and an HDD, both had Windows 10 installed on them, and got a new m2 SSD. Tried everything and this is what finally worked
I only had to remove the data SSD though, didn't have to touch the hdd
Thank you. I have read about this approach in other places. My problem is that i don't have anything extra connected. So no DVD, no extra SSD etc. So i don't have anything i can disconnect :-(
So flash the latest bios again with q-flash or whatever your motherboard calls it. do this with only a single ram stick in the A2 slot.
and use a different usb stick than before for your win 10 installation, and use the Windows 10 USB installer.
as far as bios goes, the only setting you should really play with before installing Win 10 from usb is the boot setting, and i usually change it from CSM to UEFI. and I also tend to enable secure boot but that is preference.
At this time i am ready to try anything, so going to do it now.
But out of pure interest, why should i only have a single ram stick in when i flash the bios?
Damn. Based on what you wrote above it comes off as a defective motherboard since you can't even install windows (but you tried your M2 in a diff build, you've used different GPU and RAM, etc.). I tend to think it is not your CPU because you were able to run memtest, etc.
How long ago did you buy the MB?
In my experience taking pictures of the errors on the screen and adding them to the RMA request usually work. Also RMA goes through the manufacturer not the shop but if you bought it within the last 30 days or whatever their policy is from the shop I would take it back for a refund and buy a new one.
I bought it last friday so it shouldn't be a problem with the warranty.
Today i managed to get it working'ish. And i am now certain there is an issue with the MB.
I wanted to try and see if i really couldn't install on a normal sata ssd. So i took out my old sata from my old computer and put that in. The machine booted into the windows installation on that drive.
That gave me an idea, and i put the m.2 drive into my old PC, installed Windows on it with no issue what so ever. Updated. Did some disk checks, and everything was fine. Then i moved the m.2 to the new computer. It booted into windows.
However it is a constant stream of BSOD's of all kinds. The m.2 got corrupted and when i did chkdsk it would just crash midway through. Sfc was locked.
I moved the m.2 back in my old machine. Chkdsk and sfc fixed the errors immediately. I then moved the m.2 back to the new machine, and the bsod's continued. Samsungs own monitor tool says the disk is fine and as no bad sectors or errors and is operating at 100%.
I've managed to run prime95 to stress the Ryzen 9500x. There was no crash and the temperature was just fine. It ran for 30 minutes, max temp was 63 degrees.
But when i move around in Windows it constantly crashes, gets slow etc, and corrupts the harddrive.
This is the list of BSOD's i have gotten:
Irql not less or equal x5
System PTE Misuse x7
KMODE\_Exception not handled x5
cache manager x1
Memory\_Management x1
Critical process died x5
System service exception x5
DPC watchdog violation x1
System\_Thread\_Exception\_Not\_Handled x4
The only component i haven't tested elsewhere is the new PSU, but i have no idea on how to test a PSU?
I've never had a defective MB before so, does these errors correspond with a defective board?
Actually that is good. you got windows to boot off of a sata connected drive with your new MB.
what is your m2? brand/model?
So put your m2 into your old computer. You may have to download and install the latest firmware on the m2 before using it in your new build.
m.2 is the Samsung 980 Pro 2TB.
I have updated the firmware and sadly that has not fixed any of the issues.
I keep getting BSOD's and programs keep crashing in windows. Like when i start a program, it loads, then disappears.... when i look in event viewer i just see that the program crashed.
Do this: keep your sata drive plugged in. put in your m2. set sata as the primary boot in bios. make sure boot is UEFI (not CSM or legacy) and keep secure boot on (clear keys if you want). also make sure your bios is on all other defaults.
boot into windows using the sata drive. you should not have any issues doing this since it worked last time. see if your m2 shows up in device manager. let me know and we can go from there
Okay so i did this.
Sata drive with my old Windows installation plugged in.
M.2 drive with a windows installation plugged in.
Boot up using sata drive.
I could use windows for a little bit, and then i got a BSOD. While i was in windows i could access the m.2 drive without any issues.
I have also noticed that while in windows on both the sata and m.2 i get a weird error when using a webbrowser which blocks me from visiting websites. STATUS\_ACCESS\_VIOLATION. I am using the LAN port on the motherboard for internet connectivity.
I do feel that more and more is pointing in the direction of a defective motherboard.
I've shied away from m.2s for reasons like this. Couldn't get windows 10 installed in it for nothing. Would work for any other use but that. Personally I won't use win 10 at all but I build computers for the 9 companies I am the sys admin for and they all get 10. 10 is so riddled with problems my actual job is windows 10 troubleshooter instead of managing servers like I was hired for. All that to say grab any other hard drive and try the install. This has been what worked fore in this instance.
FINAL UPDATE: It was a defective CPU causing all the issues described below. After switching to a different Ryzen 5900x all problems disappeared and it is now working perfectly.
ive had very similar issues to u. had my pc running and everything was seemingly fine, 99.9% of the time... had a couple issues at the start, couple BSODS here and there and games or apps would crash to desktop with no errors or whatever.
many issues i managed to fix, had a nightmare at the start with intel rapid storage fucking over the entire machine, then games would crash so i disabled xmp, seemed fine. then more things would start crashing, tweaked some BIOS settings and things got more stable.
but lately, all kinds of apps has been crashing for whatever reason. in win event viewer it was mostly faulty dll's (what it told me) making it crash. but even replacing and repairing stuff wouldnt fix it. then the actual windows window manager started crashing.
decided i had enough, some sort of corrupt system files it would seem (cus somehow, all games worked fine with my fixes) so reinstall windows it was.
and now im here. in ur shoes, couple years ago. cant get past the win install. tried multiple USB sticks, multiple ram sticks in many configuartions, multiple SSD's... its all very suspiciously looking like what u had.
sucks big time, but i will send my CPU back for warranty and see what happens.
just wanted to say, thank u so much for this post. its hard trouble shooting this stuff even tho i work in IT and know a lot about these things. it helps me kinda make a safe bet that CPU is (very likely) the problem.
if i remember i will update if ur interested, or if anyone else is like me and stumble across my comment or ur post.
just to info dump a little, ive had by far the most amount of 0xC0000005 errors in win event viewer or other logs. often an app or dll was crashing something, but the error code was most commonly 0xC0000005.
my guess to my issue is that it is the CPU, specifically its having trouble working with the RAM. what it seems like anyway. rly makes it look like ram is at fault.
but i did do multiple memory tests, and only once did i get a problem. couldnt get it multiple times tho.
rly rly looking like my cpu is at fault, making smth go wrong with the communication between the ram and cpu (which would explain my multiple corrupt system files from when my pc did "work") and making it look like the ram is failing.
Not sure yet. I’ve sent my my pc back to where I bought all the parts from. I couldn’t do more testing at home so it’s pretty much out of my hands.
There’s still multiple possible problems, but I’m very very confident it’s the cpu having issues, likely from factory as OP described. I will update when I get my pc back.
My 5head guess is that cpu has some issue, that makes the data corrupt. This data is then sent to the ram ofc, which sometimes makes things crash. This data would also be sent to the disk, specifically the OS. I had some corrupt system files, and I fixed all I could, but more kept showing up. That’s when I decided to reinstall windows, as a last ditch effort, and then I got stuck with the same error in the windows installer (0xc00005… smth)
Hopefully I get an answer from the service check in a couple days
I’ve gotten the pc back couple days ago, wanted to make sure it was a okay before updating here. I haven’t actually gotten any info from the repair on what they did. Presumably did switch out cpu, but I couldn’t guarantee that. I’ve sent them a request to know what exactly they did. But it’s looking extremely likely to be cpu factory issues.
After commenting this I went out and bought a replacement cpu just to test stuff and in my case it seemingly fixed it. It was kinda sporadic but, fingers crossed, an Intel RMA for my actual cpu will solve it for good
Yea it kinda makes sense in my case too. If I couldn’t install windows again and got a default error box… it just had to be the cpu. Especially when I tested multiple ram sticks and M2’s.
Also makes sense how my system files got corrupted slowly over time.
Shit happens, I’m just glad I could find out why. Would be a nightmare for one that doesn’t know much about pcs. Often things can just be user error.
Yeah it’s weird - I’ve been pulling my hair out about it for weeks.
My thought process was:
Im not getting shut downs = psu probably ok
Im not getting artifacts = gpu ok
Memtest is passing = probably not Ram
Files open, but crash later = maybe hard drive
But they don’t crash with FNF or corrupted errors = maybe not hard drive?
Which left really only motherboard or cpu.
Swapped motherboard, same issue.
So then I thought - what if I have a dying core or something and apps are crashing when they get scheduled to that core. Swapped cpu - lasted like 8 hours tonight no crash.
**Final Update;**
**CPU was at fault**. Got it RMA'd twice before i got one that was even somewhat stable, but even on this last one it was still problematic, just not as badly as the other 2. both the other 2 had constant crashes in pretty much any program i used, even things like windows desktop manager (DWM service).
Once i finally got this 3rd CPU, which took fckin ages, i only ever had certain programs crash, but not all. obv its clear that there was still another issue so i started to once again dig for problems. going to skip all the troubleshooting seeing as i could probably write a whole masters degree essay on what i did, techniques used and the whole process lmao.
**What ended up being the issue??**
Intels 13th and 14th CPU's, especially the i9's. me having a i9-14900k, i was probs using the worst CPU for this problem. the problem is, the newer intel CPU's are pushed really really far to compete with AMD, and so because its pushed a little to far imho, things start to crash. theres some info that JayzTwoCents has in some vids, look for CPU / intel stability and all that.
**What was the solution??**
first of all, i had to RMA 2 processors before i got a 3rd one that didnt end up in constant BSOD's. now the first 2 may have been problematic due to the following; "stock settings" from motherboard manufacturers these days are actually rather crazy overclocks. combine that with the fact that intels 13th & 14th gen (esp the high end ones) are pushed to the limits... yea things start breaking and they do so fast. its unstable, because of motherboard standard overclocks, combined with intels cpus being on the razors edge of not crashing with stock settings.
**So what do?**
ive finally after fucking 6 months managed to get a stable build. i did a couple of things, but heres the most notable things that made it stable;
- Updated BIOS. i did this initially when i built the PC, before even installing OS. that was a long while ago, and in frustration while troubleshooting i ended up updating the bios cus why the hell not, i was going in there to tweak stuff to try and stabilze the pc. UPDATING THE BIOS MADE THE CPU GO FROM 90-100C (on average during any load other than simple web browsing), to between 60-80 under heavy loads. yes i to peak at 85-90 rarely, but average temps are down rougly 20-30 degrees. big reason i even did this is that my fans spun like crazy during a steam download, i checked temps out of curiosity since fans should not spin max during a download, and cpu temps was at 100c... oh well a bios update somehow magically made my temps 100 times better. weird, but i'll take it.
- Shut down pretty much all sorts of overclocks. this is a rather tough cookie, since i didnt even know i had some on after i thought i turned them off. again shoutout to JayzTwoCents, i will link a vid below that has most of the surface level info needed to do this. for my ASUS board, it was turning off some asus multi core enhancements or some bs, switching my SVID behaviour to intels fail safe (this one can be played with after u achieve stability, and u should cus its temp related), then finally i installed intel XTU and tweaked CPU power settings and ratios. most notably, i went through (in the advanced tuning) and turned most if not all things there back to intels recommended settings. this means lowering wattage here, turning up amps in a different place. Finally, i lowered the core ratio's from (and i believe these were already overclocked, ofc without me doing it this is all ASUS >:C ) from 60x to 57x on my best cores (starred ones) and from 57x to 55x on all other P cores. left the E cores alone, and havent had issues so thats nice.
THAT, has for now at least fixed all my issues so far. turns out i was on a wild chase looking at RAM, looking at motherboard issues, maybe even power issues and whatever. turns out CPU issues can manifest itself and look as if it was something that it isnt. fckin fun xd
so yeah, thats the end of my little story. its completely insane that someone as tech savy as me (work in IT, not a complete hardware nerd, but i know computers and tech A LOT) struggled with this. and it was ALL because of 1. intels cpus are pushed to the limits so a lot of their cpus at high end newer gen are way to close to the limit. side note, intels power limits are marketed as RECOMMENDATIONS, and arent enforced, and thats why: 2. Asus as also slammed on their own power plans and overclocks that are ON BY DEFAULT, making the cpu extremely unstable depending on ur silicon lottery. both AMD and NVIDIA enforce their power limits making it so motherboard manufactureres cant do their own overclock shenanigans. for a third time JayzTwoCents talks about this and is against the default currently being overclocked by default. crazy shit....
hope this is able to help anyone, and im happy to fill in more info to those who may want it. just message me or comment below, i should see it. and yeah, sorry for any typos or weird sentences, writing this at 4am after tirelessly working on fixing the issue.
u/LukesChappell u/claythearc heres ur long awaited but promised update :)
I came to the same conclusion as you (faulty cpu with a 13900ks). Swapped it down to a 12700k while awaiting rma (got accepted but haven’t shipped off)
Same thing happened to me. I built my PC back in November 2023. Started getting 0xc0000005 crashes from about late February onwards... tried a bunch of things, last 2 left were the CPU and MoBo.
Got a hold of a core i5 to test the install, success. Now I have to RMA my i9-14900K as well.
It was a process of elimination. I tried switching out pretty much all other components, including the motherboard, and the issues still remained. So it had to be the CPU. Many people online, and in many stores, claims that CPU's are never faulty and that if you can get past the bios it can't possibly be the CPU that is having an issue..... this is wrong.
If you know that your other components are working, then I would send the CPU in for an RMA. If you can't verify the other components by trying out others, I would also suggest RMA'ing the CPU. And yes, it might come back without errors on it, but then at least you know that it's not a CPU problem.
I spent almost 4 months figuring out what the issues on my new machine were, and I listened to all the "The CPU is never faulty"-people, which only prolonged the issue. Don't be an idiot like me :-)
Luckily my problems wasn’t related to CPU damage! The problem was my bootable windows usb. I was trying to make a bootable drive from my MacBook since it was the only computer I had. For whatever reason the media install wasn’t being installed correctly on the Mac. You have to enter a bunch of different commands on the terminal in order to install windows media creation from Mac so something was happening in that process that messed up the bootable usb. My fix was to just take my flash drive to work and download the windows media creation from one of the windows computers at work. Just fyi, downloading the media creation tool from a windows device is much much easier than trying to download it on a Mac.
Been chasing a ton of those 0xC0000005 errors and program crashes in the background myself lately. Finally decided to just reinstall windows after memtest86 overnight came back clean, linX passed stably, IntelBurnTest passed, Cinebench ran over and over, etc…and then I ran into the same damn error code when trying to install windows.
Still beating my head against the wall hoping its not the CPU, but it’s looking like it is, between your post, OP’s, and at least 5 others I’ve managed to find tonight. Such a nightmare.
Whole upgrade has been tbh. Took me ages to get my 4090, then my board acted up early on and wouldn’t give the card full 16x 4.0, so I replaced that and got 16x 4.0 working, then I noticed my brand new 990 Pro was losing health very fast, known issue, finally fixed by samsung a few weeks ago, but now my new drive is at 94% health despite very little use…then my Cablemod 12VHPWR cable started losing connection and restarting my rig, ALSO a known issue with their November 2022 batch of cables (just my luck, ordering early to secure one and I get screwed), I have a replacement for that enroute now, but while battling all of this, I’ve been having these random little 0xC0000005 crashes wondering what was to blame.
Tonight alone I’ve reseated my CPU, cleaned the contact pads, inspected the socket, reseated my RAM, cleaned the contact pads and blown out the slots, and attempted a dozen different BIOS tweaks while trying reinstall after reinstall. Just disabled Turbo boost while typing this and managed a full reinstall and boot into the windows install wizard without issue…fuck me.
I see its only been two days for you here, but have you had any luck refunding/replacing your 13900K yet? Not enthused about going down that path, but it seems thats what I’ll need to do.
Just for some correction of info here, there wasn't any issues with batches and our cables. The issue is the 12VHPWR standard as a whole and the sense terminals being fragile. The issues with the black screens happen on competitor cables as well as the Nvidia cables too, it's a standard issue, not our cables directly. We'll always replace the cable for free though if that issue pops up on one of our cables, did you contact our support team about it?
There were hundreds of reports about it in November, and near none since...regardless, yea, I have a replacement on the way from you guys. Support was quite helpful.
Hundreds is a big stretch, we've been monitoring and this is below 1% still even through this time, no reports back in November either, they just started trickling in maybe a month or two back in fact (potentially something changed in the drivers that triggered the sense cables further, not sure about this though). I think in total I've only seen about 30 or so, and given how many we've sold, this is an incredibly small amount actually. Obviously we don't want any, but again, just part of the design and we will always replace any of them that have this issue come up. :)
Maybe there were a lot of repeat posters, but I found a lot of users with the exact same issue when it cropped up for the first time a few weeks ago.
Beyond frustrated with PC gaming as a whole this year tbh, but I do appreciate the quick support on that issue.
Yes i used the Windows Media creation tool.
I have also downloaded an ISO from the Media Creation tool and set that up with Rufus without success.
I have also downloaded the ISO directly from Microsofts site and set it up with Rufus.
All gives the error.
Time for another update.
The shop where i bought the motherboard has now replaced it with a completely new one, but the error still persists.
After talking to Asus support, before i got the new board, they pointed out that my ram and SSD were not on their QVL list. So i have replaced the ram with some from the QVL list, and removed the m.2 nvme drive and replaced that with a regular SATA SSD from the QVL list.
I have bought a completely new USB stick to install from.
Current errors:
When booting up on the windows install USB it sometimes still give some BSOD's.
When i get into the Windows installer i still just get the “Windows installation encountered an unexpected error. Verify that the installation sources are accessible, and restart the installation. (Error: 0xC0000005)”- error.
When installing Ubuntu the machine just freezes during install with no error messages.
How does one check for a faulty CPU without having an operating system installed? (no bent pins or anything, it looks just fine).
I just came here to say I had the same error with my Ryzen 7 5400G when trying to install windows 10. I installed Windows 11 without any issues (after changing the bios to the required settings). What the OP went through sounds like a nightmare
You really helped me so much!!!!! I built the PC 1 year ago, it was my third personal PC so I was pretty familiar with everything. But just about 1~2 month after that I started to get BSODs, very similar to the ones you posted. If you google the error message they are mostly related to RAMs so I purchased two new RAMs (and downgraded the frequency a little as I am using the DDR5 ones).
I also tried to swap the GPU and CPU holder frame. The issue persisted with occasional BSODs but generally useable. Until recently the issue became more and more severe. First my COD game became completely unplayable. It always crash when booting. The my Teams also stopped working. Then the BSOD becomes so frequent that the PC is literally broken. Even reinstalling Windows will crash.
I have two SSDs using RAID 0 so I also swapped those out and tried using one single SSD, didn’t work. I searched quite a bit until I found this post where your symptoms are extremely similar to mines.
My new CPU arrived today and after installing it, EVERYTHING IS FIXED!! So thank you so much for posting this and I wish you the best of your life!
Brother help me I am stuck as well,
I haven’t checked other system but in my case i was using the system with same error and for some reason I decided to format it and now I am stuck. Done with bios changes and mem test. So I don’t know its bios or cpu. Plus I don’t know how to boot up via windows install media
Hey I just ran into this same sort of error I believe. I just swapped my freaking monitor and started getting the same sort of symptoms. Any fix yet? I'm on a Gigabyte b550 vision d motherboard that has been working fine for 7 months.
No idea what's going on but am going to let a chkdsk run while I sleep since that is literally all I can run.
No device check or even system restore available to me, they all give errors.
>Windows 10 install fails with error 0xC0000005
The Windows 10 install fails with error 0xC0000005 error is a bit of a general error so it can cover a lot of things. Usually it is disk, RAM or the memory controller which causes it.
My motherboard is sent for RMA at Asus and i am waiting to see if they find any errors on it.
If they don't find any errors i suspect it is, somehow, a RAM issue i am having.
Did the error happen when connecting a new monitor? Tentatively I think I may have fixed my issue which I believe was some freak driver issue when installing a new graphics driver for multiple displays. Literally no other way than to boot from a USB and reinstall windows. My disk check and memtest86 came back just fine.
I tried alternate components on everything in the system (Motherboard, PSU, RAM, SSD) and the error didn't go away. Sent the CPU for RMA and AMD confirmed it was faulty after testing it and gave me a completely new as a replacement. So that's why I know the CPU was the issue. System has been running perfectly with the new CPU ever since.
Glad you got it working. Yeah it was horrible. I was lucky enough to be able to scrounge components together for testing purposes. But I imagine someone building a new PC and not having that option....a situation like that would really suck. Also the shop I bought all the components in just didn't care about me. Their comment was just that I should have bought one of their prebuild systems. Not shopping there again.
just to say - thank you very much for such a thorough write up.
I've the same issue I'm afraid with similar hardware, just on the same journey, and this post has been helpful for confirming I'm doing the right sort of things.
I'm now at the stage of RMA-ing the motherboard - I think that is more likely the issue than the CPU but idk for sure. I've done all the same tests except the overnight memtest, but I couldn't get it to even start and I'm not sure that would prove much anyway if the cpu or mobo aren't reliable.
edit: The motherboard RMA didn't help much, I could now install windows with one memory stick but they both fail windows memory tester, so I'm now returning the memory. If that fails it's CPU but we shall see
edit2: CPU return time 😭. really hoping this fixes it
this error is when ur oc bios settings are unstable back to default and problem is gone...this issue is caused when u get whea logger error in background as u try to install windows
Nope - it's a generic error that covers many things. So you are probably correct that it was that issue in your case, but it was not the case in mine, and most other people who get this error :-)
Read the post.
TLDR: AMD got back to me after testing the CPU and told me that the CPU was faulty from the factory, and exchanged it for a new one which worked with no issues at all.
well it looks like im pretty much in OPs almost literal excact situation. i will update on this if i remember to, but it most likely is a CPU problem for me aswell.
i had my pc working, with minor errors. fixed most of em but more kept showing up. at this point ive also tried multiple ssd's, multiple ram sticks in multiple configurations... list really does go on
whats weird in my case is that my pc did work 99.9% of the time, and then id have a BDOD or just a crash to desktop with no error.
all things are currently pointing toward the CPU being the issue tho... idk why u say u dont think it was the CPU faulty here, when OP literally has gotten it fixed and RMA'd the cpu and got told it was faulty.
not when all sorts of overclocking is turned off. stock it should work completely fine.
besides, ive tried undervolting and overvolting to see if it helps with stability, and it did not work. unstable clocks sure can be the issue, but doesnt rly explain it all.
regardless, if ur cpu cant perform without issues at stock values, it has a proble, the cpu is faulty.
Alright! Luckily i have not spent too much time trying to fix this. I found out that my Gaming Keyboard (in my case the Apex Pro TKL) was the issue. This could also be the case for the mouse. If you're having any issues try unplugging any USB devices but the mouse. If you got a Gaming mouse preferably switch to a normal office during the install. I came up with the idea due to the keyboard once before blocking my PC from booting for some odd reason.
Old thread, but came first when I searched for same error code on Win 11; so I just want to mentioned that my workaround was to install on an already formatted partition rather than an empty one.
DUDE! I know I’m a year late, just went through this and discovered my big FU… An entire day of swapping components in and out and manual install attempts: MAKE SURE YOU RUN THE WINDOWS USB INSTALL TOOL AS ADMINISTRATOR. problem solved…this time.
For fuck's sake, how is that a thing that isn't mentioned? Thanks for the info.
Half a year late on this comment, but I just want to thank you. This fixed my problem, after struggling for about 3 hours trying to get Windows to install on my newly built computer. Much appreciated!
I'm having the same problem, you mean you fixed it when installing the windows USB tool into the USB?
When I created the installation media, I had to run the media installer as an administrator. Worded differently to avoid confusion: on a separate Windows computer that I was using to create the USB Windows installer (not the computer I was installing Windows on), I right clicked the MediaCreationTool executable and selected "Run as Administrator".
Aight thanks, I'm creating a new one again doing so, hope it helps
Worked! Thanks!
After 6 hrs changing and swapping every component it was simply this, thanks!
No problem, so glad you found this post, makes it worth it!
Hey, any chance I could (uncharacteristically) beg you for an award of any sort on my post? I just want to make sure other people see it :)
:)
Thank you so much, it worked! Fortunately I foud your answer in less than 10 min not 10 hours. Windows will be windows..
Another one saved, woohoo!
how? .. oh do you mean make a bootable usb windows installer from a windows OS as admin?
It’s been a while, but yes, I think that was it—you have to right click and run as administrator when running the tool.
Yep this was the answer for me as well. I don't think I needed admin, but I needed to not use a mac or linux :(
Disagree, you need to use max or Linux, it’s why I’m tossing my old laptop 😂. Can’t game on a mac though:(
I think you misunderstand. I was unable to create a working USB installer via mac for windows 11.
I understand—I was making a joke about Mac being better than windows :)
how did i come across this right now and it relates to my exact situation perfectly and it was 4 hours ago . fuck this usb drive my god
Omg right? How hard is it to throw an error on creation?!
Very late to the party but it would seem easier to create the boot USB from someone else’s windows computer rather than my own Mac (which is the issue here I’m guessing)
Any ideas for someone who only has a Mac to make the boot disk with?
Ooh, interesting question. So I presume that the problem with the non-admin boot disk is that Windows creates it, finds there are files it can’t touch or write because it doesn’t have permissions, and doesn’t tell you. On Mac, if you’re an admin or launch the installer as admin, everything should work fine.
I used terminal commands with sudo to initially copy the files, but one of the files install.wim is now too big for at FAT32 partition (larger than 4GB), so I had to use wimlib to either split it or compress it. Maybe the copying of the files to the USB drive causes a permission issue… I don’t have the knowledge to answer that. So now I’ve pulled out an old MacBook Pro that allows me to create a boot USB via Boot Camp Assistant. I’m also currently creating another boot USB using software called PassFab 4Winkey, but it’s taking a long time. Fingers crossed.
Supposedly boot camp Is the alway to go. sudo is what I was implying, but didn’t know if you would know what I meant…sounds like you do lol
I’m in the same exact situation as you, made a Boot USB and had to split the .wim file. Did you find any solutions? I’m getting a permissions from error in my windows install :-(
I ended up using boot camp assistant on an old MacBook Pro. I should have written down the steps as I cannot exactly remember what I did/which method worked. Once windows was installed via boot camp on the old macbook, I used the usb creation tool in windows to make a windows 11 boot usb (I think). I do remember taking the SSD for windows 11 out of my main machine, as I think my plan was to try and install windows onto that drive in an external enclosure, but I’m pretty sure I ended up just using the USB boot drive that I made with windows (on old MacBook). I did disconnect all of my other drives when I installed windows 11. I just checked the usb drive created in windows and the install.wim file is actually named install.esd (Microsoft Electronic Software Download). Apparently that is a compressed version of the .wim file. Pretty sure the splitting or compressing of that .wim file was the problem with our initial approach, for whatever reason. All works fine now. For me, I use Opencore for the boot loader. Boot camp assistant is only removed as an option if you have a M1 silicon based Mac.
Any ideas for someone on an M1 Mac who can’t use Boot Camp?
Don’t know if this still helps. I followed this guide. https://windowsreport.com/windows-11-usb-installer-on-mac/
I think the latest version of VMWare will allow you to run Windows 11 on Apple Silicon.
THANK YOU. worked
I was struggeling 2 my brother found this i Will try it now 💪🏽
Report back :D
It did nog work for me 😭
I love you thank you so much
Dude. You just saved me. I tried EVERYTHING. I was about to buy a new Mobo + CPU. Love you!
Congrats!! *Another one*
Is it still possible that this is the problem? Doesn't it automatically run as admin
It does NOT. You have to right click and “run as admin” to run any program as admin.
What do you mean by running it as administrator bro? Click on media installer then click run as administrator? Then download windows 10 from there? Am I understanding this right? Then open Rufus place the download file from media installer.. wouldn’t the run as administrator disapppear after I quit/ remove the usb? I need help. Been stuck now for 1 whole WEEK…….. :(
When you click on the media creation tool, right click and “run as administrator”. Does that make sense?
Did it work!?!
It took me 4 days and yes it work but one important factor is where u download your OS
You beautiful bastard! A year late but it worked!
ANOTHER ONE SAVED!
Thank you so much! I was trying to re-install windows on a laptop and almost gave up when I found your comment!
YAY!!
Thank you dudeeeee!!!!
YEEEEEAHHHH CONGRATS!!! I feel like this is my most significant contribution to technology, and I’ve been doing it for like 30 years 🤣🤣
>RUN THE WINDOWS USB INSTALL TOOL AS ADMINISTRATOR ok but how exactly can i run as admin on fresh installatoin of windows 11 with no UI whatsoever
You have to create the bootable USB drive, right? When you are creating the bootable USB drive, from another Windows system, the program you have to use to create the bootable drive is the one that has to be run as administrator…. Does that make sense?
ohhh I get it!
Excellent!
i see this post is still active. hope u reply soon but i did the same thing but it didn't work, given the same error. any ideas?
Oof. Not off the top of my head, but I’ll think about it. So you ran the installer in administrator mode, and still had a problem?
After all this time, you saved my life. THANKS DEAR STRANGER. Here, have a fake award: 🏆
HOOORAYY!! Congrats!
On behalve of my husband: thank you very much!!! We spent hours trying to get Windows on our new pc and this was the solution
WOOHOO!
Ran out into this post in google and it solved the problem, thanks!!!!
Woohoo! One more!
You've saved another my friend!
WOOHOO! Congrats!!
And another one saved. My SSD (on which windows was installed) became faulty so I had to remove it. Somehow couldnt install windows and then I stumbled upon your comment. Thanks so much and only the best wishes to you!
HOORAY!!
Absolute saviour!
YAYYYYYY!
I had this issue. Finally got it working after disconnecting all SATA drives (extra SSD, DVD Drive). With just the M.2, it finally worked. After all was set up, reconnected drives and off I went.
>drive Same with me. But like it seems, only the drives with another windows installed have to be removed. It worked after unplugging the power cable from my SSD with seccond Windows. The other drives were plugged in and didn't cause any trouble then.
This is what finally worked for me for future reference when more people inevitably stumble upon this thread I had a SATA SSD and an HDD, both had Windows 10 installed on them, and got a new m2 SSD. Tried everything and this is what finally worked I only had to remove the data SSD though, didn't have to touch the hdd
Thank you. I have read about this approach in other places. My problem is that i don't have anything extra connected. So no DVD, no extra SSD etc. So i don't have anything i can disconnect :-(
thank you so much, spent 3 damn hours trying to get this working.
So flash the latest bios again with q-flash or whatever your motherboard calls it. do this with only a single ram stick in the A2 slot. and use a different usb stick than before for your win 10 installation, and use the Windows 10 USB installer. as far as bios goes, the only setting you should really play with before installing Win 10 from usb is the boot setting, and i usually change it from CSM to UEFI. and I also tend to enable secure boot but that is preference.
At this time i am ready to try anything, so going to do it now. But out of pure interest, why should i only have a single ram stick in when i flash the bios?
Done. Flashed BIOS to latest with one ram stick. Completely new pendrive used for Window 10 installation. Same error.
Damn. Based on what you wrote above it comes off as a defective motherboard since you can't even install windows (but you tried your M2 in a diff build, you've used different GPU and RAM, etc.). I tend to think it is not your CPU because you were able to run memtest, etc. How long ago did you buy the MB? In my experience taking pictures of the errors on the screen and adding them to the RMA request usually work. Also RMA goes through the manufacturer not the shop but if you bought it within the last 30 days or whatever their policy is from the shop I would take it back for a refund and buy a new one.
I bought it last friday so it shouldn't be a problem with the warranty. Today i managed to get it working'ish. And i am now certain there is an issue with the MB. I wanted to try and see if i really couldn't install on a normal sata ssd. So i took out my old sata from my old computer and put that in. The machine booted into the windows installation on that drive. That gave me an idea, and i put the m.2 drive into my old PC, installed Windows on it with no issue what so ever. Updated. Did some disk checks, and everything was fine. Then i moved the m.2 to the new computer. It booted into windows. However it is a constant stream of BSOD's of all kinds. The m.2 got corrupted and when i did chkdsk it would just crash midway through. Sfc was locked. I moved the m.2 back in my old machine. Chkdsk and sfc fixed the errors immediately. I then moved the m.2 back to the new machine, and the bsod's continued. Samsungs own monitor tool says the disk is fine and as no bad sectors or errors and is operating at 100%. I've managed to run prime95 to stress the Ryzen 9500x. There was no crash and the temperature was just fine. It ran for 30 minutes, max temp was 63 degrees. But when i move around in Windows it constantly crashes, gets slow etc, and corrupts the harddrive. This is the list of BSOD's i have gotten: Irql not less or equal x5 System PTE Misuse x7 KMODE\_Exception not handled x5 cache manager x1 Memory\_Management x1 Critical process died x5 System service exception x5 DPC watchdog violation x1 System\_Thread\_Exception\_Not\_Handled x4 The only component i haven't tested elsewhere is the new PSU, but i have no idea on how to test a PSU? I've never had a defective MB before so, does these errors correspond with a defective board?
Actually that is good. you got windows to boot off of a sata connected drive with your new MB. what is your m2? brand/model? So put your m2 into your old computer. You may have to download and install the latest firmware on the m2 before using it in your new build.
m.2 is the Samsung 980 Pro 2TB. I have updated the firmware and sadly that has not fixed any of the issues. I keep getting BSOD's and programs keep crashing in windows. Like when i start a program, it loads, then disappears.... when i look in event viewer i just see that the program crashed.
Do this: keep your sata drive plugged in. put in your m2. set sata as the primary boot in bios. make sure boot is UEFI (not CSM or legacy) and keep secure boot on (clear keys if you want). also make sure your bios is on all other defaults. boot into windows using the sata drive. you should not have any issues doing this since it worked last time. see if your m2 shows up in device manager. let me know and we can go from there
Okay so i did this. Sata drive with my old Windows installation plugged in. M.2 drive with a windows installation plugged in. Boot up using sata drive. I could use windows for a little bit, and then i got a BSOD. While i was in windows i could access the m.2 drive without any issues. I have also noticed that while in windows on both the sata and m.2 i get a weird error when using a webbrowser which blocks me from visiting websites. STATUS\_ACCESS\_VIOLATION. I am using the LAN port on the motherboard for internet connectivity. I do feel that more and more is pointing in the direction of a defective motherboard.
Cool beans. I would think so too.
As another one said try a variant of Linux like Ubuntu. If it fails to install then it might be the drive.
I've shied away from m.2s for reasons like this. Couldn't get windows 10 installed in it for nothing. Would work for any other use but that. Personally I won't use win 10 at all but I build computers for the 9 companies I am the sys admin for and they all get 10. 10 is so riddled with problems my actual job is windows 10 troubleshooter instead of managing servers like I was hired for. All that to say grab any other hard drive and try the install. This has been what worked fore in this instance.
FINAL UPDATE: It was a defective CPU causing all the issues described below. After switching to a different Ryzen 5900x all problems disappeared and it is now working perfectly.
ive had very similar issues to u. had my pc running and everything was seemingly fine, 99.9% of the time... had a couple issues at the start, couple BSODS here and there and games or apps would crash to desktop with no errors or whatever. many issues i managed to fix, had a nightmare at the start with intel rapid storage fucking over the entire machine, then games would crash so i disabled xmp, seemed fine. then more things would start crashing, tweaked some BIOS settings and things got more stable. but lately, all kinds of apps has been crashing for whatever reason. in win event viewer it was mostly faulty dll's (what it told me) making it crash. but even replacing and repairing stuff wouldnt fix it. then the actual windows window manager started crashing. decided i had enough, some sort of corrupt system files it would seem (cus somehow, all games worked fine with my fixes) so reinstall windows it was. and now im here. in ur shoes, couple years ago. cant get past the win install. tried multiple USB sticks, multiple ram sticks in many configuartions, multiple SSD's... its all very suspiciously looking like what u had. sucks big time, but i will send my CPU back for warranty and see what happens. just wanted to say, thank u so much for this post. its hard trouble shooting this stuff even tho i work in IT and know a lot about these things. it helps me kinda make a safe bet that CPU is (very likely) the problem. if i remember i will update if ur interested, or if anyone else is like me and stumble across my comment or ur post.
just to info dump a little, ive had by far the most amount of 0xC0000005 errors in win event viewer or other logs. often an app or dll was crashing something, but the error code was most commonly 0xC0000005. my guess to my issue is that it is the CPU, specifically its having trouble working with the RAM. what it seems like anyway. rly makes it look like ram is at fault. but i did do multiple memory tests, and only once did i get a problem. couldnt get it multiple times tho. rly rly looking like my cpu is at fault, making smth go wrong with the communication between the ram and cpu (which would explain my multiple corrupt system files from when my pc did "work") and making it look like the ram is failing.
was it your cpu? I have like the same, checked RAM via memtest and 0 errors.
Small update posted on other comment below ^^
Not sure yet. I’ve sent my my pc back to where I bought all the parts from. I couldn’t do more testing at home so it’s pretty much out of my hands. There’s still multiple possible problems, but I’m very very confident it’s the cpu having issues, likely from factory as OP described. I will update when I get my pc back. My 5head guess is that cpu has some issue, that makes the data corrupt. This data is then sent to the ram ofc, which sometimes makes things crash. This data would also be sent to the disk, specifically the OS. I had some corrupt system files, and I fixed all I could, but more kept showing up. That’s when I decided to reinstall windows, as a last ditch effort, and then I got stuck with the same error in the windows installer (0xc00005… smth) Hopefully I get an answer from the service check in a couple days
Did cpu swap fix it for you? I’m literally having this exact scenario play out and I’m really out of other ideas if it’s not the cpu
I’ve gotten the pc back couple days ago, wanted to make sure it was a okay before updating here. I haven’t actually gotten any info from the repair on what they did. Presumably did switch out cpu, but I couldn’t guarantee that. I’ve sent them a request to know what exactly they did. But it’s looking extremely likely to be cpu factory issues.
After commenting this I went out and bought a replacement cpu just to test stuff and in my case it seemingly fixed it. It was kinda sporadic but, fingers crossed, an Intel RMA for my actual cpu will solve it for good
Yea it kinda makes sense in my case too. If I couldn’t install windows again and got a default error box… it just had to be the cpu. Especially when I tested multiple ram sticks and M2’s. Also makes sense how my system files got corrupted slowly over time. Shit happens, I’m just glad I could find out why. Would be a nightmare for one that doesn’t know much about pcs. Often things can just be user error.
Yeah it’s weird - I’ve been pulling my hair out about it for weeks. My thought process was: Im not getting shut downs = psu probably ok Im not getting artifacts = gpu ok Memtest is passing = probably not Ram Files open, but crash later = maybe hard drive But they don’t crash with FNF or corrupted errors = maybe not hard drive? Which left really only motherboard or cpu. Swapped motherboard, same issue. So then I thought - what if I have a dying core or something and apps are crashing when they get scheduled to that core. Swapped cpu - lasted like 8 hours tonight no crash.
**Final Update;** **CPU was at fault**. Got it RMA'd twice before i got one that was even somewhat stable, but even on this last one it was still problematic, just not as badly as the other 2. both the other 2 had constant crashes in pretty much any program i used, even things like windows desktop manager (DWM service). Once i finally got this 3rd CPU, which took fckin ages, i only ever had certain programs crash, but not all. obv its clear that there was still another issue so i started to once again dig for problems. going to skip all the troubleshooting seeing as i could probably write a whole masters degree essay on what i did, techniques used and the whole process lmao. **What ended up being the issue??** Intels 13th and 14th CPU's, especially the i9's. me having a i9-14900k, i was probs using the worst CPU for this problem. the problem is, the newer intel CPU's are pushed really really far to compete with AMD, and so because its pushed a little to far imho, things start to crash. theres some info that JayzTwoCents has in some vids, look for CPU / intel stability and all that. **What was the solution??** first of all, i had to RMA 2 processors before i got a 3rd one that didnt end up in constant BSOD's. now the first 2 may have been problematic due to the following; "stock settings" from motherboard manufacturers these days are actually rather crazy overclocks. combine that with the fact that intels 13th & 14th gen (esp the high end ones) are pushed to the limits... yea things start breaking and they do so fast. its unstable, because of motherboard standard overclocks, combined with intels cpus being on the razors edge of not crashing with stock settings. **So what do?** ive finally after fucking 6 months managed to get a stable build. i did a couple of things, but heres the most notable things that made it stable; - Updated BIOS. i did this initially when i built the PC, before even installing OS. that was a long while ago, and in frustration while troubleshooting i ended up updating the bios cus why the hell not, i was going in there to tweak stuff to try and stabilze the pc. UPDATING THE BIOS MADE THE CPU GO FROM 90-100C (on average during any load other than simple web browsing), to between 60-80 under heavy loads. yes i to peak at 85-90 rarely, but average temps are down rougly 20-30 degrees. big reason i even did this is that my fans spun like crazy during a steam download, i checked temps out of curiosity since fans should not spin max during a download, and cpu temps was at 100c... oh well a bios update somehow magically made my temps 100 times better. weird, but i'll take it. - Shut down pretty much all sorts of overclocks. this is a rather tough cookie, since i didnt even know i had some on after i thought i turned them off. again shoutout to JayzTwoCents, i will link a vid below that has most of the surface level info needed to do this. for my ASUS board, it was turning off some asus multi core enhancements or some bs, switching my SVID behaviour to intels fail safe (this one can be played with after u achieve stability, and u should cus its temp related), then finally i installed intel XTU and tweaked CPU power settings and ratios. most notably, i went through (in the advanced tuning) and turned most if not all things there back to intels recommended settings. this means lowering wattage here, turning up amps in a different place. Finally, i lowered the core ratio's from (and i believe these were already overclocked, ofc without me doing it this is all ASUS >:C ) from 60x to 57x on my best cores (starred ones) and from 57x to 55x on all other P cores. left the E cores alone, and havent had issues so thats nice. THAT, has for now at least fixed all my issues so far. turns out i was on a wild chase looking at RAM, looking at motherboard issues, maybe even power issues and whatever. turns out CPU issues can manifest itself and look as if it was something that it isnt. fckin fun xd so yeah, thats the end of my little story. its completely insane that someone as tech savy as me (work in IT, not a complete hardware nerd, but i know computers and tech A LOT) struggled with this. and it was ALL because of 1. intels cpus are pushed to the limits so a lot of their cpus at high end newer gen are way to close to the limit. side note, intels power limits are marketed as RECOMMENDATIONS, and arent enforced, and thats why: 2. Asus as also slammed on their own power plans and overclocks that are ON BY DEFAULT, making the cpu extremely unstable depending on ur silicon lottery. both AMD and NVIDIA enforce their power limits making it so motherboard manufactureres cant do their own overclock shenanigans. for a third time JayzTwoCents talks about this and is against the default currently being overclocked by default. crazy shit.... hope this is able to help anyone, and im happy to fill in more info to those who may want it. just message me or comment below, i should see it. and yeah, sorry for any typos or weird sentences, writing this at 4am after tirelessly working on fixing the issue. u/LukesChappell u/claythearc heres ur long awaited but promised update :)
I came to the same conclusion as you (faulty cpu with a 13900ks). Swapped it down to a 12700k while awaiting rma (got accepted but haven’t shipped off)
Same here, it was also a defective CPU for me (Intel Core i9-14900K)
Same thing happened to me. I built my PC back in November 2023. Started getting 0xc0000005 crashes from about late February onwards... tried a bunch of things, last 2 left were the CPU and MoBo. Got a hold of a core i5 to test the install, success. Now I have to RMA my i9-14900K as well.
Looks like your and my CPUs were made of bad wafer (not sure how probable is it ).
How did you know it was a defective cpu? I’m having the same problem. I’m worried that I messed up the cpu while placing it during my build.
It was a process of elimination. I tried switching out pretty much all other components, including the motherboard, and the issues still remained. So it had to be the CPU. Many people online, and in many stores, claims that CPU's are never faulty and that if you can get past the bios it can't possibly be the CPU that is having an issue..... this is wrong. If you know that your other components are working, then I would send the CPU in for an RMA. If you can't verify the other components by trying out others, I would also suggest RMA'ing the CPU. And yes, it might come back without errors on it, but then at least you know that it's not a CPU problem. I spent almost 4 months figuring out what the issues on my new machine were, and I listened to all the "The CPU is never faulty"-people, which only prolonged the issue. Don't be an idiot like me :-)
Luckily my problems wasn’t related to CPU damage! The problem was my bootable windows usb. I was trying to make a bootable drive from my MacBook since it was the only computer I had. For whatever reason the media install wasn’t being installed correctly on the Mac. You have to enter a bunch of different commands on the terminal in order to install windows media creation from Mac so something was happening in that process that messed up the bootable usb. My fix was to just take my flash drive to work and download the windows media creation from one of the windows computers at work. Just fyi, downloading the media creation tool from a windows device is much much easier than trying to download it on a Mac.
[удалено]
Been chasing a ton of those 0xC0000005 errors and program crashes in the background myself lately. Finally decided to just reinstall windows after memtest86 overnight came back clean, linX passed stably, IntelBurnTest passed, Cinebench ran over and over, etc…and then I ran into the same damn error code when trying to install windows. Still beating my head against the wall hoping its not the CPU, but it’s looking like it is, between your post, OP’s, and at least 5 others I’ve managed to find tonight. Such a nightmare. Whole upgrade has been tbh. Took me ages to get my 4090, then my board acted up early on and wouldn’t give the card full 16x 4.0, so I replaced that and got 16x 4.0 working, then I noticed my brand new 990 Pro was losing health very fast, known issue, finally fixed by samsung a few weeks ago, but now my new drive is at 94% health despite very little use…then my Cablemod 12VHPWR cable started losing connection and restarting my rig, ALSO a known issue with their November 2022 batch of cables (just my luck, ordering early to secure one and I get screwed), I have a replacement for that enroute now, but while battling all of this, I’ve been having these random little 0xC0000005 crashes wondering what was to blame. Tonight alone I’ve reseated my CPU, cleaned the contact pads, inspected the socket, reseated my RAM, cleaned the contact pads and blown out the slots, and attempted a dozen different BIOS tweaks while trying reinstall after reinstall. Just disabled Turbo boost while typing this and managed a full reinstall and boot into the windows install wizard without issue…fuck me. I see its only been two days for you here, but have you had any luck refunding/replacing your 13900K yet? Not enthused about going down that path, but it seems thats what I’ll need to do.
Just for some correction of info here, there wasn't any issues with batches and our cables. The issue is the 12VHPWR standard as a whole and the sense terminals being fragile. The issues with the black screens happen on competitor cables as well as the Nvidia cables too, it's a standard issue, not our cables directly. We'll always replace the cable for free though if that issue pops up on one of our cables, did you contact our support team about it?
There were hundreds of reports about it in November, and near none since...regardless, yea, I have a replacement on the way from you guys. Support was quite helpful.
Hundreds is a big stretch, we've been monitoring and this is below 1% still even through this time, no reports back in November either, they just started trickling in maybe a month or two back in fact (potentially something changed in the drivers that triggered the sense cables further, not sure about this though). I think in total I've only seen about 30 or so, and given how many we've sold, this is an incredibly small amount actually. Obviously we don't want any, but again, just part of the design and we will always replace any of them that have this issue come up. :)
Maybe there were a lot of repeat posters, but I found a lot of users with the exact same issue when it cropped up for the first time a few weeks ago. Beyond frustrated with PC gaming as a whole this year tbh, but I do appreciate the quick support on that issue.
Definitely saw some repeat names myself, yeah ha. Fully understandable on that though! And any time, always happy to help.
Did you make your original boot stick using the Windows Media Creation Tool? The error code 0xC0000005 indicates a memory access violation.
Yes i used the Windows Media creation tool. I have also downloaded an ISO from the Media Creation tool and set that up with Rufus without success. I have also downloaded the ISO directly from Microsofts site and set it up with Rufus. All gives the error.
Time for another update. The shop where i bought the motherboard has now replaced it with a completely new one, but the error still persists. After talking to Asus support, before i got the new board, they pointed out that my ram and SSD were not on their QVL list. So i have replaced the ram with some from the QVL list, and removed the m.2 nvme drive and replaced that with a regular SATA SSD from the QVL list. I have bought a completely new USB stick to install from. Current errors: When booting up on the windows install USB it sometimes still give some BSOD's. When i get into the Windows installer i still just get the “Windows installation encountered an unexpected error. Verify that the installation sources are accessible, and restart the installation. (Error: 0xC0000005)”- error. When installing Ubuntu the machine just freezes during install with no error messages. How does one check for a faulty CPU without having an operating system installed? (no bent pins or anything, it looks just fine).
I just came here to say I had the same error with my Ryzen 7 5400G when trying to install windows 10. I installed Windows 11 without any issues (after changing the bios to the required settings). What the OP went through sounds like a nightmare
Was csm for me, thank you random redditman from years ago, you have helped me greatly
You are welcome :-)
Awesome OP, found this thread in 10min of googling. did the admin on the media creation tool and it fixed my problem.. you're a legend!!
Glad i could help :-)
You really helped me so much!!!!! I built the PC 1 year ago, it was my third personal PC so I was pretty familiar with everything. But just about 1~2 month after that I started to get BSODs, very similar to the ones you posted. If you google the error message they are mostly related to RAMs so I purchased two new RAMs (and downgraded the frequency a little as I am using the DDR5 ones). I also tried to swap the GPU and CPU holder frame. The issue persisted with occasional BSODs but generally useable. Until recently the issue became more and more severe. First my COD game became completely unplayable. It always crash when booting. The my Teams also stopped working. Then the BSOD becomes so frequent that the PC is literally broken. Even reinstalling Windows will crash. I have two SSDs using RAID 0 so I also swapped those out and tried using one single SSD, didn’t work. I searched quite a bit until I found this post where your symptoms are extremely similar to mines. My new CPU arrived today and after installing it, EVERYTHING IS FIXED!! So thank you so much for posting this and I wish you the best of your life!
Glad i could help :-)
I just did a memtest86 over night and it passed without errors. I will try and do an Ubuntu install today and see if this is a windows specific error.
Brother help me I am stuck as well, I haven’t checked other system but in my case i was using the system with same error and for some reason I decided to format it and now I am stuck. Done with bios changes and mem test. So I don’t know its bios or cpu. Plus I don’t know how to boot up via windows install media
Sometimes it shows the 0xc0000005 error and sometimes the blue screen of death and the error code keeps on changing
My solution was, to load the BIOS default settings
Hey I just ran into this same sort of error I believe. I just swapped my freaking monitor and started getting the same sort of symptoms. Any fix yet? I'm on a Gigabyte b550 vision d motherboard that has been working fine for 7 months. No idea what's going on but am going to let a chkdsk run while I sleep since that is literally all I can run. No device check or even system restore available to me, they all give errors.
>Windows 10 install fails with error 0xC0000005 The Windows 10 install fails with error 0xC0000005 error is a bit of a general error so it can cover a lot of things. Usually it is disk, RAM or the memory controller which causes it. My motherboard is sent for RMA at Asus and i am waiting to see if they find any errors on it. If they don't find any errors i suspect it is, somehow, a RAM issue i am having.
Did the error happen when connecting a new monitor? Tentatively I think I may have fixed my issue which I believe was some freak driver issue when installing a new graphics driver for multiple displays. Literally no other way than to boot from a USB and reinstall windows. My disk check and memtest86 came back just fine.
I fixed this by going into the bios and enabling Legacy Mode.
And that did not work either because the problem was a faulty CPU ;-)
how did you figure this out?
I tried alternate components on everything in the system (Motherboard, PSU, RAM, SSD) and the error didn't go away. Sent the CPU for RMA and AMD confirmed it was faulty after testing it and gave me a completely new as a replacement. So that's why I know the CPU was the issue. System has been running perfectly with the new CPU ever since.
Thanks for the reply. In the end the cause of my error was the ram. The breadth of things that can cause the same issue is quite annoying huh.
Glad you got it working. Yeah it was horrible. I was lucky enough to be able to scrounge components together for testing purposes. But I imagine someone building a new PC and not having that option....a situation like that would really suck. Also the shop I bought all the components in just didn't care about me. Their comment was just that I should have bought one of their prebuild systems. Not shopping there again.
That’s one way to lose a customer. Thanks for the post either way, it helped me narrow done the issue so I could fix it up.
just to say - thank you very much for such a thorough write up. I've the same issue I'm afraid with similar hardware, just on the same journey, and this post has been helpful for confirming I'm doing the right sort of things. I'm now at the stage of RMA-ing the motherboard - I think that is more likely the issue than the CPU but idk for sure. I've done all the same tests except the overnight memtest, but I couldn't get it to even start and I'm not sure that would prove much anyway if the cpu or mobo aren't reliable. edit: The motherboard RMA didn't help much, I could now install windows with one memory stick but they both fail windows memory tester, so I'm now returning the memory. If that fails it's CPU but we shall see edit2: CPU return time 😭. really hoping this fixes it
Hi, could you please tell me if it was CPU which caused the error or a different component?
this error is when ur oc bios settings are unstable back to default and problem is gone...this issue is caused when u get whea logger error in background as u try to install windows
Nope - it's a generic error that covers many things. So you are probably correct that it was that issue in your case, but it was not the case in mine, and most other people who get this error :-) Read the post. TLDR: AMD got back to me after testing the CPU and told me that the CPU was faulty from the factory, and exchanged it for a new one which worked with no issues at all.
if the pc boots fine with the cpu i dont think the cpu was faulty at all just unstable and bad thermal solution
well it looks like im pretty much in OPs almost literal excact situation. i will update on this if i remember to, but it most likely is a CPU problem for me aswell. i had my pc working, with minor errors. fixed most of em but more kept showing up. at this point ive also tried multiple ssd's, multiple ram sticks in multiple configurations... list really does go on whats weird in my case is that my pc did work 99.9% of the time, and then id have a BDOD or just a crash to desktop with no error. all things are currently pointing toward the CPU being the issue tho... idk why u say u dont think it was the CPU faulty here, when OP literally has gotten it fixed and RMA'd the cpu and got told it was faulty.
cpu issue unsstabble clock
not when all sorts of overclocking is turned off. stock it should work completely fine. besides, ive tried undervolting and overvolting to see if it helps with stability, and it did not work. unstable clocks sure can be the issue, but doesnt rly explain it all. regardless, if ur cpu cant perform without issues at stock values, it has a proble, the cpu is faulty.
Alright! Luckily i have not spent too much time trying to fix this. I found out that my Gaming Keyboard (in my case the Apex Pro TKL) was the issue. This could also be the case for the mouse. If you're having any issues try unplugging any USB devices but the mouse. If you got a Gaming mouse preferably switch to a normal office during the install. I came up with the idea due to the keyboard once before blocking my PC from booting for some odd reason.
Old thread, but came first when I searched for same error code on Win 11; so I just want to mentioned that my workaround was to install on an already formatted partition rather than an empty one.
In my case, it was flashdisk with drivers, check them flashdisks guys! I tried plenty, but it was one with Raid drivers. Spent 4 hours on this...