BSOD analysis

mikephillips said:

All passed, just a firmware update needed.

The firmware update can sometimes fix things so see how it goes for the next day or so. Post new logfiles if you get any further BSODs.

Run HD Sentinel > extremely quick results (often useful for cables)

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


Please run Sea Tools long generic test overnight.

Code:

KINGSTON SA400S37480G

Code:

WDC WD5000AAKX-001CA0

Code:

WDC WD1600AAJS-08WAA0

Will run Seatools overnight

Kingston sa400s37480g
- - - Updated - - -

WDC WD5000AAKX-001CA0

WDC WD1600AAJS-08WAA0

It displayed communication problems on WDC WD5000AAKX-001CA0

Hard disk case: communication errors

I saw that, but why would that affect the boot sequence? That drive is not really used, just a store drive.

In two of the BSOD mini dump files there were misbehaving Avast drivers.
Uninstalling the AV software with its misbehaving drivers may have fixed the BSODs.
The bugchecks 154 and EF are often seen with malfunctioning hardware.
So drives are tested in the workup.

I ran the C drive overnight on SeaTools and this is the log.
13-Oct-20 8:23:36 AM
Model Number: KINGSTON SA400S37480G
Serial Number: 50026B77824DE686
Firmware Revision: SBFKB1C3
Long Generic - Started 13-Oct-20 8:23:36 AM
Short Generic - Started 13-Oct-20 10:16:20 AM
Short Generic - Pass 13-Oct-20 10:17:20 AM
Long Generic - Started 13-Oct-20 8:51:22 PM
Long Generic - Pass 13-Oct-20 11:05:56 PM

I am now running the SeaTools on the drive that indicated the intermittent comms issue. Can an intermittent drive affect the boot sequence so the machine cannot find the boot drive?

For software / hardware nearly anything can happen.
It's highly likely that the BSOD were caused by misbehaving AV drivers.
It's best to rule out drive problems to complete the workup.
The software can be ran overnight.

Problem drive SeaTools log

14-Oct-20 7:48:50 PM
Model Number: WDC WD5000AAKX-001CA0
Serial Number: WD-WMAYUM309647
Firmware Revision: 15.01H15
Long Generic - Started 14-Oct-20 7:48:50 PM
Long Generic - Pass 14-Oct-20 9:08:53 PM

CCleaner does not have System/Advanced (Free edition)

Have you had any further BSOD events? If you have then please post new log files.

I think it is unlikely that the AV software was causing the history of BSODs, it is more likely that the Avast driver just appeared in the thread because it was working in tandem with the disk read and write processes.

It is not easy to determine which drive was involved in the store management processes captured in the crash dump files, therefore we can't know for sure which drive was triggering the crash. Typically it would be the system drive and in some of the error messages the C:\ drive was mentioned.