BSOD 0x0000000A IRQL_NOT_LESS_OR_EQUAL

digity

Honorable
Sep 25, 2013
6
0
10,510
Having (apparently) random BSODs all the time. Ran memtest86 for about half an hour, 2 passes. BSODs started occuring approx. 15 days ago, and it's started getting on my nerves.

Here's what WhoCrashed says:

On Sun 9/8/2013 7:57:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090813-15880-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0xA (0x0, 0xF, 0x1, 0xFFFFF80002C76EED)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 9/8/2013 10:28:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090813-15553-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x310E)
Bugcheck code: 0xD1 (0x920, 0x9, 0x1, 0xFFFFF88002CC110E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Sun 9/8/2013 6:16:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090813-14882-01.dmp
This was probably caused by the following module: aswsp.sys (0xFFFFF88003EBF53A)
Bugcheck code: 0x50 (0xFFFFFA0001CEE2E0, 0x0, 0xFFFFF88003EBF53A, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software PAGE_FAULT_IN_NONPAGED_AREA

On Mon 9/9/2013 1:25:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090913-14913-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF880015786EE)
Bugcheck code: 0x3D (0xFFFFF880060981C0, 0x0, 0x0, 0xFFFFF880015786EE)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This bug check appears very infrequently.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Mon 9/9/2013 3:37:11 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x1E726)
Bugcheck code: 0xD1 (0x105C44, 0x9, 0x0, 0xFFFFF88002C030BC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: ATI Technologies Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

Solution?
 
1) Disable the AVAST antivirus or use other antivirus software, because you can see from the 9/8 error, the avast casues the problem. You can try to reinstall it too if you like it.
2) Download and install the newer version AMD GPU driver from AMD website.
http://support.amd.com/us/gpudownload/Pages/index.aspx

You need to clean the register files before you reinstall the new driver by either CCleaner or Advanced Systemcare. You can get them from cnet.com:
http://download.cnet.com/windows/
 

digity

Honorable
Sep 25, 2013
6
0
10,510
I will try reinstalling AVAST, and I have installed newest AMD GPU drivers a few days ago from that site (just checked, to be on the safe side). I use CCleaner, and didn't know it can clean registry, I use it to clean my PC from junk and free space. I also ran memtest86 again, this time for 4 passes. I think RAM isn't the problem, although I had MEMORY_MANAGEMENT BSODs that weren't even logged.

Currently cleaning registry as I type.

EDIT: CCleaner just fixed about 8600 registry errors. o_O
 

digity

Honorable
Sep 25, 2013
6
0
10,510
Quick update: Just got a MEMORY_MANAGEMENT BSOD, here's WhoCrashed Analysis:

On Fri 9/27/2013 5:50:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092713-17706-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x1A (0x888A, 0xFFFFF8A0020F6568, 0xFFFFF68000034FF1, 0xFFFFFA800117FE10)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I will leave memtest86 running overnight.