Re: IS THIS A FAULTY PROCESSOR? WHEA_UNCORRECTABLE_ERROR (124) PROCESSOR: INTEL PENTIUM D 920 D 2.80 GHZ NORMALLY CRASHES TOWARDS THE END OF A DEFENDE...

PPatt3 · ‎11-29-2019

MACHINE ORIGINALLY XP - NOW WIN 10 PRO - USING WIN XP CHIPSET DRIVERS?

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

Arg2: 9201f024, Address of the WHEA_ERROR_RECORD structure.

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

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

Debugging Details:

------------------

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec

Value: 11

Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on WIN10PC

Key : Analysis.DebugData

Value: CreateObject

Key : Analysis.DebugModel

Value: CreateObject

Key : Analysis.Elapsed.Sec

Value: 14

Key : Analysis.Memory.CommitPeak.Mb

Value: 55

Key : Analysis.System

Value: CreateObject

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffffff9201f024

BUGCHECK_P3: ffffffffb2000000

BUGCHECK_P4: 1040080f

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: MsMpEng.exe

BAD_STACK_POINTER: 8883c074

STACK_TEXT:

8883c070 81249c70 00000124 00000000 9201f024 nt!KeBugCheckEx

8883c0a0 814f7b46 8921d620 9201f144 873f5960 hal!HalBugCheckSystem+0x6d

8883c124 8124b23e 873f5910 00000000 873f5910 nt!WheaReportHwError+0x319

8883c248 8124b4be 00000001 00000000 00001388 hal!HalpMcaReportError+0x53

8883c270 8124b3d9 00000001 00000000 00000002 hal!HalpMceHandlerCore+0xcf

8883c298 8124b5b1 88880000 00000000 00000000 hal!HalpMceHandler+0x52

8883c2b0 8124ad3c 00000000 00000000 00000000 hal!HalpMceHandlerWithRendezvous+0xb3

8883c2c0 8124bb81 88880000 8883c3f0 00000000 hal!HalpHandleMachineCheck+0x3f

8883c3e4 813f9965 00000000 0f0f0f0f 0f0f0f0f hal!HalpMcaExceptionHandler+0x8f

8883c3e4 69d1b2cb 00000000 0f0f0f0f 0f0f0f0f nt!KiMcaExceptionHandlerWrapper+0x2d5

WARNING: Frame IP not in any known module. Following frames may be wrong.

0339c880 00000000 00000000 00000000 00000000 0x69d1b2cb

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS_LG_SRC_ERR_*_NOTIMEOUT_STACKPTR_ERROR

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x86

OSNAME: Windows 10

FAILURE_ID_HASH: {b67df69e-a1ab-d4a0-edea-83bbe929dc64}

Followup: MachineOwner

---------

WARNING: Process directory table base 7D8609C0 doesn't match CR3 001A8000

1: kd> !errrec 9201f024

===============================================================================

Common Platform Error Record @ 9201f024

-------------------------------------------------------------------------------

Record Id : 01d57911bed8e4af

Severity : Fatal (1)

Length : 936

Creator : Microsoft

Notify Type : Machine Check Exception

Timestamp : 10/2/2019 18:22:36 (UTC)

Flags : 0x00000000

===============================================================================

Section 0 : Processor Generic

-------------------------------------------------------------------------------

Descriptor @ 9201f0a4

Section @ 9201f17c

Offset : 344

Length : 192

Flags : 0x00000001 Primary

Severity : Fatal

Proc. Type : x86/x64

Instr. Set : x86

Error Type : BUS error

Operation : Generic

Flags : 0x00

Level : 3

CPU Version : 0x0000000000000f62

Processor ID : 0x0000000000000001

===============================================================================

Section 1 : x86/x64 Processor Specific

-------------------------------------------------------------------------------

Descriptor @ 9201f0ec

Section @ 9201f23c

Offset : 536

Length : 128

Flags : 0x00000000

Severity : Fatal

Local APIC Id : 0x0000000000000001

CPU Id : 62 0f 00 00 00 08 02 01 - 3d e4 00 00 ff fb eb bf

00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0 @ 9201f23c

===============================================================================

Section 2 : x86/x64 MCA

-------------------------------------------------------------------------------

Descriptor @ 9201f134

Section @ 9201f2bc

Offset : 664

Length : 272

Flags : 0x00000000

Severity : Fatal

Error : BUSLG_SRC_ERR_*_NOTIMEOUT_ERR (Proc 1 Bank 0)

Status : 0xb20000001040080f

AlHill · ‎11-29-2019

First, do not be afraid to release the CAPS LOCK.

Second, your processor is not supported on Windows 10.

https://www.intel.com/content/www/us/en/support/articles/000006105/processors.html

Third, your processor is from 2006 - 13 years ago:

https://ark.intel.com/content/www/us/en/ark/products/27516/intel-pentium-d-processor-920-4m-cache-2-80-ghz-800-mhz-fsb.html

Doc

n_scott_pearson · ‎11-29-2019

To answer your question, a WHEA Uncorrectable Error does not necessarily mean a problem with the processor. It can (also) occur because of failures on the motherboard or in the memory DIMMs or in a device driver.

As Doc has pointed out, this could be caused by down-rev drivers. You should never upgrade from Windows XP to Windows 10, even if you did come via Windows 7; you should always install from scratch.

...S

PPatt3 · ‎11-29-2019

Thanks for your reply, I had the same problem under windows 7 Pro BSOD 0x124

I performed a clean install of windows 10 to troubleshoot this problem.

Is there anything else I can do to identify what is causing this problem.?

I've replaced the TIM on processor.

Mainly only happens on security scans or prolonged disk access?

Is the bus error on the processor or in between the processor and disk or memory.

All Disk \ memory \ graphics card \ file scans - sfc /scannow ok?

I installed the original win xp chipset drivers is that ok?

Thanks

n_scott_pearson · ‎11-30-2019

You may also be seeing an overheating issue, either in the CPU or in the PCH (chipset) component. Run AIDA64 or HWiNFO64 or some similar tool that can display the CPU and PCH temperatures and watch what happens as you do these activities. I am not sure if a failure occurring in the PCH's SATA controllers (as a result of overheating or otherwise) can result in a WHEA Uncorrectable Error, but it is a possibility.

...S

IS THIS A FAULTY PROCESSOR? WHEA_UNCORRECTABLE_ERROR (124) PROCESSOR: INTEL PENTIUM D 920 D 2.80 GHZ NORMALLY CRASHES TOWARDS THE END OF A DEFENDER ANTI-VIRUS SECURITY SCAN