Win10 not booting after multiple BSODs, updated GPU driver and chkdsk

zbook · 24 Jan 2020

The image displayed a scroll bar.
Please post images so that all of the clean settings are viewable.
What registry cleaning has been performed?

Uncheck these boxes:
a) Memory Dump files
b) Error report files
c) System log files

Many of the important files had been cleaned and were unavailable for troubleshooting.

For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

JWW2020 · 26 Jan 2020

Unchecked the relevant boxes, a lot disappeared from the second list then, Further screenshots are below.

Attachment 264618 Attachment 264619 Attachment 264620 Attachment 264621 Attachment 264622

I have not done any registry clean.

Attach the v2 as there were a couple yesterday which happened. It seems as though windows update has somehow installed the GPU driver. However, definitely still getting some BSODs, though they seem less frequent.

Ill provide memory dump attachment when it uploads....its just under 1gb and will take some time.

zbook · 26 Jan 2020

The attachments displayed invalid.

Please post working links.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) 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

13) Make sure that there is no over clocking while troubleshooting

14) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

15) Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.

a) Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool

The testing is done not by time but by passes.
The more passes the better the testing conditions.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 4 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.

b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
https://answers.microsoft.com/en-us/...f-ecc7b7ff6461
MemTest86+ - Test RAM

Code:

Event[3929]:
  Log Name: System
  Source: Display
  Date: 2020-01-19T20:56:45.823
  Event ID: 4115
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Michelle-PC
  Description: 
Display driver failed to start; using Microsoft Basic Display Driver instead. Check Windows Update for a newer display driver.

Code:

Event[3299]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2020-01-19T18:49:51.079
  Event ID: 5
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Michelle-PC
  Description: 
{Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.

Code:

Event[3298]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2020-01-19T18:49:37.630
  Event ID: 5
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Michelle-PC
  Description: 
{Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\DEFAULT' was corrupted and it has been recovered. Some data might have been lost.

JWW2020 · 01 Feb 2020

Hey,

Finally managed to do all the tasks.

Posting the screens that did not work last time for some reason:

Attachment 265400
Attachment 265401
Attachment 265402
Attachment 265403
Attachment 265404

I also had another set of BSODs, I managed to catch the last one as the PC was idle, having restarted from one. So reattach a V2 log and the link to the memory dump on my google drive is below.

MEMORY.DMP - Google Drive

CMD log

Please note the compute BSOD between step 3 and 4 the first time, so I restarted it from scratch:

Microsoft Windows [Version 10.0.18363.592]
(c) 2019 Microsoft Corporation. All rights reserved.

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>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.592

[==========================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.18362.1

Image Version: 10.0.18363.592

[==========================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 did not find any integrity violations.

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

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

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

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

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

487698541 KB total disk space.
354108464 KB in 588296 files.
296616 KB in 86803 indexes.
0 KB in bad sectors.
1087893 KB in use by the system.
65536 KB occupied by the log file.
132205568 KB available on disk.

4096 bytes in each allocation unit.
121924635 total allocation units on disk.
33051392 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\MICHELLE-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\MICHELLE-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE

C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7

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

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

Screenshot of startup settings

Attachment 265407

Screenshot of virtual memory

Attachment 265406

Screenshot of memtest results

Attachment 265408

I can do the log and memory dump again if I manage to get another one?

zbook · 02 Feb 2020

First scannow:

Code:

Windows Resource Protection found corrupt files but was unable to fix some of them.

Second scannow:

Code:

Windows Resource Protection did not find any integrity violations.

Memtest 86+ version 5.01
11 passes
4 GB RAM
Test pass

Today is 2/1/2020.
The V2 uploaded was from 1/25/2020.
Please upload a new V2.

JWW2020 · 02 Feb 2020

Latest attached.

Thanks

MrPepka · 02 Feb 2020

Send full memory dump (MEMORY.DMP in C:\Windows)

zbook · 02 Feb 2020

1) As above post a share link for C:\windows\memory.dmp

Code:

LastWriteTime       Size (MB) FullName             
-------------       --------- --------             
02/02/2020 11:55:56    587.06 C:\WINDOWS\MEMORY.DMP

2)Make a new restore point:

Create System Restore Point in Windows 10

3) Read these links on Windows driver verifier: (learn how to use the reset and bootmode commands in Windows Recovery Environment (RE)) (do not use the tool until it is communicated in the thread)

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

4) Find a flash drive that you can format (> or = 8 GB)

5) Create a bootable Windows 10 iso:
https://www.microsoft.com/en-us/soft...load/windows10
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10

6) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

JWW2020 · 03 Feb 2020

Another BSOD

So memory dump attached as a share link

MEMORY2-2-20.DMP - Google Drive

V2 log attached.

This one happened on startup just after the windows load screen.

On the above, I have done step 2. I cannot boot from a USB stick as I found out when trying to run memtest. I ended up having to create a DVD bootable one. As these only go up to 4.7GB is there any other option. I could perhaps obtain a cheapish external hard drive that plugs in to USB?

zbook · 03 Feb 2020

The log collector was dated: Date: 2020-02-02T22:50:49.659

Please upload a new V2 and memory dump when available.

If you have fast boot or ultra fast boot enabled in your UEFI firmware settings, then you will need to temporarily disable fast boot or ultra fast boot to be able to boot from a USB.

1. Try another USB stick
2. Try all USB ports (2.0 and 3.0)
3. Maybe when using UEFI Bios you have to temporarily switch to Legacy in BIOS settings
4. Turn off temporarily fast boot, secure boot, CSM if enabled

See these links:

Boot from USB Drive on Windows 10 PC
Enable or Disable Fast Boot in UEFI Firmware Settings for Windows