Solved

Win7 64-bit Random Bsod. irql_not_less_or_equal ntoskrnl.exe 0x0000000a

Greetings, about a month ago i built my own pc here are the components:

http://pcpartpicker.com/user/Clawx207/saved/3lbq

Things have been running smoothly for the most part, air-flow is correct and nicely cooled, memory comes up with no errors after countless tests, swapped my graphics card, tested CPU. All of these check out but, still i have constant 'Bsod's'. The game that triggers it the most is Metal gear rising revengeance.

Here's the most common crash.dmp files:
052214-5865-01.dmp 5/22/2014 10:30:44 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`0000a825 00000000`0000000f 00000000`00000001 fffff800`030bb15e ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18409 (win7sp1_gdr.140303-2144) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\052214-5865-01.dmp 8 15 7601 293,296 5/22/2014 10:31:36 PM

052214-6520-01.dmp 5/22/2014 4:49:13 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`0000349b 00000000`00000002 00000000`00000000 fffff880`0183e81e ndis.sys ndis.sys+181e NDIS 6.20 driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\052214-6520-01.dmp 8 15 7601 293,256 5/22/2014 4:49:49 PM

List of installed programs/drivers: http://i.imgur.com/72os3ie.png

i have done 2 clean installs out of frustration, no change after installing all the basics.
19 answers Last reply Best Answer
More about win7 bit random bsod irql equal ntoskrnl exe 0x0000000a
  1. Hello... a few observations from your img...
    1) are you running two Lan cards?
    2) are your running 3D glasses and/or monitor?
    3) are you running phyX games/hardware?
    4) are you running audio out of your Video card?

    Have you tried an earlier/dfferent Video card driver version?
  2. Ironsounds said:
    Hello... a few observations from your img...
    1) are you running two Lan cards?
    2) are your running 3D glasses and/or monitor?
    3) are you running phyX games/hardware?
    4) are you running audio out of your Video card?

    Have you tried an earlier/dfferent Video card driver version?


    1)No im only running the Asus Lan card, the realtek driver is for ethernet.
    2)No
    3)I have played call of duty ghosts and metro last light
    4)Yes i have realtek motherboard sound disabled

    I have, my graphics card comes with a disk of earlier versions.
  3. Here are all of my crashes, counting 4 today

    On Fri 5/23/2014 6:28:33 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\052314-5631-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0xA (0x24, 0x2, 0x0, 0xFFFFF8000307077F)
    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 Fri 5/23/2014 6:28:33 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: iusb3xhc.sys (iusb3xhc+0x6337B)
    Bugcheck code: 0xA (0x24, 0x2, 0x0, 0xFFFFF8000307077F)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\iusb3xhc.sys
    product: USB 3.0 Device Driver
    company: Intel Corporation
    description: Intel(R) USB 3.0 eXtensible Host Controller Driver
    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.
    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: iusb3xhc.sys (Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation).
    Google query: Intel Corporation IRQL_NOT_LESS_OR_EQUAL


    On Fri 5/23/2014 6:11:21 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\052314-4414-01.dmp
    This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x8DBC)
    Bugcheck code: 0xD1 (0x188, 0x2, 0x1, 0xFFFFF88004208DBC)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\dxgmms1.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics MMS
    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 Fri 5/23/2014 6:08:54 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\052314-4742-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD8, 0x0, 0xFFFFF800030CDC1A, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 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.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Fri 5/23/2014 5:35:05 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\052314-4680-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFC2, 0x1, 0xFFFFF80003084990, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 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.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Fri 5/23/2014 5:20:40 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\052314-4648-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
    Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    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 program generated an exception which the error handler did not catch.
    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 Fri 5/23/2014 5:08:40 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\052314-4992-01.dmp
    This was probably caused by the following module: cng.sys (cng+0x7585)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001614585, 0xFFFFF880035CB388, 0xFFFFF880035CABE0)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\cng.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Kernel Cryptography, Next Generation
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    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 Fri 5/23/2014 2:30:44 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\052214-5865-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0xA (0xA825, 0xF, 0x1, 0xFFFFF800030BB15E)
    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 Fri 5/23/2014 1:58:24 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\052214-5506-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0xA (0xFFFFF8A007BDB024, 0xE, 0x0, 0xFFFFF800030AAA9F)
    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 Fri 5/23/2014 1:43:02 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\052214-5616-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD8, 0x0, 0xFFFFF8000308EC1A, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 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.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


  4. Hello... all my experience with Windows BSOD is because of a loss of communications of hardware, through your MB, as seen to the OS. Find a Loose connector/pin, Power/Data connector or Hardware device causing it.
    Try removing hardware/connectors for a minimum of things connected for Windows to boot and tested with just those devices... start adding a piece at a time till the BSOD returns.
    1) Sound chip and Lan on the MB is also a "Hardware Device" disable in BIOs
    2) CD/DVD is a "Hardware Device"
    3) HD/SSD is a "Hardware Device"
    4) Look very close to all your Pins on all your Power connectors for a pushed out pin/loose connection.
    5) use some rubbing alcohol to clean memory/Video card/Data connectors and re-insert.
    6) remove your video card and use the onboard CPU/Video to determine if your Video card is causing it.

    If possible Test Hardware in another computer and see if it causes a BSOD.

    It's a tuff problem to find at times but stay calm and be Logical about your work and testing methods.
  5. Ironsounds said:
    Hello... all my experience with Windows BSOD is because of a loss of communications of hardware, through your MB, as seen to the OS. Find a Loose connector/pin, Power/Data connector or Hardware device causing it.
    Try removing hardware/connectors for a minimum of things connected for Windows to boot and tested with just those devices... start adding a piece at a time till the BSOD returns.
    1) Sound chip and Lan on the MB is also a "Hardware Device" disable in BIOs
    2) CD/DVD is a "Hardware Device"
    3) HD/SSD is a "Hardware Device"
    4) Look very close to all your Pins on all your Power connectors for a pushed out pin/loose connection.
    5) use some rubbing alcohol to clean memory/Video card/Data connectors and re-insert.
    6) remove your video card and use the onboard CPU/Video to determine if your Video card is causing it.

    If possible Test Hardware in another computer and see if it causes a BSOD.

    It's a tuff problem to find at times but stay calm and be Logical about your work and testing methods.


    As i said i have already tried another video card and that was not the issue. I've checked all my ram sticks, cords, and my graphics card again to make sure they are in correctly. The issue still persist.
  6. Most common one recently:

    On Sun 5/25/2014 3:34:10 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\052514-5335-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0xD1 (0xFFFFF880FFFFF880, 0x6, 0x8, 0xFFFFF880FFFFF880)
    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.

    I ran driver verifier on all my drivers and it seemed to prevent bsod's, but killed my computers performance. I'm running it now on all non-microsoft drivers to see if it can catch anything.
  7. Hello... Don't use MS drivers ever for hardware, use the companies that make the product always... for a simple test to prove it's not your Hardware would be to...
    1) fresh install of Windows
    2) Mfgr's drivers install... driver only for hardware - No bloat ware.
    3) DO NOT get any MS updates to the files.
    4) Load what ever program you want to test with, ? Game, Game Demo.
    5) Leave computer on and play, what ever.

    My point is Windows 7 basic install will not software BSOD if your computer does? it is a Hardware problem.
  8. Ironsounds said:
    Hello... Don't use MS drivers ever for hardware, use the companies that make the product always... for a simple test to prove it's not your Hardware would be to...
    1) fresh install of Windows and
    2) Mfgr's drivers install... driver only for hardware - No bloat ware.
    3) DO NOT get any MS updates to the files.
    4) Load what ever program you want to test with, ? Game, Game Demo.
    5) Leave computer on and play, what ever.

    My point is Windows 7 basic install will not software BSOD if your computer does? it is a Hardware problem.


    Alright, I did a clean install, didnt download any MS system updates, and installed my WLAN driver and Graphics drivers. Both were installed from the support disks. Sure enough when i opened Geforce Experience, BSOD. I suspect it is my graphics card, but to be sure, what would be the best way to diagonse all of my hardware?
  9. Hello... Geforce Experience/ Phyx to me is a bloatware app...( only load Graphic & Audio drivers - chose custom install ) and "Program and Features" can be used to un-installed to make sure it's not the app.
    1) You can try your Video card/memory/etc in another working computer? Thats the only way to be sure!!!
    2) Check very carefully your power connectors to your video card from your power supply... look for a bad crimped wire, Pin pushed out the back, slightly close/adjust a socket/female pin for a tighter connection to the male pins.
    3) clean your card edges that insert into your computer with rubbing alcohol.
    4) Try using the Realtek lan on your MB only... it's drivers and chips are Rock Solid stuff.
    5) Try the Asus Wlan card in another Computer.
    6) Did you install your Chipset Drivers?
    7) Do you have latest Bios installed on your MB.... Once agian the MFG'r site...
  10. Ironsounds said:
    Hello... Geforce Experience/ Phyx to me is a bloatware app...( only load Graphic & Audio drivers - chose custom install ) and can be un-installed to make sure it's not the app.
    1) You can try your Video card/memory/etc in another working computer? Thats the only way to be sure!!!
    2) Check very carefully your power connectors to your video card from your power supply... look for a bad crimped wire, Pin pushed out the back, slightly close/adjust a socket/female pin for a tighter connection to the male pins.
    3) clean your card edges that insert into your computer with rubbing alcohol.


    Alright i tried my Graphics card in my dad's computer and it had no issues. I tried running Integrated graphics on mine again, but it got the same result as the graphics card. Uninstalling Geforce Experience or physx didnt change anything.

    I ran another test on my CPU and that came up ok. Im going to see what asus has for motherboard diagnostics....
  11. Hello... Good Testing.... Well... down to your MB ( Hardware ), Wan card, CPU Fan, Power Supply and Memory !!!
    Power connector Bad to Graphics card?
    Also another thing ...
    8) make sure your BIO's has any Thermal/Fan conditions to shut down the computer Disabled. ( Bad CPU FAN signal )
    9) Disable MB Bios "Hardware" Audio, Video and Lan... and use known Good Video card ( Bad MB )
  12. Ironsounds said:
    Hello... Good Testing.... Well... down to your MB ( Hardware ), Wan card, CPU Fan, Power Supply and Memory !!!
    Power connector Bad to Graphics card?
    Also another thing ...
    8) make sure your BIO's has any Thermal/Fan conditions to shut down the computer Disabled. ( Bad CPU FAN signal )
    9) Disable MB Bios "Hardware" Audio, Video and Lan... and use known Good Video card ( Bad MB )


    Well i believe i just found the issue...my ssd just died. None of my sata ports or cables pick it up in bios. Could it be possible that a faulty ssd could cause bsod's?
  13. Hello...
    3) HD/SSD is a "Hardware Device"
  14. It's not my Graphics card, hdd, ssd, memory or cpu.i installed windows to my ssd again and still having the same results without any excess drivers. My stress level is off the charts right now...
  15. Take out your PNY ram module. Be sure that you took only PNY module, not the gskills. Try now..
  16. geekIN said:
    Take out your PNY ram module. Be sure that you took only PNY module, not the gskills. Try now..


    I'm a bit past that. The PNY Ram is a test part to see if my g.skill ones were bad.
  17. Best answer
    Hello... Remain calm and Logical in your efforts... Your getting pretty fast at Loading Windows and drivers now I Bet... B )

    Good Testing... You are able to repeat the results so far, so your on the right Track in your Methods...

    10) Try just IDE mode... Not AHCI driver and MB Bios controller... And other MB SATA inputs.
    11) Make sure you Delete all Partitions each time, You Load WINDOWS INSTALL with a reboot, Before you install, on your HD/SSD.
    Start a RMA on your MB... Pretty easy and Friendly service... You can always cancel it...
  18. Forgive me for never posting a proper solution, but the issue was a faulty CPU. Sounds impossible, but i had it replaced, no issues since.
  19. Can anyone help me interpret the following crash data?
    Been getting BSODs and ntoskrnl.exe seems to be the culprit but I'm not sure how to fix it?

    MoBo: Asus P5Q-E (old mobo, so no updates available)
    CPU: Intel Core 2 Quad Q6600 @ 2.40GHz
    Graphics: 2048MB ATI ASUS HD7770

    Dump File : 122414-13390-01.dmp
    Crash Time : 24-12-2014 18:45:13
    Bug Check String : IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code : 0x0000000a
    Parameter 1 : ffffe021`5ea23478
    Parameter 2 : 00000000`00000002
    Parameter 3 : 00000000`00000000
    Parameter 4 : fffff801`6d6a88ca
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+150aa0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.3.9600.17476 (winblue_r5.141029-1500)
    Processor : x64
    Crash Address : ntoskrnl.exe+150aa0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\122414-13390-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 9600
    Dump File Size : 280,112
    Dump File Time : 24-12-2014 18:51:54

    ==================================================
Ask a new question

Read More

Blue Screen Windows 7 Ntoskrnl.Exe