BSOD analysis

Thanks to all for the help. Here is my zip file.

Hi mikephillips,

Please perform the following steps:

1) Run: Tuneup.bat

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

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

4) Uninstall Avast using the applicable uninstall tool:
Avast Uninstall Utility | Download aswClear for Avast Removal

5) Open Ccleaner > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread

6) Avast can be reinstalled in 3 - 4 days if there are no BSOD

Code:

###########################################################
# The following commands will be run in sequence.         #
# The first 5 will take quite a while to run, be patient. #
#########################################################
sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

chkdsk /scan

wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot
wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType

wmic pagefile list /format:list
wmic Computersystem where name="MIKE-PC" get AutomaticManagedPagefile
wmic Computersystem where name="MIKE-PC" set AutomaticManagedPagefile=True
wmic Computersystem where name="MIKE-PC" get AutomaticManagedPagefile

bcdedit /enum {badmemory}


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

Deployment Image Servicing and Management tool
Version: 10.0.19041.329

Image Version: 10.0.19041.508

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

Image Version: 10.0.19041.508

[==========================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.
Volume label is Disk0_Part1.

Stage 1: Examining basic file system structure ...
  954112 file records processed.
File verification completed.
 Phase duration (File record verification): 15.30 seconds.
  9876 large file records processed.
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 1.07 milliseconds.

Stage 2: Examining file name linkage ...
  3448 reparse records processed.
  1215782 index entries processed.
Index verification completed.
 Phase duration (Index verification): 1.58 minutes.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 6.56 seconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 0.54 milliseconds.
  3448 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 21.06 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 261.47 milliseconds.
  130836 data files processed.
 Phase duration (Data attribute verification): 1.22 milliseconds.
CHKDSK is verifying Usn Journal...
  40722240 USN bytes processed.
Usn Journal verification completed.
 Phase duration (USN journal verification): 739.20 milliseconds.

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

 432795598 KB total disk space.
 319896548 KB in 586215 files.
    330096 KB in 130837 indexes.
         0 KB in bad sectors.
   1088562 KB in use by the system.
     65536 KB occupied by the log file.
 111480392 KB available on disk.

      4096 bytes in each allocation unit.
 108198899 total allocation units on disk.
  27870098 allocation units available on disk.
Total duration: 1.96 minutes (117938 ms).

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


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

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


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


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

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


C:\WINDOWS\system32>wmic pagefile list /format:list


AllocatedBaseSize=12288
CurrentUsage=59
Description=C:\pagefile.sys
InstallDate=20181007103001.503455+060
Name=C:\pagefile.sys
PeakUsage=61
Status=
TempPageFile=FALSE




C:\WINDOWS\system32>wmic Computersystem where name="MIKE-PC" get AutomaticManagedPagefile
AutomaticManagedPagefile
FALSE


C:\WINDOWS\system32>wmic Computersystem where name="MIKE-PC" set AutomaticManagedPagefile=True
Updating property(s) of '\\MIKE-PC\ROOT\CIMV2:Win32_ComputerSystem.Name="MIKE-PC"'
Property(s) update successful.

C:\WINDOWS\system32>wmic Computersystem where name="MIKE-PC" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


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

RAM Defects
-----------
identifier              {badmemory}
Press any key to continue . . .

Your post title suggests you wanted an analysis of the BSOD crashes you have been getting. Here is some more background on them.

Four of the six crashes recorded are 0x154 (unexpected store exception) bugchecks which are most commonly associated with harddisk failure. The other two crashes were 0xEF (critical process died) bugchecks which are also often associated with harddisk or RAM failure.

Code:

2020-10-12T12:17:59.2490000Z        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000154 (0xffffe18962bc9000, 0xffffa08790141d20, 0x0000000000000002, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 9e0d5352-a719-47e7-90c4-a7bbb7d533cf.   
2020-10-11T16:55:45.3310000Z        The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ef (0xffffc806fbc89080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.   
2020-10-06T15:56:52.6620000Z        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000154 (0xffffe5013513f000, 0xffff828ceb8d3130, 0x0000000000000002, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 547a0aa6-0a98-40fa-94a2-c6c33bed3689.   
2020-10-05T16:05:42.9040000Z        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000154 (0xffff800c17919000, 0xffffec0c76d29c90, 0x0000000000000002, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 38fa4bc5-6275-4688-a430-6b214cef0ba0.   
2020-09-29T12:52:19.5530000Z        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000154 (0xffffb20f5731e000, 0xfffffd8d768f1150, 0x0000000000000002, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e2e98b9f-d5dd-44b3-a03c-9ebbcbe330e3.   
2020-09-26T08:33:38.9490000Z        The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000ef (0xffff948e2bc020c0, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: db1dd255-bacd-42a9-8d2b-ae9ef0ab81cf.

There were eight cases of the the crash dump file creation failing which could also point to disk failure.

On the 4th October you had a number of warnings like this:

Code:

   2020-10-04T19:15:52.2010000Z        svchost (3180,T,0) SRUJet: A request to write to the file "C:\WINDOWS\system32\SRU\SRUDB.dat" at offset 49352704 (0x0000000002f11000) for 4096 (0x00001000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Again this suggests faulty hardware and in particular I would suspect the C:\ drive.

Let's see what the results of the tests requested by @zbook show. I have posted this just so that you know the background to what we are suspecting and why you should pay particular attention to the system disk and be prepared for possible imminent failure.

philc - that fits with my experience. Recently I had an occasional 'Cannot find boot drive' which I thought I had tracked down to a dodgy SATA cable. My (gigabit) board has 4 SATA3 connectors and 2 SATA 2. The C drive is on a SATA2 which sits in a 'shoulder' on the m/board. I swapped the C Drive connector AND cable to the other connector and all was well until recently. My gut feeling is that the SSD C Drive is 'ok' and it is the connectors that are faulty? Here are the initial results of the HDTune for the C drive. The Error check was very slow as you can see and the speed varied wildly. Can the team make an initial assessment on the SATA side from this? NB The 'health' check screen was too 'long' to image so I copied to a text file.

1) Please post Sea Tools for Windows long generic tests when available.

2) Test all drives

3) When available update the progress with post #2, steps #4 and #5.

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 115.9 GB
Total Space: 422.7 GB
File System: NTFS
      Model: KINGSTON SA400S37480G

      Drive: F:
 Free Space: 22.9 GB
Total Space: 70.5 GB
File System: NTFS
      Model: WDC WD5000AAKX-001CA0

      Drive: H:
 Free Space: 42.2 GB
Total Space: 42.4 GB
File System: NTFS
      Model: WDC WD1600AAJS-08WAA0

      Drive: I:
 Free Space: 39.2 GB
Total Space: 77.3 GB
File System: NTFS
      Model: WDC WD5000AAKX-001CA0

      Drive: K:
 Free Space: 14.5 GB
Total Space: 46.3 GB
File System: NTFS
      Model: WDC WD1600AAJS-08WAA0

      Drive: L:
 Free Space: 63.8 GB
Total Space: 64.0 GB
File System: NTFS
      Model: WDC WD1600AAJS-08WAA0

      Drive: P:
 Free Space: 21.0 GB
Total Space: 34.5 GB
File System: NTFS
      Model: KINGSTON SA400S37480G

      Drive: T:
 Free Space: 13.6 GB
Total Space: 124.9 GB
File System: NTFS
      Model: WDC WD5000AAKX-001CA0

      Drive: Z:
 Free Space: 130.3 GB
Total Space: 204.2 GB
File System: NTFS
      Model: WDC WD5000AAKX-001CA0

I was wondering why you had connected to a SATA2 which is the slower interface rather than the SATA3? Your SSD is rated for the higher 6GB/s speed - it will benefit from the SATA3 connection. Your point about the cables is good and sometimes the cable can be faulty. It is worth noting that the SATA3 cables generally have a clip that makes sure they are firmly connected.

Phil - long story won't bore you, and don't want to interfere with current diagnostic process. Seatools 'long ' taking an age!

- - - Updated - - -

zbook - I had to abandon the C Drive long generic as after 2 hours it was only at 24%. It was running 'on its own' too. It seems that there is something else perhaps more basic I need to do to sort this? Should I perhaps swap drive cables?

Have you checked the SSD with the Kingston SSD manager that you have installed? Things to do are check that the firmware is up to date, check that it is trimmed and passes any diagnostic checks.

All passed, just a firmware update needed.