[SOLVED] Whea uncorrectable error on startup "sometimes"

[mono343]

I recently build a new computer with a mixture of new parts and old parts from a different computer and have been getting this "whea uncorrectable error" sometimes. It used to be all the time until I replaced the power cable with a new one( No Idea why that worked). Now it's a coin flip, sometime it would give "whea uncorrectable error", sometimes the computer turns on but the screen would remain black forever and other times it boots up normally.

When the computer boots up normally, there are no errors or anything. It plays games smoothly. I ran a Userbenchmark test and it gave good results. I ran a "windows memory diagnostic" test and there were no issues.

I did do a backup to an external hard drive which included the program file and program file 86x folders and replace those folders when bringing back the old files. Keep in mind I was going from an intel CPU to an AMD CPU so not sure if that could be affecting something.

Here is is my list of my computers parts

Case: P101 Silent Antec (new part)
Motherboard: GIGABYTE X670E AORUS Master (new part)
CPU:Ryzen 7 7700x (new part)
2 x 8 GB DDR5 RAM (new part)
GPU: 3080 ti (old part)
2 SSD and 1 Hard drive (old parts)
Power supply 750w (new part)

Any ideas on what to check next or software test to run.

 

[Hecticon]

[SOLVED] - WHEA Uncorrectable Error, Clock Watchdog Timeout, and about four more BSODs ?

I keep getting whea uncorrectable errors, clock watchdogtimeouts and I've also got like four other errors. whea uncontrollable error is by far the most common though. I've just done a clean windows install and I still get them. They happen with a sort of pattern, like when I boot the computer...

forums.tomshardware.com

 

[Hecticon]

I recently build a new computer with a mixture of new parts and old parts from a different computer and have been getting this "whea uncorrectable error" sometimes. It used to be all the time until I replaced the power cable with a new one( No Idea why that worked). Now it's a coin flip, sometime it would give "whea uncorrectable error", sometimes the computer turns on but the screen would remain black forever and other times it boots up normally.

When the computer boots up normally, there are no errors or anything. It plays games smoothly. I ran a Userbenchmark test and it gave good results. I ran a "windows memory diagnostic" test and there were no issues.

I did do a backup to an external hard drive which included the program file and program file 86x folders and replace those folders when bringing back the old files. Keep in mind I was going from an intel CPU to an AMD CPU so not sure if that could be affecting something.

Here is is my list of my computers parts

Case: P101 Silent Antec (new part)
Motherboard: GIGABYTE X670E AORUS Master (new part)
CPU:Ryzen 7 7700x (new part)
2 x 8 GB DDR5 RAM (new part)
GPU: 3080 ti (old part)
2 SSD and 1 Hard drive (old parts)
Power supply 750w (new part)

Any ideas on what to check next or software test to run.

I know its for a game but try this out and see if it works.
That error has been coming up for the new Ryzen 7 series CPUs

 

[mono343]

I know its for a game but try this out and see if it works.
That error has been coming up for the new Ryzen 7 series CPUs

Well I check out the mindump file all I got was this:

***

• *
• Bugcheck Analysis *
• *

***

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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000001, Corrected Machine Check
Arg2: ffffa3019f5cc208, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000086ced535
Arg4: 000000003c800f9e

Debugging Details:
------------------

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3421

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 49754

Key : Analysis.IO.Other.Mb
Value: 21

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 31

Key : Analysis.Init.CPU.mSec
Value: 343

Key : Analysis.Init.Elapsed.mSec
Value: 57568

Key : Analysis.Memory.CommitPeak.Mb
Value: 96

Key : Bugcheck.Code.DumpHeader
Value: 0x124

Key : Bugcheck.Code.KiBugCheckData
Value: 0x124

Key : Bugcheck.Code.Register
Value: 0x124

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: 011523-10593-01.dmp

BUGCHECK_CODE: 124

BUGCHECK_P1: 1

BUGCHECK_P2: ffffa3019f5cc208

BUGCHECK_P3: 86ced535

BUGCHECK_P4: 3c800f9e

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff808fa703ee28 fffff8042beb697a : 0000000000000124 0000000000000001 ffffa3019f5cc208 0000000086ced535 : nt!KeBugCheckEx
ffff808fa703ee30 fffff804284815b0 : 0000000000000000 ffffa3019f5cc208 ffffa30185f6ea40 ffffa3019f5cc208 : nt!HalBugCheckSystem+0xca
ffff808fa703ee70 fffff8042bfb8b9e : 0000000000000000 ffff808fa703ef19 ffffa3019f5cc208 ffffa30185f6ea40 : PSHED!PshedBugCheckSystem+0x10
ffff808fa703eea0 fffff8042beb82a1 : ffffa3018da56900 ffffa3018da56900 ffffa30185f6ea90 ffffa30185f6ea40 : nt!WheaReportHwError+0x46e
ffff808fa703ef80 fffff8042be9ff8b : 0000000000000002 0000000000000001 ffffb9007d71c100 0000000000000002 : nt!HalpMcaReportError+0xb1
ffff808fa703f0f0 fffff8042bd9ffd2 : 0000000000000002 ffff808fa703f2e0 ffff808fa703f4b0 0000000000000e48 : nt!HalpCmcPollProcessor+0xfff9b
ffff808fa703f180 fffff8042bd8ceb6 : ffffb9007d71f240 000021c2e9fd4101 ffffb9007d71c180 0000000000000004 : nt!HalpCmciPollProcessor+0x46
ffff808fa703f1b0 fffff8042bc3d10e : ffffb9007d71f240 ffffa301870db000 ffff808fa703f2e0 ffffb90000000002 : nt!HalpCmciDeferredRoutine+0x16
ffff808fa703f1e0 fffff8042bc3c3f4 : 0000000000000000 0000000000000000 0000000000140001 0000000000000000 : nt!KiExecuteAllDpcs+0x30e
ffff808fa703f350 fffff8042bdfeace : ffffffff00000000 ffffb9007d71c180 ffffb9007d727440 ffffa3019812f040 : nt!KiRetireDpcList+0x1f4
ffff808fa703f5e0 0000000000000000 : ffff808fa7040000 ffff808fa7039000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e


MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_1_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7cf2a33e-22ba-d47f-d16c-25ce0c4027d7}

Followup: MachineOwner


So no idea what that means. I check out CrystalDiskInfo and it said all the drives were "good" and the 61% cpu thing isn't exaclty the solution what I'm looking for.

 

[Bob.B]

I recently build a new computer with a mixture of new parts and old parts from a different computer and have been getting this "whea uncorrectable error" sometimes. It used to be all the time until I replaced the power cable with a new one( No Idea why that worked). Now it's a coin flip, sometime it would give "whea uncorrectable error", sometimes the computer turns on but the screen would remain black forever and other times it boots up normally.

When the computer boots up normally, there are no errors or anything. It plays games smoothly. I ran a Userbenchmark test and it gave good results. I ran a "windows memory diagnostic" test and there were no issues.

I did do a backup to an external hard drive which included the program file and program file 86x folders and replace those folders when bringing back the old files. Keep in mind I was going from an intel CPU to an AMD CPU so not sure if that could be affecting something.

Here is is my list of my computers parts

Case: P101 Silent Antec (new part)
Motherboard: GIGABYTE X670E AORUS Master (new part)
CPU:Ryzen 7 7700x (new part)
2 x 8 GB DDR5 RAM (new part)
GPU: 3080 ti (old part)
2 SSD and 1 Hard drive (old parts)
Power supply 750w (new part)

Any ideas on what to check next or software test to run.

Did you do a clean windows install after the new build?

 

[mono343]

Did you do a clean windows install after the new build?

Yea I formatted one of the ssd and clean installed window 10 on it.

 

[Bob.B]

Yea I formatted one of the ssd and clean installed window 10 on it.

Did you then get the proper bios and mobo drivers?

 

[mono343]

Did you then get the proper bios and mobo drivers?

Well I check and there was an update for the bois so I download and manage to install it. So far out of the three boot ups, two of them booted up noramlly. Second time was a black screen but I did turn off the computer then turn it back on right away so Im going to chalk that up to the computer needs a couple of minutes before turning back on again.

So I'll give it a week before solving this thread in case the "whea" error appears again.