BSOD/freeze after exactly 11min 15sec uptime everytime

(Frustrating - wrote another post which got wiped when I went to add an image)
Anyway, this shows MsMpEng using a lot of CPU shortly before the PC froze. Unusually this time the disk blue line didn't max out when it happened. However all files in the disk pane were MsMpEng when it froze. Seems like Windows Defender might be overloading the disk to the point that a dump file can't be written and even the boot device becoming unavailable until a hard reset. Will pick it up again tomorrow.

Many thanks axe0. The difficulty I have is that the system is only up for 11 minutes maximum which doesn't always allow time for these scans to complete. I'll post the HDscan results as text, below, for now as scanning and then creating images often leaves me out of time.

I had to run chkdsk from the command prompt accessed from Windows 10 media installation disk. I haven't found a way to feed the results into a text file. (Event Viewer didn't show much detail and I suspect was only refering to scans at startup). There were however several disk errors not of of which seem to have been repaired.

I've managed to create a Macrium rescue DVD and will probably go ahead get a new SSD drive to clone to.
Must reboot now before lock up.
Here's HDscn results in text

HD Tune: Samsung SSD 840 EVO 120G Benchmark

Transfer Rate Minimum : 1.4 MB/sec
Transfer Rate Maximum : 408.9 MB/sec
Transfer Rate Average : 268.2 MB/sec
Access Time : 1.7 ms
Burst Rate : 171.0 MB/sec
CPU Usage : 9.3%


HD Tune: Samsung SSD 840 EVO 120G Information

Firmware version : EXT0AB0Q
Serial number : S1D5NEAD705408N
Capacity : 111.8 GB (~120.0 GB)
Buffer size : n/a
Standard : ATA/ATAPI-0 - SATA II
Supported mode : UDMA Mode 6 (Ultra ATA/133)
Current mode : UDMA Mode 6 (Ultra ATA/133)

S.M.A.R.T : yes
48-bit Address : yes
Read Look-Ahead : yes
Write Cache : yes
Host Protected Area : yes
Device Configuration Overlay : yes
Automatic Acoustic Management: no
Power Management : yes
Advanced Power Management : no
Power-up in Standby : no
Security Mode : yes
Firmware Upgradable : yes

Partition : 1
Drive letter :
Label :
Capacity : 350 MB
Usage : 0.00%
Type : NTFS
Bootable : Yes

Partition : 2
Drive letter : C:\
Label :
Capacity : 113671 MB
Usage : 53.37%
Type : NTFS
Bootable : No

Partition : 3
Drive letter :
Label :
Capacity : 450 MB
Usage : 0.00%
Type : unknown (27h)
Bootable : No



HD Tune: Samsung SSD 840 EVO 120G Health

ID Current Worst ThresholdData Status
(05) Reallocated Sector Count 100 100 10 0 Ok
(09) Power On Hours Count 98 98 0 7753 Ok
(0C) Power Cycle Count 97 97 0 2880 Ok
(B1) (unknown attribute) 97 97 0 33 Ok
(B3) (unknown attribute) 100 100 10 0 Ok
(B5) (unknown attribute) 100 100 10 0 Ok
(B6) (unknown attribute) 100 100 10 0 Ok
(B7) (unknown attribute) 100 100 10 0 Ok
(BB) (unknown attribute) 100 100 0 0 Ok
(BE) Airflow Temperature 73 65 0 27 Ok
(C3) Hardware ECC Recovered 200 200 0 0 Ok
(C7) Ultra DMA CRC Error Count 99 99 0 4 Ok
(EB) (unknown attribute) 99 99 0 421 Ok
(F1) (unknown attribute) 99 99 0 -1497246429 Ok

Power On Time : 7753
Health Status : Ok


HD Tune: Samsung SSD 840 EVO 120G Error Scan

Scanned data : 114427 MB
Damaged Blocks : 0.0 %
Elapsed Time : 0:21

OK, booted from the excellent Bitdefender Rescue CD (on USB) and logged in from Firefox on that.
Bitdefender showed 12 I/O errors before the CHKDSK scan mentioned in my previous post and still one afterwards. I can't get any detail on what these errors are but I'm feeling the disk is a bit flaky and should clone the image as a precaution if not an actual resolution.

I'm wondering if disk errors could cause the 11 minute lockup (perhaps by corrupting a certain file that is accessed by some delayed service or something. It's 11 minutes whether the system is in use of left idle, btw). Or perhaps the disk errors are caused by the frequent hard rebooting of the PC with all the lock ups. It's an SSD drive but I guess they're susceptible to some of the same issues as magnetic drives in this regard?

I know it might take a while for a response to this post and am thinking I might just pop out and get a new drive anyway.

Yay! Three more chkdsks later (the last from the command prompt of Macrium Reflect rescue disk being the only one to actually finish (and repair the MFT)) and the clone process finally worked and the computer has now been running on a new disk for more than 11m 15s for the first time in weeks.
Many thanks to axe0 and all.