(Solved) BSoD on everyday's first start-up.. (new PC, Windows 10 home)

[shen_ji]

Edit: I think the VPN (ExpressVPN 6.7.2.5163) is the culprit, by disabling it from auto-start, system goes smoothly for several days now.
Following is the original post.

===================OP====================

Hello,

I just built a new PC for my son to play Minecraft. The first week had no trouble. Several days ago, there was an unexpected power cut, then I got this daily BSoD- 'DPC Watchdog violation'-- always in the first 10 minutes on the first start-up of the day, then everything was fine after restart.

(tl;dr, The memory dump link was on the end of the post)

System spec:
Intel G4560,
Kingston 8G DDR4 2400,
Nvidia GT1030 2G/DDR5,
480 watt power unit which bought 3 years ago and never failed.
No overclock.

What I have tried:
Virus check, no issue (Windows defender and Avast! home);
Bought a new SSD and clean installed the Windows (10, home);
Updated drivers (Graphic card, sound and maybe something else in the device management but I can't recall);
Windows Extended memory test without issue;
Chkdsk /f /r /b without issue (but sometimes one 6 years old Seagate hard-disk got really annoying speed reduces);
SFC /scannow, no issue found;
Run windows Verifier on some suspected drivers also no issue found;
Furmark (newest version) stress test the GPU for 3-4 hours without issue;
Speedfan log reports no overheating, CPU under 30'C, GPU and disks all under 40 (room is 28.7)..

Every time, the system stopped respond first, then within 3 to 5 seconds, the mouse pointer frozen, while sound stuttered first then totally cut off.

Checked the memory dump by Nirsoft's BlueScreen view, crash was always caused by the ntoskrnl.exe but no other (dump file link was on the end of this post).

///In one occasion, system recovered itself, and event-viewer recorded a graphic-card driver fail, but since I tested the graphic-driver a lot, I'm not sure about it. Also updated the driver, then uninstall-reinstalled and clean installed it but noting helps///
I think maybe the graphic card has some problem not still not sure, since I stress tested it a lot and found no issue yet.

Other than that, event-viewer didn't record much useful before the crash. But it did report some errors, though I didn't know if it's related to my problem. I just listed them here:
================================
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscDataProtection
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
================================
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
================================
(These two errors were recorded couple of minutes before the crash.)

Now the most suspicious part was graphic-card or memory chip, could anyone point out exactly which one please? Or I'll exchange both of them, and hope things will be fine.. And I am quite curious about why looks like the bug only affects my system on the first start-up? What magic stopped it from wrecking the system again during the rest of the day? (A lazy bug?)

And the most recently dump file is here:
https://1drv.ms/u/s!An7ryidTdTPTiRkgFUkFU8hCS_RP

Any help or suggestion will be appreciated!

SJ

 

[Kashimi]

DPC Watchdog violation is an SSD issue.

http://www.tomshardware.com/faq/id-3128566/fix-windows-error-dpc-watchdog-violation.html

If the GPU drivers are showing as failing it seems like the power cut may have damaged your components.

 

[shen_ji]

Thanks for your reply.

The crash happened before I installed the SSD, before that I was using a hard-disk as boot disk. And I recalled that I tried the AHCI Controller update before I installed the SSD, but no luck.

And the graphic card is primary suspect now, I'm thinking about find and install an old card now..

 

[Kashimi]

I'd suggest trying the old GPU, also try to update your windows creation media to allow you to not have to update. That should help you with the SSD issue, but it would require a clean install of windows.

 

[shen_ji]

I think the culprit is the VPN (ExpressVPN 6.7.2.5163, I'm behind the GFW), it possibly caused some kind of driver conflict. For some unknown reason, when it was set to auto-start with Windows, it caused some kind of trouble(event viewer recorded some vpn related errors and warnings but were overlooked by me). Then I just disabled VPN from auto-start, then start it after Windows finished loading other drivers, now I got no more errors and warnings in event viewer, and system running stable for several days.