Windows 10: Random BSOD not sure what the catalyst is - IRQL NOT LESS OR EQUAL

I'm getting random BSOD, I can't explain when or why because they are seemingly random!

My specs are pretty old - I built this years ago, I honestly don't remember.

cpu: Intel Q6600 (was overclocked but I've returned to stock settings)
mb : MSI P35 Platinum (ms-7345)
ram : 8GB DDR2
gpu : NVIDIA GeForce GTX 560
OS : windows 10 pro

:)

 

Windows 10 BSOD

Well i didn't have any problems for the first 4/6 months, they only started after that and the BSODs have given me a range of messages from irql not greater or equal to kmode exception not handled (there are many more).

 

BSOD WINDOWS 10 64 BIT, NOT SURE WHAT IS THE PROBLEM

So looks like that's the drivers in early win10 versions, since I got the newer version, it doesn't happen any more!

 

Someone will beyond doubt reply to the blue screen log but its always advised top check the drivers before hand mainly the nvidia drivers matey.

Id start with that in the mean time by removing and reinstalling the latest drivers for it *Smile

 

Good idea, I was struggling to install anything nvidia for the past day or so. it kept failing. Full disclosure: my PC kind of just "shut off" and got into a reboot "loop" about 4 months ago and I didn't feel like dealing with it.

3 days ago I figured I'd try turning it back on and it worked, other than this new random BSOD, I was thinking maybe one of my RAM sticks was failing/dead. I just tried the nvidia installer again and it seems to be working now.

 

I've managed to update my Nvidia drivers which seems to have slowed the BSOD's but they are still happening. Do I need to provide more info? Not sure where to look to get it however.

 

Sorry it took so long for us to pick up your BSOD thread. I looked through the dumps and there is not a lot there to go on.
The latest dumps indicate problems with Microsoft Windows files which I doubt is the case, something else is going on.

as you mentioned, this is an old system with a BIOS from 2009, but older machines run fine with Windows 10.

You say you updated your NVIDIA GeForce GTX 560 driver. I see you 388.13 dated 10/26/2017. There is a newer one available:

GeForce Game Ready Driver

Version: 388.43 WHQL Release Date: 2017.11.30 Operating System: Windows 10 64-bit Language: English (US) File Size: 441.41 MB


Remove and install latest Nvidia drivers:

I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads

Then do a custom install of only the NVidia graphics driver and the PhysX driver.

See if that gets rid of the problem.

 

Thanks for the response, I wiped and reinstalled/updated Nvidia drivers (388.59) as instructed - the BSOD have increased and changed. Trying to get this written before another happens.

 

Only 1 new dump in the zip and it did not have any clue as to the driver causing of the BSOD. Nothing evident in the event log or msainfo32 data.

At this point I think the best thing to do is start stressing the system components to see if we can induce a failure.
==================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to

PART TWO

and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun dm_log_collector and upload the resulting zip file. DO NOT RUN any hard drive cleaners please.

If this doesn't show us anything then we'll try RAM, CPU and GPU next.