Random BSOD While Doing Just About Anything On My PC

zbook said:

1) The last BSOD was on 8/4 and today is 8/9.

2) However the last unexpected shutdown / restart was on 8/7 (2019-08-07 T19:01:41.483).
Another was on 8/6 (2019-08-06 T16:24:28.748).
These entries in the logs are also seen when there are power offs.
Please report into the thread whether there were power offs.

3) Uninstall Driver Easy.
The best drivers are always displayed on the computer or motherboard manufacturer's websites.
For any needed drivers that were not displayed use the hardware manufacturer's websites: (Nvidia, AMD, Intel, Killer Networks, Realtek, etc.

4) Open administrative command prompt and type or copy and paste:
5) sfc /scannow
6) dism /online /cleanup-image /restorehealth
7) chkdsk /scan
8) wmic recoveros set autoreboot = false
9) bcdedit /enum {badmemory}
10) 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

11) Make sure that there is no over clocking while troubleshooting.

Thanks for the fast reply!

It's true, I havent had a BSOD in a few days. Those unexpected shutdowns are probably me rebooting my PC because they occur around the times i was on it.

I uninstalled DriverEasy.

Here is the log from the command prompt...




Microsoft Windows [Version 10.0.17763.615]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Windows\system32>

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\system32>
C:\Windows\system32>
C:\Windows\system32>
C:\Windows\system32>
C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.615

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>
C:\Windows\system32>
C:\Windows\system32>
C:\Windows\system32>
C:\Windows\system32>
C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
231424 file records processed.
File verification completed.
6902 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
281 reparse records processed.
319248 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
281 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
43913 data files processed.
CHKDSK is verifying Usn Journal...
33819824 USN bytes processed.
Usn Journal verification completed.

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

243568639 KB total disk space.
62987596 KB in 167093 files.
111736 KB in 43914 indexes.
0 KB in bad sectors.
341799 KB in use by the system.
65536 KB occupied by the log file.
180127508 KB available on disk.

4096 bytes in each allocation unit.
60892159 total allocation units on disk.
45031877 allocation units available on disk.

C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-O6NS543\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk1\\Partition4"'
Property(s) update successful.

C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\Windows\system32>

Open administrative command prompt and type or copy and paste:
5) dism /online /cleanup-image /scanhealth
6) dism /online /cleanup-image /restorehealth
7) sfc /scannow
8) 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

If there is any displayed problems with scannow > find: C:\Windows\Logs\CBS\CBS.log > post a share link using one drive, drop box, or google drive

zbook said:

Open administrative command prompt and type or copy and paste:
5) dism /online /cleanup-image /scanhealth
6) dism /online /cleanup-image /restorehealth
7) sfc /scannow
8) 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

If there is any displayed problems with scannow > find: C:\Windows\Logs\CBS\CBS.log > post a share link using one drive, drop box, or google drive

Microsoft Windows [Version 10.0.17763.615]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.615

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.615

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\system32>

Post a share link for the cbs log:
C:\Windows\Logs\CBS\CBS.log

zbook said:

Post a share link for the cbs log:
C:\Windows\Logs\CBS\CBS.log

CBS.log - Google Drive

The recent scannow corruption is well known in Ten Forums and will need Microsoft updates to windows defender and/or Windows updates.

zbook said:

The recent scannow corruption is well known in Ten Forums and will need Microsoft updates to windows defender and/or Windows updates.

I was able to update windows to 1903. Although, when i searched the settings to update windows defender, there was no option to do so.

The logs displayed hash mismatch for scannow and the componet store.
This has affected many end users.
Microsoft needs to fix by a Microsoft defender or Windows update.

zbook said:

The logs displayed hash mismatch for scannow and the componet store.
This has affected many end users.
Microsoft needs to fix by a Microsoft defender or Windows update.

okay so i should just wait for the next update?

There should be comments in existing threads or new threads when it has a Microsoft fix.