Windows Crashing - How to identify the cause?

[sporadic_kit]

So I recently built my system. Asus Maximus viii, Corei7 6800k, 16gb pc3200 ram (not OC'd), kingston hyperx 480gb SSD (C:\), Kingston M.2 SSD 480gb (D:\), overspecced PSU (can't remember brand) Nvidia 980 TI 6gb (Factory OC).

Updated mobo, gpu and hdd firmwares. Running Windows 10 with latest patches. Latest driver versions as far as I can tell.

Occaisonally windows freezes and a reboot fixes it.
Occaisonaly windows freezes and then the machine won't boot. Blank screen not even a POST screen. Its weird when it happens as I have to leave it a day before it'll come back on again. Not even a few hours - a day.

Pretty Annoying. It freezes about once a week where the reboot fixes it. Every couple of weeks it does a mega freeze. Any ideas how I can track down what is causing this? I've been keeping an eye on heat and its not really getting hot. Sometimes I game and it'll happily game on max settings for hours.

No dodgy software installed (EVER!). Im stumped. Pretty annoying seeing as I tipped so much money into this!

 

[corndog1836]

check windows event viewer and change search parameters to critical.

 

[corndog1836]

1. go to event viewer
2. on the left , right click windows logs
3. then click system to see all info, critical, and errors
4. filter your search to critical by using the filter option on the top right menu.

 

[sporadic_kit]

Haha I stopped being a sysadmin many years ago - I hoped my days of looking at event logs were behind me. Guess I was wrong 😉

 

[sporadic_kit]

Deleted this post

 

[sporadic_kit]

Found some relevant stuff. Event log closest to crash first in list:

1. The Viveport Services service failed to start due to the following error:
The system cannot find the file specified.

2. Session "ReadyBoot" stopped due to the following error: 0xC0000188

2.1 The maximum file size for session "ReadyBoot" has been reached. As a result, events might be lost (not logged) to file "C:\Windows\Prefetch\ReadyBoot\ReadyBoot.etl". The maximum files size is currently set to 20971520 bytes.

2.2 (There are about 8 of these) The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{8d9ed2bc-7916-11e6-8626-806e6f6e6963}#0000000008100000.


3. Audit events have been dropped by the transport. 0

4. The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Hmmm so it got its nickers in a right twist. Strange that the whole crash process started with notification that the last boot was from crash.

 

[sporadic_kit]

OK so this is the fix for these

Fix: https://social.technet.microsoft.com/Forums/office/en-US/d74859fb-f1c1-434f-b084-fd26da581c6e/session-readyboot-stopped-due-to-the-following-error-0xc0000188?forum=w7itprogeneral

Error:

2. Session "ReadyBoot" stopped due to the following error: 0xC0000188

2.1 The maximum file size for session "ReadyBoot" has been reached. As a result, events might be lost (not logged) to file "C:\Windows\Prefetch\ReadyBoot\ReadyBoot.etl". The maximum files size is currently set to 20971520 bytes.

 

[sporadic_kit]

Fix: https://appuals.com/driver-wudfrd-failed-to-load-for-the-device-with-event-id-219/

2.2 (There are about 8 of these) The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{8d9ed2bc-7916-11e6-8626-806e6f6e6963}#0000000008100000.

Also removed all traces of the HTC vive from my machine because im selling it. Hopefully that is enough to stabilise things.

 

[corndog1836]

did u get things fixed?