Repeated almost daily BSOD for several months

JamminR · 01 Mar 2024

I run a win10 22h2 machine in a rack in a utility closet.
On that machine, I run Plex media server for family, and Tautulli monitoring app.
About 6-7 months ago (to my memory) - I started experiencing frequent restarts - I thought it was 'just' Plex - the Tautulli monitoring app emails when Plex is back up. Until recently when I made some time, I determined that the machine was BSOD'ing and Tautulli was simply letting me know it had come back online again.
I've thrown everything I know to do in hopes to correct the issue.
One bad experience I had was throwing an incorrect driver at it - system restore didn't fix, pc wouldn't boot.
About the 11th of February (I think), I used a 'restore Windows' advanced feature - then re-installed updated drivers, minimum software. PC seemed to run smoothly for a week - then started doing almost daily BSOD and restarts.

Anyone's help in getting a machine that will last until a script i have to reboot it manually once a week again would be welcome.
Link to the v2 data as requested in 'how to report'
VAULT-(2024-03-01_17-14-19).zip - Google Drive

JamminR · 05 Mar 2024

Berton said:

Read the link but didn't find mention of using a UPS, think anything running in a server function should have one to mitigate any type of power fluctuations to the machine, would help to determine if the issues are in the computer or not. If heat could be an issue perhaps a ventilated door on the closet/storage room would help or maybe a grill over a hole above the door to let the rising heat escape.

A Cyberpower 1500va/1350W UPS is used to power the rack that contains this PC (850W psu), an 8bay (5 disks) Synology NAS, a TP-link 16 port 1GB switch, a Motorola MB8600 cable modem, a netgear R7000 router and a 15 inch LCD monitor.
UPS reports 12-15% load average, bounces 18-20 at highest peak during PC start after a crash.

HWINfo64, with logging enabled since I've not been able to continuously keep Windows running for more than 3-4 days straight lately, shows a average CPU temp of 38C. PC is a 4U ATX rack case with 3 120mm front inbound fans and 2 80mm rear exhaust (+ PSU exhaust)

The closet's door remains open, connected to a laundry room 3-4x as long but same width. That laundry room has a single HVAC vent. It get's slightly warmer (7-8F/15-16C more) during Summer months when dryer is running, but over heating seems to not be related from logs. (hwinfo or event logs)

zbook · 08 Mar 2024

Please post share links:

1) Long Generic test:

https://www.seagate.com/content/dam/...00869623_B.pdf

https://www.seagate.com/content/dam/...sInstaller.exe

2) HD Tune website

a) Health
b) Benchmark
c) Full error scan

3) chkdsk /b /v C:
4) chkdsk /b /v D:
5) chkdsk /b /v E:
6) chkdsk /b /v F:
7) chkdsk /b /v G:

C:\WINDOWS\system32>chkdsk /b /v C:
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 as needed

8) https://www.tenforums.com/attachment...p_plus_log.bat

9) https://www.tenforums.com/attachment...kfromevent.bat

Batch files for use in BSOD debugging

10) 8 or more passes:

Memtest86+ | The Open-Source Memory Testing Tool

MemTest86+ - Test RAM

Code:

      Drive: C:
 Free Space: 889.1 GB
Total Space: 953.3 GB
File System: NTFS
      Model: NVMe Samsung SSD 970 SCSI Disk Device

      Drive: D:
 Free Space: 583.5 GB
Total Space: 1907.2 GB
File System: NTFS
      Model: AMD-RAID Array 3  SCSI Disk Device

      Drive: E:
 Free Space: 5273.7 GB
Total Space: 7630.8 GB
File System: NTFS
      Model:  TOSHIBA HDWG180 SCSI Disk Device

      Drive: F:
 Free Space: 4245.0 GB
Total Space: 7630.9 GB
File System: NTFS
      Model:  TOSHIBA HDWG180 SCSI Disk Device

      Drive: G:
 Free Space: 2626.5 GB
Total Space: 2861.0 GB
File System: NTFS
      Model: AMD-RAID Array 5  SCSI Disk Device

JamminR · 08 Mar 2024

Thank you @zbook - It seems about the time you were posting instructions for me to gather information, I was shutting the machine down and unracking it.
For list of things I tried to fix too long to mention in time i have, i broke the system worse than when i reported.
Rather than run another 'repair' windows like I did Feb 11, i've taken the machine out of the rack, am cleaning internals (for running almost 24/7 for two years, it's extremely clean - the sponge filter on the front of the case must work amazingly well)
I'm also updating the GPU so I can hardware transcode x265.
After the physical work, I'm going to wipe C drive, and the D RAID1, then re-image from clean install and AMD's recommended RAID driver (sigh, they have 3 in same pre-Windows zip, and finding the documented table of which to use was challenging and painful - it doesn't so much differ for bridge chipset as it does the processor running on it)
D was the only true RAIDed drives - all others just listed that way.

I'll be back with the requested information if after wipe/re-image it still acts quirky.

Thanks again all
I had already run memtest 2-3 days without issue, so reasonably sure it's not a memory issue.
Very well could be something else.

JamminR · 17 Mar 2024

Some time later...
Still crashing but much less regularly. I've started a post in the Plex forums as it always seems to crash during Plex maintenance, and might be related to when Plex updates it's EPG.
I'm also going to start obtaining the information requested by @zbook in case it can help determine if it's a 'plex software primary culprit' issue versus 'Plex maintenance just causes the main culprit to kick in'