BSOD WHEA_UNCORRECTABLE_ERROR GenuineIntel.sys

Question

BSOD WHEA_UNCORRECTABLE_ERROR GenuineIntel.sys

Anonymous

My computer is going to BSOD randomly. When this problem started occurring, I also stopped being able to hear any sound on the computer and it's saying, "an error saying no output audio device" and when I shut it down, it never turns off fully. It sounds like the fan might quiet down and the screen shuts down but the light on the front of the computer never goes off and the tower is still on. I do not play games on this computer or anything like that, it's just a run of the mill computer I bought from the store that I do work on. No mods or anything like that. Below are the windbg details. I ran the Intel Diagnostic tool and it passed. Hopefully I ran the error address check information correctly in Windbg; I pasted the output at the end of all the output of the debugger.

I tried to run !errpkt for ffff978983912028, but it gave me the error, "Unable to locate symbol for nt!WHEA_ERROR_PACKET."

Can you tell me what's wrong, please? Thank you,

Jen

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: 0000000000000000, Machine Check Exception

Arg2: ffff978983912028, Address of the nt!_WHEA_ERROR_RECORD structure.

Arg3: 00000000fe000000, High order 32-bits of the MCi_STATUS value.

Arg4: 0000000000801136, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 4671 

Key  : Analysis.Elapsed.mSec 

Value: 4905 

Key  : Analysis.IO.Other.Mb 

Value: 5 

Key  : Analysis.IO.Read.Mb 

Value: 0 

Key  : Analysis.IO.Write.Mb 

Value: 20 

Key  : Analysis.Init.CPU.mSec 

Value: 937 

Key  : Analysis.Init.Elapsed.mSec 

Value: 16210 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 89 

Key  : Analysis.Version.DbgEng 

Value: 10.0.27704.1001 

Key  : Analysis.Version.Description 

Value: 10.2408.27.01 amd64fre 

Key  : Analysis.Version.Ext 

Value: 1.2408.27.1 

Key  : Bugcheck.Code.KiBugCheckData 

Value: 0x124 

Key  : Bugcheck.Code.LegacyAPI 

Value: 0x124 

Key  : Bugcheck.Code.TargetModel 

Value: 0x124 

Key  : Failure.Bucket 

Value: 0x124\_0\_GenuineIntel\_PROCESSOR\_CACHE\_IMAGE\_GenuineIntel.sys 

Key  : Failure.Hash 

Value: {b70a049a-4a17-5749-b5df-df070316ca7d} 

Key  : Hypervisor.Enlightenments.Value 

Value: 0 

Key  : Hypervisor.Enlightenments.ValueHex 

Value: 0 

Key  : Hypervisor.Flags.AnyHypervisorPresent 

Value: 0 

Key  : Hypervisor.Flags.ApicEnlightened 

Value: 0 

Key  : Hypervisor.Flags.ApicVirtualizationAvailable 

Value: 0 

Key  : Hypervisor.Flags.AsyncMemoryHint 

Value: 0 

Key  : Hypervisor.Flags.CoreSchedulerRequested 

Value: 0 

Key  : Hypervisor.Flags.CpuManager 

Value: 0 

Key  : Hypervisor.Flags.DeprecateAutoEoi 

Value: 0 

Key  : Hypervisor.Flags.DynamicCpuDisabled 

Value: 0 

Key  : Hypervisor.Flags.Epf 

Value: 0 

Key  : Hypervisor.Flags.ExtendedProcessorMasks 

Value: 0 

Key  : Hypervisor.Flags.HardwareMbecAvailable 

Value: 1 

Key  : Hypervisor.Flags.MaxBankNumber 

Value: 0 

Key  : Hypervisor.Flags.MemoryZeroingControl 

Value: 0 

Key  : Hypervisor.Flags.NoExtendedRangeFlush 

Value: 0 

Key  : Hypervisor.Flags.NoNonArchCoreSharing 

Value: 0 

Key  : Hypervisor.Flags.Phase0InitDone 

Value: 0 

Key  : Hypervisor.Flags.PowerSchedulerQos 

Value: 0 

Key  : Hypervisor.Flags.RootScheduler 

Value: 0 

Key  : Hypervisor.Flags.SynicAvailable 

Value: 0 

Key  : Hypervisor.Flags.UseQpcBias 

Value: 0 

Key  : Hypervisor.Flags.Value 

Value: 131072 

Key  : Hypervisor.Flags.ValueHex 

Value: 20000 

Key  : Hypervisor.Flags.VpAssistPage 

Value: 0 

Key  : Hypervisor.Flags.VsmAvailable 

Value: 0 

Key  : Hypervisor.RootFlags.AccessStats 

Value: 0 

Key  : Hypervisor.RootFlags.CrashdumpEnlightened 

Value: 0 

Key  : Hypervisor.RootFlags.CreateVirtualProcessor 

Value: 0 

Key  : Hypervisor.RootFlags.DisableHyperthreading 

Value: 0 

Key  : Hypervisor.RootFlags.HostTimelineSync 

Value: 0 

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled 

Value: 0 

Key  : Hypervisor.RootFlags.IsHyperV 

Value: 0 

Key  : Hypervisor.RootFlags.LivedumpEnlightened 

Value: 0 

Key  : Hypervisor.RootFlags.MapDeviceInterrupt 

Value: 0 

Key  : Hypervisor.RootFlags.MceEnlightened 

Value: 0 

Key  : Hypervisor.RootFlags.Nested 

Value: 0 

Key  : Hypervisor.RootFlags.StartLogicalProcessor 

Value: 0 

Key  : Hypervisor.RootFlags.Value 

Value: 0 

Key  : Hypervisor.RootFlags.ValueHex 

Value: 0 

Key  : SecureKernel.HalpHvciEnabled 

Value: 0 

Key  : WER.OS.Branch 

Value: vb\_release 

Key  : WER.OS.Version 

Value: 10.0.19041.1

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff978983912028

BUGCHECK_P3: fe000000

BUGCHECK_P4: 801136

FILE_IN_CAB: MEMORY.DMP

FAULTING_THREAD: ffffaa01a63cb1c0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:

ffffaa01a655b8f8 fffff8074bcba21a : 0000000000000124 0000000000000000 ffff978983912028 00000000fe000000 : nt!KeBugCheckEx

ffffaa01a655b900 fffff80747fb15b0 : 0000000000000000 ffff978983912028 ffff97897eb9d750 ffff978983912028 : nt!HalBugCheckSystem+0xca

ffffaa01a655b940 fffff8074bdbc82d : 0000000000000000 ffffaa01a655b9d9 ffff978983912028 ffff97897eb9d750 : PSHED!PshedBugCheckSystem+0x10

ffffaa01a655b970 fffff8074bcbbb41 : ffff97897e8b8a80 ffff97897e8b8a80 ffff97897eb9d7a0 ffff97897eb9d750 : nt!WheaReportHwError+0x3dd

ffffaa01a655ba40 fffff8074bcbbeb3 : 0000000000000001 ffff97897eb9d7a0 ffff97897eb9d750 0000000000000001 : nt!HalpMcaReportError+0xb1

ffffaa01a655bbb0 fffff8074bcbbd90 : ffff97897e8f69c8 2907e77c00000001 0000000000000000 c967261cf8eb4504 : nt!HalpMceHandlerCore+0xef

ffffaa01a655bc00 fffff8074bcbbfe1 : 0000000000000006 0000000000000001 0000000000000000 65b8e9dff119c285 : nt!HalpMceHandler+0xe0

ffffaa01a655bc40 fffff8074bcbb24b : 0000000000000000 0000000000000000 ffffaa01a655bed0 d9b0e26e15dbfaa8 : nt!HalpMceHandlerWithRendezvous+0xc9

ffffaa01a655bc70 fffff8074bcbda95 : ffff97897e8f69c8 f160ca3e3d83d2f8 b1f8ca063d9bd2f0 b278cba63c1bdb60 : nt!HalpHandleMachineCheck+0x5f

ffffaa01a655bca0 fffff8074bd13919 : 52b3948218e10027 52339442182100a7 5a7b9c0a102108e7 5a778c46102508e3 : nt!HalHandleMcheck+0x35

ffffaa01a655bcd0 fffff8074bc0f57a : 1b542392121e7106 3b52239412087104 3b52239012587100 39922354129c71c0 : nt!KiHandleMcheck+0x9

ffffaa01a655bd00 fffff8074bc0f237 : 0000000000000000 fffff8074bc0f16c ffffaa01a63c0180 0000000000000000 : nt!KxMcheckAbort+0x7a

ffffaa01a655be40 fffff8074ba6a22b : 0000000000003c5a 0000000000000087 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277

ffff88014922f5f0 fffff8074ba691a4 : 0000000000000000 00001f8000000000 0000000000000000 0000000000000002 : nt!PpmIdleExecuteTransition+0xf0b

ffff88014922f9f0 fffff8074bc02dc4 : ffffffff00000000 ffffaa01a63cb1c0 ffff97898d3a8080 00000000000002ea : nt!PoIdle+0x374

ffff88014922fb60 0000000000000000 : ffff880149230000 ffff880149229000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x54

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .process /r /p 0xfffff8074c524a00; .thread 0xffffaa01a63cb1c0 ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR_CACHE_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b70a049a-4a17-5749-b5df-df070316ca7d}

Followup: MachineOwner

1: kd> !errrec ffff978983912028
===============================================================================
Common Platform Error Record @ ffff978983912028
-------------------------------------------------------------------------------
Record Id     : 01db1b79f988b929
Severity      : Fatal (1)
Length        : 936
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/11/2024 12:34:38 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Data Read
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000906ea
Processor ID  : 0x0000000000000002

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

Local APIC Id : 0x0000000000000002
CPU Id        : ea 06 09 00 00 08 10 02 - bf fb fa 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  @ ffff978983912280

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffff978983912138
Section       @ ffff9789839122c0
Offset        : 664
Length        : 272
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL2_DRD_ERR (Proc 1 Bank 11)
  Status      : 0xfe00000000801136
  Address     : 0x000000008b800000
  Misc.       : 0x00000430e4000086

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

7 answers

Answer 1

Anonymous

OK. I hope everything will go well.

0 comments

Answer 2

Yuhao, you're AMAZING! Thank you for taking the time and trouble to give me extra information about this problem. I was unable to try anything yesterday due to plans this weekend, but will be working on it more this week. I hope you're doing well today and I sincerely appreciate your quick reply. Have a blessed day,

Jen

Answer 3

Hello, Jen Autumn

But do you think that a CPU problem could be making my computer say, "No Audio Output Device is installed" and have caused the sound to go out?

It’s not just a guess that the issue is related to the Intel CPU. The debug records you provided specifically indicate MODULE_NAME: GenuineIntel and IMAGE_NAME: GenuineIntel.sys, which point directly to the Intel CPU drivers.

The CPU (Central Processing Unit) is the brain of your computer, responsible for executing instructions and managing communication between different hardware components. When the CPU encounters an error, such as the DCACHEL2_DRD_ERR (which indicates an issue with the L2 cache), it can cause a ripple effect throughout the system. Here’s how it can affect the audio:

Interrupt Handling: The CPU handles interrupts, which are signals from hardware components like the audio device. If the CPU is malfunctioning, it might not process these interrupts correctly, leading to issues like “No Audio Output Device is installed.”
Resource Allocation: The CPU allocates resources to various components. If it’s experiencing errors, it might fail to allocate resources properly to the audio device, causing it to malfunction.
System Instability: A faulty CPU can cause overall system instability, which can manifest in various ways, including audio problems. The audio drivers might not load correctly, or the audio hardware might not be initialized properly during startup.
Data Corruption: Errors in the CPU’s cache can lead to data corruption, which can affect the drivers and software responsible for managing audio output.

The fact that the BSOD occurs only on startup and then the system runs normally could indicate an intermittent hardware issue or a problem that manifests under specific conditions during boot.

Professional hardware diagnostics I mentioned are advanced diagnostic tools used by technicians to thoroughly test hardware components. You don’t necessarily need to buy one; you can take your computer to a professional repair service where they have these tools.

Yuhao L

Microsoft Community Technical Support

Answer 4

Ok, thank you, I will try the things you mentioned. But do you think that a CPU problem could be making my computer say, "No Audio Output Device is installed" and have caused the sound to go out? I started getting the BSOD on the same day that the audio went out. Also, I received the Error: DCACHEL2_DRD_ERR (Proc 1 Bank 11) when debugging, which does not make it seem like an audio problem but an L2 cache problem? It only does the BSOD upon startup. Then after it BSODs one time, it will let me get on the computer and work normally for the rest of the day. Did you see this error code and can you comment on that? So I will try all these things you mentioned, but wondered if you could make an educated guess with the additional information I provided about the error address, the time that I get the BSOD and the audio going out, in addition to the intel information that the whea error gave. Also, what is a professional hardware diagnostics? Do I have to buy that? Can you recommend one, please? I will write back after I've done the steps you mentioned. Thank you for your time and have a blessed day.

Jen

Answer 5

Hello, Jen Autumn

Welcome to Microsoft Community.

I’m sorry to hear about the issues you’re experiencing with your computer. The WHEA_UNCORRECTABLE_ERROR (124) typically indicates a hardware problem, often related to the CPU, memory, or other critical components. The MODULE_NAME: GenuineIntel and IMAGE_NAME: GenuineIntel.sys indicate that the issue is related to your Intel CPU. Here are a few additional steps you can take:

Update Intel Drivers: Visit the Intel Driver & Support Assistant to ensure all your Intel drivers are up to date.
Run Windows Memory Diagnostic: Press Win + R, type mdsched.exe, and follow the prompts to check for memory issues.
Check Event Viewer: Open Event Viewer (Win + X > Event Viewer) and look for any critical errors around the time of the BSOD. This might give more clues about what’s causing the issue.
Disable Overclocking: If your CPU is overclocked, revert it to its default settings in the BIOS.
Test with Minimal Hardware: Disconnect all non-essential hardware (USB devices, additional drives) and see if the issue persists. This can help identify if a peripheral is causing the problem.
Check for BIOS Updates: Sometimes, a BIOS update can resolve hardware compatibility issues. Check your motherboard manufacturer’s website for any available updates.

If these steps don’t resolve the issue, it might be worth considering a professional hardware diagnostic.

Yuhao L

Microsoft Community Technical Support

Share via

BSOD WHEA_UNCORRECTABLE_ERROR GenuineIntel.sys

7 answers