ESATA/USB/Card Reader causing Win7 to be snotty during boot up
adarryl
No Man Stands So Tall As When He Stoops To Help a Child. Icrontian
Hello everyone. I have an X4-955 build with this motherboard: http://www.newegg.com/Product/Product.aspx?Item=N82E16813128378 and this card reader: http://www.newegg.com/Product/Product.aspx?Item=N82E16820223108.
When I first built this PC, I installed Win XP Pro on it and the machine + card reader + windows worked perfectly. Since then, I have fresh installed Win 7 Home Premium and with the card reader plugged in, I get hard freezes at boot up. If I completely disconnect the card reader (both the USB and SATA lines) everything works normally. If I just unplug the SATA cable and leave the USB plugged into the motherboard, I get freezes again. There have been no other hardware or software changes.
Anyone have any ideas on how to get this hardware to get along with Win 7? Thanks!
When I first built this PC, I installed Win XP Pro on it and the machine + card reader + windows worked perfectly. Since then, I have fresh installed Win 7 Home Premium and with the card reader plugged in, I get hard freezes at boot up. If I completely disconnect the card reader (both the USB and SATA lines) everything works normally. If I just unplug the SATA cable and leave the USB plugged into the motherboard, I get freezes again. There have been no other hardware or software changes.
Anyone have any ideas on how to get this hardware to get along with Win 7? Thanks!
0
Comments
I don't have any thoughts about the unallocated space. Hope it works out for you.
Win 7 installs a 100mb recovery partition on every new install. You cannot avoid it.
Thanks. Yep, I found that out by doing some research, but I have been grabbing at straws here. When I first built this PC, I put XP on it and everything worked beautifully. Trying to put Win 7 on it has been a nightmare. Last night I used KillDisk to erase the HD and this morning I am trying a new install of 7. If things didn't work so well under XP, I would begin to suspect a hardware problem but there have been no changes. The only change is 7. Hmmm. :/