Partition letters changed after shutdown - now won't boot

Thau

Honorable
Jul 3, 2013
5
0
10,510
Hey everyone,

Thank you in advance for taking the time to read this thread, and possibly provide some help if you're in position to do so.

Alright so the problem is basically: After a shutdown (presumably after a Windows 7 update) the partition letters on my drives has swapped around. A system reserved windows partition which was hidden, is now visible and has taken over the partition letter C: and replaced the previous partition C: with the letter D:, and swapped the remaining three partitions with letters chronologically following thereafter. It now won't boot properly.

I'm running a install of Windows 7 64-bit. Installed on a SSD drive, without my other drive plugged in. I formatted it, made a clean install and all was well and good. I later installed my secondary HDD with all my data. No issues so far.

Fast forward 7 weeks...

However yesterday I shut it down and all seemed normal. I came back home from work and turned on the pc, went to make dinner and came back down to see it's loaded up the Startup Repair tool, which shows a window saying it's unable to repair the issues automatically.

I thought to myself, what issues ? So I went on about it and found out later when starting command prompt and checking disk volumes and partition names that it's swapped all letters around and shows an additional (previously hidden) system reserved drive.

It used to be in this order: C:\ (Windows (SSD)) D:\ (Data (HDD)) E:\ (Data (HDD)) F:\ (HDD))
It's now in this order: C:\ (System reserved (SSD)) D:\ (Windows (SSD)) E:\ (Data (HDD)) F:\ (Data (HDD)) G:\ (Data (HDD))

Basically it loads up the windows loading screen, and when it's just about done and about to display the login screen, I get nothing but a black screen with the cursor hovering over. After 4-5 minutes it automatically reboots and tries to boot up the startup repair, which ultimately fails.
I've tried to boot up in safe mode, however it (again) shows the loading screens with nescessary drivers etc. and then goes to black screen with cursor hovering over it and... you guessed it, reboots.

Soloutions already tried:
SFC /Scannow - Doesn't seem to recognize any corrupt system files
System Restore Point - It does load a restore point, though the result is the same. Blank screen and restart. I haven't gotten multiple restore points so I can't go further back either.
System Startup Repair - Can't fix the issues automatically
Bootrec.exe - Doesn't help either.
Memory diagnostisation of RAM - Found no errors.
Checked that it's booting in the right order. - It is.

I've experienced this before, last time it could boot up and uptill loading explorer.exe and then crashed over, and over, and over, and over, and over again making it impossible to open up files / folders to check for logs etc.
Last time the soloution was a complete reformat of the SSD and clean install of Windows 7, but that was mainly due to the fact I needed it quickly the day after. However it's only 7 weeks since then and now jumps to the same issue.

I'm desperately looking for advice, and any thoughts on this if possible.
I'm willing to provide all the information I can, however since I cannot boot up Windows 7 I cannot retrieve any detailed log files explaining the reasons for the failed boot / crash.

I'm beggining to think that this might be caused by faulty hardware, and in that case how do I pinpoint which module is faulty.

Best regards,
Jakob
 
Solution
Check BIOS to see if you can mark the correct drive as being the boot drive. You may have to use the install disc to run a repair install if using the normal windows repair screen fails. See if you can get a normal boot first and then you can run tests on your HDD and ram for errors.

Dee Kay

Reputable
Dec 22, 2014
863
0
5,360
Check BIOS to see if you can mark the correct drive as being the boot drive. You may have to use the install disc to run a repair install if using the normal windows repair screen fails. See if you can get a normal boot first and then you can run tests on your HDD and ram for errors.
 
Solution

Thau

Honorable
Jul 3, 2013
5
0
10,510


I've been to BIOS settings to see what the current boot order is, it's correct already. I've also disconnected my other harddrive, though I can't get it to load windows.

Also I've already tested RAM blocks for errors using memtest as well as windows memory diagnostisation tool. It's all fine. So is the SSD and HDD when running chckdisk. I can't work this one out.

I've also used my installation disc, however it says it's incompatible with the current version installed on the system. Makes no sense to me since it's the disc I used to install... Might be because it's outdated. The disc is quite a few years old.

Thanks for the suggestions though.

Update: I did some thinking and well, I have an idea that there might be some interrupting element on the HDD doing some stuff to Windows files.
Let me explain; I've installed my OS on a clean SSD disk. I later (after installing Windows) installed my secondary HDD with the rest of my data etc. It also includes a previous installation of Steam, which seems to run fine and also so does any other application, however everytime it launches a game (no matter the fact it's already run before) it goes through the first time setup, trying to install DirectX, Microsoft Visual Studio, Runtime environments etc.
Could that somehow be affecting system files it perhaps doesn't have privilegies to alter and hence corrupts some files ? If that's the case I'd rather wipe the secondary disk as well, make a clean install and never experience this again.
 

Thau

Honorable
Jul 3, 2013
5
0
10,510
Conclusion: Went to a friends computer setup and slapped the SSD in his pc and ran HD Tune Pro to test it out for errors. It's got multiple errors on it and is simply dying. Would not expect after this short-term usage of the SSD, but that's the issue.

Strange how it didn't show any errors at home though.

Thanks for the help. Hope this may help out others in same situation.
 

Dee Kay

Reputable
Dec 22, 2014
863
0
5,360


Sorry about the bad luck with the SSD but your post shows that they DO go bad. Thanks for posting what you found Thau.