BSOD 0x00000124 hal.dll+12a3b and ntoskrnl.exe+75bc0

[Sanborn32]

I built a new machine about 4 weeks ago. MAchine booted up fine and ran with no issues. All drivers installed fine ..no errors. A few days later i started getting minidump errors when coming to my machine after it was sitting idle for a time. So i dont turn my machine off at night, I have been having Random crashes, ALWAYS when the machine is idle. If i am physically using the machine ie, browsing, gaming etc no crash... if i walk aways for a time and leave it running. i till come back to a "your machine has recovered from a serious error" message saying the error occured 0x00000124 hal.dll+12a3b and ntoskrnl.exe+75bc0.

I have removed all components, blown out all the sockets and replaced them making sure each one is properly seated in the sockets. I am using an after market Cooler on the CPU, real temp shows the temps are normal, though i dont know if this ever changes. Only going by the real temp display on my notification bar. All fans are running ntoskrnl.exe+75bc0 and set to full speed. 5 Hard drives are inside the case SATA drives. The others are external USB 3

Machine has crashed 30 times since the 13th july, all for same error. Hope someone can help cause i am stumped.

last 3 Minidump files are here Pogoplug: Minidump.zip
Speccy Report is here : http://speccy.piriform.com/results/gR1YnYI041cglguXyCSkTCY
Minitool Report is here View attachment minitool dump.txt
Sfc /Scannow report View attachment sfcdetails.txt

I am not overclocking, everything is running at stock settings. Aftermarket CPU Cooler is a thermaltake NIC F4 cooler.

Thanks for any help you can offer

 

[Patrick]

Hi,

WHEA_UNCORRECTABLE_ERROR (124)

A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).

If we run an !errrec on the 2nd parameter of the bug check (address of the WER structure) we get the following:

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

[COLOR=#ff0000]Error         : Internal unclassified (Proc 7 Bank 1)[/COLOR]
  Status      : 0xbf80000000200401
  Address     : 0x00000000fee00040
  Misc.       : 0x0000000000000086

Internal unclassified implies this is not a publicly documented error, therefore we cannot get any information as to what specifically caused it.

---

Try the following first:

1. AppleCharger.sys is listed and loaded which is the GIGABYTE On/Off Charge driver. See here for details - GIGABYTE ON/OFF Charge

Very troublesome software, so please uninstall ASAP!

2. Uninstall Gigabyte Easy Saver as well as any/all Gigabyte bloatware, it's extremely old and problematic.

3. Remove and replace Norton with Microsoft Security Essentials for temporary troubleshooting purposes as it may be causing conflicts:

Norton removal - https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;jsessionid=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&pvid=f-home

MSE - Microsoft Security Essentials - Microsoft Windows

4. Navigate to services.msc and disable the nVidia Streaming Service, and then restart the system.

---

If all of the above fails, there is only so much you can do with a bug check like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - Speccy - System Information - Free Download

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - How To Clear CMOS (Reset BIOS) [Easy, 10 to 15 Min]

3. Ensure your BIOS is up to date.

4. If all of the above fail, the only left to do is replace your processor as it is faulty.

Regards,

Patrick