Windows 10: BSOD DPC_Watchdog_Violation

Dear Sir/Madame,
I have received a few messages since upgrading to Windows 10 saying my computer needed to restart and that I could find the answer at DPC Watchdog Violation. I have not had this happen while I am using the computer but the message seems to happen when the computer is coming out of sleep or has been sitting idle and I hip enter to use it again. I had a problem several months ago with BSOD that we believed were related to my hard drive needing to be reseated but I had no more problems with BSOD like issues until I upgraded to windows 10 but that did not happen immediately -- only recently.

Additionally, I am getting another message (after startup) stating an error occurred while initializing SQL Server Compact: System.InvalidOperationException:Cannot open 'C:\ProgramData\DDNi\Oasis2Service\Data\Oasis2.sdf'. Provider 'System.Data.SqlServerCe.3.5' not installe. at Sysem.Data.Linq.SqlClient.SqlProvider.System.DAta.Linq.Provider.IProvider.Initialize(IDataServices dataServices, Object connection) at System.Data.Linq.DAtaContext.Init(Object connection, MappingSource mapping) at System.Data.Linq.DataContext.ctor(String fileOrServerOrConnection, MappingSource mapping) at DDNi.Domain.Context.DBContext(Guid context) at DDNi.Domain.Context. tor() at DDNi.Domain.Context.GetInstance() at DDNiDomain.UserBO.GetBO(Func '2 predicate) at DDNi.Domain.UserBO.GEtUser(String username) at DDNi.CenterStage.CenterStage.a(Boolean A_0).

This message happens shortly after the computer restarts and after I open internet explorer (I guess now actually Microsoft Edge). I am not familiar with this new Windows operating system at all and I am still trying to figure out how to get to many of the old tools as well as finding files on my computer. Any assistance you can give me on what I believe to be a BSOD since it is not the same as the original BSOD that would create a dump would be greatly appreciated.

:)

 

New 2520 multiple lockups BSD and reboot

more errors BSOD

DPC_WATCHDOG_VIOLATION



going to send it back

 

Windows 10 build 10586 BSOD DPC_WATCHDOG_VIOLATION

Check (enable) it then do Step #5 & test.

The above notwithstanding...

Are you still getting the DPC_WATCHDOG_VIOLATION BSODs or...?

 

Dear Sir/Madame,
I am attaching the log collector file that I needed in the original message.

Attachment 34028

 

Please upload a new zip file, the attached zip file is empty
Please check {windows partition}\windows\minidump and check if there are any dump files saved.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial

 

I ran the collector again. I tried to view the tutorial on configuring minidumps but the webpage must be down.

Attachment 34035

 

Try again, the link is the same but should work, just updated it.

 

Axe0,
I reconfigured the system for minidumps and ran the collector again.

Attachment 34072

 

Please upload a new zip file, the attached zip file is empty

 

Attachment 34223Attachment 34223Dear Axe0,
I think the problem may be that the data was not collected in the dump the last time there was a BSOD. I think I may have caused that problem by shutting down the computer before the dump collected all of the data. There was a message that said the computer was restarting and it showed the progress of 100% but it did not restart. After about 20 min of seeing that screen I manually powered off the computer and forced a restart -- so I believe now that there was either an error in collecting that data or because I forced the restart that data was lost. I cannot see any other explanation for the collector file to still be empty. I am attaching another file but if it is still empty I think I will just have to wait for another BSOD before running the collector.

 

Dear Axe0,
I think the problem may be that the data was not collected in the dump the last time there was a BSOD. I think I may have caused that problem by shutting down the computer before the dump collected all of the data. There was a message that said the computer was restarting and it showed the progress of 100% but it did not restart. After about 20 min of seeing that screen I manually powered off the computer and forced a restart -- so I believe now that there was either an error in collecting that data or because I forced the restart that data was lost. I cannot see any other explanation for the collector file to still be empty. I am attaching another file but if it is still empty I think I will just have to wait for another BSOD before running the collector.

 

Please check {windows partition}\windows\minidump and check if there are any dump files saved.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial
The configuration of the dump files could be the cause why collecting the data takes so long.

 

I did a search and the only place it finds it is in the collector zip-files. I did reconfigure the system to collect minidumps after you sent me the updated link so as I suspected I will have to wait for another BSOD.