My computer has been crashing with BSODs and I couldn't really fix the problem after trying multiple things, so I decided to format my whole computer. After low-level formatting the hard drive with the hard drive manufacturer utility (which worked fine), I proceeded with installing the OS. When the OS was in the process of formatting the hard drive in preparation for the install, I received a BSOD. It was a DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD. Since it was prior to even a fresh install of the OS, it is not a driver's problem (and hence there was no filename associated with the BSOD error), so I'm guessing it must be hardware. I've ran memtest and the extended test for the hard drive, which both came out fine. So I've narrowed it down to possibly the vid card, motherboard, cpu or psu. Aside from swapping out those hardwares (which I don't have spares of), is there any other way I can further isolate the problem? Thanks a lot for the help.
-
We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.
Computer Crashing with BSOD: DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD
- Thread starter Fleshie
- Start date
KB
Diamond Member
I had similar problems when I had bad RAM. I know you said memtest reported no problems, but try running with just one known-good stick of RAM.
It is unlikely to be CPU or PSU, because they cause other issues (on average) and your vid card is not even being worked hard during install.
You can also try reseating your components. Good luck!
It is unlikely to be CPU or PSU, because they cause other issues (on average) and your vid card is not even being worked hard during install.
You can also try reseating your components. Good luck!
Hi there!
I've had this problem twice, both with different culprits. The 1st time it was the Hard Drive, and replacing it with another solved the issue. The 2nd time, it was the CPU, when I'd moved the machine with a Zalman Flower on it must have dispalced slightly and the thing had overheated [old Palamino XP2000 - toasty!] and replacing that solved the issue. It is rare, but it does happen.
Test the CPU in another MB if possible to see if there are any issues with it, and try another HD in that machine. Personally, I'd say it's likely to be the Hard Drive myself.
HTH
MikeHP
I've had this problem twice, both with different culprits. The 1st time it was the Hard Drive, and replacing it with another solved the issue. The 2nd time, it was the CPU, when I'd moved the machine with a Zalman Flower on it must have dispalced slightly and the thing had overheated [old Palamino XP2000 - toasty!] and replacing that solved the issue. It is rare, but it does happen.
Test the CPU in another MB if possible to see if there are any issues with it, and try another HD in that machine. Personally, I'd say it's likely to be the Hard Drive myself.
HTH
MikeHP
