PC displays blue screens each time I power it on following a complete shutdown, needs system restore.
PC displays blue screens each time I power it on following a complete shutdown, needs system restore.
Hi all, this is an issue I've been experiencing ever since I upgraded to Windows 11 (from Windows 10) and I cannot for the life of me figure out why it might be happening, so I thought I might be able to ask you all. Please, if anybody has the necessary expertise to help fix this, I would really appreciate a hand. I'm worried that one day this error will happen again and it won't be recoverable, and my entire C drive will be gone. First, here's what I'm running: Specs CPU: Ryzen 9 5950x GPU: TUF RTX 3090 Ti C:/ Drive: Samsung SSD 860 EVO 2TB (CrystalDiskInfo reports no issues at all, 12058 power on hours and 1348 power on count, about 62TB of host writes) Motherboard: TUF B450-PLUS GAMING PSU: Corsair HX1200 I have an Elgato Game Capture HD60 Pro and some cheap amazon wifi card in the other PCIE slots on my motherboard. I also have a Focusrite Solo Gen3 plugged in at all times. (I mention these things just in case they turn out to be the root of the issue) The Problem Ever since I went through the whole process of enabling secure boot, the trusted platform module stuff and upgraded to windows 11, my computer blue screens every time I boot. This isn't a boot loop, because sometimes after the first blue screen it just boots up like normal. Other times, and increasingly more often recently, it will actually start repairing the C drive, and automatic repair fails. I then go and do a system restore to a restore point that is never older than a week, and then it boots up like normal. It boots up like normal even if the restore fails. An error message might come up like "failed to extract" something or "ran out of storage on the disk" and it will still boot up like normal after. Quitting out of this menu before going through with any system restore doesn't seem to work though. Restarting my computer after it was already on hasn't ever triggered this. It only appears to happen when I'm turning my computer on after a substantial enough period of it being shut down. I thought maybe the issue was related to just having the PC powered on for a period of time before it tried to start windows, but waiting in the BIOS menu for a bit hasn't seemed to have allowed me to bypass the problems. I'd need to test this next time I go to turn my computer on, where I go into the BIOS menu before it has a chance to blue screen mid-startup and see if that fixes the problem. At this stage I have been backing up some of my most important files to a seperate, very new samsung NVME SSD just in case something happens to the drive, but given my C drive's age and status as a samsung/reportedly well functioning SSD, I don't see why it would be failing. My PC's almost never left where it lives so I doubt there's been any damage in transport since I built it. It may be worth mentioning at one point this drive was partitioned, but since then I removed it. I don't think I did it fully correctly, there might be something about the master boot record being a little messed up, but I think I fixed it. I also think I successfully switched it from MBR to GPT since that seemed to be the better format, and I think doing that fixed the issue that was preventing me from upgrading to Windows 11 in the first place. Checking Disk Management says I've got my healthy 1861GB NTFS C drive, 580MB unallocated, healthy 773MB and healthy 526MB recovery partitions, and a healthy 100mb EFI system partition. I've tried consulting google for others with the same issue to no avail. So what I'm asking : Has anybody seen this issue before, and knows how to solve it? Or if not, anybody got any ideas? I'd really appreciate any help you guys have to offer. Thanks a tonne for reading all of this.
Have you looked inside the Windows Event Viewer for any details? You might also want to export all logs to check for issues that appear during the next reboot.
It occurred once more today, yet following the initial blue screen it didn't require repair and started normally. I reviewed the event viewer which showed: The computer rebooted after a bugcheck. The specific issue was 0x0000001a (hash 0xffffe3bfff63c330, offset 0x0800000000000000). A dump was saved at C:\WINDOWS\MEMORY.DMP. Report ID: e35bb7dc-71d0-4907-8f91-c863d9bce7d6. The note mentions "Event ID: 1001," which seems acceptable based on the information shared.
0x0000001a signals a memory error, event 1001 generally points to a crash but isn't specific—it might indicate hardware issues or malware. It’s not a precise diagnosis. I recommend performing a memory check using Windows tools. Run sfc /scannow via the search bar, typing the command above and pressing enter. This could resolve corrupted files and improve stability. If bad files were created during the crash, the fix should help. Also, if your system has XMP enabled, you may want to disable it in BIOS to see if that resolves the problem.
I understand, I noticed a mismatch in the RAM sticks but didn't think it mattered much. I have two 16GB sticks in the first two slots and two 8GB sticks in the remaining two, using DDR4 from Corsair. DOCP is enabled, which raises the memory speed from 2333Hz to 3000Hz. I'm not sure why this issue only appeared with Windows 11, and I'd rather avoid running all my memory at that frequency. I thought the scan would still work with four slots covered, but I didn't expect it to fail. I've scheduled a diagnostic check for when I restart the PC. Feel free to reach out again once I get the results. Thanks for your help, Johno!
I use an AMD 5900x and an MSI 3080 with all memory OC set to XMP or DOCP turned off. The system runs smoothly without any problems. I usually play Warframe, which tends to cause crashes and random desktop jumps to their support pages when memory overclocks are enabled. Your setup is higher performing than mine, so you probably won’t see much speed drop—maybe a few frames lost at most if OC is off. You might want to test it for a short time to check if the issues persist.
I could be facing the same problems... Disabling XMP might help. How can I make the RAM run at 3600MHz instead of the usual 2800MHz? Do I need to use the B450 Tomahawk Max?
It seems unlikely. The actual RAM speed is around 2800, but using XMP as "safe" is really an overclock. Under proper conditions, your RAM should handle 3600 safely, though overclocking can sometimes cause minor issues. Most users can safely use XMP, but some opt to disable it or find alternatives. For instance, with certain AMD CPUs, people have found success by entering XMP values manually in BIOS and then adjusting them later. If you're gaming, stability at maximum speed is usually better, and any extra frames gained are usually hard to notice.
Interestingly, after completing the memory diagnostic, my system ran smoothly without any interruptions. It seems the test finished successfully even though it took a long time, and I didn’t notice any errors. There were no logs saved to my desktop, but the Event Viewer displayed the MemoryDiagnostics-Schedule event. The article’s wording about not generating an event if no errors are found might be unclear for me.