dpc_watchdog_violation - bsod Win 8.1

[Teddy]

Hi,

Back when Windows 10 was released I made the apparent fatal mistake of updating to it. I immediately became haunted by repeating issues, it was first a random "lockup" caused by my 970, which I have since sent back due to it being a memory leak, in immediate effort to fix this I reset windows 10 and got raped by a new error, a bsod with dpc_watchdog_violation. So severe I got the error even during safe mode (all safe modes). I did the next logical step to do a fresh install of Windows 8, which I did yesterday. I was met with a random error during the windows 8.1 update last night so I restarted with 8 again this morning and everything was going well, updated from 8 fresh to 8.1 and just as I start installing things.. bsod. dpc_watchdog_violation again.. thanks Aiden.

I'm seriously out of options at this point. I can't get into safe mode long, I can't really do anything without a crash.

I have a Samsung 850 Pro SSD, WD Black Series as storage, and currently using my old NVIDA GTX 760 TI while I get refunded from the defunct GTX 970.

Any ideas?

[Leroy_Kolta]

The above issue is being resolved/discussed via Skype PM.

[Leroy_Kolta]

Resolved.

[Teddy]

Unresolved

Fix was temporary, longer than normal but occurring again :/

[Axison]

Sad to hear.


I, actually my brother experienced this issue with his pc while updating to W10 or W8 . He said he gave up and the computer wasn't used for a while. He then turned it on after a few months(2 and a half) and it worked all fine, no bsod's after that. It works perfectly. He said he didn't do anything but let the computer sit at its spot.

Why don't you purchase  new gear if it isn't working out for you?

[CharlieKasper]

I had this error for the first time on the day I clean installed Windows 10 a few weeks ago. The laptop booted extremely slow and logged into windows even slower. Everything was extremely slow and suddenly got that error.

It did some error running on itself and it never appeared again until a few days ago. Same symptoms... Slow booting, logging in and no start up apps loading.

Would like to know whats causing this..

[Janar]

What was the temporary fix?

[CharlieKasper]

Just had this again. Forgot the mention that before this error occurred the last time and this time, I got the error message that Start menu and cortana have stopped working and asked to me signout and re login. I couldn't close that critical error. Signing out and logging back in doesn't fix it. Rebooting doesn't fix it.


Several attempts later I had BSOD with watchdog warning. Please help. Can't go through reinstalling windows again with this 3rd world internet.

[Leroy_Kolta]

Hmm. Looks like more people have this issue than I anticipated.

Temporary fix - we reset the ram and uninstalled the graphics drivers and installed the basic Microsoft ones and then on top of that updated it with the Geforce Experience software.
Our next step was to unplug the WD Storage device (since it was pegging at 100% utilization) - not sure if this was done yet or not.

[Archie]

The funny thing is, I got that BSOD while I was playing Watch Dogs 

[Leroy_Kolta]

The funny thing is, I got that BSOD while I was playing Watch Dogs 

That's pretty funny. Maybe that's why they named the game that - because people get that BSOD when they play the game lmfao.

[CharlieKasper]

Had this again... I read through some websites and they say it could be fast start up or Avast antivirus causing this.

Do people experiencing this error have Avast and/or fast start up turned on?

EDIT: For the moment I have turned off fast statrup. will return with results

[MrTony]

so you guys all started getting that error from updating to Win10 or what?

[CharlieKasper]

People with W8 had this too. This started for me after doing a clean install to Windows 10 the second time. Upgrading from 8.1 and clean installing the first time didn't cause this..

[Teddy]

so you guys all started getting that error from updating to Win10 or what?

I got a different problem when I upgraded to 10 that I later found a fix to. I first tried clean installing 10 which gave me this problem, I then now clean installed 8/8.1 and this new bsod issue has continued.

Had this again... I read through some websites and they say it could be fast start up or Avast antivirus causing this.

Do people experiencing this error have Avast and/or fast start up turned on?

EDIT: For the moment I have turned off fast statrup. will return with results

I am still getting this on a clean install, without Avast and with Fast Startup turned off

Hmm. Looks like more people have this issue than I anticipated.

Temporary fix - we reset the ram and uninstalled the graphics drivers and installed the basic Microsoft ones and then on top of that updated it with the Geforce Experience software.
Our next step was to unplug the WD Storage device (since it was pegging at 100% utilization) - not sure if this was done yet or not.

I haven't done this yet, was fairly ill yesterday.