Windows 10: Reoccuring BSOD WHEA_Uncorrectable_Error (logs attached)

Discus and support Reoccuring BSOD WHEA_Uncorrectable_Error (logs attached) in Windows 10 BSOD Crashes and Debugging to solve the problem; DM Log: Attachment 114026 Minidump: Attachment 114027 BlueScreenView: Attachment 114028 Any help would be appreciated. Been happening... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by timchya, Dec 17, 2016.

  1. timchya Win User

    Reoccuring BSOD WHEA_Uncorrectable_Error (logs attached)


    DM Log: Attachment 114026
    Minidump: Attachment 114027
    BlueScreenView:
    Attachment 114028

    Any help would be appreciated. Been happening consistently for a few months now. Just updated to Windows 10 last night with an in-place upgrade and no change. Unfortunately, it looks like I lost the previous minidumps so all I have is the one from this morning at the moment.

    :)
     
    timchya, Dec 17, 2016
    #1

  2. DPC Watchdog BSOD- logs attached

    Hello,

    I just completed a new build based on Windows 7 with the Windows 10 upgrade. Everything went fine during the installation and updating phase, but all of a sudden last night I started getting unexplained DPC Watchdog BSODs. I tried to track down the root
    cause, but I am unsure of exactly how to read the errors in the memory dump files. I have already run one full pass of MemTest and it did not return any errors, so I am thinking this issue is driver-related, since so many new things were installed during the
    initial Windows install and subsequent Windows 10 upgrade. I am writing this on my laptop because every time I try to research the problem on the new desktop, it eventually crashes- maybe this is linked to an updated network driver? I have attached the last
    few dump files in an attempt to provide enough information to decode the info.

    Thanks in advance.

    -----------------------------------------------------------------------

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\MEMORY.DMP]

    Kernel Bitmap Dump File: Full address space is available

    Symbol search path is: *** Invalid ***

    ****************************************************************************

    * Symbol loading may be unreliable without a symbol search path. *

    * Use .symfix to have the debugger choose a symbol path. *

    * After setting your symbol path, use .reload to refresh symbol locations. *

    ****************************************************************************

    Executable search path is:

    *********************************************************************

    * Symbols can not be loaded because symbol path is not initialized. *

    * *

    * The Symbol Path can be set by: *

    * using the _NT_SYMBOL_PATH environment variable. *

    * using the -y <symbol_path> argument when starting the debugger. *

    * using .sympath and .sympath+ *

    *********************************************************************

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -

    Windows 8 Kernel Version 10240 MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 10240.16590.amd64fre.th1_st1.151104-1714

    Machine Name:

    Kernel base = 0xfffff802`7ee7c000 PsLoadedModuleList = 0xfffff802`7f1a1070

    Debug session time: Mon Nov 23 08:24:58.277 2015 (UTC - 6:00)

    System Uptime: 0 days 0:19:29.009

    *********************************************************************

    * Symbols can not be loaded because symbol path is not initialized. *

    * *

    * The Symbol Path can be set by: *

    * using the _NT_SYMBOL_PATH environment variable. *

    * using the -y <symbol_path> argument when starting the debugger. *

    * using .sympath and .sympath+ *

    *********************************************************************

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ........................................................

    Loading User Symbols

    .....

    *** ERROR: Module load completed but symbols could not be loaded for ntdll.dll

    Loading Wow64 Symbols

    ...............................................................

    ************* Symbol Loading Error Summary **************

    Module name Error

    ntkrnlmp The system cannot find the file specified

    ntdll The system cannot find the file specified

    You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.

    You should also verify that your symbol search path (.sympath) is correct.

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 133, {1, 1e00, 0, 0}

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll -

    *** ERROR: Module load completed but symbols could not be loaded for mwac.sys

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for NETIO.SYS -

    *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for fwpkclnt.sys -

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64cpu.dll -

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64.dll -

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files (such as the public OS symbols) do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: nt!_KPRCB ***

    *** ***

    *************************************************************************

    *************************************************************************

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files (such as the public OS symbols) do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: nt!_KPRCB ***

    *** ***

    *************************************************************************

    *************************************************************************

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files (such as the public OS symbols) do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: nt!_KPRCB ***

    *** ***

    *************************************************************************

    *********************************************************************

    * Symbols can not be loaded because symbol path is not initialized. *

    * *

    * The Symbol Path can be set by: *

    * using the _NT_SYMBOL_PATH environment variable. *

    * using the -y <symbol_path> argument when starting the debugger. *

    * using .sympath and .sympath+ *

    *********************************************************************

    Probably caused by : mwac.sys ( mwac+6f4c )

    Followup: MachineOwner

    ---------

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\MEMORY.DMP]

    Kernel Bitmap Dump File: Full address space is available

    Symbol search path is: *** Invalid ***

    ****************************************************************************

    * Symbol loading may be unreliable without a symbol search path. *

    * Use .symfix to have the debugger choose a symbol path. *

    * After setting your symbol path, use .reload to refresh symbol locations. *

    ****************************************************************************

    Executable search path is:

    *********************************************************************

    * Symbols can not be loaded because symbol path is not initialized. *

    * *

    * The Symbol Path can be set by: *

    * using the _NT_SYMBOL_PATH environment variable. *

    * using the -y <symbol_path> argument when starting the debugger. *

    * using .sympath and .sympath+ *

    *********************************************************************

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -

    Windows 8 Kernel Version 10240 MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 10240.16590.amd64fre.th1_st1.151104-1714

    Machine Name:

    Kernel base = 0xfffff803`06018000 PsLoadedModuleList = 0xfffff803`0633d070

    Debug session time: Mon Nov 23 08:36:51.409 2015 (UTC - 6:00)

    System Uptime: 0 days 0:10:53.140

    *********************************************************************

    * Symbols can not be loaded because symbol path is not initialized. *

    * *

    * The Symbol Path can be set by: *

    * using the _NT_SYMBOL_PATH environment variable. *

    * using the -y <symbol_path> argument when starting the debugger. *

    * using .sympath and .sympath+ *

    *********************************************************************

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ........................................................

    Loading User Symbols

    .....

    *** ERROR: Module load completed but symbols could not be loaded for ntdll.dll

    Loading Wow64 Symbols

    ...............................................................

    ************* Symbol Loading Error Summary **************

    Module name Error

    ntkrnlmp The system cannot find the file specified

    ntdll The system cannot find the file specified

    You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.

    You should also verify that your symbol search path (.sympath) is correct.

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 133, {1, 1e00, 0, 0}

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll -

    *** ERROR: Module load completed but symbols could not be loaded for mwac.sys

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for NETIO.SYS -

    *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for fwpkclnt.sys -

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64cpu.dll -

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for wow64.dll -

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files (such as the public OS symbols) do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: nt!_KPRCB ***

    *** ***

    *************************************************************************

    *************************************************************************

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files (such as the public OS symbols) do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: nt!_KPRCB ***

    *** ***

    *************************************************************************

    *************************************************************************

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files (such as the public OS symbols) do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: nt!_KPRCB ***

    *** ***

    *************************************************************************

    *********************************************************************

    * Symbols can not be loaded because symbol path is not initialized. *

    * *

    * The Symbol Path can be set by: *

    * using the _NT_SYMBOL_PATH environment variable. *

    * using the -y <symbol_path> argument when starting the debugger. *

    * using .sympath and .sympath+ *

    *********************************************************************

    Probably caused by : mwac.sys ( mwac+6f4c )

    Followup: MachineOwner

    ---------

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\Minidump\112315-7421-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***

    ****************************************************************************

    * Symbol loading may be unreliable without a symbol search path. *

    * Use .symfix to have the debugger choose a symbol path. *

    * After setting your symbol path, use .reload to refresh symbol locations. *

    ****************************************************************************

    Executable search path is:

    *********************************************************************

    * Symbols can not be loaded because symbol path is not initialized. *

    * *

    * The Symbol Path can be set by: *

    * using the _NT_SYMBOL_PATH environment variable. *

    * using the -y <symbol_path> argument when starting the debugger. *

    * using .sympath and .sympath+ *

    *********************************************************************

    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for ntoskrnl.exe

    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

    Windows 8 Kernel Version 10240 MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 10240.16590.amd64fre.th1_st1.151104-1714

    Machine Name:

    Kernel base = 0xfffff800`cbe83000 PsLoadedModuleList = 0xfffff800`cc1a8070

    Debug session time: Mon Nov 23 08:04:48.136 2015 (UTC - 6:00)

    System Uptime: 0 days 0:13:53.869

    *********************************************************************

    * Symbols can not be loaded because symbol path is not initialized. *

    * *

    * The Symbol Path can be set by: *

    * using the _NT_SYMBOL_PATH environment variable. *

    * using the -y <symbol_path> argument when starting the debugger. *

    * using .sympath and .sympath+ *

    *********************************************************************

    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for ntoskrnl.exe

    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    .........................................................

    Loading User Symbols

    ************* Symbol Loading Error Summary **************

    Module name Error

    ntoskrnl The system cannot find the file specified

    You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.

    You should also verify that your symbol search path (.sympath) is correct.

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 133, {1, 1e00, 0, 0}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files (such as the public OS symbols) do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: nt!_KPRCB ***

    *** ***

    *************************************************************************

    *************************************************************************

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files (such as the public OS symbols) do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: nt!_KPRCB ***

    *** ***

    *************************************************************************

    *************************************************************************

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files (such as the public OS symbols) do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: nt!_KPRCB ***

    *** ***

    *************************************************************************

    Probably caused by : ntoskrnl.exe ( nt+14f4d0 )

    Followup: MachineOwner
     
    PotatoMasher, Dec 17, 2016
    #2
  3. DPC Watchdog BSOD- logs attached

    Thanks for the reply. The computer was just built and it has an AMD 8320e on a MSI 970A-G46 motherboard. I have uploaded all of the files into a shared folder on OneDrive for review- all reports were obtained in normal mode.

    Error files:

    http://1drv.ms/1Tahhkc
     
    PotatoMasher, Dec 17, 2016
    #3
  4. lifetec Win User

    Reoccuring BSOD WHEA_Uncorrectable_Error (logs attached)

    Your still on the first release BIOS version 0416 from 2012 , update to the latest version 1505 from 2015.

    Update all drivers to latest windows 10 version from your supportpage Access Denied

    Older drivers:
    Intel manegement driver
    Realtek high definition audio driver
     
    lifetec, Dec 17, 2016
    #4
  5. timchya Win User
    Hey Lifetec, thanks I'll go through that today and let you know.
     
    timchya, Dec 17, 2016
    #5
  6. Spectrum Win User
    Have you overclocked your processor and/or changed voltages? Make sure everything is set to defaults in the BIOS after upgrading it per lifetec's recommendation.

    If you are still experiencing blue screens, I'd suggest running memtest86+ to see if any memory errors are found. If your memory passes, try keeping an eye on your hardware temperatures to see if heat is playing a role. I like using Open Hardware Monitor for monitoring temperatures.
     
    Spectrum, Dec 17, 2016
    #6
  7. timchya Win User
    Hi Lifetec, the BIOS update seems to have fixed it. Haven't had an issue in a few days, so fingers crossed! Thanks for your help!
     
    timchya, Apr 5, 2018
    #7
Thema:

Reoccuring BSOD WHEA_Uncorrectable_Error (logs attached)

Loading...
  1. Reoccuring BSOD WHEA_Uncorrectable_Error (logs attached) - Similar Threads - Reoccuring BSOD WHEA_Uncorrectable_Error

  2. Reoccurring BSOD Crashes

    in Windows 10 Drivers and Hardware
    Reoccurring BSOD Crashes: Hello, I've been having serious issues with BSOD crashes for the past week or so First I was getting something along the lines of Memory Management Error and then some of the ''coded'' errors like 0xc000007 don't remember the exact names of these errors. Those guys vanished...
  3. Bsod WHEA_UNCORRECTABLE_ERROR

    in Windows 10 BSOD Crashes and Debugging
    Bsod WHEA_UNCORRECTABLE_ERROR: I have spent a month trying out multiple things to fix this error, yet none of it has worked, from using Windows Memory Diagnostic to resetting my pc. I have some of the errors that happened recently here: https://1drv.ms/u/s!AozCYWxP6q71jSflW-syxiVQUW_0?e=ZMUnCX and some...
  4. Reoccuring BSOD

    in Windows 10 BSOD Crashes and Debugging
    Reoccuring BSOD: I've been getting random BSOD's when closing a few online games. I've checked, rechecked and tested all hardware. The only thing the BSOD shows for the stop code is REFERENCE_BY_POINTER The Event Viewer show's the following The computer has rebooted from a bugcheck. The...
  5. BSOD - WHEA_UNCORRECTABLE_ERROR

    in Windows 10 BSOD Crashes and Debugging
    BSOD - WHEA_UNCORRECTABLE_ERROR: As the title indicates I've been getting non-stop BSOD for months now and finally had the patience to do smthing about it but cant seem to fix it. I have done almost everything I can, I've done memtest86 but RAMS are not at fault, I tried different GPU but still get it, I...
  6. BSOD - driver verifier log attached

    in Windows 10 BSOD Crashes and Debugging
    BSOD - driver verifier log attached: Hi Guys, my PC is crashing and I found on forums, that I need to run driver verifier and attach dump file: https://drive.google.com/open?id=1vj3zBjLejIAF2vm9gn7xLsA0m6FhgPlL Can someone help? Crashes are random. Thanks...
  7. Bsod whea_uncorrectable_error

    in Windows 10 BSOD Crashes and Debugging
    Bsod whea_uncorrectable_error: Hello there! I need a bit help. This issue have bogging me for like a real period of time. I have try to fix it my self. But i cant solve it. Its getting frustrating now. BSOD appiers randomly like really randomly. If im doing something on computer or if im away from it and...
  8. Bsod: Whea_uncorrectable_error

    in Windows 10 BSOD Crashes and Debugging
    Bsod: Whea_uncorrectable_error: For the past month, I have been trying to diagonose the WHEA_UNCORRECTABLE_ERROR BSOD. The issue started occurring after I upgraded to Windows 10 build 1151. I had updates disabled for a while, and I believe that it is some kind of chipset driver and hardware issue....
  9. Bsod - whea_uncorrectable_error

    in Windows 10 BSOD Crashes and Debugging
    Bsod - whea_uncorrectable_error: Hello everyone. As stated in the title I am experiencing BSOD with the message "WHEA_UNCORRECTABLE_ERROR". The computer usually loads up to 100% and then restarts, but not always. Sometimes I will have to manually restart the computer. System Specs: i7-4790K Cooler...
  10. BSOD WHEA_Uncorrectable_Error

    in Windows 10 BSOD Crashes and Debugging
    BSOD WHEA_Uncorrectable_Error: Hello everyone, I've recently purchased a new SSD and upon receiving it decided to do a complete wipe of my system including resetting BIOS back to default. I have two SSD's installed in my system, with the OS installed onto the old ssd. This error has been happening...

Users found this page by searching for:

  1. WHEA is not fully initialized