Windows 10: Can't boot, not even in safe mode due to INACCESSIBLE BOOT DEVICE

What method was used to boot into safe mode?
Were you able to use safe mode for a day or more without any bsod?

 

Safe Mode was working originally, but it is something I rarely use. A week or two ago I ran Tweaking.com's Windows Repair. I used the option to boot into Safe Mode. After that, my comper was getting a BSOD, every time I tried to boot. I eventually found that Windows Repair had configured my computer to always boot to Safe Mode, and that the BSOD was happening due to booting into Safe Mode. I used a recovery drive to fix the bootloader to boot normally, and after that my computer was booting normally again (but still could not boot into Safe Mode).

It had been many months since I'd tried to boot to Safe Mode, and back then it did work.

 

I restored the working image back to my SSD, and have run scans on the old computer.

Here are the links for the scan result and the screenshots:
ROGER-PC-Thu_07_09_2017_175210_29.zip - pCloud
Screenshots.zip - pCloud
As you will see from the screenshots, I have no FAT32 partition on my SSD. This is also the case on the Windows 10 computer I'm posting this from too.

 

The event log displayed a lot of problems with the drive:
Corruption
Bad block
etc.

Find a method to run chkdsk /x /f /r on the drive
It may take many hours so plan to run overnight

Please run HD tune as per the earlier post.
Please post images in the thread.
For the chkdsk please post a report into the thread using the information in this link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

There was no surface error scan in the attachment.
There was a problem with Interface CRC error count


Please post the results of scannow, restorehealth, and diskpart.



Code: Event[41159]: Log Name: System Source: Service Control Manager Date: 2017-09-07T17:55:33.594 Event ID: 7005 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Roger-PC Description: The LoadUserProfile call failed with the following error: The configuration registry database is corrupt.[/quote] Code: Event[41155]: Log Name: System Source: Service Control Manager Date: 2017-09-07T17:53:33.487 Event ID: 7005 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Roger-PC Description: The LoadUserProfile call failed with the following error: The configuration registry database is corrupt.[/quote] Code: Event[41153]: Log Name: System Source: Service Control Manager Date: 2017-09-07T17:52:56.917 Event ID: 7005 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Roger-PC Description: The LoadUserProfile call failed with the following error: The configuration registry database is corrupt.[/quote] Code: Event[41146]: Log Name: System Source: Ntfs Date: 2017-09-07T17:51:26.182 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Roger-PC Description: A corruption was discovered in the file system structure on volume C:.A corruption was found in a file system index structure. The file reference number is 0x2730000000074c3. The name of the file is "\Program Files (x86)\EaseUS\Todo Backup\BUILDPE\EaseUS-x64\tb\bin". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".[/quote] Code: Event[41146]: Log Name: System Source: Ntfs Date: 2017-09-07T17:51:26.182 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Roger-PC Description: A corruption was discovered in the file system structure on volume C:.A corruption was found in a file system index structure. The file reference number is 0x2730000000074c3. The name of the file is "\Program Files (x86)\EaseUS\Todo Backup\BUILDPE\EaseUS-x64\tb\bin". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".[/quote] Code: Event[41146]: Log Name: System Source: Ntfs Date: 2017-09-07T17:51:26.182 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Roger-PC Description: A corruption was discovered in the file system structure on volume C:.A corruption was found in a file system index structure. The file reference number is 0x2730000000074c3. The name of the file is "\Program Files (x86)\EaseUS\Todo Backup\BUILDPE\EaseUS-x64\tb\bin". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".[/quote] Code: Event[41144]: Log Name: System Source: Service Control Manager Date: 2017-09-07T17:51:17.933 Event ID: 7005 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Roger-PC Description: The LoadUserProfile call failed with the following error: The configuration registry database is corrupt.[/quote] Code: Event[40396]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-08-31T15:21:01.692 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Roger-PC Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: J:, DeviceName: \Device\HarddiskVolume20.(A device which does not exist was specified.)[/quote] Code: Event[739]: Log Name: System Source: Disk Date: 2017-04-09T13:48:16.953 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Roger-PC Description: An error was detected on device \Device\Harddisk2\DR18 during a paging operation.[/quote] Code: Event[740]: Log Name: System Source: Disk Date: 2017-04-09T13:48:16.953 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Roger-PC Description: An error was detected on device \Device\Harddisk2\DR18 during a paging operation.[/quote] Code: Event[4016]: Log Name: System Source: Disk Date: 2017-04-20T17:54:51.205 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Roger-PC Description: The device, \Device\Harddisk1\DR4, has a bad block.[/quote]

 

I'm running chkdsk now. Here's the benchmark and health screenshots (they were also attached in the second link):
Attachment 152262
Attachment 152263

I'll post the error check image when my computer finishes booting, as it seems I accidently saved over it with one of the other screenshots. But, tt finished with no errors, or slowdowns.

There's a description of the only error found in the health tab, at the bottom of the screenshot. It's not a serious issuse, as recent versions of Hard disk Sentinel do not even list it as an error (old versions did).

 

Here is the SSD Health screenshot and the logs form the scans. As I mention in a previous post, there is not FAT32 partition.

Attachment 152269Attachment 152270Attachment 152271

Attachment 152272

 

Chkdsk txt displayed:
Write failure with status 0xc0000022 at offset 0x2000 for 0x1000 bytes.An unspecified error occurred (6e74667363686b2e 1485).

See what happens when run again to fix the drive file structure.
Administrative command prompt: chkdsk /x /f /r

 

I've run chkdsk a few more times. However there always is the write failure and I don't know why. Both HD Tune and Hard Disk Senitnel find no errors on the drive. Also, I scanned the entire drive in DOS with DRevitalize, which also found no errors.
I have attached the last two Wininit logs. There have not been any more logs generated by chkdsk.
Attachment 152370
Attachment 152371

 

For all tests please post images and test results

 

The only new scan I did was from DRevitalize. I didn't take a screenshot, as there was nothing to report. The test ran with zero erorrs or issues found.

 

See if you can clean install windows 10 on the drive and then run chkdsk /x /f /r and find no errors.

Clean Install Windows 10 Windows 10 Installation Upgrade Tutorials

 

I did a clean install and chkdsk found no errors. I had to run Windows Update before I could get chkdsk to run at startup.
Attachment 152388

 

There were problems on the image.
You can try transferring the image again and then another chkdsk /x /f /r.
If that produces an unspecified error then you may need a drive enclosure to move the files.


Was there ever a HD involved in making images?

 

No, I just did a backup from my SSD with Todo Backup to a hard drive. This Windows install was originally on a hard drive. I transferred it to my SSD two years ago, and since then it has just been installed on the one SSD.

 

So you had a HD from which you made an image to a SSD?

Then you made an image from the SSD to another SSD?

So the same image has moved from HD to SSD over time?