Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Blue Screen and "WHEA_UNCORRECTABLE_ERROR"


  • Please log in to reply
8 replies to this topic

#1 amineg

amineg

  • Members
  • 4 posts
  • OFFLINE
  •  

Posted 02 January 2018 - 05:25 PM

Hello everyone,

 

I have sometimes a bluescreen with this error "WHEA_UNCORRECTABLE_ERROR"

 

Do you know what is it exactly please?

 

A report with WhoCrashed:

 

Welcome to WhoCrashed (HOME EDITION) v 6.00

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...

 

Home Edition Notice

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
 

System Information (local)

Computer name: DESKTOP-AMINE
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., X99-E
CPU: GenuineIntel Intel® Core™ i7-6800K CPU @ 3.40GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 34266378240 bytes total


 

Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Tue 02/01/2018 23:04:57 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010218-13546-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x124 (0x0, 0xFFFFC00AAAB54028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys WHEA_UNCORRECTABLE_ERROR



On Tue 02/01/2018 23:04:57 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x124 (0x0, 0xFFFFC00AAAB54028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys WHEA_UNCORRECTABLE_ERROR



 

Conclusion

2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nt_wrong_symbols.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


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 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.


Thanks in advance for your help!
 



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,951 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:11:58 AM

Posted 02 January 2018 - 05:30 PM

We need more information about your system than what you've provided. Hence, please follow these BSOD posting instructions and attach the requested files by replying to this topic. You may skip the part of step three where it instructs you to create a new topic, since you already have a topic here. There's no need to create another topic. :wink:

Thank you.

Regards,
bwv848


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 amineg

amineg
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  

Posted 02 January 2018 - 05:46 PM

Thanks for your quick answer:

 

Here is a snapshot of my specs: http://speccy.piriform.com/results/O77AzbAt8aIBsFAWDnB3Xnb

 

And the zip attached.

 

Thanks

Attached Files



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,951 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:11:58 AM

Posted 02 January 2018 - 06:25 PM

There was only one dump file in the SFCA output. Has this been your only BSOD? Did it occur during RealFlow?

As you mentioned it's a STOP 0x124.

9: kd> !analyze -show 124 0 ffffc00aaab54028 be000000 800400
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffc00aaab54028, Address of the WHEA_ERROR_RECORD structure.
Arg3: ffffffffbe000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Dumping the WHEA error record we obtain

9: kd> !errrec ffffc00aaab54028
===============================================================================
Common Platform Error Record @ ffffc00aaab54028
-------------------------------------------------------------------------------
Record Id     : 01d37e7607c784b0
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 1/2/2018 22:04:57 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffc00aaab540a8
Section       @ ffffc00aaab54180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000406f1
Processor ID  : 0x0000000000000009

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffc00aaab540f0
Section       @ ffffc00aaab54240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000009
CPU Id        : f1 06 04 00 00 08 10 09 - bf fb fe 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffffc00aaab54240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffc00aaab54138
Section       @ ffffc00aaab542c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 9 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0xfffff802d916a212
  Misc.       : 0xfffff802d916a212

which is to say that there has been an internal timer error on processor nine.

Unfortunately there isn't much to conclude from one dump file. What's strange is that there were a few Live Kernel Events before the crash as recorded in WER.

02/01/2018 22:10    Windows Error Reporting    Récipient d’erreurs , type 0
Nom d’événement : LiveKernelEvent
Réponse : Non disponible
ID de CAB : 0

Signature du problème : 
P1 : 1a1
P2 : ffffba09d965e700
P3 : 0
P4 : 0
P5 : 0
P6 : 10_0_16299
P7 : 0_0
P8 : 768_1
P9 : 
P10 : 

Fichiers joints :
\\?\C:\WINDOWS\LiveKernelReports\PoW32kWatchdog\PoW32kWatchdog-20171223-1400.dmp
\\?\C:\WINDOWS\TEMP\WER-17343-0.sysdata.xml
\\?\C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20171223-1400.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50B0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50BF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50D0.tmp.txt

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a1_9911479fc7a76a59b756e662e9cf1f3d797315cf_00000000_cab_1868513c

Symbole d’analyse : 
Nouvelle recherche de la solution : 0
ID de rapport : 3fa5310b-d48e-40ca-98e8-3b11ecca2ca3
Statut du rapport : 2049
Récipient avec hachage :
02/01/2018 22:10    Windows Error Reporting    Récipient d’erreurs , type 0
Nom d’événement : LiveKernelEvent
Réponse : Non disponible
ID de CAB : 0

Signature du problème : 
P1 : 1a1
P2 : ffffba09d965e700
P3 : 0
P4 : 0
P5 : 0
P6 : 10_0_16299
P7 : 0_0
P8 : 768_1
P9 : 
P10 : 

Fichiers joints :
\\?\C:\WINDOWS\LiveKernelReports\PoW32kWatchdog\PoW32kWatchdog-20171223-1400.dmp
\\?\C:\WINDOWS\TEMP\WER-17343-0.sysdata.xml
\\?\C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20171223-1400.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50B0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50BF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50D0.tmp.txt

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a1_9911479fc7a76a59b756e662e9cf1f3d797315cf_00000000_038850cf

Symbole d’analyse : 
Nouvelle recherche de la solution : 0
ID de rapport : 3fa5310b-d48e-40ca-98e8-3b11ecca2ca3
Statut du rapport : 4
Récipient avec hachage :

Live Kernel Events are nearly 100% related to graphics cards and their drivers, and it is quite interesting two popped up right before the crash.

I've double-checked the compatibility of your CPU and ensured that you're not overclocking. Can you try to update your BIOS to the latest version — you seem to be a little behind. Apart from that, I would suggest you run these hardware diagnostics www.carrona.org/hwdiag.html You must run MemTest86 for eight passes, SeaTools for all drives, and Prime95's blend test to stress the CPU and RAM. I would also suggest that you use one the temperature monitoring programs listed on the same webpage.

 

How old is this PC?


Edited by bwv848, 02 January 2018 - 06:26 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#5 amineg

amineg
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  

Posted 02 January 2018 - 07:03 PM

Thanks for this review.

 

Yes it's the only BSOD that I have when a bluescreen appear.

 

I have it when I'm working for few hours and usually when I'm on Cinema 4D and sometimes it used 100% of the memory when I look the task manager. I will try to update my BIOS and test all the things you mentioned and will tell you what's going on.

 

It's a custom config I did 6 months ago now.

 

Thank you very much



#6 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,951 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:11:58 AM

Posted 02 January 2018 - 11:43 PM

You're welcome. :) If this the first BSOD you've experienced, I would quite honestly ignore it for the time being. Engineering simulation programs are very strenuous on hardware, and it isn't a surprise that you got a BSOD. How many hours were you running RealFlow during the time of the crash? It could just be that the CPU got too hot after hours of computation.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#7 amineg

amineg
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  

Posted 03 January 2018 - 04:48 AM

It's really not the first time in fact 

 

I have a second problem beside the bluescreen, sometimes I can't boot the computer the first time, I have to put off the PSU and press the on/off button during 10sec to "reset" and then I can start the computer. I will make these hardaware diagnostic today.

 

And about Realflow, I don't use it so much, I use only 90% of the time c4d alone with a render engine like Arnold with IPR (CPU) and for 5/6 hours per day.


Edited by amineg, 03 January 2018 - 04:48 AM.


#8 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,951 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:11:58 AM

Posted 03 January 2018 - 10:34 AM

:thumbup2:


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#9 GraceHudson642pS

GraceHudson642pS

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:11:58 PM

Posted 07 March 2018 - 04:21 PM

if you did overclock your CPU you need to reset bios to default. then 
Much better to run a windows defender anti-virus makes sure it is fully updated the virus definition. to detect newer malware that is running in the background of your computer, some viruses will run background that consumes a lot of processes of the CPU might your CPU will fry itself...
i found the Solution 4. Run Anti-virus on this website that actually works for me.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users