Occasional PC freeze

Thank you. V2 log attached.

Thanks.

Timeline is used to take on-the-fly backups every few minutes of changed files, I've used it for 6 or more years, been very useful. I believe it's analogous to Apple's Time Machine. I've disabled the Timeline service so it doesn't start. The Timeline drive is also the drive that Reflect writes to. However I also copy MR files to a second drive for security.

Disk 9 isn't listed in the Disc Management list currently but that may be because I sometimes have extra external drive(s) powered up so drive numbers are, I assume, dynamically assigned.

Currently running a CHKDSK /r on the Timeline drive, it's showing >6.5 hours to go so I'll leave it running overnight.

Should I run CHKDSK on any other drives? SSD or spinning or both?

The symptoms which you give point to a hardware problem,because-
1 Freezing occurs during POST,which eliminates Windows and software.
2 Freezing occurs during Windows operation,which eliminates BIOS.
The POST process checks attached hardware---all types of drives,keyboard,memory etc,so it would be a good idea to disconnect unnecessary ones,such as printer, webcam,before proceeding further.
The only safe and satisfactory method of hardware checking is by substitution,including leads,or if possible by removal e.g. USB sticks.
The PSU is almost invariably overlooked.There are three [3] output rails,3.3v,5v.12v and the only way to positively check is by meter.Unless you are an expert,waving probes around a live circuit will"light up your life",probably once only.
Best not to.

I've now run CHKDSK on drive E: the external "Timeline" drive; on the SSD C: (which completed instantly with no visible log, what does CHKDSK do for an SSD?); and on the internal spinning drive D:

The event log entries are attached as text files, neither the E: or D: results show any bad sectors.

Clearly the PSU is a possibility, photo of the spec. details attached.

The PC was built in March 2011. Since then I've changed the original single spinning drive to an 512GB SSD (C:) and a WD 2TB spinning drive (D:); the memory changed to Corsair Vengeance; the optical drive changed. And a 4-port USB3 card added. So the MB, CPU, PSU are original.

The PSU is becoming long in the tooth and 500w could now be borderline.The addition of a usb card further drains avilable power and is often missed when calculating power usage.
Perhaps a minimum of 600w,or more,is a preferable option.
Also when changing components,the power plug and socket sometimes don't have a snug fit.

Firstly thanks to all who have contributed to this thread. It's both helped me and educated me. As said elsewhere, every day is a school day - even to a septuagenarian like me.

After being powered off for 12 hours overnight, PC booted up fine this morning. Sadly it's had good days before, I want a couple of weeks of no problems before being comfortable with it.

Some quick comments. Likely to be too busy over the next few days to progress this significantly:

• SAM & MBM are rarely run, as far as I'm aware they don't load with Windows, I just run them ever 2 or 3 weeks or so in scan mode to check things. I then ensure that anything left running, especially MBM, is closed. However just checked Services and found that SAS Core Service was running, now stopped and disabled.
• I ran CHKDSK on the C: drive (it's an SSD). It ran on the next reboot and went to 100% instantly but no entry in the Event log. When time permits I'll boot into command mode and rerun.
• I reverted to 1909 by Windows GO BACK to earlier image.
• PSU:
  
  • I'm increasingly tempted to change it, as you say it's long in the tooth.
  • Purely for indicative purposes I've run the config through a couple of wattage calculators, they both suggested 350-400W, but I'd also thought 600W would give a reasonable margin.
  • Any thoughts on brands to go for? Corsair? Coolermaster? Seasonic? Others?
  • Is it worth going modular? I currently have 3 or 4 unused internal power leads unused.

- - - Updated - - -

Before going out managed to get CHKDSK C: to run via Safe Mode / Command prompt boot.

Event log result attached, doesn't look to be any issues.