BSOD always involving ntoskrnl.exe and hal.dll

[BERGO27]

Had this problem since I first built the system in December, wasn't too bad since it usually only happened during idle but lately it has been happening whilst gaming (during boss fights ). About all the info I can give really

 

[SGT Oddball]

You dumps point to a 0124 hardware problem, these are notoriously hard to track down, I'd start with checking CPU temperatures etc, then the following tests.

RAM:
You MUST use Memtest86+ to test RAM - everything else is inferior. Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Use this tutorial to help you use MemTest86+:
RAM - Test with Memtest86+

CPU:
CPU - Stress Test Using IntelBurnTest
Hardware - Stress Test With Prime95

Video:
Video Card - Stress Test with Furmark

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007460028, bf800000, 200401}
[B][COLOR=red]Probably caused by : GenuineIntel[/COLOR][/B]
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
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: 0000000000000000, Machine Check Exception
Arg2: fffffa8007460028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200401, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------

BUGCHECK_STR:  0x124_GenuineIntel
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  thermald.exe
CURRENT_IRQL:  f
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`009f7a58 fffff800`03613a37 : 00000000`00000124 00000000`00000000 fffffa80`07460028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`009f7a60 fffff800`031a71ff : 00000000`00000001 fffffa80`07461ea0 00000000`00000000 fffffa80`07461ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f7aa0 fffff800`036136fc : 00000000`00000728 fffffa80`07461ea0 fffff880`009f7e30 fffff880`009f7e00 : nt!WheaReportHwError+0x26f
fffff880`009f7b00 fffff800`0361304e : fffffa80`07461ea0 fffff880`009f7e30 fffffa80`07461ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f7c50 fffff800`03612f09 : 00000000`00000004 00000000`00000001 fffff880`009f7eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f7c90 fffff800`03606e88 : 00000000`00000000 00000000`00000010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f7cc0 fffff800`0308caac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f7cf0 fffff800`0308c913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f7e30 fffff800`03084e08 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`12145638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memcpy+0x208

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME:  GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP:  0
IMAGE_VERSION:  
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_mae
FAILURE_ID_HASH:  {addebe90-d04a-b9c9-a39c-2531fe75dd4e}
Followup: MachineOwner
---------

 

[BERGO27]

Okay, I've gone to start with IntelBurnTest and I've looked at the idle temp of the CPU, seems to be averaging around the middle of 50 and 60deg. This sounds a little high to me? Just looking for someone to confirm that isnt out of the ordinary before i go ahead and stress test anything.

EDIT: Got antsy and ran the test anyway, all cores jump over 80 initially as well as during the remainder of the test, and that was just on standard. Soooo cooling problem then? I applied my own thermal paste between the heatsink and the CPU during build, I thought I had put enough on... Could this be the issues? If so would it help if i dissassmbled and take some photos to show the contact patch?

 

[Golden]

That certainly sounds way too hot. From your eventlog, we see the following:

Event[32955]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2015-02-09T21:23:00.910
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: The-Rig
  Description: 
A [B][COLOR="Red"]fatal hardware[/COLOR][/B] error has occurred.

Reported by component: [B][COLOR="red"]Processor Core[/COLOR][/B]
Error Source: Machine Check Exception
Error Type: Internal Unclassified Error
[B][COLOR="red"]Processor ID: 2[/COLOR][/B]

That CPU's maximum rated temperature is 72.72°C - it should comfortably pass a Standard test of IntelBurnTest.

Do the following:

1. Check the cooler to ensure its free of dust and crap
2. Remove the cooler, clean the contact plate and also the CPU surface with an alchohol rub - let it dry for 5 mins
3. Reseat the cooler using new thermal paste.



Reboot and run IBT. Post screen capture image of the results. Follow the IntelBurnTest tutorial Sgt Oddball posted.

 

[BERGO27]

Okay tried that, rebooted and the temps looked fairly normal. Ran the test according to the tutorial and the temps jumped up to high 80s by the 3rd pass. I uploaded the original contact patch. The CPU fan is stock and definitely operating. Any other susuggestions?

 

[Golden]

You might try an after-market cooler or even a self contained water-cooling kit.

 

[BERGO27]

I have thought about doing that, however I wouldn't think that such a large temperature spike at relatively low loads is likely to happen using a stock fan? It seems as though something else could be causing the problem. Or is that a know problem with gen 4 Intel fans?

 

[Golden]

I don't know. I never use the stock fans.

 

[BERGO27]

Any recommendations for a good fan preferably under $50? Keeping in mind I'm not overclocking

 

[Golden]

Try this one - good brand. Double check compatibility with your socket.

CoolerMaster Hyper 212X CPU Cooler [21C-CPUHYP212X] - $45.00 : PC Case Gear

 

[BERGO27]

Went one step further and bought a cooler master seidon 120V+ so the cooling should be more than sufficient. Ran the burn test and temperatures are still mid 80s even on standard. I have all the software that came with the motherboard installed, could this be an issue? I am also only running 1 stick of RAM, I was planning on upgrading later on, I didn't think this would be an issue but now I'm just trying to think of anything unconventional that may be affecting the system

 

[Golden]

Uninstall all the Gigabyte applications, then run IBT again.