DPC_Watchdog_Violation on Clevo P775DM3

So whenever I play Destiny 2 or ME:A, the game will run for 10-15 minutes and then it will crash with the BSOD error "DPC_Watchdog_Violation". Older games like ME3 don't cause the error.

Relevant info for my build is:
Maker: HIDEvolution
Shell: Clevo P775DM3
Processor: i7-7700K
GPU: NVidia GTX 1060
RAM: 16GB DDR4 4200 MHz
Storage: 256 GB M.2 SSD for the boot drive, 1 TB HDD

Temps (using Hardware Monitor Pro)
Processor (package): 78C. Also, I do not have overclocking enabled.
GPU: 55C


I've gone around and checked a variety of potential causes, and the fixes that I have tried so far include:
-Making sure all drivers are updated
-Setting ATA/ATAPI drivers to "standard SATA AHCI controller"
-Rolling back NVidia Driver
-Checked all drivers from the Clevo website, mine are all newer versions
-Ran chkdsk /f /r, no reported errors
-Ran mdsched.exe, no reported errors.

None have worked, Microsoft support says to check hardware, and HIDEvolution doesn't have tech support on weekends.

 

Are running at stock clocks and voltage?

Enviado de meu Pixel 2 usando Tapatalk

 

Hardware Monitor Pro has the processor running at 4.7 GHz, 1.25 V

 

Perhaps raise the voltage a little bit?

Enviado de meu Pixel 2 usando Tapatalk

 

How? I've never really tried modifying the CPU or GPU clock speeds or voltages, always figured that was best left to professionals

 

Yeah that VCORE is way too low for 4.7ghz on 70% of kabys. 4.7 is not stock at all.... You want to set it to 1.3v, 1.35v is safest top end for 24/7 on these laptops I would be concerned with 1.4 even though it is also safe and lots of motherboards default it to 1.38v... You will want to boot into bios again first and report back if you can even set vcore options since its from HID it may have prema in there otherwise you will want to use our lord and savior of an app...Throttlestop.

 

How would I go about doing that? I definitely have Prema, but as I said earlier, Never tried playing around with voltage settings.

 

@Kittys 1.3v seems really high for a 7700K delidded CPU.
Even my BGA turd needs less voltage than that for 4.7 ghz.

Papusan's 7700K can do 4.7 ghz at 1.20v if I recall.
@Papusan ?

 

Yah and my 7700K can do 5 at 1.25v but not everyone gets a good bin... which is why lots of motherboards like ROG default it so high. 1.3 is still within lower end bin limitations...A really bad one would need 1.35v but I doubt thats the case here since it can boot into windows and everything but DPC violation means vcore for sure if he reinstalled gpu drivers and everything*

 

DPC watchdog violation?

I don't think that's vcore.
Vcore should cause "WHEA correctable errors" in event viewer or "WHEA uncorrectable error" (STOP 0x124 BSOD)".
I've never seen such an error before and I've crashed many times because of vcore.

@hendenburg2 Are you sure you disabled these settings?

 

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..

 

Technically an unstable CPU can throw out a whole host of different errors depending on what is messing up and when.

 

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?

 

I would just run Hyper-PI because it will throw an error if there are any improper calculations from cpu instantly.

 

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

 

Good good now try those games seems there is some significant vdroop.

 

Yep. Starting now, will update. I'm running the logger on Hardware Monitor Pro. Maybe that will provide some insight

 

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.

 

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.

 

Variable names can change between board manufacturers.

 

VRMS and CPU gettting to hot causing this error. You generally don't want it to go above 80c in gaming. Otherwise you will kill your notebook in around 1-2years. The VRMS will likely die and then you can have a fun time paying for a new mainboard. The CPU itsellf will likely be fine but the board will not be happy.

 

CPU temps and VRM temps are not linearly related in the same manner in all machines.

 

Utterly, completely *WRONG*.