Windows 8 and 8.1 Forums


BSOD WHEA_UNCORRECTABLE_ERROR - Random intervals.

  1. #21


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Quote Originally Posted by Gumble316 View Post
    Hi Again,

    Just had a new BSOD Following a freeze which is new... MACHINE_CHECK_EXCEPTION

    Have uploaded all the bits again.

    Kind Regards
    Please check this **LINK**.

    It appears that the the BIOS updates are only available for the Windows 8 and not Windows 8.1. Your BIOS dates back to 2012 and the update of 2014 is only available for Windows 8 dunno why -_-

    Also, update your chipset drivers from the link.

    Let me know how it goes ^_^

      My System SpecsSystem Spec

  2. #22


    Posts : 25
    Win 8.1


    Hi Blueelvis,

    Seems my BIOS is as up to date as it can be as I get this message when installing:

    Attachment 51157

    Update: Updated the chipset then had another freeze but this one came with an WHEA_UNCORRECTABLE_ERROR BSOD
      My System SpecsSystem Spec

  3. #23


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Gumble ^_^,

    Apparently, this was pulled out from your latest ZIP file-
    Code:
    BIOS Version:              Phoenix Technologies Ltd. 5FCN95WW, 25/12/2012
    I have asked a friend of mine to look into this. Let us wait till he says
      My System SpecsSystem Spec

  4. #24


    Posts : 25
    Win 8.1


    Quote Originally Posted by blueelvis View Post
    Hi Gumble ^_^,

    Apparently, this was pulled out from your latest ZIP file-
    Code:
    BIOS Version:              Phoenix Technologies Ltd. 5FCN95WW, 25/12/2012
    I have asked a friend of mine to look into this. Let us wait till he says
    Legend, thanks once again
      My System SpecsSystem Spec

  5. #25


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Quote Originally Posted by Gumble316

    Legend, thanks once again
    The friend has asked for a Complete Memory Dump file. The complete Dump file is located at "C:\Windows\Memory.dmp" . It would be a large file so please make sure that you ZIP it up before uploading to a file hoster like OneDrive or Mediafire.

    Let me know how it goes ^_^.
      My System SpecsSystem Spec

  6. #26


    Posts : 25
    Win 8.1


    Hi,

    OK, think this is what you need
    MEMORY
      My System SpecsSystem Spec

  7. #27


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Gumble316 ^_^,

    Thanks for following the instructions closely and uploading the required file. This reveals the culprit. Below is the stack information obtained from the Dump File :-
    Code:
    0: kd> k
    Child-SP          RetAddr           Call Site
    fffff803`394fca38 fffff803`3783f213 nt!KeBugCheckEx
    fffff803`394fca40 fffff803`37a37f71 hal!HalBugCheckSystem+0xcf
    fffff803`394fca80 fffff803`3783f6a0 nt!WheaReportHwError+0x22d
    fffff803`394fcae0 fffff803`3783fa0d hal!HalpMcaReportError+0x50
    fffff803`394fcc30 fffff803`3783f8f8 hal!HalpMceHandlerCore+0xe1
    fffff803`394fcc80 fffff803`3783fb42 hal!HalpMceHandler+0xe4
    fffff803`394fccc0 fffff803`3783fccf hal!HalpMceHandlerWithRendezvous+0xce
    fffff803`394fccf0 fffff803`379d67bb hal!HalHandleMcheck+0x40
    fffff803`394fcd20 fffff803`379d6571 nt!KxMcheckAbort+0x7b
    fffff803`394fce60 fffff800`4d53e318 nt!KiMcheckAbort+0x171
    fffff803`394e8690 fffff800`4d53e171 athw8x!readPlatformRegOnce+0xa8
    fffff803`394e86e0 fffff800`4d4f7aec athw8x!ath_hal_reg_read+0x25
    fffff803`394e8730 fffff800`4d56454d athw8x!ar9300_get_11n_ext_busy+0x5c
    fffff803`394e8790 fffff800`4d5e5c5f athw8x!ath_printreg+0x399
    fffff803`394e87c0 fffff800`4d5e46ff athw8x!ath_cwm_get_extchbusyper+0x27
    fffff803`394e87f0 fffff800`4d5e4576 athw8x!cwm_stop+0x7a7
    fffff803`394e8830 fffff800`4d5761e5 athw8x!cwm_stop+0x61e
    fffff803`394e8890 fffff800`4d6dd6f3 athw8x!ath_led_suspend_stop+0x109d
    fffff803`394e88d0 fffff800`4bc95f76 athw8x!ndis_timer_handler+0x283
    fffff803`394e8960 fffff803`378ba760 ndis!ndisMTimerObjectDpc+0xc6
    fffff803`394e89b0 fffff803`379cf7ea nt!KiRetireDpcList+0x4f0
    fffff803`394e8c60 00000000`00000000 nt!KiIdleLoop+0x5a
    So, do you see the red highlighted driver? It is the "athw8x.sys" which is the Qualcomm Atheros Wireless LAN Driver. This is the first time that I have seen that a WHEA Bugcheck being caused by a driver. I was told that it can also be done by a low level driver like Disk, Processor etc but this was the first time in front of me. So, Thanks for providing the dump!

    Now, if we check the date of the driver :-
    Code:
    0: kd> lmvm athw8x
    start             end                 module name
    fffff800`4d47c000 fffff800`4d805000   athw8x     (pdb symbols)          c:\symbols\athw8x.pdb\E6244F77554F462D8314845F508649BB1\athw8x.pdb
        Loaded symbol image file: athw8x.sys
        Image path: \SystemRoot\system32\DRIVERS\athw8x.sys
        Image name: athw8x.sys
        Timestamp:        Thu Jan 17 14:45:39 2013 (50F7C13B)
        CheckSum:         00386204
        ImageSize:        00389000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    2013 drivers of Qualcomm Atheros installed by the Windows 8.1 (Most likely) almost always cause BSOD's. Happened with my machine and some other machines as well which I saw.

    Please download and install the latest drivers from this **LINK** and then install them. You would need to install them manually as I don't think there would be an executable file. Don't worry about the site, it is trusted.

    Let me know how it goes ^_^.


    EDIT :- I forgot to mention that since the QUALCOMM Atheros Driver is calling a WHEA or Machine Check Exception, there is a possibility that the Network Card is dying. But, before that let us make sure that the outdated driver is not causing it ^_^.
    Last edited by blueelvis; 21 Sep 2014 at 10:57. Reason: Added more info.
      My System SpecsSystem Spec

  8. #28


    Posts : 25
    Win 8.1


    Quote Originally Posted by blueelvis View Post
    Hi Gumble316 ^_^,

    Thanks for following the instructions closely and uploading the required file. This reveals the culprit. Below is the stack information obtained from the Dump File :-
    Code:
    0: kd> k
    Child-SP          RetAddr           Call Site
    fffff803`394fca38 fffff803`3783f213 nt!KeBugCheckEx
    fffff803`394fca40 fffff803`37a37f71 hal!HalBugCheckSystem+0xcf
    fffff803`394fca80 fffff803`3783f6a0 nt!WheaReportHwError+0x22d
    fffff803`394fcae0 fffff803`3783fa0d hal!HalpMcaReportError+0x50
    fffff803`394fcc30 fffff803`3783f8f8 hal!HalpMceHandlerCore+0xe1
    fffff803`394fcc80 fffff803`3783fb42 hal!HalpMceHandler+0xe4
    fffff803`394fccc0 fffff803`3783fccf hal!HalpMceHandlerWithRendezvous+0xce
    fffff803`394fccf0 fffff803`379d67bb hal!HalHandleMcheck+0x40
    fffff803`394fcd20 fffff803`379d6571 nt!KxMcheckAbort+0x7b
    fffff803`394fce60 fffff800`4d53e318 nt!KiMcheckAbort+0x171
    fffff803`394e8690 fffff800`4d53e171 athw8x!readPlatformRegOnce+0xa8
    fffff803`394e86e0 fffff800`4d4f7aec athw8x!ath_hal_reg_read+0x25
    fffff803`394e8730 fffff800`4d56454d athw8x!ar9300_get_11n_ext_busy+0x5c
    fffff803`394e8790 fffff800`4d5e5c5f athw8x!ath_printreg+0x399
    fffff803`394e87c0 fffff800`4d5e46ff athw8x!ath_cwm_get_extchbusyper+0x27
    fffff803`394e87f0 fffff800`4d5e4576 athw8x!cwm_stop+0x7a7
    fffff803`394e8830 fffff800`4d5761e5 athw8x!cwm_stop+0x61e
    fffff803`394e8890 fffff800`4d6dd6f3 athw8x!ath_led_suspend_stop+0x109d
    fffff803`394e88d0 fffff800`4bc95f76 athw8x!ndis_timer_handler+0x283
    fffff803`394e8960 fffff803`378ba760 ndis!ndisMTimerObjectDpc+0xc6
    fffff803`394e89b0 fffff803`379cf7ea nt!KiRetireDpcList+0x4f0
    fffff803`394e8c60 00000000`00000000 nt!KiIdleLoop+0x5a
    So, do you see the red highlighted driver? It is the "athw8x.sys" which is the Qualcomm Atheros Wireless LAN Driver. This is the first time that I have seen that a WHEA Bugcheck being caused by a driver. I was told that it can also be done by a low level driver like Disk, Processor etc but this was the first time in front of me. So, Thanks for providing the dump!

    Now, if we check the date of the driver :-
    Code:
    0: kd> lmvm athw8x
    start             end                 module name
    fffff800`4d47c000 fffff800`4d805000   athw8x     (pdb symbols)          c:\symbols\athw8x.pdb\E6244F77554F462D8314845F508649BB1\athw8x.pdb
        Loaded symbol image file: athw8x.sys
        Image path: \SystemRoot\system32\DRIVERS\athw8x.sys
        Image name: athw8x.sys
        Timestamp:        Thu Jan 17 14:45:39 2013 (50F7C13B)
        CheckSum:         00386204
        ImageSize:        00389000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    2013 drivers of Qualcomm Atheros installed by the Windows 8.1 (Most likely) almost always cause BSOD's. Happened with my machine and some other machines as well which I saw.

    Please download and install the latest drivers from this **LINK** and then install them. You would need to install them manually as I don't think there would be an executable file. Don't worry about the site, it is trusted.

    Let me know how it goes ^_^.


    EDIT :- I forgot to mention that since the QUALCOMM Atheros Driver is calling a WHEA or Machine Check Exception, there is a possibility that the Network Card is dying. But, before that let us make sure that the outdated driver is not causing it ^_^.
    Hi Again, Ok, forgive my ignorance, I have downloaded the latest drivers, how do I install them?

    Kind Regards

    Garry
      My System SpecsSystem Spec

  9. #29


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Go here - Download and install drivers - Windows Help

    Click on the - "Installing Drivers Yourself"


    Let me know how it goes ^_^
      My System SpecsSystem Spec

  10. #30


    Posts : 25
    Win 8.1


    Quote Originally Posted by blueelvis View Post
    Go here - Download and install drivers - Windows Help

    Click on the - "Installing Drivers Yourself"


    Let me know how it goes ^_^
    Many Thanks, Updated them,will get you posted
      My System SpecsSystem Spec

Page 3 of 4 FirstFirst 1234 LastLast
BSOD WHEA_UNCORRECTABLE_ERROR - Random intervals.
Related Threads
Hi guys, First of all, this is my first post on here so I apologize if I am not 100% on the etiquette of posting questions. The story goes; Bought an Acer V3-772G a couple of weeks ago and got quite a few BSoD's straight off the bat, so I did a factory reset hoping it would solve the problem,...
This has been going on for a very long while and now it is becoming extremely frustrating as from what I can see the Bug Check String is almost different at various occasions and also I cannot seem to reproduce the BSOD and cannot work out a regular pattern. This is happening on Windows 8.1 fully...
BSOD at random intervals in BSOD Crashes and Debugging
52865 I tried to get all the files however I noticed there was some errors when issuing commands such as tasklist (I was running as administrator) The crashes have occurred ever since I built this computer, been re-installed several times (windows 8/8.1) and has a new GPU as to what it used to...
I'm getting random BSOD's, with WHEA_UNCORRECTABLE_ERROR. Here is the SF Diag. Tool output Attahed). Would love to get some ideas about what can be done. Cheers!
Random BSOD, WHEA_UNCORRECTABLE_ERROR in BSOD Crashes and Debugging
Hello, I've been getting a random WHEA_UNCORRECTABLE_ERROR BSOD, sometimes while idle other times while gaming or just browsing reddit. I ran SF diagnostic tool and attached the file to this post. Thanks for your help.
Solved Random BSOD - WHEA_UNCORRECTABLE_ERROR in BSOD Crashes and Debugging
Hi, I was using a Windows 7 Professional (64 bit) for some time on my Lenovo E531 laptop and it was just fine - no crashes, no problems. I made an upgrade to Windows 8.1 Pro 64bit in the beginning of December and I am getting random BSOD crashes with WHEA_UNCORRECTABLE_ERROR message. When I mean...
BSOD happening at random intervals in BSOD Crashes and Debugging
Just got my new computer set up. Have installed everything myself, and everything seamed to work perfectly in the beginning. After a while(same day) I started to get BSOD at random intervals. I don't know where the problem is, but I have been using Prime95 to stress-test the computer....
Eight Forums Android App Eight Forums IOS App Follow us on Facebook