BSOD when running UserBenchmark

zbook · 14 Mar 2020

V2 can be ran after a clean install.
A clean install will fix the piracy / cracked third party software.
And a clean install may fix the BSOD and other log file problems.

ntd252 · 14 Mar 2020

zbook said:

V2 can be ran after a clean install.
A clean install will fix the piracy / cracked third party software.
And a clean install may fix the BSOD and other log file problems.

I know. Because the clean install has different drivers, so i don't think the log will be the same anymore.
The thing i want to know is the cause of BSOD, not just fix it (Fixing it as I say is not too important since the bsod happened just one time).

This is the new log.

zbook · 14 Mar 2020

The piracy was fixed by the clean install.

Additional dump files were needed to troubleshoot the prior crash.

The file collected was a mini dump file.

A memory dump was needed for this type of bugcheck.

Windows automatically deletes memory dump files when the drive free space is < 25 GB.

What was volume P ?

1) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan

2) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows |
Seagate
How to use SeaTools for Windows | Seagate Support US

3) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

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

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

6) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of

Code:

Event[3526]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2020-03-13T00:56:14.687
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DUONG-PC
  Description: 
The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.

MrPepka · 14 Mar 2020

Update Samsung SSD firmware - SSD Tools & Software | Download | Samsung V-NAND SSD | Samsung Semiconductor Global Website

ntd252 · 14 Mar 2020

zbook said:

The piracy was fixed by the clean install.
Additional dump files were needed to troubleshoot the prior crash.The file collected was a mini dump file.A memory dump was needed for this type of bugcheck.Windows automatically deletes memory dump files when the drive free space is < 25 GB.What was volume P ?

Thank you for your careful explanation.
The disk space at that time was about 14 GB free, so no doubt that the memory dump was deleted. The most important thing has gone. I also accidentally ignore the error code when blue screen appeared, I just thought minidump file was enough.
P was probable the USB drive. From what you explained, I guess you are thinking there's problem in the storage drive. I use SSD 860 Evo, and Samsung Magician tells my SSD is still healthy, and firmware update is waiting. Do I need to run chdsk anymore?

Attachment 270379 Attachment 270381 Attachment 270382
Attachment 270380

MrPepka said:

Update Samsung SSD firmware - SSD Tools & Software | Download | Samsung V-NAND SSD | Samsung Semiconductor Global Website

I have finished it! So you think it was caused by the SSD?

MrPepka · 14 Mar 2020

It's worth checking out any circumstantial evidence that's why I recommended it to you. Do you still have BSODs?

ntd252 · 14 Mar 2020

MrPepka said:

It's worth checking out any circumstantial evidence that's why I recommended it to you. Do you still have BSODs?

I haven't experience one. As what I recall, this was the first time it happened, when I was running User Benchmark, not sure which step in the benchmarking. At first I think it was the VGA driver, but the log seems to say the storage drive. Just a bit lazy to run check disk. I already update the SSD to latest firmware.

zbook · 14 Mar 2020

Please test all drives with:
a) HD Tune
b) Sea Tools
c) chkdsk /r /v
d) HD Sentinel

These steps / tests can be performed overnight:
a) HD Tune full error scan
b) Sea Tools long generic test
c) chkdsk /r /v

Run HD Sentinel: (free or trial edition)
Hard Disk Sentinel - HDD health and temperature monitoring
Hard Disk Sentinel - HDD health and temperature monitoring
Post images of each of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance

Code:

Event[2631]:
  Log Name: System
  Source: Microsoft-Windows-Ntfs
  Date: 2020-03-11T21:53:29.761
  Event ID: 140
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DUONG-PC
  Description: 
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: P:, DeviceName: \Device\HarddiskVolume10.
(The I/O device reported an I/O error.)

Code:

Event[2642]:
  Log Name: System
  Source: Microsoft-Windows-Ntfs
  Date: 2020-03-11T21:53:34.469
  Event ID: 140
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DUONG-PC
  Description: 
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: P:, DeviceName: \Device\HarddiskVolume14.
(The volume for a file has been externally altered such that the opened file is no longer valid.)

Code:

Event[2645]:
  Log Name: System
  Source: Microsoft-Windows-Ntfs
  Date: 2020-03-11T21:53:35.975
  Event ID: 140
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DUONG-PC
  Description: 
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: P:, DeviceName: \Device\HarddiskVolume16.
(The I/O device reported an I/O error.)

Code:

Event[2647]:
  Log Name: System
  Source: Microsoft-Windows-Ntfs
  Date: 2020-03-11T21:53:40.715
  Event ID: 140
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DUONG-PC
  Description: 
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: P:, DeviceName: \Device\HarddiskVolume18.
(The I/O device reported an I/O error.)

Code:

Event[2652]:
  Log Name: System
  Source: Microsoft-Windows-Ntfs
  Date: 2020-03-11T21:53:48.261
  Event ID: 140
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DUONG-PC
  Description: 
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: P:, DeviceName: \Device\HarddiskVolume22.
(The I/O device reported an I/O error.)

Code:

Event[2654]:
  Log Name: System
  Source: Ntfs
  Date: 2020-03-11T21:53:48.386
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DUONG-PC
  Description: 
A corruption was discovered in the file system structure on volume P:.

The exact nature of the corruption is unknown.  The file system structures need to be scanned online.

Code:

Event[3633]:
  Log Name: System
  Source: Ntfs
  Date: 2020-03-13T18:10:30.182
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DUONG-PC
  Description: 
A corruption was discovered in the file system structure on volume P:.

A corruption was found in a file system index structure.  The file reference number is 0x5000000000005.  The name of the file is "<unable to determine file name>".  The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".

Code:

Event[2715]:
  Log Name: System
  Source: disk
  Date: 2020-03-11T21:54:42.309
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DUONG-PC
  Description: 
The driver detected a controller error on \Device\Harddisk1\DR12.

Event[2716]:
  Log Name: System
  Source: disk
  Date: 2020-03-11T21:54:43.336
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DUONG-PC
  Description: 
The driver detected a controller error on \Device\Harddisk1\DR12.

ntd252 · 14 Mar 2020

zbook said:

Please test all drives with:
a) HD Tune
b) Sea Tools
c) chkdsk /r /v
d) HD Sentinel

Seems the problem is not that easy as I thought. From what I remember, P was the USB drive. But the timestamp was from (2020-03-11), while I just plugged the USB in 2020-03-12 or 13.
The old disk scheme had 3 partition C, D, E and 2 partition for linux (which was invisible in Windows).
I will run chkdsk tonight to see how it goes.