Computer Multiple crashes and reboots at random

coolmariodude said:

So i got the new motherboard this week, So far no more crashes what so ever and the computer even acts more stable then it ever has. Thank you all for the help.

That is good news! Hopefully you won't need our help again but we are here if you need us :)

Computer Randomly Freezes until Reboot - Windows 10 Forums
Please post a new zip in this thread.
BSOD - Posting Instructions - Windows 10 Forums

Sorry for the late reply, But Finally got to the DMLogger. Here you guys are.. My computer froze up and I am doing a little troubleshooting of my own tonight.. I rolled bakc from the Windows 10 fall update 1709 to the Creators update to see if anything happens like that again.. Hopefully if any hardware issues the zip will show you. If not Chances are I'm going Linux and praying that a kernel panic happens in which i could debug.Attachment 168359

The logs displayed 2 crashes.
There was 1 crash dump fail.
Windows fast startup failed.
Windows indexing is corrupt.
The WHEA has disappeared.

Open administrative command prompt and type or copy and paste:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3) chkdsk /scan
4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
5) If you use Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread
6) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread
7) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
> on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
> on the advanced tab under performance > click on settings > click on advanced tab > under virtual memory click on change > post an image of the virtual memory tab into the thread
8) In the left lower corner search type services > open windows error reporting service > scroll to the startup type column > right click > left click on properties > post an image into the thread
9) Download and install Whocrashed > in the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
http://www.resplendence.com/whocrashed
10) Click analyze > look for dead or deaddead in the results > post the results into the thread
11) Run the DM log collector after all of the above steps and post a zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums
BSOD - Posting Instructions - Windows 10 Forums
12) Turn off Windows fast startup
Turn On or Off Fast Startup in Windows 10 Performance Maintenance Tutorials
13) In the left lower corner search type: index > open indexing options > click advanced > click rebuild
This may take a long time so plan to run overnight.

Code:

Event[1054]:  Log Name: System  Source: Microsoft-Windows-Kernel-Boot  Date: 2017-12-09T20:44:06.757  Event ID: 29  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-G5RP0J9  Description: Windows failed fast startup with error status 0xC0000411.

Code:

Event[1583]:  Log Name: System  Source: volmgr  Date: 2017-12-15T22:02:27.736  Event ID: 46  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-G5RP0J9  Description: Crash dump initialization failed!

Code:

Event[987]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-12-09T06:52:34.299  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-G5RP0J9  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

12/16/2017 3:04 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: WsearchHealth
Response: Not available
Cab Id: 0

Problem signature:
P1: Corruption
P2: 0xc0041801
P3: unknown
P4: 0
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: c3cebeca-fd12-4b9a-8da9-12e9107b64ff
Report Status: 262148
Hashed bucket:12/16/2017 3:04 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: WsearchHealth
Response: Not available
Cab Id: 0

Problem signature:
P1: Corruption
P2: 0xc0041801
P3: unknown
P4: 0
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B4E.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3158.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER359C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35BD.tmp.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_Corruption_a2a79d47665bc8036efb3f8e779a3d0e9b12e93_00000000_cab_16b63723\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_Corruption_a2a79d47665bc8036efb3f8e779a3d0e9b12e93_00000000_cab_16b63723

Analysis symbol: 
Rechecking for solution: 0
Report Id: c3cebeca-fd12-4b9a-8da9-12e9107b64ff
Report Status: 100
Hashed bucket:

Code:

12/16/2017 3:04 AM    Windows Error Reporting    Fault bucket 90721584420, type 5
Event Name: WsearchHealth
Response: Not available
Cab Id: 0

Problem signature:
P1: Corruption
P2: 0xc0041801
P3: unknown
P4: 0
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B4E.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3158.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER359C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35BD.tmp.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_Corruption_a2a79d47665bc8036efb3f8e779a3d0e9b12e93_00000000_cab_16b63723\memory.hdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_Corruption_a2a79d47665bc8036efb3f8e779a3d0e9b12e93_00000000_cab_16b63723

Analysis symbol: 
Rechecking for solution: 0
Report Id: c3cebeca-fd12-4b9a-8da9-12e9107b64ff
Report Status: 268435552
Hashed bucket: 8e8a63a10380a528478f978ddd29ea10

Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Another servicing or repair operation is currently running.Wait for this to finish and run sfc again.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 520704 file records processed.File verification completed. 11130 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 608724 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed. 44011 data files processed.CHKDSK is verifying Usn Journal... 37667032 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 975316144 KB total disk space. 93591924 KB in 217310 files. 140108 KB in 44012 indexes. 0 KB in bad sectors. 661412 KB in use by the system. 65536 KB occupied by the log file. 880922700 KB available on disk. 4096 bytes in each allocation unit. 243829036 total allocation units on disk. 220230675 allocation units available on disk.C:\WINDOWS\system32>

Attachment 168374Attachment 168373Attachment 168372Attachment 168375

Here is the DM-log-collector report zip file after the whocrashed was completed.

Edit: Windows fast startup is now off, and the indexer is rebuilding.

1) For startup and recovery > system failure > un-check automatically restart
2) For windows error reporting > change manual > automatic > start > ok > reboot
3) Place the computer in clean boot:
https://support.microsoft.com/en-us/...oot-in-windows
How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

Evaluate the computer for 1 - 2 days to see if there is any freezing or spontaneous crashes or crashes with BSOD.

Options include placing the computer in
b) safe mode (or safe mode with networking or command prompt) > this may also help differentiate software from hardware problems
c) using windows driver verifier to find misbehaving drivers (there was a failed crash dump)

This is reading material on windows driver verifier (do not start using it until its communicated in the thread)
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials


4) Make a brand new restore point
5) Back up all files
6) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free
7) Place the backup image onto another drive or into the cloud
8) learn the methods to turn off windows driver verifier

The thing is though, this is another clean install of Windows that i have done.. About a week or 2 ago the PC was on 1709 with no way to rollback the update.. The Computer was like freezing up so easily and then i reinstalled Windows and this is where i am now. So I don't think its a driver issue as i even updated all the drivers to see if it fixed it before the clean install. I'm officially starting to think this computer is cursed. If it does Freeze up again.. I'm highly thinking of just installing Ubuntu and doing the GRUB bootloader edit for my Mobo to support its USB ports (Gigabyte issue very common) and see if Ubuntu gives me a Kernel Panic any.. Only would really lose a game or 2.