Unable to restart or shutdown PC

nakedtons

Banned
Joined
May 31, 2010
Messages
5,219
Reaction score
1,832
I installed Windows 10 on a new SSD but the current HDD drive is no longer accessible as secondary storage drive or even getting chkdsk to fix it due to multiple corrupt system files because of improper shutdowns as I was left with no option but to turn it off with the power on/off button.

I am asking if I connect the dead HDD with a docking station, will the files still be readable? I cannot afford to lose all my important data.
 
Last edited:

kracie17

Member
Joined
Oct 19, 2017
Messages
268
Reaction score
1
I installed Windows 10 on a new SSD but the current HDD drive is no longer accessible as secondary storage drive or even getting chkdsk to fix it due to multiple corrupt system files because of improper shutdowns as I was left with no option but to turn it off with the power on/off button.

I am asking if I connect the dead HDD with a docking station, will the files still be readable? I cannot afford to lose all my important data.

Yes, you can read off your data provided there is no physical or mechanical failure on the drive.
 

nakedtons

Banned
Joined
May 31, 2010
Messages
5,219
Reaction score
1,832
can the drive still be seen in the Disk Manager?


It may appear as RAW. Use testdisk to dig up the data.

Yes it can be seen but access is denied. Access is only denied after an interrupted automatic canceled disk check upon startup. Guess the process had corrupted the entire drive. I can no longer run chkdsk on it as all access to the drive is denied.
 

Koenig168

Arch-Supremacy Member
Joined
Nov 4, 2007
Messages
10,038
Reaction score
1,748
You can take ownership of the drive and then edit the permissions if necessary (google it) to restore access. This is a bit technical.

Alternatively, you can run a data recovery software like easeus to backup the files to another HDD.
 

nakedtons

Banned
Joined
May 31, 2010
Messages
5,219
Reaction score
1,832
You can take ownership of the drive and then edit the permissions if necessary (google it) to restore access. This is a bit technical.

Alternatively, you can run a data recovery software like easeus to backup the files to another HDD.

Unable to do so. Windows Explorer hangs when editing permissions.
 

kracie17

Member
Joined
Oct 19, 2017
Messages
268
Reaction score
1
Yes it can be seen but access is denied. Access is only denied after an interrupted automatic canceled disk check upon startup. Guess the process had corrupted the entire drive. I can no longer run chkdsk on it as all access to the drive is denied.

im curious to know what you meant by access denied? in terms of permission? if it takes too long to get that permission settings or even load the contents of the drive in explorer, likely chance is that your drive is dying.

pardon me if im wrong. what i understand from you is when you connect the drive, intend to open the explorer and it loads forever till you click cancel, and for you to access the drive it says denied. is that right?
 

nakedtons

Banned
Joined
May 31, 2010
Messages
5,219
Reaction score
1,832
im curious to know what you meant by access denied? in terms of permission? if it takes too long to get that permission settings or even load the contents of the drive in explorer, likely chance is that your drive is dying.

pardon me if im wrong. what i understand from you is when you connect the drive, intend to open the explorer and it loads forever till you click cancel, and for you to access the drive it says denied. is that right?

Location is not available. Access is denied. Even in CMD, access is also denied.
 

nakedtons

Banned
Joined
May 31, 2010
Messages
5,219
Reaction score
1,832
that is essentially what you did


have you tried accessing the drive with linux? CAUTION: This may screw your disk further but it's already screwed so much anyway...:s22:


DO NOT!!! use any linux ntfs repair tools on NTFS drives.

I used to have full access to the drive before the damn Windows automatic repair of my storage drive and then canceled without warning upon startup one day screwed up my drive. I think that it isn't about the security permission. It is that my drive is screwed.

I should not had plugged it into my motherboard. Should had used it as an external drive with a docking station or enclosure and only switch it on after Windows is fully loaded. The best thing I can do is data recovery unto another new storage drive.

The worse thing is that even my SSD is experiencing the same shutdown problem from a fresh install and I am forced to turn off my computer using the power on/off button. Not sure if it is a bug from Windows 10. If this carries on, even my SSD will be screwed up too and I can forget about using my desktop PC.
 
Last edited:

nakedtons

Banned
Joined
May 31, 2010
Messages
5,219
Reaction score
1,832
Finally, obtained a crash analysis on what has been preventing my computer from shutting down and restarting. Any solution is appreciated.

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 5/1/2019 12:35:46 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050119-10218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3730)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFF880A0ED59040, 0xFFFFFC0E85645900)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 5/1/2019 12:35:46 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFF880A0ED59040, 0xFFFFFC0E85645900)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ Forums. Forum members and moderators are responsible for their own posts. Please refer to our Community Guidelines and Standards and Terms and Conditions for more information.
Top