BSOD (DPC_WATCHDOG_VIOLATION) with Skype, OBS and Starcraft 2

Maarsch

Distinguished
Sep 14, 2012
684
0
19,360
So I've been getting freezes lately.
Mostly it resolves into a bluescreen, the DPC Watchdog violation, but sometimes I don't let it just hangs till I get bored and I press the actual hardware power button.

Event viewer record Kernel power 41 error

This happens when I engage in a video call with Skype, am in Starcraft 2 and have OBS studio open (actually broadcasting seems to be irrelevant).
If I cut out any of these three it doesn't seem to happen, although I'm not entire sure about this, but with the 3 it is a very reliable BSOD.
I have used hangouts and zoom for video with discord for audio and I had no problems.
I have also used other programs that utilize stuff a lot, video editing while uploading and playing games. No problem.

This seems to have appeared around the time of the anniversary update, My OS is Win 10.

Obligatory spec post:
i5-3570 (non-K)
Cooler master 212 (not-evo, I think)
Z77 Pro3
MSI Gaming X GTX1060 6GB (This one is also new, but I had some months of worry free recording after switching from MSI to Nvidia drivers)
OCZ Agility 3 SSD
Seagate green 2TB HDD
16 GB RAM (Corsair)

Things I've tried:

  • Changed IDE ATA/ATAPI controller to standard SATA AHCI controller (I actually just changed that back to intel 7 series chipset sata ahci controller)
    Disabled quick boot
    Updated GPU drivers
    Memory test
    Chkdsk (both)
    SFC
    Windows 10 disc error check
    Updated most other drivers probably
    Scanned for virusses
    Scanned for malware
    Skype app rather than skype . . . program?
    OBS studio 32 bit
    Uninstalled/re-installed all the programs
    Temperatures (I don't overheat)
    Probably some other things I can't think to name now.

Things it could still be/could still check

  • PSU?
    Re-install win10
    Stuff?
    Change of power strip?

Anyone have any ideas?
Am I even right focusing on this software combination? Or mentioning the anniversary edition? Should I ignore the GTX1060, it is newish.
 
If you didnt press the on/off button Kernel power 41 error can mean a faulty PSU

That stop error can be cpu related. Updating the BIOS may fix it

If it wasnt on AHCI (if it was on IDE), when you installed Windows, dont change it AHCI after you install windows. It'll crash

Upload the small dmp files to onedrive then post the link


 

Maarsch

Distinguished
Sep 14, 2012
684
0
19,360


I got a PSU tester on the way home.
I might still upload a DMP file (I updated the BIOS as well in previous attempts, just forgot to mention it)
But I think the PSU might just be the issue
msIUSI5.jpg


It was beeping too


Edit: can't see pic on mobile. http://m.imgur.com/msIUSI5
 

Maarsch

Distinguished
Sep 14, 2012
684
0
19,360
Just happened with my workaround of discord for audio and hangouts for video

I guess I'll go back to testing whether just sc2 and obs cause it or whether a video being sent to me (decrypting video?) is required.
 
Uninstall Asrock Extreme tuner. This file is 6 yrs old AxtuDrv.sys.

Update Intel(R) Smart Connect Technology Device Driver the drivers for it are 5 yrs old

Update or uninstall Manycam, this file mcaudrv_x64.sys is 4 yrs old

Your logitech cam drivers lvrs64.sys are 5 yrs old






 

Maarsch

Distinguished
Sep 14, 2012
684
0
19,360



  • asrock - uninstalled
    smart - uninstalled, disabled in bios
    manycam - uninstalled
    webcam - got latest drivers (which are 4 days older than previously used ones)

Running stability test now. So far OBS has crashed once, but no BSOD yet.
May run again w/o webcam if it fails with current setup.

The C920 is such a mainstay in 1080p webcams, it's still on every recommendation list of webcams, I'd be surprised if this was what was causing it.
But I'm not ruling it out.
 

Maarsch

Distinguished
Sep 14, 2012
684
0
19,360
Meh . . . inelegant solution.

But necessary apparently
CPU usage of both SC2 and OBS while broadcasting has reduced. I can get through a broadcast with about 20% less CPU usage now.

Still don't know what the issue was though.
Other than gradual cloggage of Windows arteries . . . or something.