none
WHEA_UNCORRECTABLE_ERROR BSOD Crashes

    Question

  • Testing Windows 7 x64 running a machine with the following specs:

    CPU: E6750
    Motherboard: Gigabyte GA-P35-DS4
    Memory: 4 x 1GB Corsair TWIN2X2048-6400C4
    Video Card: Nvidia 9800 GTX
    Power Supply: Corsair HX-520
    Case: Antec P180

    I'm getting regular (every hour or so) BSOD crashes with the following details:

    This was likely caused by the following module: hardware
    Bugcheck code: 0x124 (0x0, 0xFFFFFA80047BE038, 0xB2000040, 0x800)
    Error: WHEA_UNCORRECTABLE_ERROR


    I run Vista x64 with a 100% stable system that I've extensively stress tested so I know there is no 'real' hardware issue.

    Am I correct in assuming this is a driver issue? If so, is there any way I can isolate the driver?
    Thursday, January 15, 2009 10:21 AM

Answers

  • For the benefit of other people encountering this issue, I resolved this by updating from the NVIDIA drivers installed automatically by Windows 7 Update to the 181.20 drivers currently available. While on the NVIDIA site it says they are only for Vista x64, when installed the Windows 7 logo is shown in the installation screen and I didn't have to run in Vista compatibility mode.

    While I thought that Windows 7 was introducing a system where all drivers came through Windows Update, this clearly isn't the case yet so go hunting for the latest yourself, don't wait for them to come to you. :)
    Sunday, January 18, 2009 6:51 AM

All replies

  • i dont know if this will have any bearing as the error your getting might be win 7 specific, but try checking through this

    http://msdn.microsoft.com/en-us/library/bb725851.aspx
    Thursday, January 15, 2009 10:39 AM
  • Thanks. I'd already found this site but coudln't really glean any more out of it. Is there a way to trace the problematic driver some other way?
    Friday, January 16, 2009 5:20 AM
  • Hi there,

    Make sure that your Windows is setup to make a minidump under Windows Error Reporting in the Advanced System Settings.

    When your computer reboots, download the Windows Debugging Tools and follow the instructions here:


    http://support.microsoft.com/kb/315263


    Please post the output from the Tools after you have analysed the minidump.

    Henry
    [CPU] - Intel Core 2 Quad Q9300 @ 2.50 GHz, 1333 MHz FSB [MOBO] - Gigabyte EP35-DS4 F2 [RAM] - 2 x 2GB (4GB) Transcend DDR2 SDRAM 800MHz [GPU] - Galaxy Geforce 9800GTX [SFX1] - Realtek High Definition Audio (ALC889A) [SFX2] - ASUS XONAR D2 (USB2.0) [HDD1] - 500GB Western Digital 7200RPM / Partition 1 - WinXP Pro SP2 32-bit (Clean install) / Partition 2 - Win7 Beta (Build 7000) 64-bit (Clean install) [HDD2] - 120GB Western Digital 7200RPM [LCD] - 17" Samsung Syncmaster 240N [HID1] - Microsoft Habu (2,000 DPI) [HID2] - Logitech LX 710 Laser Mouse (1,100 DPI) [KBD] - Logitech Wireless Desktop LX 710 Keyboard [MIC] - ASUS Array Microphone
    Friday, January 16, 2009 5:42 AM
  • Hi Henry, thanks for taking an interest. Here is the analysis of the crash dump log:

    WHEA_ERROR_RECORD: !errrec fffffa800491a038
    BUGCHECK_STR:  0x124_GenuineIntel
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    CURRENT_IRQL:  0

    STACK_TEXT: 
    fffff880`0b496898 fffff800`02ff3063 : 00000000`00000124 00000000`00000000 fffffa80`0491a038 00000000`b2000040 : nt!KeBugCheckEx
    fffff880`0b4968a0 fffff800`02b8e2c3 : 00000000`00000001 fffffa80`048fa4d0 00000000`00000000 fffffa80`048fa520 : hal!HalBugCheckSystem+0x1e3
    fffff880`0b4968e0 fffff800`02ff2d28 : 00000000`00000728 fffffa80`048fa4d0 fffff880`0b496c70 fffff880`0b496c00 : nt!WheaReportHwError+0x263
    fffff880`0b496940 fffff800`02ff26af : fffffa80`048fa4d0 00000000`00000000 fffffa80`048fa4d0 fffff880`0b496c70 : hal!HalpMcaReportError+0x4c
    fffff880`0b496a90 fffff800`02ff2578 : 00000000`00000002 00000000`00000001 fffff880`0b496cf0 00000000`00000000 : hal!HalpMceHandler+0x90
    fffff880`0b496ad0 fffff800`02fe6d50 : 00000000`fe0b2ced fffff880`0b48c180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`0b496b00 fffff800`02a9c1ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`0b496b30 fffff800`02a9c053 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`0b496c70 fffff800`02aaccce : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`06932a10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x23e

    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: hardware
    IMAGE_NAME:  hardware
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel
    BUCKET_ID:  X64_0x124_GenuineIntel
    Followup: MachineOwner


    Any insights?
    Friday, January 16, 2009 10:18 AM
  • For the benefit of other people encountering this issue, I resolved this by updating from the NVIDIA drivers installed automatically by Windows 7 Update to the 181.20 drivers currently available. While on the NVIDIA site it says they are only for Vista x64, when installed the Windows 7 logo is shown in the installation screen and I didn't have to run in Vista compatibility mode.

    While I thought that Windows 7 was introducing a system where all drivers came through Windows Update, this clearly isn't the case yet so go hunting for the latest yourself, don't wait for them to come to you. :)
    Sunday, January 18, 2009 6:51 AM
  • Hi,

     

    If you run into this particular BSOD again, I wrote a post that details some debugging steps,

    http://mikemstech.blogspot.com/2010/07/windbgkd-debugging-processor-cache.html


    -- Mike Burr
    Technology
    Saturday, December 3, 2011 10:03 PM