New
#1
BSOD: Possibly caused by Errors on Hard Drive. Not sure...
For more on this BSOD (Crash), please refer to C Drive Missing in Windows 10 - Page 3 - Windows 10 Forums.
Attachment 81014
For more on this BSOD (Crash), please refer to C Drive Missing in Windows 10 - Page 3 - Windows 10 Forums.
Attachment 81014
That link to the BSOD doesn't work. So I am uploading a new one.
Hello? Can someone tell me what happened here and why it crashed?
Unfortunately you need to be patient Jesse. This section is under served and over populated.
You also didn't read the first post of this thread,
Waiting for a response? Post here. - Windows 10 Forums
Before posting in it, it is for those waiting longer than 24 hours.
Unfortunately that is just how it is, so just be patient.
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.
Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests
- Short Drive Self Test
- Short generic
- Long generic
If the short generic fails, no need for the long generic.
NoteDo 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 Forums
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 Source: 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\00000029) was retried. Event[10415]: Log Name: System Source: disk Date: 2016-05-21T17:23:17.695 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Cindy-PC Description: The device, \Device\Harddisk0\DR0, has a bad block.
Axe,
This BSOD thread is an offshoot thread: C Drive Missing in Windows 10 - Page 2 - Windows 10 Forums
Chkdsk /R and Defrag (NavyLCDR post) were executed and then the BSOD.
There should be event logs for the Chkdsk /R
Backup the user data, check HDD cables, re-seat memory??
Just some thoughts ...
Bill
.
I'd like to see the event log then:
Chkdsk Log in Event Viewer - Read in Windows 10 - Windows 10 Forums
On the right side in event viewer you see the options 'save selected events', save the log as .txt and upload the .txt file.