Fix 0xc1900101 DPC_WATCHDOG_VIOLATION GSOD

%3CLINGO-SUB%20id%3D%22lingo-sub-1887775%22%20slang%3D%22en-US%22%3EFix%200xc1900101%20DPC_WATCHDOG_VIOLATION%20GSOD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1887775%22%20slang%3D%22en-US%22%3EHello%20everyone!%3CBR%20%2F%3E%3CBR%20%2F%3ERecently%20for%20the%20past%20few%20release%20previews%2C%20after%20updating%20sometimes%20you%20might%20get%20interrupted%20by%20a%20GSOD.%20I've%20got%20a%20lot%20of%20experience%20with%20these...%20And%20they're%20the%20worst.%20But%20this%20one%20in%20particular%20bugs%20be%20a%20lot%2C%20because%20many%20deal%20with%20it.%20So%20I%20wanted%20to%20share%20my%20confirmed%20fix%2C%20that%20I%20worked%20on%20with%20another%20Insider.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20works%20for%20the%200xc1900101%20DPC_WATCHDOG_VIOLATION%20error.%3CBR%20%2F%3E%3CBR%20%2F%3EStep%201.%20Uninstall%20previous%20release%20preview.%20DO%20NOT%20restart.%3CBR%20%2F%3EStep%202.%20Do%20a%20disk%20cleanup%2C%20clean%20system%20file%2C%20remove%20previous%20versions.%3CBR%20%2F%3EStep%203.%20Delete%20C%3A%2FWINDOWS%2FSoftwareDistribution%20(it%20will%20be%20D%3A%2FWINDOWS%2FSoftwareDistribution%20on%20some%20systems)%3CBR%20%2F%3EStep%204.%20Now%20you%20should%20be%20able%20to%20install%20the%20update%20without%20any%20issues.%3CBR%20%2F%3E%3CBR%20%2F%3E*For%20optimal%20use%20after%20the%20update%2C%20don't%20forget%20to%20do%20a%20disk%20cleanup%20after%20to%20remove%20the%20previous%20stuff%20left%20over!%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20this%20can%20help%20someone%20out!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1891420%22%20slang%3D%22en-US%22%3ERe%3A%20Fix%200xc1900101%20DPC_WATCHDOG_VIOLATION%20GSOD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1891420%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F802383%22%20target%3D%22_blank%22%3E%40Angelina2552%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20sharing%2C%20there%20is%20article%20discussing%20about%20Blue%20Screen%20error%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fsbs%2Fwindows%2Ftroubleshoot-blue-screen-errors-5c62726c-6489-52da-a372-3f73142c14ad%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fsbs%2Fwindows%2Ftroubleshoot-blue-screen-errors-5c62726c-6489-52da-a372-3f73142c14ad%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20case%20you%20enable%20Microsoft%20to%20collect%20log%2C%20dump%20files%20will%20be%20shared%20with%20Microsoft%20and%20user%20could%20also%20share%20the%20issue%20through%26nbsp%3B%3CSTRONG%3EFeedback%20Hub%26nbsp%3B%3C%2FSTRONG%3Eapp.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1908339%22%20slang%3D%22en-US%22%3ERe%3A%20Fix%200xc1900101%20DPC_WATCHDOG_VIOLATION%20GSOD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1908339%22%20slang%3D%22en-US%22%3EThe%20latest%20update%20has%20fixed%20all%20the%20GSODs%2C%20at%20least%20all%20the%20known%20ones%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.windows.com%2Fwindows-insider%2F2020%2F11%2F18%2Fannouncing-windows-10-insider-preview-build-20262%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.windows.com%2Fwindows-insider%2F2020%2F11%2F18%2Fannouncing-windows-10-insider-preview-build-20262%2F%3C%2FA%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1909133%22%20slang%3D%22en-US%22%3ERe%3A%20Fix%200xc1900101%20DPC_WATCHDOG_VIOLATION%20GSOD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1909133%22%20slang%3D%22en-US%22%3EThanks%20Reza!%20I'll%20put%20something%20about%20this%20there.%3C%2FLINGO-BODY%3E
Occasional Contributor
Hello everyone!

Recently for the past few release previews, after updating sometimes you might get interrupted by a GSOD. I've got a lot of experience with these... And they're the worst. But this one in particular bugs be a lot, because many deal with it. So I wanted to share my confirmed fix, that I worked on with another Insider.

This works for the 0xc1900101 DPC_WATCHDOG_VIOLATION error.

Step 1. Uninstall previous release preview. DO NOT restart.
Step 2. Do a disk cleanup, clean system file, remove previous versions.
Step 3. Delete C:/WINDOWS/SoftwareDistribution (it will be D:/WINDOWS/SoftwareDistribution on some systems)
Step 4. Now you should be able to install the update without any issues.

*For optimal use after the update, don't forget to do a disk cleanup after to remove the previous stuff left over!

Hope this can help someone out!
9 Replies

@Angelina2552 

Thank you for sharing, there is article discussing about Blue Screen error:

https://support.microsoft.com/en-us/sbs/windows/troubleshoot-blue-screen-errors-5c62726c-6489-52da-a... 

In case you enable Microsoft to collect log, dump files will be shared with Microsoft and user could also share the issue through Feedback Hub app.

Thanks Reza! I'll put something about this there.
Alright. That's strange to hear since when I did the update last night I got the DPC_WATCHDOG_VIOLATION GSOD during the update.
There is a BSOD/GSOD crash dump analyzer called WhoCrashed,
that might come handy if you want to find out more about the cause of it

@Angelina2552 0xc1900101 error is a generic error, usually driver related. Watchdog bugchecks are usually caused by drivers as well. This could very well be a different issue. Recommend you start by ensuring all your drivers are running the latest from the device manufacturer's website. Do not update using Device Manager or Windows Update. Please manually get the latest ones. Should your problem persist, please log it in Feedback Hub and share the link.

 

-Eddie

Yes, it can definitely be driver related. I've experienced that in other systems before that aren't running Insider Preview Builds. I didn't know that getting the builds directly online could solve the issue, I'll definitely try that. Thanks!

@Angelina2552 Seems I may have caused some confusion. Windows builds should still come from WU. The device drivers (network card, etc.) should come from the device manufacturer's website.

 

-Eddie

My apologies. That makes more sense. I already get all driver updates from the manufacturer. I'll double check and see if any require any additional updates.