Help DCP Watchdog Violation

[LeRavenNight]

Correction says windows on volume 1. That one works fine. The one that says Windows 10 immediately says to repair.

[jmarket]

I used to have DCP Watchdog Timeouts myself a while back until I upgraded to 1909. I haven’t had any since.

I personally run a beta build of Windows 10 and I haven’t had any issues.

[LeRavenNight]

It’s reinstalling windows now.

[LeRavenNight]

Finished reinstalling. Can get into settings now. Says version is 2004

[LeRavenNight]

Seems fine so far. Event viewer did have 1 or 2 dcom errors. I’ll probably just leave it on desktop and go wash the car, give it some time to see if it crashes.

[LeRavenNight]

Was hoping it was solved this time. My pc ran for 5 hours yesterday with no crashes and ran some games for an hour. Booted it up today. Very fast load but as soon as I put in my password, bluescreen again. Starting to get to my wits end. It was working perfect a few weeks ago.

[LeRavenNight]

I’ll have to type this out on my phone as my pc crashed twice trying to type this. I’ve had a few more crashes since last. Event viewer was showing a bunch of distributed com warnings for Windows security. Were as my pc lasted for 5 hours running fine last weekend after jmarket suggested resting windows, now it is crashing like clockwork, even at the login screen if I just leave it. Is there any chance this could be caused by damsmaged hardware? And would it be helpful if I provided another synsative dump after the reinstall I did and the 3 recent crashes? You guys really are my last hope, otherwise I might just have to fork out the money and take it in to a repair shop. In the event that’s the case thank you for the help you have already given.

[jmarket]

Yes please. Upload the most recent dumps if you can

[LeRavenNight]

Sorry for the late reply. I had a funeral on. Here is the file you requested. I hope it helps.

[phillpower2]

Each one of your latest crashes was caused by the same [COLOR=rgb(41, 105, 176)]rtwlanu.sys drivers that I mentioned back in my replies #4 and #6, you need to find and delete these drivers from whatever drive they are on.

Create a new system restore point.

Look under Network adapters in Device Manager to see if there is any network device other than the Simplecom that you presently have, if not there, look under the USB devices.

If you find any network device other than the Simplecom that you presently have, uninstall it/them, restart, test then post back with an update for us.[/COLOR]

[LeRavenNight]

Hey Phill, just saw your comment. I removed the driver and ran my pc today without wifi. The computer ran fine, no errors whatsoever. I also made the system recovery while it was running. Rtwlanu.sys is the driver for this specific wifi adapter, which I guess means its useless. I tried reinstalling a newer version but that made it crash faster. I didn’t think a wifi adapter could cause bsod, it was a cheap one. I have my old d link adapter that uses a different driver. I think i will just go back to that since it worked for years. My apologies for dragging this out for so long. You have been immensely helpful.

[phillpower2]

I[ICODE]ve never been a fan of anything that uses another companies components and then rebrands them as their own, as you have found it doesn[/ICODE]t tend to work out too well when it comes to the drivers for the device/s.

If the D - Link still works ok you could stick to what you mention above but if me I would try something else with the Simplecom/Realtek device first, see what happens if you restart the computer without the rtwlanu.sys drivers installed to see if Windows loads any generic drivers for the device that allows the system to run stable.

Just a fyi, as long as folk keep their threads updated we never have an issue with how long it takes to resolve an issue.

You are welcome btw