BSOD with IRQL_NOT_LESS_OR_EQUAL

[cloudnyn3]

So my OS started randomly BSOD'ing and at first it was
Memory_Management

I pulled RAM out and reinserted, set everything to stock and checked compatibility. Everything was good, even did Memtest86. I updated all my drivers and reinstalled my AV/Firewall.

I got rid of the BSOD for about a day and now its giving the IRQL_NOT_LESS_OR_EQUAL.
I have the crash dump analysis, but I have no idea where to go from here. I understand that something is trying to improperly use an IRQ, but how do I continue on from this point?

http://pastebin.com/3BrthprK

Thats the crash dump, if anyone can help i'd greatly appreciate it.

 

[johnbl]

memory address 20 is most likely just a bad address.
I would be looking for a bug in a device driver. put your memory dump on a server and post a link or here are two debugger commands that might help:

lmiftsm
!for_each_module !chkimg @#ModuleName

the first will dump your drivers names and dates in alphanumerical order
the second will look for corrupted microsoft drivers that you might have in memory. All non microsoft drivers will show as ERROR. This will provide a good suspect drivers list.

 

[cloudnyn3]

How would I go about doing this? I know what IRQ's are, but I don't really know how to use the debugger that well.

 

[johnbl]

sorry, you put up debugger output so I figured you had a debugger running.
Best to just copy the memory dump file .dmp to a server an post a link.
for the debugger, you enter in the commands at the bottom of the page and hit enter.

How would I go about doing this? I know what IRQ's are, but I don't really know how to use the debugger that well.

 

[cloudnyn3]

sorry, you put up debugger output so I figured you had a debugger running.
Best to just copy the memory dump file .dmp to a server an post a link.
for the debugger, you enter in the commands at the bottom of the page and hit enter.

How would I go about doing this? I know what IRQ's are, but I don't really know how to use the debugger that well.

Okay, There's a bunch of errors with finding images for the modules?
Not sure what this means. I will post the .Dmp to a file server. Also just curious, is this .Dmp file static, or does it clear the dump everytime my OS restarts?

https://www.dropbox.com/s/9w1qn4ixq6tbo49/MEMORY.DMP?dl=0

Heres the dump. Its pretty big 😵

Thank you for the help by the way!

 

[johnbl]

the errors for the debugger are most likely because you don't have a symbol path set up to point to microsoft's symbol server. You would just open the debugger, select file->symbol file path and paste in this path and select ok and save the workspace.
http://msdl.microsoft.com/download/symbols

sorry, you put up debugger output so I figured you had a debugger running.
Best to just copy the memory dump file .dmp to a server an post a link.
for the debugger, you enter in the commands at the bottom of the page and hit enter.

How would I go about doing this? I know what IRQ's are, but I don't really know how to use the debugger that well.

Okay, There's a bunch of errors with finding images for the modules?
Not sure what this means. I will post the .Dmp to a file server. Also just curious, is this .Dmp file static, or does it clear the dump everytime my OS restarts?

https://www.dropbox.com/s/9w1qn4ixq6tbo49/MEMORY.DMP?dl=0

Heres the dump. Its pretty big 😵

Thank you for the help by the way!

 

[johnbl]

I would start by booting windows and run verifier.exe /standart
this will make windows check device drivers for common programming mistakes and will force a bugcheck when it detects the mistake. (if it detects the mistake)

I am still looking at the memory dump. I just don't see the likely cause yet.
here are my notes so far:

***you have one device with a failed device install:
PCI\VEN_8086&DEV_1D3A&SUBSYS_1D3A1849&REV_05\3&11583659&0&B0

- driver list and dates look pretty good.
- you are running ESET software.
- no overclocking
- you had armsvc.exe adobe reader update running
- java was running and was using the most memory of all your apps.

***BIOS date and version is newer that what was listed on the ASROCK website.
as the current version. You should make sure your version was not removed for some reason. (or I looked up the wrong motherboard)
it looks like you have:
Manufacturer ASRock
Product X79 Extreme4
BIOS Version P3.70
BIOS Release Date 02/13/2014

Processor Manufacturer Intel
Processor ID d7060200fffbebbf
Processor Version Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz
Processor Voltage 80h - 0.0V
External Clock 100MHz
Max Speed 4000MHz
Current Speed 3200MHz

kingston memory running at 1600Mhz
Part Number KHX2400C11D3/

 

[cloudnyn3]

Okay, from my experience with verifier; It should crash and provide data in the crash dump after restarting correct?

Also, if it helps any. After I restart, sometimes it won't get past POST. it takes 3 or 4 restarts for it to finally make it to the OS.
This doesn't happen everytime and its not a heat issue. I have everything set to shutdown at certain temps. I also monitor my temps and they have been consistently good.

I use JDK and run some Java intensive applications, so that makes sense. I also updated all of my drivers and rolled back some to see if that help. As of now, my computer has crashed 3 times today and it was still the IRQL and Memory_Management errors.
Could this possibly be that one of memory modules is bad? Even though i tested them both separately and together? I know memtest is good, but I've never known it to catch every little error.

I would start by booting windows and run verifier.exe /standart
this will make windows check device drivers for common programming mistakes and will force a bugcheck when it detects the mistake. (if it detects the mistake)

I am still looking at the memory dump. I just don't see the likely cause yet.
here are my notes so far:

***you have one device with a failed device install:
PCI\VEN_8086&DEV_1D3A&SUBSYS_1D3A1849&REV_05\3&11583659&0&B0

- driver list and dates look pretty good.
- you are running ESET software.
- no overclocking
- you had armsvc.exe adobe reader update running
- java was running and was using the most memory of all your apps.

***BIOS date and version is newer that what was listed on the ASROCK website.
as the current version. You should make sure your version was not removed for some reason. (or I looked up the wrong motherboard)
it looks like you have:
Manufacturer ASRock
Product X79 Extreme4
BIOS Version P3.70
BIOS Release Date 02/13/2014

Processor Manufacturer Intel
Processor ID d7060200fffbebbf
Processor Version Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz
Processor Voltage 80h - 0.0V
External Clock 100MHz
Max Speed 4000MHz
Current Speed 3200MHz

kingston memory running at 1600Mhz
Part Number KHX2400C11D3/

 

[johnbl]

note you could also go to here: https://technet.microsoft.com/en-us/sysinternals/bb896653
and download process explorer, find the svchost.exe process and see which ones are bundled together. I would expect your microphone talks to a service and the service talks to a driver. there would be a bug in the service where it keeps the interrupt too high then needs to get something from the hard drive and the memory manager can not provide it because it runs at a lower interrupt.
The driver can not complete because it needs the code paged in. Result is the bugcheck you got.
--------------
here is info on your usb 3.0 hub
ASMedia - PCI: VendorId 0x1b21 DeviceId 0x1042 RevisionId 0x00 SubVendorId 0x1849 SubSystemId 0x1042 Firmware 110315_010230

you have BLUE NESSIE USB MIC Speed: Full plugged in
and on the other you have USB 3.0 FD Speed: Super
which is described as DeviceDescriptor: VID 154b ( PNY Technologies Inc.) PID fa0a REV 1100, Class: (0)(0) BcdUsb: 0300


I would unplug these two devices and reboot and see if i still get a bugcheck.

I would also check to see if there is a bug in the firmware release of the USB chip. the OEM would make a BIOS update and provide special USB 3.0 drivers for your motherboard if that is the case.

sorry that is not much help, your system uptime was only 10 mins so hopefully it is easy to remove the devices and see if you still get a bugcheck.

----------------
I did find 4 error entries in the usb 3.0 internal error log that can be your root cause.
I figure it is something attached to your USB 3.0 hub. looks like the driver is a generic microsoft USB 3.0 driver \SystemRoot\System32\drivers\UsbHub3.sys
Timestamp: Thu Jul 24 04:43:31 2014

I see that it is listed as a service(svchost.exe) running on processor 8
not too helpful because of the number of generic svchost.exe host you have running.

will look thru the USB tree and see if I can match the thread.

Okay, from my experience with verifier; It should crash and provide data in the crash dump after restarting correct?

Also, if it helps any. After I restart, sometimes it won't get past POST. it takes 3 or 4 restarts for it to finally make it to the OS.
This doesn't happen everytime and its not a heat issue. I have everything set to shutdown at certain temps. I also monitor my temps and they have been consistently good.

I use JDK and run some Java intensive applications, so that makes sense. I also updated all of my drivers and rolled back some to see if that help. As of now, my computer has crashed 3 times today and it was still the IRQL and Memory_Management errors.
Could this possibly be that one of memory modules is bad? Even though i tested them both separately and together? I know memtest is good, but I've never known it to catch every little error.

I would start by booting windows and run verifier.exe /standart
this will make windows check device drivers for common programming mistakes and will force a bugcheck when it detects the mistake. (if it detects the mistake)

I am still looking at the memory dump. I just don't see the likely cause yet.
here are my notes so far:

***you have one device with a failed device install:
PCI\VEN_8086&DEV_1D3A&SUBSYS_1D3A1849&REV_05\3&11583659&0&B0

- driver list and dates look pretty good.
- you are running ESET software.
- no overclocking
- you had armsvc.exe adobe reader update running
- java was running and was using the most memory of all your apps.

***BIOS date and version is newer that what was listed on the ASROCK website.
as the current version. You should make sure your version was not removed for some reason. (or I looked up the wrong motherboard)
it looks like you have:
Manufacturer ASRock
Product X79 Extreme4
BIOS Version P3.70
BIOS Release Date 02/13/2014

Processor Manufacturer Intel
Processor ID d7060200fffbebbf
Processor Version Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz
Processor Voltage 80h - 0.0V
External Clock 100MHz
Max Speed 4000MHz
Current Speed 3200MHz

kingston memory running at 1600Mhz
Part Number KHX2400C11D3/