DPC Watchdog breach during upgrade to version 10
DPC Watchdog breach during upgrade to version 10
I experience random DPC Watchdog Violations during BSODs on my old machine. It's a desktop built around 2007 or 2008. My main use is playing Civilization 5 and Oblivion. I last used it in 2011 with Windows 7, thinking an upgrade to 10 would help. I replaced the boot drive with a second-hand Kingston SSDNow 300, which worked in Windows 7 during the download wait. After reinstalling the graphics drivers and checking chipset support, they only list compatibility up to Windows 7. NICs, Realtek audio, and my cheap Tenda Wi-Fi card also don't show any support for Windows 10. I disabled the Tenda card in Device Manager to rule it out. Games run smoothly without the crash, though. Here are my specs: AMD X2 5800+, 2.8GHz (no OC), 4GB Crucial Ballistix DDR2-800, GeForce 8800GT 512MB MSI K9N SLI with nForce 570 chipset, 120GB Kingston SSDNow 300, and a 500GB Samsung drive (has many bad sectors). I plan to replace it soon once the BSOD issue is fixed. Do you have any additional details?
It’s clearly the hardware watchdog that triggers when my OC isn’t stable—possibly due to RAM or the CPU. I believe the games won’t perform well on an 8800GT. It might be wise to save up for a better system.
Thanks for the update. I didn't find much success with that either... the attached photo doesn't show anything relevant. I looked at the three iastor devices and none had similar content—they all use atapi.sys from Dennis de Rooij [NL]. I consistently get over 50fps with Oblivion, especially on the top GPU when it launched (7900 GTX!). My screen resolution is also low. In Civ 5, the FPS stays above 100 on the same hardware before Windows 10.
In the past hour I reviewed the logs and identified the issue as ntoskrnl.exe+16bf70. Google didn’t clarify its meaning. I made a few adjustments: - Reinstalled the nForce storage controller from Nvidia’s site. It listed Windows 7/Vista, though I’m still checking that possibility. - In BIOS, the memory was running at 667MHz. I even removed a stick to confirm it wasn’t DDR2-6400 as I thought. I set the clock speed to 800MHz manually. The only BIOS changes were during a recent OS clone on the SSD last week—odd! I’ll run a memtest if the problem recurs, though I doubt hardware failure since only the software changed. I’ve been running smoothly for the past week. Ugh, Windows 10, I shouldn’t have touched it! Note—since I posted this, I haven’t seen any BSODs in about 80 minutes.
Update - the issue hasn't been resolved. Memtest single pass showed no problems. It might be the failing disk itself, given several bad sector warnings in the system log. There seems to be a link between crashes and frequent heavy disk use, though it's not clear. Any suggestions?