BSOD after Windows Updates

Status
Not open for further replies.
J

josho495

Contributor
Joined
May 30, 2021
Posts
7
Hello,

I never had BSOD until I installed latest Windows 10 updates.

I was thinking maybe I should uninstall the Updates if that is possible.

Appreciate the help.
Josh.
1622432668730.png
Desktop
Via Speccy
Operating System
Windows 10 Home 64-bit
CPU
Intel Core i5 3570K @ 3.40GHz 32 °C
Ivy Bridge 22nm Technology
RAM
8.00GB Dual-Channel DDR3 @ 798MHz (11-11-11-28)
Motherboard
Gigabyte Technology Co. Ltd. Z77X-D3H (Intel Core i5-3570K CPU @ 3.40GHz) 33 °C
Graphics
SMS27A350H (1920x1080@60Hz)
Intel HD Graphics 4000 (Gigabyte)

I have an onboard display (no installed GPU).
 

Attachments

There was 1 collected mini dump file with bugcheck 154.

The logs displayed bugchecks 154 and 1A.


The BSOD mini dump file and log files have indicated problems with the drive.



Test all disk drives:


Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools (Windows) | Seagate
http://knowledge.seagate.com/articles/en_US/FAQ/202435en


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


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



These steps / tests can be performed overnight:
a) Sea Tools for Windows long generic test
b) HD Tune full error scan







Code: 
Event[1153]:
  Log Name: System
  Source: disk
  Date: 2021-05-17T10:13:08.5250000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: ADMINRG-6U7652G
  Description:
The IO operation at logical block address 0x802d228 for Disk 1 (PDO name: \Device\00000034) failed due to a hardware error.


Event[1201]:
  Log Name: System
  Source: disk
  Date: 2021-05-17T09:38:12.1860000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: ADMINRG-6U7652G
  Description:
The IO operation at logical block address 0xebc8d470 for Disk 1 (PDO name: \Device\00000034) failed due to a hardware error.


Event[2797]:
  Log Name: System
  Source: disk
  Date: 2021-04-21T08:32:59.6060000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: ADMINRG-6U7652G
  Description:
The IO operation at logical block address 0x802d6c0 for Disk 1 (PDO name: \Device\00000034) failed due to a hardware error.


Event[2801]:
  Log Name: System
  Source: disk
  Date: 2021-04-21T08:32:39.0550000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: ADMINRG-6U7652G
  Description:
The IO operation at logical block address 0x633238e8 for Disk 1 (PDO name: \Device\00000034) failed due to a hardware error.


Event[3286]:
  Log Name: System
  Source: disk
  Date: 2021-04-19T10:07:29.1160000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: ADMINRG-6U7652G
  Description:
The IO operation at logical block address 0xebb7ebc0 for Disk 1 (PDO name: \Device\00000034) failed due to a hardware error.


Event[6229]:
  Log Name: System
  Source: disk
  Date: 2021-02-05T16:55:45.8300000Z
  Event ID: 154
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: ADMINRG-6U7652G
  Description:
The IO operation at logical block address 0x4273bbd0 for Disk 1 (PDO name: \Device\00000034) failed due to a hardware error.


Code: 
Event[2293]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2021-04-30T12:20:05.9990000Z
  Event ID: 1
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: WHEA Error Event Logs
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: ADMINRG-6U7652G
  Description:
A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.


Code: 
Error code: (NTSTATUS) 0xc0000483 (3221226627) - The request failed due to a fatal device hardware error





Code: 
------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 28.5 GB
Total Space: 114.0 GB
File System: NTFS
      Model: SanDisk SDSSDX120GG25

      Drive: F:
 Free Space: 1206.6 GB
Total Space: 1907.7 GB
File System: NTFS
      Model: WDC WD20EARX-008FB0

      Drive: H:
 Free Space: 88.4 GB
Total Space: 2861.5 GB
File System: NTFS
      Model: ST3000DM001-1CH166
 
Thanks for the reply.

Sea Tools for Windows

Sea Tools for Windows long generic test.JPG


HD Tune

SSD

HDTune_Benchmark_SanDisk_SDSSDX120GG25.png HDTune_Error_Scan_SanDisk_SDSSDX120GG25.png HDTune_Health_SanDisk_SDSSDX120GG25.png




ST3000

HDTune_Benchmark_________ST3000DM001-1CH1.png HDTune_Error_Scan_________ST3000DM001-1CH1.png HDTune_Health_________ST3000DM001-1CH1.png




WDC

HDTune_Benchmark_WDC_____WD20EARX-008FB0.png HDTune_Error_Scan_WDC_____WD20EARX-008FB0.png HDTune_Health_WDC_____WD20EARX-008FB0.png
 
Last edited:
It appears that the SeaTools drive may be beginning to fail. I would disconnect it for now and see if the crashes continue.
 
Thanks, I will disconnect and if it still Blue Screens, I will report back.

Appreciate the help. I will donate :D
 
I bought a new HD — removed both the old drives and but kept the Windows SSD.
 
The ST3000DM001-1CH166 drive tests displayed:

long generic test: fail
surface test: 5 bad blocks

Check the warranty status.

Long generic / long DST failures are used by HP and others as a threshold for warranty replacement.




Please backup any important data.

Drives with failed long generic should be replaced.

However once data is backed up failed drives can be used until the terminal event (there may be slow read / write, hangs / freezes, unexpected shutdowns and restarts, BSOD, etc.)




Current settings are:
AutoReboot=TRUE
DebugInfoType=3

It can be easy to miss BSOD with automatic reboot is checked.

It's best to uncheck autoreboot when troubleshooting / monitoring
Change debug type to 7

These can run using administrative command prompt:

1) wmic recoveros set autoreboot = false
2) wmic recoveros set DebugInfoType = 7
3) wmic recoveros get autoreboot
4) wmic recoveros get DebugInfoType
5) wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
6) wmic Computersystem where name="%computername%" get AutomaticManagedPagefile



The logs displayed BSOD on:

1/16
4/18 > 4/24
5/18 > 5/23
5/31

There were no BSOD for approximately 7 days 5/23 > 5/31 and 24 days 4/4 > 5/18.

Was the problematic drive always or intermittently connected?

If possible, leave the drive unattached for at least 10 days while monitoring for BSOD.


Also if there is another PC you can connect the problematic drive and monitor for BSOD.


Monitor using: reliability monitor:

Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using
 
Thanks for the reply. I have bought a new HD and moved data onto the new drive. Both drives were 5 years old so not worth trying to save them. Did not know they were failing, so I am very grateful for your help. Cheers. Hopefully, there are no more BSOD. I will report back if anything changes.

Josh.
 
Status
Not open for further replies.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top