IRQL_NOT_LESS_OR_EQUAL bluescreen help

Flaffino

Distinguished
May 26, 2016
45
1
18,535
I keep getting this BSOD error usually when loading up games.
Maybe this helps:
Source
Windows

Summary
Shut down unexpectedly

Date
‎06/‎01/‎2017 16:16

Status
Not reported

Problem signature
Problem Event Name: BlueScreen
Code: a
Parameter 1: 9d35
Parameter 2: ff
Parameter 3: 0
Parameter 4: fffff8008caabbaa
OS version: 10_0_14393
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.14393.2.0.0.768.101
Locale ID: 2057



System:
i5 6600k
asus z170-a
r9 390
16gb ddr4
 


Here are the results:

On Sat 07/01/2017 17:44:02 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010717-7687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x296DE, 0xFF, 0x0, 0xFFFFF803B72DB48A)
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 Sat 07/01/2017 17:44:02 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x296DE, 0xFF, 0x0, 0xFFFFF803B72DB48A)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Sat 07/01/2017 03:41:00 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010717-8671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xC4 (0xF5, 0x0, 0xFFFFE2807AD1B080, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver passed a NULL handle to ObReferenceObjectByHandle. 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 07/01/2017 01:38:01 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010717-12171-01.dmp
This was probably caused by the following module: iqvw64e.sys (iqvw64e+0x0)
Bugcheck code: 0xC4 (0x62, 0xFFFFCD05E6EDD4E8, 0xFFFFCD05E72AA2D0, 0x3)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\drivers\iqvw64e.sys
product: Intel(R) iQVW64.SYS
company: Intel Corporation
description: Intel(R) Network Adapter Diagnostic Driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. 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: iqvw64e.sys (Intel(R) Network Adapter Diagnostic Driver, Intel Corporation ).
Google query: Intel Corporation DRIVER_VERIFIER_DETECTED_VIOLATION




On Sat 07/01/2017 00:14:07 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010717-8734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x141C, 0xFF, 0x0, 0xFFFFF801A72EC48A)
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.


Thank you for helping!

 
ntoskrnl = new technology operating system kernel = brains of win 10, PC will crash when it does
ntkrnlmp.exe = kernel as well, its initials aren't as clear (never worked out what they all mean)
these two aren't to blame, they just crashed due to a driver request

iqvw64e.sys = some INtel network adapter diagnostic driver... might want to check out your lan driver on your motherboards web site

IRQ errors are driver errors, might be the lan driver
driver verifier errors just point out bad drivers
 


It most likely is the lan driver because that is the only driver I had to update after getting new hardware however it is the latest from the Asus website. Is there a way to find out if itis installed correctly?

 


Thank you I will try that one instead if my system crashes again.
 


It worked for a while but I did get the same BSOD again (IRQL_NOT_LESS_OR_EQUAL) apparently caused by ntoskrnl.exe and ntkrnlmp.exe .

Further information:



Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 10/01/2017 21:56:56
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Computer: SIMON-PC
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
and APPID
{F72671A9-012C-4725-9D2F-2A4D32D65169}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2017-01-10T20:56:56.488286300Z" />
<EventRecordID>2867</EventRecordID>
<Correlation />
<Execution ProcessID="968" ThreadID="568" />
<Channel>System</Channel>
<Computer>SIMON-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}</Data>
<Data Name="param5">{F72671A9-012C-4725-9D2F-2A4D32D65169}</Data>
<Data Name="param6">NT AUTHORITY</Data>
<Data Name="param7">SYSTEM</Data>
<Data Name="param8">S-1-5-18</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 10/01/2017 21:56:43
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SIMON-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000021bbe, 0x00000000000000ff, 0x0000000000000000, 0xfffff8018a0db48a). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0e91fedc-c84e-41eb-8048-76fdac69b5cd.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-01-10T20:56:43.410815000Z" />
<EventRecordID>2864</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>SIMON-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x0000000a (0x0000000000021bbe, 0x00000000000000ff, 0x0000000000000000, 0xfffff8018a0db48a)</Data>
<Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data>
<Data Name="param3">0e91fedc-c84e-41eb-8048-76fdac69b5cd</Data>
</EventData>
</Event>

Log Name: System
Source: Service Control Manager
Date: 10/01/2017 21:56:42
Event ID: 7000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SIMON-PC
Description:
The amdacpksd service failed to start due to the following error:
The system cannot find the file specified.
<----- I couldn't find it either.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2017-01-10T20:56:42.566974700Z" />
<EventRecordID>2863</EventRecordID>
<Correlation />
<Execution ProcessID="760" ThreadID="1016" />
<Channel>System</Channel>
<Computer>SIMON-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">amdacpksd</Data>
<Data Name="param2">%%2</Data>
<Binary>61006D0064006100630070006B00730064000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Service Control Manager
Date: 10/01/2017 21:56:42
Event ID: 7024
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SIMON-PC
Description:
The HomeGroupListener service terminated with the following service-specific error:
There are no more endpoints available from the endpoint mapper.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7024</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2017-01-10T20:56:42.504468000Z" />
<EventRecordID>2862</EventRecordID>
<Correlation />
<Execution ProcessID="760" ThreadID="864" />
<Channel>System</Channel>
<Computer>SIMON-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">HomeGroupListener</Data>
<Data Name="param2">%%2147944153</Data>
<Binary>48006F006D006500470072006F00750070004C0069007300740065006E00650072000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 10/01/2017 21:56:37
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: SIMON-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>4</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2017-01-10T20:56:37.389559900Z" />
<EventRecordID>2838</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>SIMON-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">10</Data>
<Data Name="BugcheckParameter1">0x21bbe</Data>
<Data Name="BugcheckParameter2">0xff</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0xfffff8018a0db48a</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
</EventData>
</Event>

Log Name: System
Source: EventLog
Date: 10/01/2017 21:56:41
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SIMON-PC
Description:
The previous system shutdown at 21:28:45 on ‎10/‎01/‎2017 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-01-10T20:56:41.895028300Z" />
<EventRecordID>2827</EventRecordID>
<Channel>System</Channel>
<Computer>SIMON-PC</Computer>
<Security />
</System>
<EventData>
<Data>21:28:45</Data>
<Data>‎10/‎01/‎2017</Data>
<Data>
</Data>
<Data>
</Data>
<Data>9609</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>E107010002000A0015001C002D00CF02E107010002000A0014001C002D00CF02600900003C000000010000006009000001000000B00400000100000002000000</Binary>
</EventData>
</Event>


All Amd drivers:


AmdK8 AMD K8 Processor Drive Kernel 16/07/2016 04:10:42
amdkmafd AMD Audio Bus Lower Fi Kernel 20/05/2015 01:26:48
amdkmdag amdkmdag Kernel 04/12/2016 17:30:19
amdkmdap amdkmdap Kernel 04/12/2016 17:07:30
AmdPPM AMD Processor Driver Kernel 16/07/2016 04:10:41
amdsata amdsata Kernel 14/05/2015 14:14:52
amdsbs amdsbs Kernel 11/12/2012 22:21:44
amdxata amdxata Kernel 01/05/2015 02:55:35
AtiHDAudioSe AMD Function Driver fo Kernel 0 8/12/2016 18:20:20
AtiPcie AMD PCI Express (3GIO) Kernel 24/08/2009 10:25:26

 
Turn verifier off. This is causing one of them the Intel network drivers iqvw64e.sys

Uninstall Afterburner. Programs like this crash windows.

This file CAM_V3.sys is 8-9 yrs old. Either uninstall CAM 3 Advanced PC monitoring or update it

Old drivers can crash windows

Uninstall Intel Extreme Tuning Util. Uninstall any OC software








 


Thanks for looking into it i will do that. Worth mentioning is that I used those programs before ( I got new hardware and reinstalled win10) without any issues.

 


Yea, I didn't think CAM V3 would be an issue because it was released in 2016.
Anyway I just uninstalled all Oc and monitoring software and will see if it makes a difference.
 


Especially if they want to remain relevant, as I have to assume this PC isn't a fresh install of win 10 since version 1607 as it would have rejected the drivers as not being digitally signed to work with win 10. Someone should mention it to them.

 


It's not exactly a clean installation because win failed to create a bootable usb-drive so I used the built in reset function that deletes everything and then reinstalls win10.
-So far no bluescreen

 
Samsung Evo 120gb I think however what I changed in my system was the cpu, mb, ram and psu. The SSD should be fine.

Crucial Sport LT 16GB DDR4 2400 UDIMM
Asus Z170-A
i5 6600k
rm750i

what I had before:

12gb xm3 ddr3
asus m5a87
fx8150
off-brand 800w psu

Are my parts by any chance incompatible?

 


Yea, Samsung 840 Series. I never updated the firmware so it probably isnt.

Which one should I use:


· 840 EVO mSATA Firmware

· 840 EVO Firmware