Solved

BSOD IRQL NOT LESS OR EQUAL - Windows 7

Hey guys. I'm new to posting on the site but I come here alot for PC answers. I have mediocre knowledge on computers,. I have been getting BSOD quite frequently making my pc hard to use at times. I use WhoCrashed to grab the logs, so here they are:

computer name: DICKS-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., MAXIMUS VI HERO
CPU: GenuineIntel Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17114730496 total
VM: 2147352576, free: 1968267264

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 3/28/2014 1:36:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032814-13993-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFE88003094C80, 0xA, 0x1, 0xFFFFF80002E6AEFD)
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 3/28/2014 1:36:20 PM GMT 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 (0xFFFFE88003094C80, 0xA, 0x1, 0xFFFFF80002E6AEFD)
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 Fri 3/28/2014 1:35:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032814-6786-01.dmp
This was probably caused by the following module: volsnap.sys (volsnap+0x23C35)
Bugcheck code: 0xD1 (0xFFFFEA800D7545E0, 0x2, 0x1, 0xFFFFF880018B2C35)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\volsnap.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Volume Shadow Copy 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.
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 3/28/2014 1:19:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032814-7004-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFE880009B7C80, 0xF, 0x1, 0xFFFFF80002C7900F)
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.


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

4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


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.


The strangest thing was this happened a few times during the installation of windows 7 from booting of the disk as well. PC is about 4 months old and have always had random BSOD but now its much more frequent. I also can't install all the windows updates I get errors : Code 800B0100 and Code 80073712 and Code 9C47.

Any suggestions I would love to try! thanks!
3 answers Last reply Best Answer
More about bsod irql equal windows
  1. whamondator said:
    Hey guys. I'm new to posting on the site but I come here alot for PC answers. I have mediocre knowledge on computers,. I have been getting BSOD quite frequently making my pc hard to use at times. I use WhoCrashed to grab the logs, so here they are:

    computer name: DICKS-PC
    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., MAXIMUS VI HERO
    CPU: GenuineIntel Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz Intel586, level: 6
    8 logical processors, active mask: 255
    RAM: 17114730496 total
    VM: 2147352576, free: 1968267264

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Fri 3/28/2014 1:36:20 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\032814-13993-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0xA (0xFFFFE88003094C80, 0xA, 0x1, 0xFFFFF80002E6AEFD)
    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 3/28/2014 1:36:20 PM GMT 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 (0xFFFFE88003094C80, 0xA, 0x1, 0xFFFFF80002E6AEFD)
    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 Fri 3/28/2014 1:35:45 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\032814-6786-01.dmp
    This was probably caused by the following module: volsnap.sys (volsnap+0x23C35)
    Bugcheck code: 0xD1 (0xFFFFEA800D7545E0, 0x2, 0x1, 0xFFFFF880018B2C35)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\volsnap.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Volume Shadow Copy 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.
    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 3/28/2014 1:19:51 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\032814-7004-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0xA (0xFFFFE880009B7C80, 0xF, 0x1, 0xFFFFF80002C7900F)
    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.


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

    4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


    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.


    The strangest thing was this happened a few times during the installation of windows 7 from booting of the disk as well. PC is about 4 months old and have always had random BSOD but now its much more frequent. Any suggestions I would love to try! thanks!


    Try a system restore. I received this same error and a system restore helped me. Also try swapping out and cleaning ram sticks.
  2. already tried both of those things :p thanks for input :)
  3. Best answer
    Replace ram in other slots or interchange them or run one by one on all slots and also if possible use your ram on some other pc and other pc's ram on your mobo.
Ask a new question

Read More

Windows Blue Screen Systems