Attempting to identify a BSOD linked exclusively to a Windows 11 Update event
Attempting to identify a BSOD linked exclusively to a Windows 11 Update event
Recent reliability check results from the past three days:
https://www.dropbox.com/scl/fi/5bzj...4-...7nvs1&dl=0
https://www.dropbox.com/scl/fi/1h4w...4-...avos2&dl=0
https://www.dropbox.com/scl/fi/as3j...4-...zwmwi&dl=0
I reviewed the information from that link, but I'll continue monitoring it and attempt to grasp it.
The CPU stress test was run by @ubuysa, and they mentioned appreciating the help received so far.
Windows 10 Event Viewer serves as a window into your computer’s operations. It often becomes the initial tool when trying to diagnose problems, providing valuable clues about what might be wrong. Although it can sometimes be confusing or misleading, understanding it can help you navigate effectively. For more details, check forums.
Start the Windows installation media, choose Repair My Computer, go to the Command prompt. Find your system drive (drive letters might vary in this WinRE interface) and place the file C:\Windows\Memory.dmp onto the USB drive. You may transfer it from another PC.
While doing so, also move all dumps from C:\Windows\Minidump to the USB drive.
If the system doesn’t boot, remove a RAM stick and attempt again. Change RAM sticks one by one until you succeed or reach a working configuration.
If that doesn’t work, enter BIOS setup and disable C-States for the CPU to test if it allows booting. This prevents the processor from entering a low-power state when idle, which some CPUs find difficult.
A fresh Windows update arrived today. Thinking it might return, I handled the installation myself, rebooted, and the problem persisted.
Now I’m hoping to find a boot file, but I’ll have to wait until after work.
I think your RAM configuration might be the problem. Multiple modules from various kits can lead to compatibility problems. Please share screenshots from CPU-Z showing memory and speed details. (Upload to imgur.com and provide the link)
Ensure DDR voltage is configured at 1.35V in BIOS and Command Rate is set to 2T.
If this doesn't resolve the issue, try using two RAM modules from the same kit (disable the second one).