Windows 10: BSOD - PowerSpec 1510

Memtest86+ version 5.01 passed the test with 8 passes and 0 errors using 16GB RAM.
The fast startup feature can be used.
the last failure was approximately 1 month ago.
If there are failure events in the event log or problems with boot and shutdown then reevaluate.
Turn On or Off Fast Startup in Windows 10 Windows 10 Tutorials
Code: Event[2]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2018-02-12T12:56:10.799 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: laptop-NE0OLRC Description: Windows failed fast startup with error status 0xC00000D4[/quote] After the driver changes > restart Windows driver verifier to test for other misbehaving drivers.

 

I have gone back to the Nvidia Display driver from the PowerSpec site. I will re-enable the Driver verifier later tonight. Can I reload Norton?

Old driver:
23.21.13.9101
Original driver (now reloaded):
22.21.13.8205

 

Please wait 1 week after the last BSOD to reinstall Norton.
This way it will not confound the troubleshooting.
Please make sure Windows defender is on.

There were drivers that you had reported in the opening post that did not appear in the multiple memory dumps.
So Windows driver verifier will be useful to see whether they were causes or BSOD or whether they were standby crashes.

 

New BSOD - Nothing showed on the display, so I don't have the associated message.

Dropbox - 20180316.zip

 

Nothing definitive in the dump.
Please run the beta log collector with each dump and post a new zip into the thread:
log collector v2-beta08.zip

 

Ran chkdsk with no issues





Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows.


A disk check has been scheduled.
Windows will now check the disk.


Stage 1: Examining basic file system structure ...
405760 file records processed. File verification completed.
9594 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
378 reparse records processed. 502846 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found. 378 reparse records processed.
Stage 3: Examining security descriptors ...
Cleaning up 4467 unused index entries from index $SII of file 0x9.
Cleaning up 4467 unused index entries from index $SDH of file 0x9.
Cleaning up 4467 unused security descriptors.
Security descriptor verification completed.
48544 data files processed. CHKDSK is verifying Usn Journal...
41683544 USN bytes processed. Usn Journal verification completed.


Stage 4: Looking for bad clusters in user file data ...
405744 files processed. File data verification completed.


Stage 5: Looking for bad, free clusters ...
35292901 free clusters processed. Free space verification is complete.


Windows has scanned the file system and found no problems.
No further action is required.


243280945 KB total disk space.
101427980 KB in 250641 files.
153668 KB in 48545 indexes.
0 KB in bad sectors.
527689 KB in use by the system.
65536 KB occupied by the log file.
141171608 KB available on disk.


4096 bytes in each allocation unit.
60820236 total allocation units on disk.
35292902 allocation units available on disk.


Internal Info:
00 31 06 00 63 85 04 00 8f 05 08 00 00 00 00 00 .1..c...........
d3 00 00 00 a7 00 00 00 00 00 00 00 00 00 00 00 ................


Windows has finished checking your disk.
Please wait while your computer restarts.

 

Turned on 19 driver verifier tests per the link instructions. Got BSOD on restart immediately on boot. This occurred multiple times until I got verifier turned off.

Message did not include the driver name - "Driver Verifier Detected Violations"

Dropbox - LAPTOP-NE0OLRC (2018-03-17 08 58).zip

Memory.dmp
Dropbox - MEMORY 03172018.zip

 

Update this misbehaving driver:

SvThANSP.sys


Savitech Hotkey Driver


Code: None at http://www.savitech-ic.com/[/quote]
Must get from OEM.

Code: svthansp SvThANSP \??\c:\program files (x86)\hotkey\svthansp.sys Kernel Driver Yes System Running OK Normal No Yes[/quote]

 

1) Submit a support ticket if available
2) Find out what happens without a working driver
3) When using driver verifier in the custom settings check all non-Microsoft drivers except this one so that you can test the other drivers.

 

I wanted to thank you for your help. Finding SvThANSP.sys was the key.

Using that while searching further I found a Discussion thread concerning my laptop. There is a known issue with ControlCenter and the XTU driver. There are instructions on the thread to install ControlCenter without the driver or you can use the CLEVO Drivers Update Utility by OBSIDIAN-PC to load ControlCenter cleanly.

I have gone a week without any BSOD since going to the Update Utility.

The thread
PowerSpec 1710 + 1510? | NotebookReview

The Update Utility
CLEVO Drivers Update Utility by OBSIDIAN-PC | Page 79 | NotebookReview

 

That's great news.
Glad to know it got sorted out.
You are welcome.
Let us know if you need help in the future.