hardware failure, missing WinDbg symbols

coleio · Jun 9, 2023

Used pc, Ryzen 5 5600X, 32gb ddr4 3200mhz, RTX 3060 Ti.
PC crashes with WHEA_UNRECOVERABLE_ERROR during times of intense computation (games, mostly).
I threw the dumps created into WinDbg, but I can't get the symbols to work when I run !errrec, even after stating microsoft's symbols online as a search path and reloading.

Code:

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************

So, instead, can somebody reply with the !errrrec they get (assuming you have the symbols)
An interpretation of the results of that !errrec would also be appreciated
Here are two of the dump files on pastebin. Not sure how to attach them on this forum, sorry. Each are two hours apart, experienced while playing games for a short time
first dump
second dump

x BlueRobot · Jun 9, 2023

All not symbols are available on the public symbol server so I wouldn't worry about those symbol warnings. Please also follow these posting instructions: Blue Screen of Death (BSOD) Posting Instructions - Windows 11, 10, 8.1 and 8

coleio · Jun 9, 2023

Here's the zip file.
Thank you for your help.

x BlueRobot · Jun 9, 2023

Thanks, it looks like all of the WHEA error records have been corrupted. As you already know, the issue is going to be due to some form of hardware failure, while troubleshooting, please ensure that you aren't overclocking any components and your BIOS settings have been set to their factory defaults.

Let's begin with your testing your RAM with MemTest86, please ensure that you run it for 8 passes (2 sets of 4 passes): Test RAM with PassMark MemTest86 (version 7.4 was used)

coleio · Jun 9, 2023

x BlueRobot said:
Thanks, it looks like all of the WHEA error records have been corrupted. As you already know, the issue is going to be due to some form of hardware failure, while troubleshooting, please ensure that you aren't overclocking any components and your BIOS settings have been set to their factory defaults.

Let's begin with your testing your RAM with MemTest86, please ensure that you run it for 8 passes (2 sets of 4 passes): Test RAM with PassMark MemTest86 (version 7.4 was used)

No overclocking at all, just got this system yesterday (but it IS refurbished). Fresh installation of Windows too, and I've reset my BIOS to factory defaults twice. Running MemTest86 now

x BlueRobot · Jun 9, 2023

Okay, once you've completed 8 passes, then please let me know. If it shows any errors then you know either one of the RAM sticks is bad or possibly one of the motherboard DIMM slots.

coleio · Jun 9, 2023

x BlueRobot said:
Okay, once you've completed 8 passes, then please let me know. If it shows any errors then you know either one of the RAM sticks is bad or possibly one of the motherboard DIMM slots.

Memtest86 isn't booting. I've tried all the steps listed in the article to the best extent. Here are my boot options:

The BIOS is empty of any other applicable features like CSM. When running imageUSB, I used all default settings: I only selected the USB and pressed Write.

coleio · Jun 9, 2023

…nevermind. After 5 attempts without changing any BIOS settings, Memtest86 has run (completely arbitrarily).

coleio · Jun 9, 2023

x BlueRobot said:
Okay, once you've completed 8 passes, then please let me know. If it shows any errors then you know either one of the RAM sticks is bad or possibly one of the motherboard DIMM slots.

Seems like something cut the first pass short during test #6. Here's the file that it produced, and these are the last logs it wrote:

Code:

2023-06-09 12:52:24 - Running test #6 (Test 6 [Block move, 64-byte blocks])
2023-06-09 12:52:24 - MtSupportRunAllTests - Setting random seed to 0x50415353
2023-06-09 12:52:24 - MtSupportRunAllTests - Start time: 288616 ms
2023-06-09 12:52:24 - MtSupportRunAllTests - Enabling memory cache for test
2023-06-09 12:52:24 - MtSupportRunAllTests - Enabling memory cache complete
2023-06-09 12:52:24 - Start memory range test (0x0 - 0x840000000)
2023-06-09 12:52:38 - Get_AMD_19_CurTmp: AMD Ryzen 5 5600X 6-Core Processor              - NB_SMN_INDEX_0=0x00059800 NB_SMN_DATA_0=0x7CFB0000
2023-06-09 12:52:38 - Get_AMD_19_CurTmp: Setting NB_SMN_INDEX_0 to 0x00059800
2023-06-09 12:52:38 - Get_AMD_19_CurTmp: NB_SMN_DATA_0=0x7CFB0000
2023-06-09 12:52:38 - Get_AMD_19_CurTmp: 0x7CFB0000, 999 (RANGE_SEL=1)
2023-06-09 12:52:38 - Get_AMD_19_CurTmp: usingBlanketOffset 75
2023-06-09 12:52:38 - Get_AMD_19_CurTmp: iTrueTmp 75
2023-06-09 12:52:38 - Current CPU temperature: 75C

ubuysa · Jun 10, 2023

Did you not get an HTML report from Memtes86? They typically have names like MemTest86-Report-20221014-182622.html.

In your system log there are a very large number of WHEA errors logged, all for a machine check exception, but for two different reasons...

Rich (BB code):

Event[25]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-06-09T10:56:47.6790000Z
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-BTMV79F
  Description:
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Bus/Interconnect Error
Processor APIC ID: 11

The details view of this entry contains further information.

And...

Rich (BB code):

Event[389]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-06-08T21:56:03.3440000Z
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-BTMV79F
  Description:
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 7

The details view of this entry contains further information.

These could be RAM or CPU related - which is why getting a full 8 iterations of Memtest86 are important.

I see that your RAM is clocked at 2133MHz but I think I'm correct in thinking your RAM is capable of 3600MHZ? I do know that AMD CPUs prefer fast RAM.

Subject to @x BlueRobot agreeing (he is far more experienced than I), I would be tempted to run all three tests in Prime 95 (small FFTs, large FFTs, and Blend). This will stress your CPU and RAM and should reveal whether there are any weaknesses in either.[/code][/code]

x BlueRobot · Jun 10, 2023

It would be probably best if we could get a full set of 8 passes beforehand but it does seem that your CPU temperature was pretty high: it reached 78C at one point. Have ensured that the thermal paste has been applied correctly to the CPU and there is adequate cooling in the case?

Search

Search

hardware failure, missing WinDbg symbols

coleio

Member

x BlueRobot

Administrator

coleio

Member

Attachments

x BlueRobot

Administrator

coleio

Member

x BlueRobot

Administrator

coleio

Member

coleio

Member

coleio

Member

Attachments

ubuysa

Sysnative Staff
BSOD Kernel Dump Senior Analyst
Contributor

x BlueRobot

Administrator

hardware failure, missing WinDbg symbols

Member

Administrator

Member

Attachments

Administrator

Member

Administrator

Member

Member

Member

Attachments

Sysnative Staff BSOD Kernel Dump Senior AnalystContributor

Administrator

Sysnative Staff
BSOD Kernel Dump Senior Analyst
Contributor