Sign in with
Sign up | Sign in
Your question
Solved

Blue Screen Of Death DRIVER_IRQL_NOT_LESS_OR_EQUAL

Last response: in Windows 7
Share
June 3, 2014 9:06:45 PM

A few months ago i was constantly getting BSOD's for random reasons. It could be triggered by just leaving the computer idle, or it could be triggered by random things like watching streams or playing games like hearthstone. but it never seems to happen when i play games that have high graphics like splinter cell or BF4. It took a break and stopped happening for about 3 months and now for some odd reason it is back. I have been searching for a solution to this for months but it seems like everything that ive tried does not work. I need help. It seems like majority of the time the BSOD is caused by ntoskrnl.exe and iusb3xhc.sys. Im just trying to find a way to fix this because ive become desperate.


file:///C:/Users/Greg/AppData/Local/Temp/report.html

Im not sure if you can read that link but i can link the BlueScreenViewer report on request. please help. Thank you.

Best solution

a b $ Windows 7
June 3, 2014 9:19:56 PM

use this it will read the minidump in plain text http://www.resplendence.com/whocrashed
Share
June 4, 2014 7:28:50 AM

On Wed 6/4/2014 3:37:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060314-33727-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x118, 0x2, 0x0, 0xFFFFF800036862F7)
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 Wed 6/4/2014 3:37:52 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xC765C)
Bugcheck code: 0xA (0x118, 0x2, 0x0, 0xFFFFF800036862F7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 335.23
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 335.23
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 335.23 , NVIDIA Corporation).
Google query: NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL



On Tue 6/3/2014 4:30:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060314-21450-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 Mon 6/2/2014 9:59:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-33337-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x7000000, 0xFFFFFA800E3FD010, 0xFFFFFA8009AA2AF0, 0xFFFFFA800D383010)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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/30/2014 6:21:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052914-27674-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0x0, 0x6, 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 Wed 3/26/2014 12:40:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032514-18907-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6B610)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000096, 0xFFFFF800034CB610, 0xFFFFF880043E67C8, 0xFFFFF880043E6020)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 3/24/2014 4:30:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032414-15896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0x0, 0x6, 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 Mon 2/24/2014 11:57:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022414-15771-01.dmp
This was probably caused by the following module: iusb3xhc.sys (iusb3xhc+0x2A14A)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFE8, 0x2, 0x1, 0xFFFFF8800302A14A)
Error: DRIVER_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 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: iusb3xhc.sys (Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Thu 12/19/2013 12:03:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121813-24960-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF800034154CA)
Bugcheck code: 0xA (0x3B, 0xD, 0x0, 0xFFFFF800034154CA)
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

9 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

iusb3xhc.sys (Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 335.23 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
m
0
l
Related resources
June 4, 2014 7:31:40 AM

Sorry for the late Reply. Fell asleep
m
0
l
June 4, 2014 7:46:33 AM

Thanks for the program by the way. So far i've done what it has asked me and updated both of the drivers it listed. We'll see if any crashes still happen. As far as the other 7 crashes i still don't know what i can do to fix them.
m
0
l
a b $ Windows 7
June 4, 2014 1:14:35 PM

witch one do you still have on the new test report .
m
0
l
June 4, 2014 1:16:49 PM

Sorry, i dont understand what that means.
m
0
l
a b $ Windows 7
June 4, 2014 1:17:56 PM

analyse again with who crashed and see what it still report as error .
m
0
l
June 4, 2014 1:21:01 PM

I believe its still the same. but since ive used who crashed and updated the said drivers i havent crashed....yet.

But here is the report again









Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 6/4/2014 3:37:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060314-33727-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x118, 0x2, 0x0, 0xFFFFF800036862F7)
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 Wed 6/4/2014 3:37:52 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xC765C)
Bugcheck code: 0xA (0x118, 0x2, 0x0, 0xFFFFF800036862F7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 337.88
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 337.88
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 337.88 , NVIDIA Corporation).
Google query: NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL



On Tue 6/3/2014 4:30:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060314-21450-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 Mon 6/2/2014 9:59:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-33337-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x7000000, 0xFFFFFA800E3FD010, 0xFFFFFA8009AA2AF0, 0xFFFFFA800D383010)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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/30/2014 6:21:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052914-27674-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0x0, 0x6, 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 Wed 3/26/2014 12:40:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032514-18907-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6B610)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000096, 0xFFFFF800034CB610, 0xFFFFF880043E67C8, 0xFFFFF880043E6020)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 3/24/2014 4:30:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032414-15896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0x0, 0x6, 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 Mon 2/24/2014 11:57:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022414-15771-01.dmp
This was probably caused by the following module: iusb3xhc.sys (iusb3xhc+0x2A14A)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFE8, 0x2, 0x1, 0xFFFFF8800302A14A)
Error: DRIVER_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 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: iusb3xhc.sys (Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Thu 12/19/2013 12:03:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121813-24960-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF800034154CA)
Bugcheck code: 0xA (0x3B, 0xD, 0x0, 0xFFFFF800034154CA)
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

9 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

iusb3xhc.sys (Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 337.88 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



m
0
l
a b $ Windows 7
June 4, 2014 1:29:49 PM

you have the usb 3.0 driver from intel that need to be update then you still have the nvida issue also check if there is any bug correction for the watchdog game i would also do a memtest one module at the time for the irql issue .
m
0
l
June 4, 2014 1:36:34 PM

So far i have updated the USB 3.0 drivers and completely uninstalled and reinstalled the nvidia drivers. How would i check bugs for watchdog? thank you for your help by the way.
m
0
l
a b $ Windows 7
June 4, 2014 1:40:45 PM

your welcome if your read the dump they report all these issue .
m
0
l
!