Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD always involving ntoskrnl.exe and hal.dll

09 Feb 2015   #1
BERGO27

Windows Home Premium 64bit
 
 
BSOD always involving ntoskrnl.exe and hal.dll

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


My System SpecsSystem Spec
.
09 Feb 2015   #2
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

Stop 0x124 - what it means and what to try

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007460028, bf800000, 200401}
Probably caused by : GenuineIntel
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
---------
My System SpecsSystem Spec
11 Feb 2015   #3
BERGO27

Windows Home Premium 64bit
 
 

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?
My System SpecsSystem Spec
.

11 Feb 2015   #4
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

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

Code:
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 fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Internal Unclassified Error
Processor ID: 2
That CPU's maximum rated temperature is 72.72C - 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.
My System SpecsSystem Spec
11 Feb 2015   #5
BERGO27

Windows Home Premium 64bit
 
 

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?
My System SpecsSystem Spec
11 Feb 2015   #6
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

You might try an after-market cooler or even a self contained water-cooling kit.
My System SpecsSystem Spec
11 Feb 2015   #7
BERGO27

Windows Home Premium 64bit
 
 

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?
My System SpecsSystem Spec
12 Feb 2015   #8
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

I don't know. I never use the stock fans.
My System SpecsSystem Spec
12 Feb 2015   #9
BERGO27

Windows Home Premium 64bit
 
 

Any recommendations for a good fan preferably under $50? Keeping in mind I'm not overclocking
My System SpecsSystem Spec
13 Feb 2015   #10
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

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

CoolerMaster Hyper 212X CPU Cooler [21C-CPUHYP212X] - $45.00 : PC Case Gear
My System SpecsSystem Spec
Reply

 BSOD always involving ntoskrnl.exe and hal.dll




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD, mostly involving ntoskrnl.exe
Hello, for around a month or two now I have been suffering from seemingly random BSODs. They can happen at any time, while changing between tabs in Chrome, or playing a game. Sometimes, after the dump file has been created during the BSOD, the computer will automatically restart and function as...
BSOD Help and Support
Many BSOD's involving ntoskrnl.exe (nt+0x75C40)
I have to admit it is scary to start a thread here. I did read the instructions and hope I did everything correct. The bsod have been going on for months now. I am using a windows 7 PC on 64 bit Intel Core i5 processor. (I've added all the info in my profile) but just to be sure I will add...
BSOD Help and Support
BSOD involving ntoskrnl.exe 4+
New to forums, forgive me if I don't provide enough information. So here's my situation. I've had this custom build computer for almost 2 years and for the past few weeks I've been receiving many BSOD's and I can really pin point the problem. I'm going to attach text files from the BLUESCREEN View...
BSOD Help and Support
BSOD involving dxgmms1.sys and ntoskrnl.exe
So, I was having BSOD's with my old system as it was set up and wanted to start fresh as I had not re-installed my OS in a while. I bought a new SSD and installed my OS on it, and formatted my old drive to use as space to install programs. However the BSOD's have started again, the first was right...
BSOD Help and Support
BSOD Involving ntoskrnl.exe
Well, after scouring the internet in an attempt to figure a solution for myself I have finally admitted defeat and here I am. The issue is hard to pinpoint as it happens at random. Be it gaming, browsing the net, or even opening a window to navigate around my computer. It is always the same. The...
BSOD Help and Support
Constant BSOD involving ntoskrnl.exe and win32k.sys
About a month ago, I started to get a lot of blue screens, which I thought was due to a new update for my Nvidia video drivers. They started getting worse so I downloaded WhoCrashed in order to get a better description of what was happening and it came to my attention that most were involving the...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 23:53.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App