BSOD hal.dll+3620f (0x124_GenuineIntel_PROCESSOR_MAE) on Windows 10 x64 1607 (14393.82)

Yesterday I encountered a BSOD just moments after I had login to Desktop and launch Metrotube app. The error code as seen from screenshots taken from BlueScreenView and Reliability History in Control Panel is hall.dll+3620f (0x124_GenuineIntel_PROCESSOR_MAE). I have been researching all day today about this error code but have found none. Can anyone know what is the cause of this BSOD?

Steps performed before BSOD:

1. Turned on computer and login to Desktop. This means that overheating or similar cannot be the issue here, since no computer can overheat in less than a minute. The BSOD also didn't happen again although I used it more than one hour after BSOD happened. The computer is not overclocked.

2. Launch Metrotube app: BSOD happened. I don't believe Metrotube is the cause, since I have been using it over a long period of time and has not given me any problem.

Screenshot 1:

Screenshot 2:

Thanks,

Mitjah

Please post a link to the dump file/s. "How to" instructions below.

Blue Screen of Death (BSOD).

http://answers.microsoft.com/en-us/windows/wiki/windows_10-update/blue-screen-of-death-bsod/1939df35-283f-4830-a4dd-e95ee5d8669d

Take time to let us know if the suggestion worked...or not.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

System specs:

CPU: Intel i5 3550

MB: Asus P8Z77-V LX with latest bios available for this MB

RAM: Kingston KHX 1600C9D3/4GX (2*4 GB), this ram is certfied by ASUS in QVL file for the MB.

GFX: Asus Radeon R9 270X on PCI Express 16x (Radeon software version 16.8.2)

SSD: Samsung 840 EVO

HDD: WD1002FAEX-00Z3A0 (swap file is set on this disk since installation of W10 and never caused problems)

Link to BSOD DMP file: https://1drv.ms/u/s!ACcedfAul6iwjZgH

Link to Sysem.nfo created by MSINFO32: https://1drv.ms/u/s!ACcedfAul6iwjZgG

I forgot to mention in my first post, that I performed CHKDSK on both disk and RAM check with no errors found.

Hope this helps,

Mitjah

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

BugCheck 124, {0, ffffcb0906920028, be000000, 800400}

Probably caused by : GenuineIntel

Followup:     MachineOwner

1: kd> !errrec ffffcb0906920028
===============================================================================
Common Platform Error Record @ ffffcb0906920028
-------------------------------------------------------------------------------
Record Id     : 01d202df8dbfef0d
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/30/2016 18:31:26 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffcb09069200a8
Section       @ ffffcb0906920180
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   : 0x00000000000306a9
Processor ID  : 0x0000000000000002

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

Local APIC Id : 0x0000000000000002
CPU Id        : a9 06 03 00 00 08 10 02 - ff e3 ba 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  @ ffffcb0906920240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffcb0906920138
Section       @ ffffcb09069202c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 1 Bank 3)
  Status      : 0xbe00000000800400
  Address     : 0x0000380006638953
  Misc.       : 0x000000000003ffff

This is most likely  Hardware error. For more information and troubleshooting tips, refer to the links below.

BugCheck Code 124.

http://answers.microsoft.com/en-us/windows/wiki/windows_10-update/bugcheck-code-124/98c998d2-447a-40ce-ae1f-8211e355f14d

Take time to let us know if the suggestion worked...or not.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Excuse my ignorance, but what do you mean by hardware error: Some occasional error or hardware about to fail?

Mitjah

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Excuse my ignorance, but what do you mean by hardware error: Some occasional error or hardware about to fail?

Mitjah

Please read the Wiki.

Computer hardware.

https://en.wikipedia.org/wiki/Computer_hardware

Take time to let us know if the suggestion worked...or not.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I know what hardware is for about 30 years, there is no need to be sarcastic.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Sorry if you felt I was being sarcastic, but my impression was that you genuinely did not know. Only trying to help.
Take time to let us know if the suggestion worked...or not.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I posted my last question about the meaning of hardware error because I did some research a found this describtion about 0x124 error at https://msdn.microsoft.com/en-us/library/windows/hardware/ff557321(v=vs.85).aspx:

"This bug check is typically related to physical hardware failures. It can be heat related, defective hardware, memory or even a processor that is beginning to fail or has failed. If over-clocking has been enabled, try disabling it. Confirm that any cooling systems such as fans are functional. Run system diagnostics to confirm that the system memory is not defective. It is less likely, but possible that a driver is causing the hardware to fail with this bug check."

According to above describtion from msdn.microsoft.com website it is quite possible this is a driver error and not hardware issue. Also, in my experience, Windows error codes aren't always correct when detecting error causes. Let me explain with a real story that happened to me some years ago: I had a computer running XP with a Geforce card. This computer suffered a lot of BSOD, which according to XP was caused by nvdisp.dll (graphic driver or graphic card). I had tried with different drivers with no luck. Then I decided to check the memory with memtest86. Memtest86 found that one memory module was defective. I removed the defective module and didn't experience any more BSOD related to nvdisp.dll. What Windows described as a graphic driver/card problem was indeed a memory problem.

Given the fact that my computer is quite stable (I had only 2 BSOD in the past 6 months) and is now working fine I guess this is more probably a driver error than a hardware issue. Still is a shame Microsoft does not offer a clear explanation about their error codes. I have yet to found what BSOD hal.dll+3620f (0x124_GenuineIntel_PROCESSOR_MAE) actually means.

Thanks for your time.

Mitjah

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated April 12, 2020 Views 1,392 Applies to: