Tech Support Forum banner
Status
Not open for further replies.

BSOD after long gaming period.

2K views 35 replies 2 participants last post by  Wrench97 
#1 ·
I'm receiving a BSOD into about 1 - 2 hours of gaming.

BlueScreenView reports the error as:

Bug Check Code: 0x00000124

Caused by driver hal.dll,
Caused By Address hal.dll+ 37213, ntoskrnl.exe+1c5f2d

Is this Hardware related, Graphics Card perhaps? I'm also constantly getting atikmdag.sys and atikmpag.sys crashes but am not sure if that is related to the BSOD in question.
 
#3 · (Edited)
Thanks for your reply. When trying to run the perfmon /report I'm getting an error:

An error occured while attempting to generate the report.

The operator or administrator has refused the request.


I've followed this thread System Health Report - Generate and View in Windows 8.1
to generate a health report but there doesn't seem to be an option to export it that way.

I'm also getting a error when opening performance monitor manually:

Unable to add these counters:

\Memory\Available MBytes
\Memory\%Committed Bytes In Use
\Memory\Cache Faults/sec
\Memory\Cache Faults/sec
\PhysicalDisk(*)\% Idle Time
\PhysicalDisk(*)Avg. Disk Queue Length
\Network Interface(*)Bytes Total/
 
#6 ·
I have the SysnativeFileCollectionApp zip here.

OS: Windows 8.1
x64
Windows 8.1 install onto brand new ssd and system
Full retail version
Age of System - Brand new - 4 weeks
OS installation - 4 weeks old
Re-installed OS - No

CPU - Intel i5 4690K
Video Card - AMD R9 270X
Motherboard - Asus Z97-A
Ram - Corsair Dominator Platinum 2400mhz 8GB
PSU - Seasonic X-660KM - 660watt
Desktop
 

Attachments

#8 ·
Just looking at the last 3 from this month you have 2 x124's which is a CPU hang and 1 x116 Video_TDR TDR is Time out, Detect and Recovery, the 116 is suppose to mean it hung and recovered as opposed to x117 where it hung and couldn't recover.

Lets get a look at the temps and voltages> D/L and run Hardware Monitor do something intense like a virus scan or gaming for a bit, Alt+Tab back to HWM expand all the trees and use the Win7 snipping tool to grab a screen shot of the HWM window, post the screen shot using the paperclip button in the advanced message box(Go Advanced button).

Also D/L and run the Intel Processor Diagnostic Tool> https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool-64-bit-
File name: IPDT_Installer_2.11.0.0.W-2_x86_2.20.0.0.W.MP-1_x64.exe

Code:
Debug session time: Sat May 16 08:44:11.138 2015 (UTC - 4:00)
Loading Dump File [C:\Bsodapp\SysnativeBSODApps\051715-3437-01.dmp]
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
System Uptime: 0 days 2:45:24.859
Probably caused by : GenuineIntel
BugCheck 124, {0, ffffe0001864b028, ff800000, 124}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]WHEA_UNCORRECTABLE_ERROR (124)[/url]
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe0001864b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ff800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  Game.exe
FAILURE_BUCKET_ID:  0x124_GenuineIntel__UNKNOWN
MaxSpeed:     3500
CurrentSpeed: 3570
BiosVersion = 2205
BiosReleaseDate = 02/12/2015
SystemManufacturer = ASUS
SystemProductName = All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue May 12 00:55:17.734 2015 (UTC - 4:00)
Loading Dump File [C:\Bsodapp\SysnativeBSODApps\051215-3484-01.dmp]
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
System Uptime: 0 days 17:31:05.454
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+b970 )
BugCheck 116, {ffffe0002d55d010, fffff800c874a970, 0, d}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]VIDEO_TDR_FAILURE (116)[/url]
Bugcheck code 00000116
Arguments: 
Arg1: ffffe0002d55d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff800c874a970, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x116_IMAGE_atikmpag.sys
MaxSpeed:     3500
CurrentSpeed: 3570
BiosVersion = 2205
BiosReleaseDate = 02/12/2015
SystemManufacturer = ASUS
SystemProductName = All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon May 11 07:23:51.440 2015 (UTC - 4:00)
Loading Dump File [C:\Bsodapp\SysnativeBSODApps\051115-3343-01.dmp]
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
System Uptime: 0 days 1:01:33.159
Probably caused by : GenuineIntel
BugCheck 124, {0, ffffe000da7e8028, bf800000, 124}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#Example]WHEA_UNCORRECTABLE_ERROR (124)[/url]
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe000da7e8028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  Game.exe
FAILURE_BUCKET_ID:  0x124_GenuineIntel__UNKNOWN
MaxSpeed:     3500
CurrentSpeed: 3570
BiosVersion = 2205
BiosReleaseDate = 02/12/2015
SystemManufacturer = ASUS
SystemProductName = All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
#9 · (Edited)
Thanks for your reply Wrench. I am getting the Video_TDR TDR Time out crash a lot, at least 3 times every few hours. I have contacted AMD and followed instructions on a fix but it hasn't worked. The instructions they gave me are the same as in this thread: http://www.tomshardware.com/answers/id-1656824/atikmdag-sys-error-bsod-startup.html

I am so fed up with it that I don't even wait for the error screen anymore, it freezes and I just restart manually. If 116 is meant to hang and recover it's definitely not, it always has to restart.

I had posted another thread about worrying CPU temps but finally figured out that the voltage in AI suite 3 was set to 1.275V which it what it seems to set it at at default. I was advised that was too high and I am currently running 1.200V @ 4.590 GHz but really aren't sure if that voltage is fully stable, I just took a guess, although other forum members thought 1.200V sounded good.

I also finally discovered that the store I brought my system from must have changed the multiplier to 45 which gives me the 4.5GHz before it arrived to me. I have a 4690K which is know for overclocking to 4.5GHz so perhaps they decided to give me head start with setting that up. As far as I can tell just the multiplier was set. I'm also running Adaptive Mode.

Doing some googling myself it could be 124 crash is cpu undervolted..
I am not attempting any fix myself though and will wait for expert advice.

I have HWMonitor screenshots here. They are with Prime95 running after 5 passes.
 

Attachments

#12 ·
Do you think the 124 crash even though it's supposed to be a cpu hang is somehow gpu related instead? It's just that with my current cpu settings it has no trouble with any stress tests and temps, also the crashes only seem to happen while gaming.
 
#13 · (Edited)
I dialed my cpu speed back to 4.284Ghz from 4.590Ghz with 1.200V and ran the same game tonight for an hour with no crash.

I think the multiplier and the voltage are the only things that have been changed for this overclock.

Could it be that 1.200V isn't enough for 4.590Ghz and causing the crash? It doesn't make a lot of sense at this stage though as I can use these settings in stress tests and have no errors and good temps.

Guessing is probably not going to provide the right answer so I will wait for more expert advice.
 
#15 · (Edited)
I'm not sure whether the OC is fully stable yet, maybe I need to run Prime95 longer. With what duration of Prime95 can you safely say your OC is stable?

Will we get to the bottom of the real cause of the 124 crash?

Can you help me with the Video_TDR TDR crash? It really is unacceptable to be getting this, it happens randomly and I lose work.
 
#25 ·
Wrench, I haven't got around to fully understanding Adaptive Voltage yet but my basic understanding so far is it regulates the voltage based on load rather than having a constant high voltage which must be good right?

I haven't got around to running the system on stock clocks yet but am definitely going to try this weekend. I'm not getting any crashes while gaming anymore after changing the voltage to 1.210V and cpu clock to 4.2 Ghz via Asus Ai Suite 3.

I'm still getting the Video_Tdr_Timeout crash but it seems to be only now every time straight after I have booted the system and before I've changed the voltage and clock in Ai Suite but no longer after they have been set. Does this indicate anything to you? Perhaps the clock and voltage should be set in the bios first as the changes I make in Ai Suite have to reset with every boot.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top