Windows start error after every power cut.

Asrock 775dual-vsta desktop motherboard...
February 22, 2012 at 03:13:02
Specs: Win7, E4500 / 2GB
I recently set up a computer to use as a server, Installed windows, updates drivers and everything smooth. Ran perfectly for a day worked fine as a minecraft server. The next day I went to start it up and it went directly to windows startup recovery. I was unable to recover it easily so I figured I would just re-install and just put it down to bad luck. I re-installed windows and once again it went smooth, installed new software and everything was working fine. Next day I boot it up and it went right to windows recovery again.

In both cases I noticed that the C: drive had been changed to D: in the dos prompt. The first time the night before I unplugged a power board it was connected to (while it was off) and this time there was a power failure during the night so I'm wondering if it is related. However all the BIOS settings are completely stock so even if the BIOS battery was flat (its not) and the power went out it was on default settings anyway. I don't want to have to re-install everything if it will do the same thing again, so I was wondering if I could get your insight on the problem.

Hardware:
ASRock 775Dual-VSTA
2GB DDR2
X800GTO AGP
320GB SATA Western Digital
Win7 Home Premium

Thanks Guys.

Mattwizz3
P35-DS3R
4GB DDR800
E7500


See More: Windows start error after every power cut.

Report •

#1
February 22, 2012 at 05:40:49
Please explain exactly where you are seeing the information below.
"In both cases I noticed that the C: drive had been changed to D: in the dos prompt."

Is anything identified as the C drive then? Do you have an external drive connected?

Is the 320GB SATA the only drive in the system?

The 320GB drive is most likely a SATA II model. Your controllers are SATA I. Setting the jumper on the rear of the drive to SATA I settings may correct the issue. Also, there may be a setting in the BIOS screen to increase the seek time to configure the drives. If you see that option then increase it to the maximum value which may be 5 seconds.

Finally, SATA data cables are susceptible to damage if tightly folded. Unfolding MAY correct the problem or you may need to replace the cable.


Report •

#2
February 22, 2012 at 13:03:45
Yes the 320GB drive is the only drive in the system and there is no other storage attached. I'm fairly sure the small 100MB partition Windows makes on setup has been assigned to C:

I didn't know SATA II Drives had jumpers to configure them to SATA I so I'll check that and the cable. Thanks for your help.

Mattwizz3
P35-DS3R
4GB DDR800
E7500


Report •

#3
February 22, 2012 at 14:53:26
Also the time delay to configure the drives in the BIOS.

Report •

Related Solutions

#4
February 22, 2012 at 23:06:02
I swapped out the cable with a known good one with no success and there does not seem to be a jumper setting on the drive for SATA I and the BIOS had no HDD configuration delay available. It is actually a WD Green 500GB drive by the way not a 320GB, sorry for that. I have another computer running on this exact same model motherboard with a 500GB WD Black drive without issues, also running windows 7 and it has run smoothly with no problems from day 1.

Mattwizz3
P35-DS3R
4GB DDR800
E7500


Report •

#5
February 22, 2012 at 23:37:08
Well, there seems to be two different WD 500GB green series drives. That said, the drive would not have come with a jumper installed on any of the pins but on at least one of the series there is a jumper block pictured on the newegg site.

I covered the jumper and the other two suggestions as places to start because those are easier to fix. I don't think that is your problem now though.

If you are correct in assuming the 100MB partition is being assigned the C letter then that partition must be marked as active. After reading about why the 100MB partition is created by default it appears that normally that partition shouldn't be assigned a drive letter.

If you are using the Windows 7 DVD to setup the partitions then according to riider, you then get the 100MB partition you mention. Using the WD drive prep utility can avoid the partition.

If you can't cure the problem and you don't use bitlocker you could merge the 100MB partition into your OS partition. At that point I think your OS partition would then be labeled C.

Click on the Google link below and read some of the technet and MS based links there to gain incite into your problem.

http://www.google.com/search?q=Why+...



Report •

#6
February 22, 2012 at 23:51:01
Thank OtheHill for your help. When I wrote that I had another PC with the same M/B and similar configuration I thought I'd compare the BIOS settings of the two PC's and one thing stuck out. On the working computer the SATA controller was set up for RAID and the non working one was set up as 'non-RAID' changed that setting and its working. I think the reason why the computer stopped working after installing windows smoothly is because windows update probably downloaded and installed RAID drivers which messed up the PC if it wasn't configured for RAID in the BIOS.

Thanks for your help, I probably would have just dumped the M/B and just used one of my S754 AMD systems.

Mattwizz3
P35-DS3R
4GB DDR800
E7500


Report •

#7
February 23, 2012 at 11:12:19
Glad you got it sorted out.

Report •

Ask Question