Just another IRQL_not_less_or_equal

[dasdet]

I've ran into an IRQL_not_less_or_equal but can't figure out for the life of me whether it's hardware, software or something else. I'll put the dump file here:
https://mega.nz/#!nclgiSjJ!tg50O0Cex1LNaTvLf27lfRxZUOOQOf3nj-zZV3z_B_A
The bugcheck code is 0x000A, and the first parameter is 00000000`00150700.
Really just want to know whether I need to RMA any hardware here. Will provide additional info as per needed.

 

[basroil]

Did you clean install the graphics drivers? That solves most issues with that error code

 

[dasdet]

Did you clean install the graphics drivers? That solves most issues with that error code

I thought that graphics driver problems usually involve the device drivers for the graphics card for themselves - in my case, it'd appear as nvlddmkm.sys.
If graphic driver instability can result in ntoskrnl.exe irql not equal or less throws then I guess I'll clean install it (since my motherboard does come with integrated graphics, though I've only ever installed the nvidia drivers after a clean install - not update - of win 10)

I'll also mention that this only seems to come up after leaving my computer on for a long time.

 

[basroil]

I thought that graphics driver problems usually involve the device drivers for the graphics card for themselves - in my case, it'd appear as nvlddmkm.sys.
If graphic driver instability can result in ntoskrnl.exe irql not equal or less throws then I guess I'll clean install it (since my motherboard does come with integrated graphics, though I've only ever installed the nvidia drivers after a clean install - not update - of win 10)

Driver issues can cause ANYTHING to give out errors because they are at the lowest level of the OS. And usually it is in the kernel that you see issues, almost never in the driver program itself. Clean install and you'll probably have a working computer in no time

 

[dasdet]

I thought that graphics driver problems usually involve the device drivers for the graphics card for themselves - in my case, it'd appear as nvlddmkm.sys.
If graphic driver instability can result in ntoskrnl.exe irql not equal or less throws then I guess I'll clean install it (since my motherboard does come with integrated graphics, though I've only ever installed the nvidia drivers after a clean install - not update - of win 10)

Driver issues can cause ANYTHING to give out errors because they are at the lowest level of the OS. And usually it is in the kernel that you see issues, almost never in the driver program itself. Clean install and you'll probably have a working computer in no time

Thanks, I'll give it a try. How do I find out which drivers I have installed though? It's easy enough to remember what I'd installed myself, but with default drivers that come with the win10 system I find it a bit hard to select which drivers to uninstall.

 

[basroil]

Thanks, I'll give it a try. How do I find out which drivers I have installed though? It's easy enough to remember what I'd installed myself, but with default drivers that come with the win10 system I find it a bit hard to select which drivers to uninstall.

You don't need to know. Just follow the instructions in the sticky on how to clean install your graphics drivers. If that doesn't fix it then you can worry about other drivers.

 

[dasdet]

Cleaned my drivers, reinstalled them, still crashing after a few day or two. guess I'll stress test again.
If anyone has any ideas I'm open to suggestions.

 

[QuentinB]

Can you open task manager (Ctrl + Alt + Del) when the screen comes up? If so, it may be a virus from the application Mint.exe, this is what I experienced.

 

[dasdet]

Can you open task manager (Ctrl + Alt + Del) when the screen comes up? If so, it may be a virus from the application Mint.exe, this is what I experienced.

Just had a crash yesterday that didn't even have a bluescreen - just froze with noise from the audio output (right into my headphones)
had to manually restart
so I dont think it's mint

 

[QuentinB]

Okay then, its probably a graphics card/driver issue like basroil said.

 

[Paul NZ]

Only thing that I can see that may cause it is this BazisVirtualCDBus.sys it belongs to WinCDEmu virtual CDROM bus

Uninstall it