Help Diagnosing Persistent BSOD Issues – Possible Hardware Problems?

0
5
Asked By TechWhiz87 On

Hey everyone,

I've been dealing with a series of pesky BSOD (Blue Screens of Death) for several days now, mostly getting errors like KMODE_EXCEPTION_NOT_HANDLED and IRQL_NOT_LESS_OR_EQUAL. These crashes often put my system into a reboot loop, and I find myself unable to even reach the desktop. I've had to restore my computer to a previous point or perform a full reinstall of Windows 10 multiple times.

I first tried using a bootable USB to install Windows 10, but the system would BSOD immediately or during the installation process. Interestingly, when I disconnected my HDD, I managed to complete the installation without issues, and my computer ran smoothly for two days before the BSODs returned.

After some trial and error, I attempted a clean install again but kept getting BSODs throughout the process. Eventually, removing one of my RAM sticks allowed me to install Windows 10 successfully once more. However, even with minimal drivers and no internet access, the BSODs came back after about 24 hours.

Here's what I've tried so far:
- Updating the BIOS to the latest version.
- Restoring to earlier save points (which worked initially).
- Performing a clean reinstall of Windows twice (both times only lasted for about a day).
- Running memory tests (Windows Memory Diagnostic and Memtest86) with no errors.
- Testing both RAM sticks in different slots and reseating them (this seemed to make things worse initially).
- Disconnecting all HDDs and reattempting the installation.

Given that the BSODs happened even during Windows installation, I suspect it might be a hardware issue but I'm not sure what is to blame. The motherboard seems to be a prime suspect, especially since disconnecting drives affected the outcome. I'm really stumped on why those adjustments seemed to work temporarily. Can anyone offer insight or share similar experiences? I've also linked my most recent minidumps for further analysis.

3 Answers

Answered By DataGuru99 On

You might want to grab those dump files I mentioned. They're crucial for figuring out the root of those BSODs. If you can boot into Windows normally or via Safe Mode, check the Minidump folder located at C:WindowsMinidump. Zip that folder and upload it to a file sharing site that works like mediafire or catbox.moe. The more dump files, the better for analysis! And make sure the dump type is set to Small Memory Dump for future errors, so they don’t overwrite each other.

Answered By HardwareHacker43 On

It sounds like your last dump files indicate some disk I/O errors, correlating with the crashes. Have you checked the Event Viewer for any prep crashes? If you want to dig deeper into CPU issues, those CLOCK_WATCHDOG_TIMEOUT errors indicate a core might be stuck. Was your system drive the only one connected when you experienced those crashes?

Answered By RAMboZone On

If you suspect CPU issues, consider running a stress test like Prime95. It can help you identify if your CPU is stable under load. The fact your computer worked fine for a couple of days after RAM manipulation suggests intermittent issues either in RAM or the motherboard itself. Testing each stick individually could clarify further!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.