IRQL_NOT_LESS_OR_EQUAL issues on clean install of Windows

blizzars

Honorable
Dec 17, 2013
51
0
10,640
Like many other users on here, I've ran into the BSOD with IRQL_NOT_LESS_OR_EQUAL listed. I noticed this on the new computer I built and ran into the issue while playing vr games with the vive. I've tried resetting my cmos on my motherboard, reseating the cpu, ram and gpu and had no luck with any of these.

I've seen users on here post dump files and that helped identify what the issue was. Perhaps I could do that if someone would be able to tell me how to do this.

Here is my system info:
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.14393 N/A Build 14393
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
Original Install Date: 2016-08-17, 11:17:22 PM
System Boot Time: 2016-08-19, 8:27:23 PM
System Manufacturer: System manufacturer
System Model: System Product Name
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 94 Stepping 3 GenuineIntel ~4001 Mhz
BIOS Version: American Megatrends Inc. 1902, 2016-06-24
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume2
System Locale: en-ca;English (Canada)
Input Locale: en-us;English (United States)
Time Zone: (UTC-06:00) Saskatchewan
Total Physical Memory: 16,304 MB
Available Physical Memory: 13,586 MB
Virtual Memory: Max Size: 19,248 MB
Virtual Memory: Available: 16,387 MB
Virtual Memory: In Use: 2,861 MB
Page File Location(s): C:\pagefile.sys
Domain: WORKGROUP
Hotfix(s): 1 Hotfix(s) Installed.
[01]: KB3176495
Network Card(s): 1 NIC(s) Installed.
[01]: Intel(R) Ethernet Connection (2) I219-V
Connection Name: Ethernet
DHCP Enabled: Yes
DHCP Server: 192.168.0.1
IP address(es)
[01]: 192.168.0.22
[02]: fe80::493e:b065:eb01:551f
[03]: fd00:fc:8d31:63f2:441:ae39:d2d5:e323
[04]: fd00:fc:8d31:63f2:493e:b065:eb01:551f
Hyper-V Requirements: VM Monitor Mode Extensions: Yes
Virtualization Enabled In Firmware: Yes
Second Level Address Translation: Yes
Data Execution Prevention Available: Yes

Thanks!
 
Solution
Did you overclock using the BIOS or software? The IRQ error is generally driver related and in both cases it could be the HTC driver.

If you are using software to overclock, I would remove the overclock while you test the PC. See if just the absence of an overclock and its software not working is enough to fix it.

Colif

Win 11 Master
Moderator
That is a driver error, I can't read the dumps but this can. Can you download and run Who crashed: http://www.resplendence.com/whocrashed
it will look at error logs and give us a summary of the error

It might just point at windows but its worth a try. If you copy/paste in here I will have a look at it :)



Also, go check motherboard makers web site and see if you have latest drivers, might need to do same for USB devices as well.

Can you give us the specs of your PC?
 

blizzars

Honorable
Dec 17, 2013
51
0
10,640


The two latest logs are below

This one is when I tried rebooting with the driver verification thing that Microsoft suggested, I was unable to boot into Windows with it on.

On Sat 2016-08-20 5:14:47 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: vivefs.sys (vivefs+0x100D6)
Bugcheck code: 0xC4 (0x2000, 0xFFFFF802A40700D6, 0x0, 0x414B4F44)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\vivefs.sys
product: Windows (R) Win 7 DDK driver
company: Windows (R) Win 7 DDK provider
description: Dokan Filesystem Driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
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: vivefs.sys (Dokan Filesystem Driver, Windows (R) Win 7 DDK provider).
Google query: Windows (R) Win 7 DDK provider DRIVER_VERIFIER_DETECTED_VIOLATION


This is the initial one that I've had issues with, would it be possible this is due to an overclocked CPU?

On Sat 2016-08-20 2:07:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081916-5343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0xA (0x3490, 0xFF, 0x0, 0xFFFFF8001A75E929)
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.


The specs of my computer are as follows:
Gaming X GTX1080
Kingston 2133 8gb DDR4 ram x2
i7-6700k
asus z170a motherboard
840 Series SSD and a WD 7.2k HDD

 

blizzars

Honorable
Dec 17, 2013
51
0
10,640


Yeah that dumpfile was from the driver verifier. I've turned it off since, I believe that is necessary for the vive to run though..
 

Colif

Win 11 Master
Moderator


thats almost exactly what the other people said when they worked out this error on the other sites. I looked at file name in google and everyone reached same conclusion. Microsoft just links you to https://www.htcvive.com/us/support/contactus/
 

Colif

Win 11 Master
Moderator
Did you overclock using the BIOS or software? The IRQ error is generally driver related and in both cases it could be the HTC driver.

If you are using software to overclock, I would remove the overclock while you test the PC. See if just the absence of an overclock and its software not working is enough to fix it.
 
Solution

blizzars

Honorable
Dec 17, 2013
51
0
10,640
so far I've over locked the CPU through the bios. I was going to set everything back to defaults and test it out.

like you said tho IRQ is a hardware issue so I don't know if it'll work. I'll try it out and report back