Processors
Intel® Processors, Tools, and Utilities
14395 Discussions

WHEA 124 Error: E5-1650 v4

idata
Employee
3,025 Views

Intel Web support was updating my account recently, and apparently my original question thread got deleted somehow. (At least I can no longer find it here).

I'll try to recreate it here.

I've gotten three WHEA 124 machine check errors in the last 2 months from my Windows 7 64-Bit Xeon system. This has 64 GB or ECC ram, and an M.2 SSD drive in an Asus X99-E WS/USB 3.1 motherboard.

So far, this seems to happen occasionally when trying to put the system to S3 suspend to RAM sleep. This normally works fine. But, when I have a problem it appears that the monitor goes blank, and the system doesn't ever get to the sleep part (where the power light blinks on and off). Instead, the power light stays on solid and I need to hit the reset button.

When it comes back up, I see 6 Event log errors about WHEA 124 problems. They call out an 'Internal Timer error' for processors 0, 2, 4, 6, 8, and 10. I also see three 'cache coherency' errors. A minidump was produced, and calls out an 'Internal timer error' for 'processor 0, Bank 3'.

I have attached some of the extracted WHEA events from the event viewer, and some results from the minidump.

The system is well cooled, passes the 'Intel Processor diagnostic tool' test, has the latest 3502 BIOS, isn't overclocked, and is using the latest drivers provided by Asus for this motherboard.

I will add another append with the answer I last got from an Intel Support representative.

Thanks;

-Greg

0 Kudos
9 Replies
idata
Employee
1,317 Views

Here is the last question I got from Intel:

/?et=watches.email.thread Intel Communities WHEA 124 errors E5-1650 v4 created by Intel Corporation in Processors - /message/478566# 478566 View the full discussion

I understand, it was a suggestion since if this were related to the processor it should be happening often.

If you are concern this is related to your processor let's check the health of it by running the Intel® Processor Diagnostic Tool: https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool Download Intel® Processor Diagnostic Tool. Run it and once done attach your report.

To attach a file, you must click "Use Advanced Editor" in the top right corner of the response box, then the "attach" option will appear in the bottom right corner of the response box.

Regards,

Amy C.

0 Kudos
idata
Employee
1,317 Views

I ran the Intel Diagnostic Tool again and it passed. Here are the results.

0 Kudos
idata
Employee
1,317 Views

Hello mysteryguy,

 

 

Thank you for contacting Intel Communities.

 

 

I am sorry to hear you are having issues with your system.

 

 

Can you please provide the following information to better assist you?
  • Memory (RAM) Frequency: (as seen in the BIOS)
  • Have you tested different sticks of RAM?
  • Have you tested the processor in a different board?
I hope to hear from you soon.

 

 

Best Regards,

 

Juan V.
0 Kudos
idata
Employee
1,317 Views

*) Memory Frequency (in BIOS and elsewhere) is DDR4-2400, which is the rated speed of the memory.

*) I have not tested other memory DIMMs. But, I have run 4 passes of Passmark's 'Memtest86 Pro'

memory test program without any errors being detected.

*) I do not have other boards to test with.

I guess I was wondering what the meanings of 'Internal Timer error' and 'cache coherency error' actually are.

0 Kudos
idata
Employee
1,317 Views

Hi mysteryguy,

 

 

These are Windows error codes, you can refer to https://social.technet.microsoft.com/Forums/windows/en-US/825f7883-8668-4e15-9eee-853da4fd9025/system-locks-and-restarts-whealogger-event-id-18?forum=w7itproperf this thread (1st response) from Microsoft for further information regarding WHEA errors.

 

 

I have also sent you a PM.

 

 

Best Regards,

 

Juan V.
0 Kudos
idata
Employee
1,317 Views

As I understand it, these are errors from the 'Windows Hardware Error Architecture' which are reporting a hardware error. The machine check exception record captured in the mini-dump is

4: kd> !errrec fffffa8033f068f8

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

Common Platform Error Record @ fffffa8033f068f8

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

Record Id : 01d2d82f7e9c59a4

Severity : Fatal (1)

Length : 928

Creator : Microsoft

Notify Type : Machine Check Exception

Timestamp : 5/29/2017 3:56:10 (UTC)

Flags : 0x00000002 PreviousError

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

Section 0 : Processor Generic

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

Descriptor @ fffffa8033f06978

Section @ fffffa8033f06a50

Offset : 344

Length : 192

Flags : 0x00000001 Primary

Severity : Fatal

Proc. Type : x86/x64

Instr. Set : x64

Error Type : Micro-Architectural Error

Flags : 0x00

CPU Version : 0x00000000000406f1

Processor ID : 0x0000000000000000

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

Section 1 : x86/x64 Processor Specific

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

Descriptor @ fffffa8033f069c0

Section @ fffffa8033f06b10

Offset : 536

Length : 128

Flags : 0x00000000

Severity : Fatal

Local APIC Id : 0x0000000000000000

CPU Id : f1 06 04 00 00 08 10 00 - f7 fb fe 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 @ fffffa8033f06b10

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

Section 2 : x86/x64 MCA

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

Descriptor @ fffffa8033f06a08

Section @ fffffa8033f06b90

Offset : 664

Length : 264

Flags : 0x00000000

Severity : Fatal

Error : Internal timer (Proc 0 Bank 3)

Status : 0xf200000000800400

So, as I understand it, this is information being reported from the hardware, presumably the Intel Chipset and processor.

I was hoping the hardware error records would be able to tell me what it thinks is wrong.

0 Kudos
idata
Employee
1,317 Views

Hi mysteryguy,

 

 

As for the dump file, you can contact Microsoft to get information about it.

 

 

I was wondering if you had the time to check the private message that I sent before.

 

 

Regards,

 

Juan V.
0 Kudos
idata
Employee
1,317 Views

Hi mysteryguy,

 

 

I have sent you a private message.

 

 

Regards,

 

Juan V.
0 Kudos
idata
Employee
1,317 Views

Hello mysteryguy,

 

 

I was reviewing this thread and I wanted to know if you need further assistance?

 

 

Best Regards,

 

Juan V.
0 Kudos
Reply