Problem with Win7

**Obert Harold** · 02-23-2012, 10:33 AM

Hello! I have a problem with Win7. It is no longer lässst start and shows no surface to more. In short, nothing works anymore. Now I have inserted the Win7 disk and wanted to make Win 7 on the new SSD on it, but he bleated around, not that it would create a system partition. So I deleted everything on the SSD and then install it wanted, however he still bitches around. I have installed a hard drive, but this is strangely treated as a dynamic disk. This can not delete them in order to install it since it. Can you help me? If my data is lost I do not care, the main thing is the PC running again.

**Obert Paschal** · 02-23-2012, 10:33 AM

You have probably blown off any service to you. Have you ever tried the repair console from the DVD? Do you have XP or Linux on CD or a lie? So you could also delete and reformat SSd then wanted to actually see the SSD Windows Seven. Boats times from the Windows DVD and hit you so far before you're up in the menu where you select the disk / partition you. Make a pic so I can make me a picture. Because the way you explain it to me I can make any sense of it.

**Donan Kevin** · 02-23-2012, 10:34 AM

What he knows because he just on the SSD? Any partitions? Have you already deleted all the partitions. So the complete SSD deleted? And look at running times in the bios to the mode in which the SSD.

**Orson Angelo** · 02-23-2012, 10:35 AM

You have installed and connected to multiple hard drives – right? Then bung times from all hard drives except the SSD. Make sure that the SSD is connected to the first SATA controller on the P67 chipset. So one of the two SATA 6Gb / s ports. My guess is that the BIOS the hard drives in a different order is entered provided as a normal way and therefore Windows produces the error. So - just connect the SSD and to the first SATA 6Gb / s port on the Intel chipset not the Marvell controller.

**Sidonia Donan** · 02-23-2012, 10:35 AM

If the SSD is set as the first drive? For me, it has also rumgemeckert times, but with a HDD. When I had it set as the first record, we went at once.

**Henry Orson** · 02-23-2012, 10:36 AM

Yes, this is somehow an Asus bug. If you have multiple hard drives are installed, they must be sorted in the correct order in the BIOS since Windows always wants to boot from the first drive on the list. This is not bootable but can not start windows and it displays an error message. This happens especially when an additional hard drive is installed and is connected to a SATA controller that has a lower number than the first plate.