Maximus VI formula1 build - C drive is now D drive

[DigitalDiver]

Hi

I have just got my new Maximus formula1 VI (horah). I removed my old mobo and installed the new MF VI with a new intel i5. I connected my original HHD which already has Win 7 installed and was working in my old PC as C: drive and boot disk.

Now when I boot up it starts to boot windows, blue screens after a couple of seconds and reboots. It then says that windows
did not shut down correctly do you want to repair. I did a "windows repair", which finds nothing. When I look at the info, it shows me that what was once my C: drive windows now sees as a 😧 drive?? I have no other SATA HDD and only SATA 1x CD drive.

When I open up a DOS box and check C: it says "volume C: is system restricted".

Any advice would be much appreciated

Thanks in advance

[HiVizMan]

You do not mention what your previous OS installed on, nor how it was installed.

My advice is please do a full clean OS install since you have a new system. That is if you want the full performance of your new system that is.

Make sure you have the right SATA mode for the old install too. IDE used to be the default it is now AHCI

[DigitalDiver]

My previous OS is Win 7 64 bit, AMD based MOBO, 1.5TB SATA (NTFS). This is my boot drive C:

What I dont get is when I plug it into my new Maximus Formula VI it freaks out and windows sees it as 😧 drive when it is the only HDD and now C: is system restricted. I put the disk back in my old case and AMD mobo and it boots up just fine.

I have now ordered a new case and HDD so I can build it all from scratch and install new OS.

Thanks for the nudge in the right direction

[HiVizMan]

Ah right, what is happening is that the new system is seeing the MBR as a drive - the system reserved space.

Yeah a new OS is a must especially going from AMD.

[Poco_OM]

Hello DigitalDiver

In Windows C: is exclusivly for your OS, regardless of the actual drive attached. When booting from a windows OS the boot disc actually creates a virtual OS on your system, that is asigned the drive :C, thus when you look for your drive in CMD it will come up as 😧 because no other version of windows other than the disc is being reconigsed.

The reason you get a BSOD is because your device has all the drivers for your last systems configuration, not the new one. If you swap a drive from identical hardware it may work, and boot, but in most cases hardware from one PC to another differs and as a result a conflict is always created resulting in an unstable OS.

It is also that the MBR is set for your last configuration and not your new one, this really is not an issue as you can rewrite the MBR, however the conflicts mentioned above with the previous drivers still more often than not results in a problomatic OS. Especially going from AMD to Intel.


You can actually install windows without losing the saved data you have on the drive, by just doing an istall without deleting or formating the drive. This will leave a folder in C: called windows old, which will be all the information from your last system. The new windows will have all the drivers for your new system. This would allow you to continue to hotswap the drives. Despite that, it is still better to do a fresh instal on a freashly formatted drive, as it reduces the chanes of conflicts occuring.

You could always back-up your data and then format and fresh install on you current storage drive, as there is no reason why this drive can not be used in this system. Unless you want to run two working PC's.

[DigitalDiver]

Thanks so much for the explanation, makes perfect sense.

I am gonna back it up to my NAS and do a fresh OS install,

Thanks again