Solved Bogging down while streaming/gaming, now BSOD (Watchdog Violation)

A basic question, is Windows up to date and are the protected files checked (sfc) after the most recent update was installed?
 
Yep, it is up to date, but I just did sfc /scannow and got a message!

"Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included..." blah blah blah.

I think I've attached the right .log... (changed it to a .txt) let me know if I haven't, or you need something else.
 
I've asked a specialist for help on the WU issue, it may take some time for him to respond.
 
Received the fix.

Please do the following
1518992802538.png

  • SFCFix will launch, please let it finish
  • Once SFCFix is done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.
  • Run SFC again and see if it still complains
 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-02-18 17:39:26.681
Microsoft Windows 8.1 Update 3 - amd64
Using .zip script file at C:\Users\Caitlin\Desktop\SFCFix.zip [1]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB

WARNING: File C:\WINDOWS\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB was not backed up as that would replace the current backup.
Successfully copied file C:\Users\Caitlin\AppData\Local\niemiro\Archive\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB to C:\WINDOWS\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB.

Successfully restored ownership for C:\WINDOWS\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.3.9600.17415_none_95dd5540d57f8c01\Amd64\CNBJ2530.DPB
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2018-02-18 17:39:26.994
Script hash: EzA0m6nD9Biz+Ac7z0OYzPZ7OMT440cvNYSVksUWXwU=
----------------------EOF-----------------------

Ran SFC again, no complaints from it this time. Started a stream test, whole PC bogged down within 10 minutes. Last night I decided to check the thermal paste on my CPU, because I hadn't touched it in quite some time, and it didn't look fabulous. Cleaned everything, repasted it... could this be a problem with the CPU? Motherboard? I've not had any heat issues, I use HWMonitor to watch my temps but... really scratching my head here.

Note: That paste is from the paste pad that was on the H60 when I bought it about two years ago so... yeah.
 

Attachments

  • 20180218_013759.jpg
    20180218_013759.jpg
    913.9 KB · Views: 176
Last edited:
I don't think it could be a problem, thermal paste can be used for a long time.

Do you always stream games when playing? I haven't been able to analyze the last trace entirely, it's quite large, but OBS is for some reason eating a lot of resources when the bogging happens.
 
I haven't been able to because of the bogging when streaming. I used to stream all the time, a year ago-ish, with no issues. I'm unfortunately unable to nail down exactly when this started happening, and I just got so discouraged I quit trying to fix it.

This bogging down happens more frequently when trying to stream, or watch a video while playing a game, but sometimes it just happens with only my game and Discord open.
 
Last edited:
Please run driver verifier using the following settings for 48 hours.
  • Special Pool
  • Force IRQL checking
  • Pool Tracking
  • Deadlock Detection
  • Security Checks
  • Miscellaneous Checks
  • Power framework delay fuzzing
  • DDI compliance checking


Warning: driver verifier can cause boot issues and/or performance issues.


Resetting driver verifier options (recommended in this order)
  1. In normal mode open an administrator command prompt and enter the below command
  2. In safe mode open an administrator command prompt and enter the below command
  3. On 3 boot failures, you'll boot automatically to the recovery options,
    • click Troubleshoot
    • go to the advanced options
    • choose command prompt
    • enter the below command
  4. Boot with the recovery media, see above 4 steps in option 3.
  5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier
Code:
verifier /reset



Crashed when running driver verifier
  1. Reset driver verifier
  2. Boot in normal mode if necessary
  3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs
 
Which selection do I make on the "What drivers to verify" screen? Same as the guide on TenForums? Once I know I'll be back in a couple days with the info.
 

Attachments

  • Untitled.png
    Untitled.png
    8.3 KB · Views: 142
Alright so, I return with some info.

I ran Driver Verifier for about 36 hours, could not get it to BSOD, though it did bog down hard a few times. Expected. Feeling disappointed I did some more googling, and a friend sent me a link to an article about my CPU and Mobo combination.

Followed the directions to turn off AMD Application Power Management Master Mode in BIOS. No bogging since. I've streamed for hours at a time now with no issues.

Thank you so much for every step and bit of advice you've offered me, one last thing before I mark solved... what the heck is this and when did it get turned on?!
 
Last edited:
AMD APM feature is a feature that regulates the speed of the processor depending on the usage. It may alter the frequency and voltage to stay under TDP limit.
 
Well, it's turned off now and I've had zero problems... I wish I'd known about this sooner, I could have spared you a lot of hard work. Thank you so much for all your help.
 
It's no problem, we've been able to tackle a Windows corruption (special thanks to @softwaremaniac for providing the fix) and filesystem issue that could've caused you future issues so it's a win-win situation for you :)
 
Just looked up the APM setting in your motherboard manual, the default setting looks to be 'automatic' which is to let the BIOS regulate the setting.
 
Back
Top