DPC_WATCHDOG_VIOLATION

[2G_Tony]

I've recently brought life back to my PC by replacing the motherboard (I broke it about a year ago). Well, after installing Windows 10 I can't boot into normal mode. It just keeps crashing and I get the DPC_WATCHDOG_VIOLATION BSOD. I've tried updating the BIOS, the GPU drivers, the chipset (which Im not sure if I actually updated it completely because it required internet connection, something I cannot access), and a few solutions such as check disk, etc.  

I'm not sure if it's a motherboard issue, a GPU issue, or a SSD issue. If it's any consolation, I've gotten the same issue on both SSDs (Kingston SSDnow and Silicone Power). 

 

Any advice will be greatly appreciated. I just really would like to get my PC back up and running.  

[BrinkGG]

1 minute ago, DarkenedTrial said:

I've recently brought life back to my PC by replacing the motherboard (I broke it about a year ago). Well, after installing Windows 10 I can't boot into normal mode. It just keeps crashing and I get the DPC_WATCHDOG_VIOLATION BSOD. I've tried updating the BIOS, the GPU drivers, the chipset (which Im not sure if I actually updated it completely because it required internet connection, something I cannot access), and a few solutions such as check disk, etc.  

I'm not sure if it's a motherboard issue, a GPU issue, or a SSD issue. If it's any consolation, I've gotten the same issue on both SSDs (Kingston SSDnow and Silicone Power). 

 

Any advice will be greatly appreciated. I just really would like to get my PC back up and running.  

Windows 10 installs are locked to the motherboard. You will need to call Microsoft and have them reactivate your windows 10 key. 

[2G_Tony]

4 minutes ago, Brink2Three said:

Windows 10 installs are locked to the motherboard. You will need to call Microsoft and have them reactivate your windows 10 key. 

Sorry but I don't understand lmao. How are they locked? And are you saying that if I hypothetically was going to crack it I would need a preactivated version? 

[redteam4ever]

From my very recent knowledge, watchdog is program malfunction prevention mechanism that works like a decreasing counter that terminates the process in case of an unexpected problem. When process runs, it periodically resets the watchdog to its original value. When something causes the process to freeze or run into problems and the process cannot run anymore, counter reaches zero and terminates the process. When this happens to a critical system process, whole operating system crashes.

 

I think that this might be a software issue as well as a hardware issue. Quick Google search suggested manually installing the SATA driver in Device Manager: http://www.tomshardware.co.uk/faq/id-3128566/fix-windows-error-dpc-watchdog-violation.html

[2G_Tony]

6 minutes ago, redteam4ever said:

From my very recent knowledge, watchdog is program malfunction prevention mechanism that works like a decreasing counter that terminates the process in case of an unexpected problem. When process runs, it periodically resets the watchdog to its original value. When something causes the process to freeze or run into problems and the process cannot run anymore, counter reaches zero and terminates the process. When this happens to a critical system process, whole operating system crashes.

 

I think that this might be a software issue as well as a hardware issue. Quick Google search suggested manually installing the SATA driver in Device Manager: http://www.tomshardware.co.uk/faq/id-3128566/fix-windows-error-dpc-watchdog-violation.html

I tried that. It did nothing for me. 

[samcool55]

8 minutes ago, redteam4ever said:

From my very recent knowledge, watchdog is program malfunction prevention mechanism that works like a decreasing counter that terminates the process in case of an unexpected problem. When process runs, it periodically resets the watchdog to its original value. When something causes the process to freeze or run into problems and the process cannot run anymore, counter reaches zero and terminates the process. When this happens to a critical system process, whole operating system crashes.

 

I think that this might be a software issue as well as a hardware issue. Quick Google search suggested manually installing the SATA driver in Device Manager: http://www.tomshardware.co.uk/faq/id-3128566/fix-windows-error-dpc-watchdog-violation.html

Why would that even be a thing? I honestly can't see the point of it...

[redteam4ever]

10 minutes ago, DarkenedTrial said:

I tried that. It did nothing for me. 

OK, then you can give us more information. Left-click the Start button and choose Event Viewer. In the left menu select Windows Logs -> System. Look for recent errors, the BSOD record should be listed in source column as Kernel-Power. When you double-click the event there will be more error codes and location of a memory dump that can be analyzed with a program like WhoCrashed.

[redteam4ever]

12 minutes ago, samcool55 said:

Why would that even be a thing? I honestly can't see the point of it...

I was just trying to suggest the most popular solution that I didn't see listed. Now I replied with more troubleshooting steps that can help narrow down possible sources of this problem.

[samcool55]

Just now, redteam4ever said:

I was just trying to suggest the most popular solution that I didn't see listed. Now I replied with more troubleshooting steps that can help narrow down possible sources of this problem.

Yeah but you seem to know what it does so i was wondering if you knew more details about it...

Maybe not the best way to ask it but i'm tired D:

[2G_Tony]

Yeah, I was AFK for about wrapping up my taxes. I'll get on it now though.

[redteam4ever]

8 minutes ago, samcool55 said:

Yeah but you seem to know what it does so i was wondering if you knew more details about it...

Maybe not the best way to ask it but i'm tired D:

Oh, you were talking about the watchdog? I thought that you were talking about my solution...

 

Watchdogs can be useful especially in systems that are hardly reachable. Imagine that you send some machine to Mars and due to some bug the whole operating system freezes (example: entering an infinite loop due to some unexpected behavior). You can't control it, because OS is not responding and you can't hard reset it because it's too far. That's why we use watchdogs.

Edited April 10, 2017 by redteam4ever
GRAMMAR -_-

[samcool55]

2 minutes ago, redteam4ever said:

Oh, you were talking about the watchdog? I thought that you were talking about my solution...

 

Watchdogs can be useful especially in systems that are hardly reachable. Imagine that you send some machine to Mars and due to some bug the whole operating system freezes (example: entering an infinite loop due to some unexpected behavior). You can't control it, because OS is not responding and you can't hard reset it because it's too far. That's why we use watchdogs.

Yes i was talking about watchdog, there's nothing wrong with the suggested solution

 

In the case you described i can see why it matters. But i can't see it being useful in like 99% of windows systems. I mean with most of them you are right in front of them, not stupidly far away

 

If it was only in the Server or Enterprise versions it would make sense, but for the normal versions, a bit weird...

[2G_Tony]

There are over 1,200 errors under the system tab lmao. I'm not sure what to really do from this point. 

[2G_Tony]

Not sure if this will help but here it is

system log.evtx

[redteam4ever]

Just now, samcool55 said:

Yes i was talking about watchdog, there's nothing wrong with the suggested solution

 

In the case you described i can see why it matters. But i can't see it being useful in like 99% of windows systems. I mean with most of them you are right in front of them, not stupidly far away

 

If it was only in the Server or Enterprise versions it would make sense, but for the normal versions, a bit weird...

That is a good point, but you will need to ask Microsoft about that. But I can see their angle - most users do not fully understand how software works, so this gives them a clear message that there is a problem that needs solving. Also, the correction mechanisms create a memory dump for analysis and let you know where the problem lies in an user-friendly(ier?) way.

 

And the second angle is - if this protection mechanism is used on thousands of places throughout the OS - why would someone be removing it? Removing it would probably create more problems.

[redteam4ever]

4 minutes ago, DarkenedTrial said:

Not sure if this will help but here it is

system log.evtx

OK, so it looks like that your last BSOD happened around 0:33, the error codes are: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff802c09ee348, 0x0000000000000000). The first one is the main error code, the ones in braces are individual problems. The memory dump is located here: C:\Windows\MEMORY.DMP. Memory dump is a copy of your memory, so this could be a huge file - I don't know if you can upload that.

 

I'm sorry that I pointed you to wrong events - right ones were Critical + Kernel-Power and Error + BugCheck. I couldn't remember the exact names.

 

So, I googled the error codes and this should be a driver issue. Analysing with WhoCrashed should give us more insight. Download and run the application. It should be pretty straightforward to spot the problem.

[2G_Tony]

1 hour ago, redteam4ever said:

OK, so it looks like that your last BSOD happened around 0:33, the error codes are: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff802c09ee348, 0x0000000000000000). The first one is the main error code, the ones in braces are individual problems. The memory dump is located here: C:\Windows\MEMORY.DMP. Memory dump is a copy of your memory, so this could be a huge file - I don't know if you can upload that.

 

I'm sorry that I pointed you to wrong events - right ones were Critical + Kernel-Power and Error + BugCheck. I couldn't remember the exact names.

 

So, I googled the error codes and this should be a driver issue. Analysing with WhoCrashed should give us more insight. Download and run the application. It should be pretty straightforward to spot the problem.

The only device I have is my phone so it's going to be near impossible to do any of that  

[redteam4ever]

Just now, DarkenedTrial said:

The only device I have is my phone so it's going to be near impossible to do any of that  

I guess that you are running in Safe Mode, right? You should be able to choose Safe Mode with Networking - that will load the network drivers giving you access to the internet.

[2G_Tony]

1 hour ago, redteam4ever said:

I guess that you are running in Safe Mode, right? You should be able to choose Safe Mode with Networking - that will load the network drivers giving you access to the internet.

Yeah, it does. But I'm using a wireless adapter that doesn't work very well with Windows 10, I'll try to fix it though. 

[redteam4ever]

5 minutes ago, redteam4ever said:

OK, so it looks like that your last BSOD happened around 0:33, the error codes are: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff802c09ee348, 0x0000000000000000). The first one is the main error code, the ones in braces are individual problems. The memory dump is located here: C:\Windows\MEMORY.DMP. Memory dump is a copy of your memory, so this could be a huge file - I don't know if you can upload that.

 

I'm sorry that I pointed you to wrong events - right ones were Critical + Kernel-Power and Error + BugCheck. I couldn't remember the exact names.

 

So, I googled the error codes and this should be a driver issue. Analysing with WhoCrashed should give us more insight. Download and run the application. It should be pretty straightforward to spot the problem.

I'm kind of worried about the third error code - 0xfffff802c09ee348. I couldn't find any info about it and it also is a very big number (in case you didn't know - it's a hexadecimal number and it equals 18446735289438102344). Error codes  aren't that big. This still might be a hardware failure... What happened to your last board?

[2G_Tony]

Okay, so I managed to download and install the program and hit analyze. The conclusion was something to do with nvlddmkm.sys

[2G_Tony]

1 hour ago, redteam4ever said:

I'm kind of worried about the third error code - 0xfffff802c09ee348. I couldn't find any info about it and it also is a very big number (in case you didn't know - it's a hexadecimal number and it equals 18446735289438102344). Error codes  aren't that big. This still might be a hardware failure... What happened to your last board?

I broke the PCI port lmao. If it is a hardware error, it could be my GPU. I just got it back from EVGA after they did an RMA though. 

[redteam4ever]

1 minute ago, DarkenedTrial said:

Okay, so I managed to download and install the program and hit analyze. The conclusion was something to do with nvlddmkm.sys

Nvlddmkm.sys is NVIDIA Windows Kernel Mode Driver file. Try reinstalling your GPU drivers. If it doesn't help, problem might really be the GPU itself.

[2G_Tony]

1 hour ago, redteam4ever said:

Nvlddmkm.sys is NVIDIA Windows Kernel Mode Driver file. Try reinstalling your GPU drivers. If it doesn't help, problem might really be the GPU itself.

Alright. I'm going to try installing 362.00 and if that doesnt work I'll try Windows 8.1. And if that still doesn't work I'll yell at EVGA.

[redteam4ever]

6 minutes ago, DarkenedTrial said:

Alright. I'm going to try installing 362.00 and if that doesnt work I'll try Windows 8.1. And if that still doesn't work I'll yell at EVGA.

Actually, we can rule out the GPU malfunction because the Safe mode is running alright. Only difference is that Safe Mode uses Microsoft Generic Graphic Driver. I was mislead by the suspicious error code.

Edited April 10, 2017 by redteam4ever
Improved readability