DPC_Watchdog_Violation on Clevo P775DM3

Discussion in 'Sager and Clevo' started by hendenburg2, Apr 21, 2018.

Thread Status:
Not open for further replies.
  1. Kittys

    Kittys Notebook Evangelist

    Reputations:
    176
    Messages:
    458
    Likes Received:
    414
    Trophy Points:
    76
    Watch Dog is just general "something really bad happened" error... first would be re-installing all the drivers cleanly, second would be raising vcore if not stock...remember cpu can be "stable" but not stable at full load or avx or other instruction sets a game can use :/ , then running memory diagnostic to check ram and then gpu.

    So its either:
    • Bad ram (op run windows memory diagnostic just type it into search)
    • Failing GPU (unlikely in this case but still a potential..)
    • Partially unstable CPU (bumping vcore rules this out even in a "soft" oc)
    • Drives (unlikely here too)
    Then all of us can go from there with the findings..
     
    Last edited: Apr 22, 2018
    Falkentyne likes this.
  2. Meaker@Sager

    Meaker@Sager Company Representative

    Reputations:
    8,115
    Messages:
    51,343
    Likes Received:
    14,646
    Trophy Points:
    931
    Technically an unstable CPU can throw out a whole host of different errors depending on what is messing up and when.
     
    Vistar Shook likes this.
  3. hendenburg2

    hendenburg2 Notebook Enthusiast

    Reputations:
    0
    Messages:
    16
    Likes Received:
    2
    Trophy Points:
    6
    So it's not bad RAM, already ran that diagnostic.
    Ran GPU-Z, temp has leveled off at 71C after 10 minutes.

    I changed my VCore offset from -0.07 (resulting in ~1.25V) to -0.04 (VCore now ~ 1.3V). Tried running Destiny 2 for a short time (~15 minutes). Didn't crash, but my CPU temp was getting up to ~94C. Gotta admit that that was making me nervous. I know Intel says Kaby's can go up to 100C before the thermal protection kicks in, but still...

    Currently running prime95.

    @Falkentyne What is that AMIBCP program you took screenshots of?
     
  4. Kittys

    Kittys Notebook Evangelist

    Reputations:
    176
    Messages:
    458
    Likes Received:
    414
    Trophy Points:
    76
    I would just run Hyper-PI because it will throw an error if there are any improper calculations from cpu instantly.
     
    Falkentyne likes this.
  5. hendenburg2

    hendenburg2 Notebook Enthusiast

    Reputations:
    0
    Messages:
    16
    Likes Received:
    2
    Trophy Points:
    6
    Ran Hyper-Pi to 1M digits, all 8 cores. Average time 12.077 seconds, no errors reported.
    Ran it to 16M digits. Average time was 5 mins, 23 seconds. During test, temps reached 81C, voltages dropped from ~1.27V to 1.2V. No reported errors
     
  6. Kittys

    Kittys Notebook Evangelist

    Reputations:
    176
    Messages:
    458
    Likes Received:
    414
    Trophy Points:
    76
    Good good now try those games :p seems there is some significant vdroop.
     
    Falkentyne likes this.
  7. hendenburg2

    hendenburg2 Notebook Enthusiast

    Reputations:
    0
    Messages:
    16
    Likes Received:
    2
    Trophy Points:
    6
    Yep. Starting now, will update. I'm running the logger on Hardware Monitor Pro. Maybe that will provide some insight
     
  8. Falkentyne

    Falkentyne Notebook Prophet

    Reputations:
    7,171
    Messages:
    5,437
    Likes Received:
    7,527
    Trophy Points:
    681
    You mean this?

    http://www.mediafire.com/file/jocdttwdwf32cff/AMIBCP5020023.zip

    You don't need this. You have a prema bios already don't you?
    and this is usually used after you back up the existing bios with FPTW64.exe or FPTW.exe so you can access hidden menus. And you had better know what you're doing because you don't want to brick it either. But its fine for opening up random bioses to see what cancer is in the bios menus :):):)

    You can still unlock menus on MSI (so you can undervolt, disable Terminal Velocity Boost and change the IA AC DC loadline setting to 1 to remove 2.10 mOhms of vid boosting). Works on eVGA boards also. But Frank Azor locked down Alienware filth more than Ngreedia locked down Pascal...no love nor hope for new 6 core alienwares....throttle city man. GAME OVER.
     
    KY_BULLET likes this.
  9. hendenburg2

    hendenburg2 Notebook Enthusiast

    Reputations:
    0
    Messages:
    16
    Likes Received:
    2
    Trophy Points:
    6
    Yeah, the only setting I've played around with in the BIOS was the voltage offset, definitely didn't play around with any watchdog timer settings. Changed VOffset from -0.07V to -0.04V and so far, so good, it seems. Just curious about those screenshots you attached. Didn't see anything about watchdog timer settings in the BIOS, but I didn't exactly do an exhaustive search because I didn't really know what to look for. Problem with all these guides on the internet is that many are outdated, and even relatively newer ones have different variable names and such.
     
    Vistar Shook likes this.
  10. Meaker@Sager

    Meaker@Sager Company Representative

    Reputations:
    8,115
    Messages:
    51,343
    Likes Received:
    14,646
    Trophy Points:
    931
    Variable names can change between board manufacturers.
     
Loading...
Thread Status:
Not open for further replies.

Share This Page