Hi Jesse,
As you suspected the hard drive is having problems, it is possible that the hard drive is the root cause as the crash was caused by a memory access violation but that cannot be said with 100% certainty until it has been tested as a memory access violation has multiple causes.
Please try to run following tests, read it carefully and provide the requested photos/screenshots, to identify what the situation is with the hard drive.
Please note that the tests may cause the system to crash again due to the bad blocks, if this is the case then I recommend to backup the data that cannot be lost and replace the hard drive a.s.a.p. or let it be replaced if there is warranty covering this.
Diagnostics Test
HDD TEST
Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help blog
Run following tests
- Short Drive Self Test
- Short generic
- Long generic
If the short generic fails, no need for the long generic.
Note
Do not run SeaTools on an SSD as the results will be invalid.
Post screenshots/photos of the test results
Run chkdsk
Disk Check - Windows 7 Help blog
Run HDTune to
- scan for errors, no quick scan but full scan
- check the health,
- benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
- the error scan,
- the health,
- the benchmark incl. following
- transfer rate,
- access time,
- burst rate,
- cpu usage.
The event logs has many of these logs that started to show up 4 months ago.
Code:
Event[10414]: Log Name: System disk Date: 2016-05-21T17:23:14.316 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Cindy-PC Description: The IO operation at logical block address 0x1c6d598 for Disk 0 (PDO name: Device