But the log aren't lying, you had a win32 error code #13 when DDU ran SetupAPI. I'll probably check my SSD after the clean install and see if there's a problem with it, but I probably won't ever touch DDU again. Needless to say, I will probably perform a reinstall of the OS, but I highly doubt any problems existed because after DDU uninstalled the driver, network services stopped working, options to reset the PC didnt work when troubleshooting, and commands such as sfc /scannow weren't working either. I had 0 issues until I ran DDU earlier this morning. Hi, send me the DDU logs at Īlso, what do you mean by the Cpu is not recognized? With the bios or device manager?Īlso, there is only a very small chance that DDU is at cause because like you said, you ran it multiple time and DDU code doesn't change much from version to version as it is quite mature and if DDU was at cause, you probably would have this problem under an old version too. I'm not exactly sure what happened, but all I know is upon running DDU (the clean drivers and restart computer option in safe mode) Windows stopped working properly, and I don't know what to do from here. I was forced to unplug the power, and once it booted up Windows seem to be working very badly: Network connection services do not work (even though I can still connect to my network just fine on my phone and other laptops still), hardware is no longer recognized (E.G doesn't recognize my I5 4690 CPU anymore),
I was running version 378.49 NVIDIA driver, and when I DDU'ed it in safe mode, the computer restarted really slowly and couldn't boot up properly. Also, I have system restore disabled on my OS, with no backups currently. I have used DDU multiple times before this with no errors.
I'm using no additional software for OC'ing, but I do use MSI Afterburner to set my own custom fan speed on the card. I am running a Windows 10 OS (Pro), with an NVIDIA Gtx 960 (manufactured by EVGA). So I had just installed the newest version of DDU today, version 17.0.5.3
0 kommentar(er)
