Windows 10: BSOD playing Battlefield 1, WHEA_Uncorrectable_Error

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.

 

What settings are you playing at in game? Maybe lowering them some will ease the load on the CPU

 

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.

and

 

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?

 

Yes, that is a BIOS setting. Look at your motherboard manual, it will show the settings.

 

Your latest dumpfile is:
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 ---------[/quote] Sadly the dumpfile does not point to a specific driver , but the procesname named is audiodg.exe.
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.

 

So I put the CPU Voltage in Offset Mode, right? I also read that the VCore Load-line Calibration is recommended to be at 75 %. Is there anything else I need to think about? Of course, I am keeping the CPU at stock frequency.

 

I thought I installed the Realtek Audio Driver; I will have a look at the ASUS site again.
EDIT: I see that the Realtek Audio Driver is actually from June 2015, on the ASUS supportpage, and that is the one I have installed. It also seems to be from 2015 on Realtek's own site:
Realtek

I am also currently installing this guy:
Download Intel® Management Engine Driver (1.5M) for Windows® 10 for Intel® NUC D54250WYK/B and D34010WYK/B

 

That IME Driver says it is for Intel® Management Engine Driver (1.5M) for Windows® 10 for Intel® NUC D54250WYK/B and D34010WYK/B
That is the Intel NUC.

 

As i mentioned in one of my earlier post.
See if you can update above drivers from your supportpage Support Center | ASUS Global
, under utilties you can find version Version*11.0.0.1146 .

 

Alright, got it. I didn't find any of the other ones you mentioned, but I downloaded the Intel Management Driver now, from the ASUS supportpage. The installation looked very similar to the NUC one, but I uninstalled that one of course. The NUC thing was the only one I found on the Intel's homepage.
I did run the game again, with bluescreen as usual after less than an hour playing, and we are back to the WHEA_UNCORRECTABLE_ERROR.

 

yes the same dumpfile with WHEA_UNCORRECTABLE_ERROR.

I found this on the Intel website Intel® Processor Diagnostic Tool, i never have used this myself. But it seems you can (stress)test your CPU with this. Maybe this will give any clues or answers.

download: Download Intel® Processor Diagnostic Tool

 

I ran it, and it passed. I'm not sure exactly what the test does besides loading the CPU to almost 100 %, and everything being monitored looked ok. I added the text file with the test results, and an updated log file (I'm not sure the one I posted last time included the correct Intel driver update). Do I have the correct Intel driver now?
I am also trying to get hold of another power supply, to see if that helps.

 

It is again the same bugcheck.

Yes.
Code: -------------- System Devices -------------- Name: Intel(R) Management Engine Interface Device ID: PCI\VEN_8086&DEV_8CBA&SUBSYS_85341043&REV_00\3&11583659&0&B0 Driver: C:\WINDOWS\system32\DRIVERS\TeeDriverW8x64.sys, 11.00.0000.1146 (English), 6/12/2015 04:54:56, 183584 bytes[/quote] Test All Passed.
Then i hopefully suspect that the processor is not the cause of the problem.

 

If you are only having this issue with Battlefield 1then it is highly likely that it has nothing to do with your system. There are thousands of people out there, one of my kids included, that have been suffering random crashes in this game after playing for an hour or more. Both NVidia and the game's creator are aware of these issues. We wait for them to do anything about it. Crashes relate to the GPU and Direct X but the error messages are varied and of course, as seems to be the stupid norm, as cryptic as can be. The fact that you get a BSOD while others get a game crash and error message does not mean the two are not related.