So.. I just had an other BSOD : DRIVER IRQL NOT LESS OR EQUAL // module : [FONT=Segoe UI, Arial]ntoskrnl.exe (said by Whocrashed)
What is it? Is it linked ?[/FONT]
What is it? Is it linked ?[/FONT]
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
There are 2 possible results from Driver Verifier:
- no BSOD crash
- a BSOD crash
All you can attribute to the absence of a crash is that nothing "tripped" Driver Verifier.
This tells us that the 3rd party drivers aren't likely to be the problem.
If you get a BSOD crash, you may or may not get a memory dump.
So it's important to read all the info on the BSOD screen
If you don't have a memory dump, then it's gonna be very difficult without a driver name from the BSOD itself
If you do have a memory dump, then it may be a bit easier
You'll either have a memory dump that's Verifier Enabled, or one that's not.
If it's not Verifier Enabled - then it's something that has to be fixed before we can re-run Driver Verifier
If it's Verifier Enabled - it'll either point to a 3rd party driver, or not
If it's a 3rd party driver - remove it or fix it (it may be corrupted)
If it's not - then we've got more work to do (you told it to verify 3rd party drivers - but there's wasn't an issue with one).
This is similar to the dump files that aren't Verifier Enabled
Most often it's a hardware problem - but it can also be a compatibility issue or a Windows problem.
(remember the hardware rule - a lot of different BSOD's with a lot of different errors and causes are usually hardware/compatibility problems)
I had the audio driver installed when i ran the verifier. I don't anymore. I'll run it again at least 24h (24h with pc switched on i presume ?) and i'll keep you updated.
Thanks !
Has Sysnative Forums helped you? Please consider donating to help us support the site!