[SOLVED] WHEA_UNCORRECTABLE_ERROR most probably caused by genuine intel sys

[LLY700]

Hi everyone. Just got a BSOD while gaming. Please help me find what caused the error and what could i do to fix it. Here's the bugcheck:


Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\georg\Desktop\031221-9906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8024ce00000 PsLoadedModuleList = 0xfffff8024da2a490
Debug session time: Fri Mar 12 23:05:48.343 2021 (UTC + 2:00)
System Uptime: 1 days 10:22:07.814
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
2: kd> !analyze -v
***

• *
• 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
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffce82121ac028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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

fffff8024da0f330: Unable to get Flags value from nt!KdVersionBlock
fffff8024da0f330: Unable to get Flags value from nt!KdVersionBlock
*
* *
* *
* 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 *
* *
*
fffff8024da0f330: Unable to get Flags value from nt!KdVersionBlock
*
* *
* *
* 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.Sec
Value: 5

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-CAUECJ8

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 33

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffce82121ac028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: FIFA21.exe

STACK_TEXT:
ffffa380d3f798e8 fffff8024d2b3a6a : 0000000000000124 0000000000000000 ffffce82121ac028 00000000be000000 : nt!KeBugCheckEx
ffffa380d3f798f0 fffff8024a1b15b0 : 0000000000000000 ffffce82121ac028 ffffce8209bdcc90 ffffce82121ac028 : nt!HalBugCheckSystem+0xca
ffffa380d3f79930 fffff8024d3b55fe : 0000000000000000 ffffa380d3f799d9 ffffce82121ac028 ffffce8209bdcc90 : PSHED!PshedBugCheckSystem+0x10
ffffa380d3f79960 fffff8024d2b5391 : ffffce821203e4c0 ffffce821203e4c0 ffffce8209bdcce0 ffffce8209bdcc90 : nt!WheaReportHwError+0x46e
ffffa380d3f79a40 fffff8024d2b5703 : 0000000000000002 ffffce8209bdcce0 ffffce8209bdcc90 0000000000000002 : nt!HalpMcaReportError+0xb1
ffffa380d3f79bb0 fffff8024d2b55e0 : ffffce8209af8660 0001a8c400000001 0000000000000000 ccccc35d5b5e5f5c : nt!HalpMceHandlerCore+0xef
ffffa380d3f79c00 fffff8024d2b5831 : 0000000000000008 0000000000000001 0000000000000000 41bf75894cfe8b45 : nt!HalpMceHandler+0xe0
ffffa380d3f79c40 fffff8024d2b4a9b : 0000000000000000 0000000000000000 ffffa380d3f79ed0 c98548cb758944df : nt!HalpMceHandlerWithRendezvous+0xc9
ffffa380d3f79c70 fffff8024d2b72e5 : ffffce8209af8660 000b9a840fc08548 30894d2839836600 0538bf0a74318945 : nt!HalpHandleMachineCheck+0x5f
ffffa380d3f79ca0 fffff8024d30ca29 : 000002bd41ffaaa5 b70ffd03490beb00 c085ffaaa51ae80f cd75223f8366f175 : nt!HalHandleMcheck+0x35
ffffa380d3f79cd0 fffff8024d204cfa : 491574c985661a74 72c63b01468ddd03 0216bfe1ebf08b04 22f983667aeb0000 : nt!KiHandleMcheck+0x9
ffffa380d3f79d00 fffff8024d2049b7 : ffffa38000000000 fffff8024d2048ec 0000000100000036 0000000000000000 : nt!KxMcheckAbort+0x7a
ffffa380d3f79e40 fffff8024d0de1af : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
ffffdf81bb1bf9c8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiUpdateStibpPairing+0x28f


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR__UNKNOWN

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {86f02343-3a24-6d22-b341-ad6c04114faf}

 

[Colif]

WHEA errors never tell me anything, but we can see if the next one - if you get another - shows us.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

Open Windows File Explorer
Navigate to C:\Windows\Minidump
Copy the mini-dump files out onto your Desktop
Do not use Winzip, use the built in facility in Windows
Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
Then post a link here to the zip file, so we can take a look for you . . .

What are specs of the PC?

 

[LLY700]

WHEA errors never tell me anything, but we can see if the next one - if you get another - shows us.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

Open Windows File Explorer
Navigate to C:\Windows\Minidump
Copy the mini-dump files out onto your Desktop
Do not use Winzip, use the built in facility in Windows
Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
Then post a link here to the zip file, so we can take a look for you . . .

What are specs of the PC?

thanks for replying. it's a lenovo legion y7000 laptop (i5 9300h, gtx 1650 4gb ddr5). i tried to do a bit of research on my own after the bsod happened, and from what i understood, it's probably a hardware issue. it also might've been caused by the fact that i've been undervolting the laptop (- 0.140 with turbo boost disabled) to lower the temperatures while gaming. however, it would be weirdif that was the case since i've been using the exact undervolting configuration for almost a year and never had a single bsod happening.

https://www.dropbox.com/s/22lc02ba6dxfc5s/031221-9906-01.dmp?dl=0 - dump file

 

[Colif]

not sure about the udervolt, i will get back to you on that.

I will ask a friend to convert the dumps, he is asleep now.

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://jsfiddle.net/x0fnmow3/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	031221-9906-01.dmp (Mar 12 2021 - 16:05:48)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	memory_corruption (Process: FIFA21.exe)
Uptime:	1 Day(s), 10 Hour(s), 22 Min(s), and 07 Sec(s)

BIOS info was not included in the dump file. This can sometimes mean an outdated BIOS is being used.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

not sure about the undervolted, i will get back to you on that.

Answer
Absolutely, because the memory controller is IN the CPU. Reductions to various CPU related voltages can have a direct, or an indirect, effect on memory performance. That's why changes to things like VCCSA and VCCIO, which are not specifically "dram voltage" can help to stabilize an unstable memory configuration.

Even changes to core voltage might have an effect. We know for sure that historically we've seen many years worth of configurations where running memory speeds above a certain frequency required a CPU overclock (And it's accompanying increase in core voltage) in order to be stable or even POST in some cases, especially when very high speed memory OR four DIMMs were in use.

none of the drivers are the kind that would obviously cause WHEA errors, no overclocking software, lingers on throttlestop …

try running this on CPU - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

 

[LLY700]

Answer
Absolutely, because the memory controller is IN the CPU. Reductions to various CPU related voltages can have a direct, or an indirect, effect on memory performance. That's why changes to things like VCCSA and VCCIO, which are not specifically "dram voltage" can help to stabilize an unstable memory configuration.

Even changes to core voltage might have an effect. We know for sure that historically we've seen many years worth of configurations where running memory speeds above a certain frequency required a CPU overclock (And it's accompanying increase in core voltage) in order to be stable or even POST in some cases, especially when very high speed memory OR four DIMMs were in use.

none of the drivers are the kind that would obviously cause WHEA errors, no overclocking software, lingers on throttlestop …

try running this on CPU - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

i ran the intel diagnostic tool and it appears that there are no problems. i also did a prime 95 stress test (smallest fft) for an hour (i wanted to run it longer but my cpu stayed constantly in low 90 C and i did not feel comfortable letting it like that for a longer period), did not encounter any crashes or bsod.

 

[Colif]

All we know for sure is its likely hardware

we don't know what yet, we can guess all we like. Need to test things to cross them off list.

CPU - passes 2 CPU tests
Ram - Prime checks ram as well, but I don't know how many tests it run
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.
Memtest is created as a bootable USB so that you don’t need windows to run it

GPU - just run benchmarks, I don't need results, just seeing if it crashes. Don't run both at once
https://geeks3d.com/furmark/

https://benchmark.unigine.com/heaven

what else is in there? what storage drives?
I don't see many laptops so can't really test PSU or MB.

 

[LLY700]

checked ram with windows memory diagnostic and memtest86 : everything seemed fine

checked gpu with furmark and unigine heaven : not a single problem

checked storage (i have a 512 gb ssd) with hdd sentinel - health was at 100%

so yea, everything seems fine.

All we know for sure is its likely hardware

we don't know what yet, we can guess all we like. Need to test things to cross them off list.

CPU - passes 2 CPU tests
Ram - Prime checks ram as well, but I don't know how many tests it run
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.
Memtest is created as a bootable USB so that you don’t need windows to run it

GPU - just run benchmarks, I don't need results, just seeing if it crashes. Don't run both at once
https://geeks3d.com/furmark/

https://benchmark.unigine.com/heaven

what else is in there? what storage drives?
I don't see many laptops so can't really test PSU or MB.

 

[Colif]

there is a bios update, it could help. make sure your model one of those listed - https://pcsupport.lenovo.com/au/en/...ownloads/driver-list/component?name=BIOS/UEFI

try running the automatic driver update on their website too, it might help as well

 

[LLY700]

i got the bios update three or four days ago through the lenovo vantage utility. same thing with drivers, everything is up to date

so yea, no idea what to do next. i did not get another bsod, so the dump i posted here is the only one i got. i guess the most probable culprit would be the undervolt (already disabled throttlestop).

 

[Colif]

no other BSOD? NO random restarts? No sign of trouble?

lets just wait and see if it happens again, BSOD aren't predictable.

 

[LLY700]

nothing. only got one bsod, no random restarts or any other things to note.

i still have a year warranty left, so if anything bad happens, i know what to do. it's just frustrating that i can't pinpoint what's wrong.

 

[Colif]

wait and see. Just use PC as normal and assume its not going to happen... saying this may jinx you but it would happen anyway.

it might have been fixed by bios update. its not like you haven't tried.

Its impossible to tell if BSOD are fixed until they stop, that is only real way to know unless driver waves a flag and shows its name and we replace/remove it.

its too soon.

 

[LLY700]

ok. thanks a lot for helping me out, i'll be back if i encounter another bsod or any other problem.