Page 2 of 3 FirstFirst 123 LastLast

  1. Joined : Oct 2013
    NW Florida
    Posts : 6,526
    Windows 10 Enterprise and Pro/Windows 7 Enterprise/Linux Mint
       1 Week Ago #11

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


  2. Joined : Nov 2016
    Bergen
    Posts : 11
    Windows 10 Home 64bit
       1 Week Ago #12

    essenbe said: View Post
    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.
      My System SpecsSystem Spec


  3. Joined : Oct 2013
    Texas
    Posts : 7,391
    Windows 10 Pro X64
       1 Week Ago #13

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


  4. Joined : Nov 2016
    Bergen
    Posts : 11
    Windows 10 Home 64bit
       1 Week Ago #14

    Dude said: View Post
    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.
      My System SpecsSystem Spec


  5. Joined : Oct 2013
    Texas
    Posts : 7,391
    Windows 10 Pro X64
       1 Week Ago #15

    Mothemotecen said: View Post
    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
      My System SpecsSystem Spec


  6. Joined : Jan 2016
    Posts : 371
    windows 10 Pro
       1 Week Ago #16

    Mothemotecen said: View Post
    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.
    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.
    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
    and
    However, 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
      My System SpecsSystem Spec


  7. Joined : Nov 2016
    Bergen
    Posts : 11
    Windows 10 Home 64bit
       1 Week Ago #17

    lifetec said: View Post
    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?
    BSOD playing Battlefield 1, WHEA_Uncorrectable_Error Attached Files
      My System SpecsSystem Spec


  8. Joined : Oct 2013
    Texas
    Posts : 7,391
    Windows 10 Pro X64
       1 Week Ago #18

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


  9. Joined : Jan 2016
    Posts : 371
    windows 10 Pro
       1 Week Ago #19

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


  10. Joined : Nov 2016
    Bergen
    Posts : 11
    Windows 10 Home 64bit
       1 Week Ago #20

    Dude said: View Post
    Yes, that is a BIOS setting. Look at your motherboard manual, it will show the settings.
    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.
      My System SpecsSystem Spec


 
Page 2 of 3 FirstFirst 123 LastLast


Similar Threads
Thread Forum
BSOD playing Battlefield 1, error 0x133 DPC_WATCHDOG_VIOLATION
Hi there! I just got my Asus Strix 1070 yesterday, updated the bios for the micron memory fix, and today, after playing a long session of Battlefield 1, I got a "DPC Watchdog Violation" Bluescreen 0x133. Can anyone help me fix this issue? The GPU...
BSOD Crashes and Debugging
BSOD playing Battlefield 1 or using Keyshot
Hello, So I've had Windows 10 since last fall, upgrade from Win 7 and it ran without issues until I replaced my video card with a EVGA GTX 960 and a new PSU. This week however the frequency has increased, and I've been gettied varried BSOD...
BSOD Crashes and Debugging
BSOD playing Battlefield 1
I've never had an issue with system crashes, or playing the new battlefield 1 beta, but after a few hours I got a BSOD with Stop Code: SYSTEM_SERVICE_EXCEPTION. I looked online, ran a few scans, and updated some software, but in the middle of that...
BSOD Crashes and Debugging
Solved BSOD playing Vermintide, WHEA_UNCORRECTABLE_ERROR
I just got a BSOD while playing Vermintide. It displayed WHEA_UNCORRECTABLE_ERROR. Looking it up online its some kind of hardware issue. The game was running kind of sluggish the fps was 40-60 but it felt much slower. I uploaded the dm log...
BSOD Crashes and Debugging
BSOD playing Battlefield 1. Whea_uncorrectable_error
So I've been playing BF1 for the last 3 days and at least once a day a BSOD happens. I want to know if it has anything to do with the latest Nvidia driver (372.70) which I installed after the first day I played the game. and what can I do to solve...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:38.
Find Us
Twitter Facebook Google+



Windows 10 Forums