So! I'm having a bit of a problem. First time I've had to post, usually if I have an issue someone, somewhere, has asked it and that works. Alas, not the case this time. I've gotten new parts for my computer, an Asus m5a97 le r2.0 mobo, an Asus r7250x 2gb vid card, an amd fx 6300, and 2x4gb Avexi 1600 ram. I've replaced the parts, insured the mobo screwed down tightly and only had mounting brackets where they belong, it powers on just fine, I can access the bios, and I can usually start installing windows 7 64bit professional. Usually. If I have anything sub plugged in, it will freeze. It sometimes gets hung up on expanding windows files, or installing updates. I've found if I wait long enough these problems usually resolve themselves (but man, patience is not my game), the big issue is directly after the first reboot on the new install, it ALWAYS hangs up on the 'starting windows' screen. If I can get past the first couple problems (patience), I ALWAYS get hung up on the next step. I've tried fiddling with the bios settings, specifically, I've tried using legacy bios, uefi settings, sata IDE instead of ahcp (I believe that was the acronym, currently trying to install again or I'd go check), turned off secure boot (though off is misleading, it says windows uefi mode and the other option was other os), tried installing with uefi rather than legacy, under clocked my ram, under clocked my processor, gave my ram a bit extra voltage in case it was a stability issue, swapped out the ram for some older 1333 ram, swapped out the video card, disconnected my extra hard drive (and the target install hard drive is a wd 2tb drive), I'm literally squashing my head in frustration. Any ideas?
Windows 7 hangs up in install
- Thread starter RaDS0N
- Start date
Solution
SaGoat2285
Reputable
- May 19, 2015
- 36
- 0
- 4,560
Awe good Sir
Note
Please use spacing as paragraph as it makes it easier to access faulty steps.
What i see is that you have new parts: so you need to do the following:
Remove everything expect,
1 RAM module(others might be faulty)
(I doubt the following but) listen for any noise regarding the hdd.
Just what you need to do in bios is reset to factory default as we need to access the fault as its new parts.
To be honest with you it does sound like a weakened Motherboard. Don't know how many hdd you have but you need to start from scratch and keep the build simple. Making sure that what you put in is not faulty.
Also, see if you can get a different copy of win(Least probably cause)< maybe you downloaded the win7 and 8 at the same site???
My money is on the motherboard..
keep updating
Note
Please use spacing as paragraph as it makes it easier to access faulty steps.
What i see is that you have new parts: so you need to do the following:
Remove everything expect,
1 RAM module(others might be faulty)
(I doubt the following but) listen for any noise regarding the hdd.
Just what you need to do in bios is reset to factory default as we need to access the fault as its new parts.
To be honest with you it does sound like a weakened Motherboard. Don't know how many hdd you have but you need to start from scratch and keep the build simple. Making sure that what you put in is not faulty.
Also, see if you can get a different copy of win(Least probably cause)< maybe you downloaded the win7 and 8 at the same site???
My money is on the motherboard..
keep updating
Back with another update! Apologies on spacing, doing this all from phone (only computer is mine, and it's down), and for whatever reason I can't see what I type after about 4 lines in (this point right here on).
I popped out the cmos battery, reset the bios to default, and used a single stick of ram. Sadly no difference at all.
Also, just in case it was a CPU error, I pulled it out, insured the appropriate amount thermal paste was there, and reinserted it.
At the moment I'm really leaning towards a faulty motherboard, but any other ideas?
One other thing, almost forgot, I have a disc copy of windows 7 64bit, and it gets one step further than windows 8. It gets to the first reboot and then stops, windows 8 has gotten as far as expanding files. Once. Usually it faults much earlier. I've not had a computer which faults like this at seemingly random times like this, so, you know, at least I'm learning something new
I popped out the cmos battery, reset the bios to default, and used a single stick of ram. Sadly no difference at all.
Also, just in case it was a CPU error, I pulled it out, insured the appropriate amount thermal paste was there, and reinserted it.
At the moment I'm really leaning towards a faulty motherboard, but any other ideas?
One other thing, almost forgot, I have a disc copy of windows 7 64bit, and it gets one step further than windows 8. It gets to the first reboot and then stops, windows 8 has gotten as far as expanding files. Once. Usually it faults much earlier. I've not had a computer which faults like this at seemingly random times like this, so, you know, at least I'm learning something new
SaGoat2285
Reputable
- May 19, 2015
- 36
- 0
- 4,560
Well, if we can factor out some parts, CPU, Ram, Hdd..... there's only the motherboard sir...
Maybe the North Bridge is not proper configure(Factory) and unable to transfer data and such. (It happens)
Maybe the North Bridge is not proper configure(Factory) and unable to transfer data and such. (It happens)
TRENDING THREADS
-
-
News Firefox user loses 7,470 opened tabs saved over two years after they can’t restore browsing session- Started by Admin
- Replies: 59
-
Facebook
Twitter
Instagram