Installation ram issue

jabbado · 23 Sep 2010

Just interested if anyone else has seen the following problem with Win 7 installation.
BTW this is a GB p55-ud3r board with 4 gig ram, core i5 not overclocked.

I decided to upgrade to 64 bit after using 32 bit since it came out last year. Back then I remember having no issues with the 32-bit install, and the comp is the same config as it was then, except for BIOS version. So to make things easier I purchased a new 500 gig drive. Tried installing x64 version and it would complete but upon the first reboot where it updates the registry settings it would restart and show the "Windows failed to start" screen. And would just remain in this reboot loop.

So I tried installing the 32 bit using the same legit copy that I used last year, and it did the same thing. OK, the hd is DOA then. So I tried installing 32 bit on my old drive and it still did the same reboot loop! I checked ram with memtest+ - all good. New HD checked out fine too.

Anyway, after flashing to the newest BIOS etc and trying just one stick of ram at a time this problem remained. Then after 2 days of hair-pulling I decided to put the single stick of ram in slot #3 (slots #1 & #3 are on different channels), thinking maybe slot #1 is fried. And ta-da, Win 7 booted.

After the successful boot I put the stick back in slot #1 and it still booted successfully. Ran the "Memory Diagnostic Tool" at startup and it found no problems. Put the other stick in as well and still no problems. It's been running like a dream since.

So any ideas why this happened - why win 7 won't install with ram in the first slot? Since the only thing that has changed with the pc config is bios updates, I'm thinking Gigabyte has screwed something there. But it doesn't explain why everything is working fine with all sticks used and windows is up and running.

TVeblen · 24 Sep 2010

Hello jabbado. Welcome to the forum.

The first idea that came to mind was that there was an error in the memory controller. This gets complicated because the Intel Core i series motherboards have moved the memory controller from the (now extinct) Northbridge controller to the processor itself.

We used to routinely do a procedure called a "CPU Parameter Recall". This was (and I think still is) important to do when updating a bios or particularly when upgrading a CPU. Here it is:

Record all your preferred BIOS settings (so you can set them back later easily).
Enter the BIOS and Restore Bios Defaults. Save & Exit to reboot.
Enter the BIOS again. Then shut down the computer.
Disconnect the power from the system and wait at least 2 minutes (This performs the CPU Parameter Recall).
Reconnect the power, boot, Enter the BIOS, and Restore BIOS defaults again, Save & Exit to reboot.
Enter the BIOS again. Now restore all your preferred settings. Exit and Save. Let it boot into Windows.

When you update a BIOS it is important to Restore BIOS defaults before flashing the BIOS and after. If you did not do this when you upgraded your BIOS that may explain what happened.

Hope that helps.

jabbado · 24 Sep 2010

TVeblen, thanks for your input.

Yeah I know about the integrated memory controller with the new cpu's. That's what had me worried at first.

I did a search about CPR and it seems to be a feature of Asus boards only?? Anyway, yes I always load defaults before and after flashing. But on this build I've been running it stock since I haven't got round to buying a decent HSF yet.

So it wasn't a problem with any oc setting or anything like that.

It's still puzzling me why this happened. The system has been running perfectly stable for the past couple of days though, knock on wood. :)