What about your GPU Temps? You can download any drivers for your motherboard here, https://www.asus.com/Motherboards/H9...Desk_Download/ (Make sure that is your board). Make sure you don't have AI Suite installed. At that link, look at the Utilities section and make sure none of that is installed.
Is BF1 the only game that causes you crashes?
I will monitor GPU temps next time I am running the game. At det beginning the GPU temp was a little lower than the CPU. As mentioned I did uninstall the AI Suite. Yes, BF1 is the only game that causes this type of crash.
I have actually formatted my drive and reinstalled Windows now. I don't know if it will have any effect, but I figured it was worth a shot. I am trying to be careful installing every necessary driver and using Windows update. I did observe during a reboot a short lasting error message (which I didn't have time to record), and the error code started with 0x0... Why is that on a fresh install? Maybe my crashing issue has something to do with this.
What cooling are you using for your CPU? You dont seem to be OCing it, looking at your specs. That type of crash in BF1 would seem to indicate unstable CPU to me, meaning you need just a little more V-core, but the temps seem high for a CPU not OCd
Correct, it is not overclocked. At the moment I am using an Intel stock cooler. I used to have watercooling in my build, but I downgraded it, for various reasons. When I recorded the CPU temperature I boosted the fan speeds as well. I agree, the temperature seems a bit higher than it should, although taking into consideration how demanded Battlefield is.
Could you run the DM Log collector Tool again and post the.zip file.
Maybe this gives us a other clue.
And as @ Dude mentioned look into the Voltage possibility.
andThat type of crash in BF1 would seem to indicate unstable CPU to me, meaning you need just a little more V-core, but the temps seem high for a CPU not OCdHowever, yes, it's clear you're dealing with an internal CPU fault and not one that could be generated by bus issues or any other external factor other than heat and voltage
Alright, I added a new zip file.
I ran the game again on a fresh install of Windows (as mentioned), and my CPU and GPU temps stay between 70 and 75 Celsius. This time the game session was longer; I was able to finish two games, lasting probably 90 mins total, which is more than previously. Then I got bluescreen again, but this time with the stop code CLOCK_WATCHDOG_TIMEOUT. The PC wouldn't restart on it's own. It just stayed on 100 % for a long time.
From what I have read, this issue is CPU related, although it could be drivers as well. So what @ Dude is saying might very well be the case.
How to get more V-core though? Is that through BIOS?
Your latest dumpfile is:
Sadly the dumpfile does not point to a specific driver , but the procesname named is audiodg.exe.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {18, 0, fffff802a09c1180, 0} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff802a09c1180, The PRCB address of the hung processor. Arg4: 0000000000000000, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: audiodg.exe CURRENT_IRQL: d ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre STACK_TEXT: ffff9201`a5c78d88 fffff802`a081f056 : 00000000`00000101 00000000`00000018 00000000`00000000 fffff802`a09c1180 : nt!KeBugCheckEx ffff9201`a5c78d90 fffff802`a074a9b9 : ffff9201`ab0ff800 00001d8d`b4a6f99c fffff780`00000320 ffffac83`b3ecf5b0 : nt! ?? ::FNODOBFM::`string'+0x466b6 ffff9201`a5c78df0 fffff802`a060d366 : ffff9201`ab0ff800 ffff9201`a5c40180 00000000`00000002 00001d8d`b4a6f99c : nt!KeClockInterruptNotify+0x469 ffff9201`a5c78f40 fffff802`a06d6357 : ffffac83`b3ecf500 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpTimerClockInterrupt+0x56 ffff9201`a5c78f70 fffff802`a07cab8a : ffffac83`b3ecf500 ffff9201`a5bc7180 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x87 ffff9201`a5c78fb0 fffff802`a07cafd7 : ffffe8e9`52aeadc6 ffffac83`b50e1800 ffffe8e9`52aeadf6 fffff802`a07cb05e : nt!KiInterruptSubDispatchNoLockNoEtw+0xea ffff9201`ab0ff800 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:clock_watchdog_timeout_8_proc_analysis_inconclusive FAILURE_ID_HASH: {f60c102e-9b2c-017b-9309-e4af1999e360} Followup: MachineOwner ---------
Maybe it could be audio-related.
looking through you driver modules i found that your Realtek Audio driver is from 2015
RTKVHD64 Tue May 05 13:18:22 2015
Driver Description: Realtek High Definition Audio Function Driver
Driver Update Site: Realtek
Look on your Asus supportpage if there is a newer driver.
Also the Intel Mangement Driver is still from 2014, did you already update this one.
Quote