Laptop randomly hangs while in sleep mode

Nice progress with the upgrade.

Over the next week see if there is or is not better performance after the cumulative steps: drivers updates, BIOS upgrade, Windows 10 upgrade, etc.

When available please post a share link for the chkdsk report:

Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

Will do. Thanks tons for all the in-depth help. I pity ordinary mortals who are trying to use these systems. I've been a computer geek for 45 years and I was lost in this morass until you jumped in!

Great.
You are very welcome.
Glad to help.

zbook said:

When available please post a share link for the chkdsk report:

?? Neither of the methods you linked return any reports!

I found a Chkdsk<timestamp>.log file from the right time, but it's in C:\System Volume Information\Chkdsk and I can't access it.

Any guesses where I should look?

Ack! I just noticed you wanted me to run chkdsk on the suspect G: drive! Duh, I ran it on C:. And don't you need /f to tell it to fix any problems, or were you just looking for a scan? But I'm confused why "chkdsk /r /v" didn't list every file as it scanned -- that's what /v should have done, yes?

When running chkdsk switches they can be ran within windows or windows recovery enironment (Windows RE).

When the switches are run within Windows the % status will rise to a low number in the teens and remain there until it completes.
In contrast, when using the Windows advanced troubleshooting menu or Windows RE it will typically display ETA.

The f switch is to fix and the r is to recover.
Running the r switch includes the f switch.

The v switch displays the most detail about the fix and recovery.

The syntax when running the switches is chkdsk /r /v which defaults to the windows drive.
If there are other disk drives then use chkdsk D: /r /v changing the letter D to the applicable drive letter.
The drive letters need to be entered into the command when using windows RE.

This is a Microsoft link:
https://docs.microsoft.com/en-us/win...ommands/chkdsk


Please upload a new V2 into this thread:
BSOD - Posting Instructions

New V2 attached.

I ran chkdsk on G: this time, output below. I was going to say it looks remarkably healthy considering I had to repair it a couple of times after using the bad USB extender. But then it got to stage 4, 27 of 412656, and it stopped dead. It's been sitting there for about 10 minutes so far. I'll let it run but I have to leave within half an hour...

It may just be busy. Resource Monitor says it's reading 32MB/sec. It's a Seagate Backup Plus portable drive, so that may be all it's capable of. Disk queue length is running over 0.90.

Code:

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


C:\WINDOWS\system32>chkdsk /r /v g:
The type of the file system is NTFS.
Volume label is Seagate Backup Plus Drive.


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


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


Stage 3: Examining security descriptors ...
Cleaning up 5 unused index entries from index $SII of file 9.
Cleaning up 5 unused index entries from index $SDH of file 9.
Cleaning up 5 unused security descriptors.
Security descriptor verification completed.
  18433 data files processed.
CHKDSK is verifying Usn Journal...
  47216 USN bytes processed.
Usn Journal verification completed.


Stage 4: Looking for bad clusters in user file data ...
Progress: 27 of 412656 done; Stage:  0%; Total:  0%; ETA:  36:22:36 .

Problematic drives may have very long chkdsk run times.
The deeper the fix and recovery and the smaller the free space the longer the running time.

Run HD Tune, Sea Tools, and HD sentinel on the drive.


When V2 was ran only the internal Toshiba drive appeared in the logs.

Yes, I don't usually have the backup drive attached. I figure it's vulnerable to a ransomware attack if it's active.

If you want the V2 with the G: drive, it'll have to wait until the chkdsk finishes. The drive is fairly full -- 220 GB free on a 2TB drive.

When there are problems with attached drives Windows may create entries in the event viewer.
The event viewer entries are collected with V2.

If you have not been using the reliability control panel it is a useful proxy for the event viewer:
Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using

Blast. I set the chkdsk running on the G: drive and left for the afternoon. I returned five hours later to find... a hung laptop. Apparently all the updates and cleanouts, while undoubtedly beneficial, didn't resolve the original problem.

And I don't know if the chkdsk completed or not. There's still no sign of a chkdsk log anywhere.

So I've launched the chkdsk on G: again. It got to Stage 4 quickly, but this time is different. No message after the "Stage 4" line for 5-6 minutes, and it's reading data 3-4x faster than it did before. I'll see what it does this time...

Meanwhile I've turned off the "turn screen off after X minutes" feature, hoping that will prevent the hung-system behavior while the chkdisk completes.