BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe+14a6f0

[eXtaZy]

My PC crashed twice today while playing H1Z1: King of the Kill with the bsod DRIVER_IRQL_NOT_LESS_OR_EQUAL
I have no idea what's causing this, all of my drivers are up to date and it only happens while I'm playing H1Z1. BlueScreenView blames ntoskrnl.exe+14a6f0.

Minidump Files: Click Here

Specs:
Z170 Pro Gaming motherboard
i5-6600k cpu
Asus Radeon RX 480 Strix 8gb gpu
Corsair Vengeance LPX 16GB 3000MHz ram
Corsair VS650 psu

 

[Lopperuk]

Try using a program called Driver Sweeper to completely remove all graphics drivers from your system and then install the latest drivers. If that doesn't work try reinstalling Windows.

 

[eXtaZy]

Try using a program called Driver Sweeper to completely remove all graphics drivers from your system and then install the latest drivers. If that doesn't work try reinstalling Windows.

I've downloaded an older version of AMD drivers, 16.11.5. It worked fine for 1 day, but now it just crashed again.
Different "cause" this time-- it says igdkmd64.sys+11e818.

 

[Colif]

igdkmd64.sys = Intel Graphics Drivers. if you using the AMD GPU you don't want Intel GPU drivers installed, so take them off.

 

[eXtaZy]

igdkmd64.sys = Intel Graphics Drivers. if you using the AMD GPU you don't want Intel GPU drivers installed, so take them off.

My secondary monitor is connected to my motherboard, will it work if I remove the Intel Graphics Drivers?
I preferred not to connect both monitors to my GPU because I don't know if it will impact performance while gaming.

 

[Colif]

You shouldn't be running both integrated graphics and GPU at same time or the drivers will conflict like this - it might have worked if CPU was AMD or you had a laptop, but generally desktops don't like it. I guess its a question of attachments as to why you don't run both screens off the GPU?

 

[eXtaZy]

You shouldn't be running both integrated graphics and GPU at same time or the drivers will conflict like this - it might have worked if CPU was AMD or you had a laptop, but generally desktops don't like it. I guess its a question of attachments as to why you don't run both screens off the GPU?

Will running both screens off my GPU impact performance?

 

[eXtaZy]

I uninstalled Intel's graphic drivers, running both monitors on gpu and now got a different bsod - IRQL_NOT_LESS_OR_EQUAL by hal.dll+17627
Minidump: Click Here

 

[Colif]

ignore my question in pm...

can you download and run who crashed - I can't read dumps but it can
It will create a summary of the errors and might give us a clue what else is happening

Copy/paste results in here

 

[eXtaZy]

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 2/22/2017 12:48:31 AM your computer crashed
crash dump file: C:\Windows\Minidump\022217-18453-01.dmp
This was probably caused by the following module: hal.dll (hal+0x17627)
Bugcheck code: 0xA (0xB0, 0xFF, 0xA7, 0xFFFFF8006F21A627)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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 Tue 2/21/2017 8:22:56 PM your computer crashed
crash dump file: C:\Windows\Minidump\022117-23093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xD1 (0x0, 0xD, 0x8, 0x0)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 2/18/2017 11:11:30 PM your computer crashed
crash dump file: C:\Windows\Minidump\021817-23593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xD1 (0x0, 0xFF, 0xF1, 0x0)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 2/18/2017 5:51:47 PM your computer crashed
crash dump file: C:\Windows\Minidump\021817-23921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x4F, 0x0)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 2/1/2017 8:31:38 PM your computer crashed
crash dump file: C:\Windows\Minidump\020117-29921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0x0)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Colif]

well, its a driver but I can't tell from who crashed report what it is.
ntoskrnl = new technology operating system kernel - brains of windows
hal.dll = hardware abstraction layer - part of windows that sits between operating system and hardware

You can read this and run driver verifer, it will check the drivers on PC and cause a crash. Once it crashes, run who crashed again and see what it finds

 

[eXtaZy]

I ran driver verifier, PC just got BSOD again... this time DRIVER_IRQL_NOT_LESS_OR_EQUAL.
BlueScreenView is blaming atikmdag.sys+9f476, and whocrashed is blaming ntoskrnl.exe
Should I upload the minidump?

On Wed 2/22/2017 8:14:37 PM your computer crashed
crash dump file: C:\Windows\Minidump\022217-22062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xD1 (0x0, 0xD, 0x8, 0x0)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Colif]

atikmdag.sys = radeon drivers... we seem to have a pattern here of display drivers.

I would try this: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html and see if it helps

 

[eXtaZy]

atikmdag.sys = radeon drivers... we seem to have a pattern here of display drivers.

I would try this: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html and see if it helps

Alright, I will.

 

[eXtaZy]

I did what you said, just got another bsod. However, seems like a different cause this time.
WhoCrashed:

On Thu 2/23/2017 5:50:42 PM your computer crashed
crash dump file: C:\Windows\Minidump\022317-25640-01.dmp
This was probably caused by the following module: aswnetsec.sys (0xFFFFF80931EBCEE3)
Bugcheck code: 0xD1 (0xFFFFDC00248F1000, 0x2, 0x0, 0xFFFFF80931EBCEE3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\aswnetsec.sys
product: Avast Antivirus
company: AVAST Software
description: Avast Firewall 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: aswnetsec.sys (Avast Firewall Driver, AVAST Software).
Google query: AVAST Software DRIVER_IRQL_NOT_LESS_OR_EQUAL

 

[Colif]

take avast off and re run driver verifer, we slowly finding all the things wrong with pc

 

[eXtaZy]

Just got another bsod. I was idle in the desktop, in teamspeak with some friends and got IRQL_NOT_LESS_OR_EQUAL bsod by ntoskrnl.exe+14a6f0... I don't know what to do anymore, I've reinstalled Windows 10 like 4 times already...

BlueScreenView: (first in the list)

WhoCrashed:

On Thu 2/23/2017 9:27:14 PM your computer crashed
crash dump file: C:\Windows\Minidump\022317-26968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0xFFFFE10977B7A230, 0x2, 0x1, 0xFFFFF802C3EEF672)
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.

 

[Colif]

can you upload the latest dumps and share the links here, and someone will read them for you.

 

[eXtaZy]

Yeah. Click Here

 

[eXtaZy]

Crashed again yesterday... DRIVER_IRQL_NOT_LESS_OR_EQUAL - ntoskrnl.exe+14a6f0
anyone?

 

[Colif]

since no one bit, we see what we can find

Can you try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, run Who crashed and see what driver it reveals

ONce, this caused a boot loop so it might help to download the Windows 10 media creation tool and use it to make a win 10 installer on USB as its a handy boot disc

 

[eXtaZy]

I ran the verifier and my windows got BSOD before I could get in, so it didn't generate a minidump 🙁
The bsod was DRIVER_VERIFIER_DETECTED_VIOLATION aswVmm.sys

 

[Colif]

Did you remove avast before??

aswVmm.sys is part of avast! Antivirus and developed by AVAST Software << this leads me to believe you didn't. Take it off and use defender until we get no errors

 

[eXtaZy]

I uninstalled avast and ran the verifier. DRIVER_VERIFIER_DETECTED_VIOLATION then showed xsplit driver.
I uninstalled xsplit and ran the verifier. no BSOD this time when booting, so I downloaded AVG antivirus.
Today I got bsod again, ran the verifier and DRIVER_VERIFIER_DETECTED_VIOLATION showed avgVmm.sys.
Uninstalled AVG antivirus, now no bsod on startup. Verifier is currently running, I will let you know it if I get another bsod.
I don't trust Windows Defender too much because I've tested it myself and avast antivirus detects more viruses than Defender.

 

[Colif]

Until you stop getting BSOD, i would stick to defender as its not likely to cause BSOD, and if it did, I would be more inclined to blame LAN drivers or a virus

I don't like Defender, AVG or Avast, I have had to use all of them and so far Bitdefender is better in my eyes.