BSOD Critical structure corruption / IRQL not less or equal

8rounds · 02 Aug 2016

Hello,

Since upgrading my laptop to Windows 10 I have had BSOD crashes with error messages including critical_structure_corruption, IRQL_not_less_than_equal and issues with generic_classpnp.sys. I have performed a clean install and have ran sfc /scannow, DISM /RestoreHealth and other manufacturer provided tools but not picked up any problems.

I suspect it is a driver issue with either my network, sound card or possibly graphics card but unsure which one or how to fix the issue. Whilst trying to update drivers last night, my laptop went completely unresponsive after a BSOD critical structure corruption and after waiting for 2 hours I had to disconnect the power supply to shut it down.

Here is my dump file:
Attachment 93568

System spec:

Operating System
Windows 10 Home 64-bit
CPU
Intel Core i7 @ 2.80GHz
RAM
16.0GB Dual-Channel DDR3 @ 800MHz
Motherboard
Alienware Alienware 17 R2
Graphics
Generic PnP Monitor (1920x1080@60Hz)
Intel Iris Pro Graphics 5200
NVIDIA GeForce GTX 980M

Storage
931GB Western Digital WDC (SATA)
476GB SAMSUNG 512GB (SSD)
Optical Drives
No optical disk drives detected
Audio
Sound Blaster Recon3Di

Any help would be greatly appreciated.

philc43 · 02 Aug 2016

Hello 8rounds and welcome to the TenForums :)

I have looked at your BSOD dump file. It tells me that a driver is the most likely cause but it does not reveal which one.

Code:

BugCheck 109, {a3a00f58b639b753, b3b71bdf08bb488c, 6, 18}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Arg. 18 is the only meaningful; paramemter: Kernel notification callout modification

CRITICAL_STRUCTURE_CORRUPTION (109)A driver has inadvertently or deliberately modified critical kernel code
 or data.
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1)  A driver has inadvertently or deliberately modified critical kernel code
 or data.  See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.

Therefore please run Driver Verifier which will test all your drivers and hopefully force one of them to crash so that we can identify it. Please read through the information and warnings; run for no more than 48h as instructed in the tutorial but as soon as there is a BSOD you can turn Driver Verifier off and report back with the details.

8rounds · 02 Aug 2016

Thanks, I will run the Driver Verifier this evening and get back to you.

8rounds · 03 Aug 2016

Hi there, I have run the driver verifier for 24 hours but no BSOD occured. The verifier is now disabled again.

My sound card driver has failed so I am reinstalling that but other than that no issues. Should I keep trying with the verifier or is there something else I can try?

philc43 · 03 Aug 2016

Let it run for a while with the new sound driver and let's see if you get a new BSOD.