Froze and then restarted

[thready]

Last time this happened somebody told me that I might have had bad SATA cables. This time it happened again. I also want to bring attention to a thread I made on Malwarebytes.

https://forums.malwarebytes.org/index.php?/topic/163644-cant-click-fix-now/

I don't know if the problems are related. I scanned my PC with Webroot Anywhere and MBAM and nothing turned up.

My thoughts are it's a bad drive because it has all of the symptoms of a bad drive. However my C drive is an SSD and AFAIK SSDs are way more stable than HDDs. But I do have 2 HDDs I use as data drives so can a bad data drive also cause this stability issue? A few months ago I turned on my PC and it didn't see my F drive which is an HDD and my main data drive. I had to restart for it to detect it. Acronis drive monitor showed some issues with it but I haven't had those issues pop up and it's been over a month.

Also I leave my PC on and I have it run a scheduled task to shut down at 1:00 AM and I made it so it will do that regardless of if a program is running and this morning it was still on with MSI afterburner giving me a message about C: being full and I had to do a hard restart.

 

[Arc]

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e

Hi.

Can you uninstall Acronis, at least as a test basis?

Also, the OCZ one seems to be the primary HDD .... make it sure that it is running with the latest firmware.

• OCZ Toolbox and Firmware Update Releases
• How to Upgrade OCZ SSD Firmware | StorageReview.com - Storage Reviews

Do the same for the Crucial SSD, too.

• How to Upgrade Crucial SSD Firmware | StorageReview.com - Storage Reviews

Let us know the results.
___________________________________

BugCheck 7A, {fffff6fc400077b0, ffffffffc000000e, b2bf5860, fffff88000ef6630}

[COLOR=Red]*** WARNING: Unable to verify timestamp for fltsrv.sys
*** ERROR: Module load completed but symbols could not be loaded for fltsrv.sys[/COLOR]
Probably caused by : partmgr.sys ( partmgr!PmPnp+b4 )

Followup: MachineOwner
---------