BSOD Random 0xA, IRQL_NOT_LESS_OR_EQUAL

Page 1 of 4 123 ... LastLast

  1. Posts : 176
    Windows 7 Ultimate x64
       #1

    BSOD Random 0xA, IRQL_NOT_LESS_OR_EQUAL


    Hello i have noticed Recently that i have been Getting a BSOD i had about 3 Today
    i have a program called Who Crashed to analyze my Dump Files i will also include BSOD Dump & System File Collection app Files etc
    PC is about 3 years old (so is all the hardware except the GFX card is like 1 year old
    i upgrade to 64 bit recently about 1 year ago
    also thanks in Advance :)
    this is all the info from the Program called Who Crashed

    System Information (local)
    computer name: MATT-PC
    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    CPU: AuthenticAMD AMD Phenom(tm) 9600 Quad-Core Processor AMD586, level: 16
    4 logical processors, active mask: 15
    RAM: 4294107136 total
    VM: 2147352576, free: 1947316224


    Crash Dump Analysis
    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.


    On Wed 1/18/2012 2:52:51 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011712-34398-01.dmp
    uptime: 03:22:56
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xA (0xFFFFFA7FFFFFFD20, 0x2, 0x0, 0xFFFFF80002C5885A)
    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 which cannot be identified at this time.


    On Wed 1/18/2012 2:52:51 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    uptime: 03:22:56
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0xA (0xFFFFFA7FFFFFFD20, 0x2, 0x0, 0xFFFFF80002C5885A)
    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 which cannot be identified at this time.


    On Tue 1/17/2012 11:27:59 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011712-21450-01.dmp
    uptime: 00:11:21
    This was probably caused by the following module: hal.dll (hal+0x12A3B)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA8004AC5028, 0xB640A000, 0x59000135)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
    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 which cannot be identified at this time.


    On Tue 1/17/2012 9:30:00 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011712-21699-01.dmp
    uptime: 00:16:47
    This was probably caused by the following module: hal.dll (hal+0x12A3B)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA8004AB2028, 0xB608A000, 0x1D000135)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
    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 which cannot be identified at this time.


    On Tue 1/17/2012 9:12:04 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011712-25459-01.dmp
    uptime: 1 day, 01:20:35
    This was probably caused by the following module: hal.dll (hal+0x12A3B)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA8004A90028, 0xB420A000, 0x135)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
    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 which cannot be identified at this time.


    On Wed 1/4/2012 4:07:01 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010312-33009-01.dmp
    uptime: 20:40:30
    This was probably caused by the following module: win32k.sys (win32k+0xC122B)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600018122B, 0xFFFFF88006516F30, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    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 which cannot be identified at this time.
      My Computer


  2. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #2

    Your .dmp file shows a stop error of 0x124 which is a general hardware error .
    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

    Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress
    Some generic advice.

    If you are overclocking STOP.
    Return to the default settings at least for now.

    If you are running a RAID update its driver.



    You can read more on this error and what to try here...


    Stop 0x124 - what it means and what to try
      My Computer


  3. Posts : 176
    Windows 7 Ultimate x64
    Thread Starter
       #3

    ok im not doing any OC and i dont have a RAID Setup and i looked at other sugestions that you said to in the link
    i know its not lack of cooling PC is 29C ATM is it posible its a "false Positive"??
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    Zeldafan1993 said:
    ok im not doing any OC and i dont have a RAID Setup and i looked at other sugestions that you said to in the link
    i know its not lack of cooling PC is 29C ATM is it posible its a "false Positive"??
    No. Unlike who crashed the tool we use WinDbg only gives a result when there is a reasonable amount of proof.

    The crashes were/are being caused by hardware. Could be RAM, CPU, etc.


    ken J
      My Computer


  5. Posts : 176
    Windows 7 Ultimate x64
    Thread Starter
       #5

    zigzag3143 said:
    Zeldafan1993 said:
    ok im not doing any OC and i dont have a RAID Setup and i looked at other sugestions that you said to in the link
    i know its not lack of cooling PC is 29C ATM is it posible its a "false Positive"??
    No. Unlike who crashed the tool we use WinDbg only gives a result when there is a reasonable amount of proof.

    The crashes were/are being caused by hardware. Could be RAM, CPU, etc.


    ken J
    ok i was just asking cuz in the link he sent me it says 0x124 can be a false positive. but what do you think i should do to "test" or narrow down what my problem is

    i have a feeling its my CPU since i tried to OC my CPU by like .3 a while ago and got a blue screen so then i set it to default Right away

    but is there a test or something i can do to see what the most likely cause is?
    Last edited by Zeldafan1993; 18 Jan 2012 at 03:48.
      My Computer


  6. Posts : 176
    Windows 7 Ultimate x64
    Thread Starter
       #6

    Sorry for Double post

    is there any way to Find out what suspected problem is???
      My Computer


  7. Posts : 28,845
    Win 8 Release candidate 8400
       #7

    Zeldafan1993 said:
    Sorry for Double post

    is there any way to Find out what suspected problem is???
    OK so you have done all the things suggested in the 124 post?

    If so what version of BIOS did you update to?


    Old drivers needing update
    Code:
    Sahdad64.sys    10/27/2008 10:56:11 PM    fffff880`019f3000    fffff880`019fe000        0x0000b000    0x49068d5b                        
    Saibad64.sys    10/27/2008 10:56:15 PM    fffff880`019ea000    fffff880`019f3000        0x00009000    0x49068d5f                        
    SaibVdAd64.sys    10/27/2008 10:56:20 PM    fffff880`04acc000    fffff880`04ad6000        0x0000a000    0x49068d64                        
    spldr.sys    5/11/2009 11:56:27 AM    fffff880`019a8000    fffff880`019b0000        0x00008000    0x4a0858bb                        
    GEARAspiWDM.sys    5/18/2009 7:17:04 AM    fffff880`04c35000    fffff880`04c42000        0x0000d000    0x4a1151c0                        
    c2scsi64.sys    5/19/2009 4:07:19 PM    fffff880`0163a000    fffff880`01686000        0x0004c000    0x4a131f87                        
    cdrbsdrv.SYS    6/16/2009 10:37:33 PM    fffff880`04333000    fffff880`04341000        0x0000e000    0x4a3864fd
    How To Find Drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - - The most common drivers are listed on this page: Driver Reference Driver Reference
    - - Driver manufacturer links are on this page: Drivers and Downloads
      My Computer


  8. Posts : 176
    Windows 7 Ultimate x64
    Thread Starter
       #8

    zigzag3143 said:
    Zeldafan1993 said:
    Sorry for Double post

    is there any way to Find out what suspected problem is???
    OK so you have done all the things suggested in the 124 post?

    If so what version of BIOS did you update to?


    Old drivers needing update
    Code:
    Sahdad64.sys    10/27/2008 10:56:11 PM    fffff880`019f3000    fffff880`019fe000        0x0000b000    0x49068d5b                        
    Saibad64.sys    10/27/2008 10:56:15 PM    fffff880`019ea000    fffff880`019f3000        0x00009000    0x49068d5f                        
    SaibVdAd64.sys    10/27/2008 10:56:20 PM    fffff880`04acc000    fffff880`04ad6000        0x0000a000    0x49068d64                        
    spldr.sys    5/11/2009 11:56:27 AM    fffff880`019a8000    fffff880`019b0000        0x00008000    0x4a0858bb                        
    GEARAspiWDM.sys    5/18/2009 7:17:04 AM    fffff880`04c35000    fffff880`04c42000        0x0000d000    0x4a1151c0                        
    c2scsi64.sys    5/19/2009 4:07:19 PM    fffff880`0163a000    fffff880`01686000        0x0004c000    0x4a131f87                        
    cdrbsdrv.SYS    6/16/2009 10:37:33 PM    fffff880`04333000    fffff880`04341000        0x0000e000    0x4a3864fd
    How To Find Drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - - The most common drivers are listed on this page: Driver Reference Driver Reference
    - - Driver manufacturer links are on this page: Drivers and Downloads
    i have Bios version 1303 thats the Latest BIOS for my Motherboard (ASUS M4N78 PRO)

    as of 3 hours ago i reinstalled Windows 7 Ultimate x64 so would you like me to Re uploaded my Info and see if there is anything strange like drivers or anything??

    Thanks
    -Matt
      My Computer


  9. Posts : 28,845
    Win 8 Release candidate 8400
       #9

    Zeldafan1993 said:
    zigzag3143 said:
    Zeldafan1993 said:
    Sorry for Double post

    is there any way to Find out what suspected problem is???
    OK so you have done all the things suggested in the 124 post?

    If so what version of BIOS did you update to?


    Old drivers needing update
    Code:
    Sahdad64.sys    10/27/2008 10:56:11 PM    fffff880`019f3000    fffff880`019fe000        0x0000b000    0x49068d5b                        
    Saibad64.sys    10/27/2008 10:56:15 PM    fffff880`019ea000    fffff880`019f3000        0x00009000    0x49068d5f                        
    SaibVdAd64.sys    10/27/2008 10:56:20 PM    fffff880`04acc000    fffff880`04ad6000        0x0000a000    0x49068d64                        
    spldr.sys    5/11/2009 11:56:27 AM    fffff880`019a8000    fffff880`019b0000        0x00008000    0x4a0858bb                        
    GEARAspiWDM.sys    5/18/2009 7:17:04 AM    fffff880`04c35000    fffff880`04c42000        0x0000d000    0x4a1151c0                        
    c2scsi64.sys    5/19/2009 4:07:19 PM    fffff880`0163a000    fffff880`01686000        0x0004c000    0x4a131f87                        
    cdrbsdrv.SYS    6/16/2009 10:37:33 PM    fffff880`04333000    fffff880`04341000        0x0000e000    0x4a3864fd
    How To Find Drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - - The most common drivers are listed on this page: Driver Reference Driver Reference
    - - Driver manufacturer links are on this page: Drivers and Downloads
    i have Bios version 1303 thats the Latest BIOS for my Motherboard (ASUS M4N78 PRO)

    as of 3 hours ago i reinstalled Windows 7 Ultimate x64 so would you like me to Re uploaded my Info and see if there is anything strange like drivers or anything??

    Thanks
    -Matt
    Matt

    Was that a clean install? Has the problem happened since?

    Clean installs are often the fastest way to get rid of a problem and get you going. Kudo's
      My Computer


  10. Posts : 176
    Windows 7 Ultimate x64
    Thread Starter
       #10

    zigzag3143 said:
    Zeldafan1993 said:
    zigzag3143 said:

    OK so you have done all the things suggested in the 124 post?

    If so what version of BIOS did you update to?


    Old drivers needing update
    Code:
    Sahdad64.sys    10/27/2008 10:56:11 PM    fffff880`019f3000    fffff880`019fe000        0x0000b000    0x49068d5b                        
    Saibad64.sys    10/27/2008 10:56:15 PM    fffff880`019ea000    fffff880`019f3000        0x00009000    0x49068d5f                        
    SaibVdAd64.sys    10/27/2008 10:56:20 PM    fffff880`04acc000    fffff880`04ad6000        0x0000a000    0x49068d64                        
    spldr.sys    5/11/2009 11:56:27 AM    fffff880`019a8000    fffff880`019b0000        0x00008000    0x4a0858bb                        
    GEARAspiWDM.sys    5/18/2009 7:17:04 AM    fffff880`04c35000    fffff880`04c42000        0x0000d000    0x4a1151c0                        
    c2scsi64.sys    5/19/2009 4:07:19 PM    fffff880`0163a000    fffff880`01686000        0x0004c000    0x4a131f87                        
    cdrbsdrv.SYS    6/16/2009 10:37:33 PM    fffff880`04333000    fffff880`04341000        0x0000e000    0x4a3864fd
    How To Find Drivers:- - The most common drivers are listed on this page: Driver Reference Driver Reference
    - - Driver manufacturer links are on this page: Drivers and Downloads
    i have Bios version 1303 thats the Latest BIOS for my Motherboard (ASUS M4N78 PRO)

    as of 3 hours ago i reinstalled Windows 7 Ultimate x64 so would you like me to Re uploaded my Info and see if there is anything strange like drivers or anything??

    Thanks
    -Matt
    Matt

    Was that a clean install? Has the problem happened since?

    Clean installs are often the fastest way to get rid of a problem and get you going. Kudo's
    Yup i delete the whole drive and installed Win7 back on again but there was no remains of the previous install

    and it was only about 3 hours ago and i haven't had the blue screen yet
      My Computer


 
Page 1 of 4 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:15.
Find Us