kiddingguy Posted October 20, 2020 Share Posted October 20, 2020 On my new Asus VivoBook I have - from this morning on - the message when booting up the error: DPC_WATCHDOG_VIOLATION error Might this have something to the KB4579311 update installed last week? I see numerous reports on errors and alike. What do you guys think? I can uninstall this, but if it doesn't solve it... why bother. I run Windows 10, May update (2004) with all latest updates installed. Link to comment Share on other sites More sharing options...
Sulphy Posted October 20, 2020 Share Posted October 20, 2020 Have you updated all firmwares and drivers (Especially SSD) You should be able to get them from the Asus support site, or use the built in Asus Management application (I forgot what its called.... ) Link to comment Share on other sites More sharing options...
goretsky Supervisor Posted October 20, 2020 Supervisor Share Posted October 20, 2020 Hello, I often see those show up when failing RAM is installed in the computer. Have you tested the computer's RAM for errors by running a program like MemTest86 over night? The free version is more than adequate for this kind of test. Regards, Aryeh Goretsky Link to comment Share on other sites More sharing options...
adrynalyne Posted October 20, 2020 Share Posted October 20, 2020 How would you uninstall it? Is it not every boot? What about Safe Mode? Link to comment Share on other sites More sharing options...
kiddingguy Posted October 20, 2020 Author Share Posted October 20, 2020 1 hour ago, Sulphy said: Have you updated all firmwares and drivers (Especially SSD) You should be able to get them from the Asus support site, or use the built in Asus Management application (I forgot what its called.... ) Everything has been updated via either (My)Asus or driver-tools like Intel's Driver & Support Assistant. 1 hour ago, goretsky said: Hello, I often see those show up when failing RAM is installed in the computer. Have you tested the computer's RAM for errors by running a program like MemTest86 over night? The free version is more than adequate for this kind of test. Regards, Aryeh Goretsky My VivoBook is just 1,5 weeks old... can RAM go bad so fast? Or was is faulty when opening the box? Link to comment Share on other sites More sharing options...
helpifIcan Posted October 20, 2020 Share Posted October 20, 2020 Possibly 56 years in the business installing and maintaining computers the hardest issue has all ways been ELF, (early life failure), means problems that arise in the first 6 months after a new install. Link to comment Share on other sites More sharing options...
spikey_richie Posted October 20, 2020 Share Posted October 20, 2020 Turn on minidumps, let it BSOD then open the dump file with WhoCrashed. It'll give you an indication of where the error lies. Also as said, try a Memtest and/or Prime95 to check your RAM and CPU. Link to comment Share on other sites More sharing options...
+Warwagon MVC Posted October 20, 2020 MVC Share Posted October 20, 2020 Does the error only show up when turning the computer on from being shut down from inside windows, or is it on a restart from inside windows too? If it's when you turn the computer on it could be a fastboot issue. By default, when you turn a windows 10 machine off, it's a hibernation shutdown hybrid. So when you turn the computer back on it's not doing a cold boot, but instead, resuming the subsystem of windows. You could try turning off hibernation from the command prompt (with admin rights) with powercfg -h off (or on to turn it back on) and then see if it still happens. Link to comment Share on other sites More sharing options...
kiddingguy Posted October 20, 2020 Author Share Posted October 20, 2020 24 minutes ago, warwagon said: Does the error only show up when turning the computer on from being shut down from inside windows, or is it on a restart from inside windows too? If it's when you turn the computer on it could be a fastboot issue. By default, when you turn a windows 10 machine off, it's a hibernation shutdown hybrid. So when you turn the computer back on it's not doing a cold boot, but instead, resuming the subsystem of windows. You could try turning off hibernation from the command prompt (with admin rights) with powercfg -h off (or on to turn it back on) and then see if it still happens. Not on every cold boot. When restarting Windows is acting as it should (restart from inside Windows). Link to comment Share on other sites More sharing options...
kiddingguy Posted October 20, 2020 Author Share Posted October 20, 2020 27 minutes ago, spikey_richie said: Turn on minidumps, let it BSOD then open the dump file with WhoCrashed. It'll give you an indication of where the error lies. Also as said, try a Memtest and/or Prime95 to check your RAM and CPU. Minidumps turned on.... spikey_richie 1 Share Link to comment Share on other sites More sharing options...
spikey_richie Posted October 20, 2020 Share Posted October 20, 2020 1 minute ago, kiddingguy said: Minidumps turned on.... https://www.resplendence.com/whocrashed when you have the dump file Link to comment Share on other sites More sharing options...
goretsky Supervisor Posted October 21, 2020 Supervisor Share Posted October 21, 2020 Hello, You could have received a computer with defective RAM. While early-life failures are rare, they do happen. Regards, Aryeh Goretsky Link to comment Share on other sites More sharing options...
spaceelf Posted October 21, 2020 Share Posted October 21, 2020 It might well be update related in this case, and sometimes the software OEMs install on their computers are more problems than solutions. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now