Help: new RAM - Windows 7 won't start, but XP does

[colombox]

Hello, I just bought two Corsair XMS3 PC3 12800 (1600 MHz) 2x4GB RAM modules and it turns out that when I start Windows 7 it gets stuck when it says "Starting Windows". However, it starts Windows XP without any problems. The BIOS values are set to default. Even with the memory at a lower frequency (1333 MHz) Windows 7 still won't start.

What could this be due to?

The motherboard is Gigabyte P55-UD3L
Intel i3-550

Thanks, goodbye.

[cobito]

Test each module separately in different slots to see how it behaves.

[whoololon]

But a CMOS reset when placing the new ones helps. ; )

[colombox]

I don't think removing the battery affects it, it seems clear that the Gigabyte P55-UD3L motherboard is very sensitive with the memories because I have tried with Kingston HiperX and Corsair XMS3, but it doesn't support them with Windows 7. With Windows XP there is no problem.

But with the old Kingston 2x2GB memories there is also no problem with Windows 7, and these are 1333 MHz, I have them set to 1600 with 1,6V and the CPU from 3,2 set to 3,8 GHz.

I have tried with the Corsair a single module in all the DIMMs and nothing, it doesn't start up on W7, with everything on Auto, then safe values in the BIOS and at 1333 MHz without OC.

[whoololon]

From what I've seen, the base voltage for the RAM on that board is 1.5 and these go to 1.6.
Just with the new ones and values set to auto, what voltage does the board give them?
If it boots with XP you can see it from there.

[colombox]

The voltages are all in Auto except the RAM which I increased by 0.1 V (1.6)

[gamingpy]

and if you set the timings in the configuration before starting, have you already tried it?
The strange thing is that if it starts up on Windows XP and not on 7, it means it's not a problem with the motherboard.

[colombox]

@gamingpy:

and if you set the timings in the configuration before starting, have you tried it yet?
The strange thing is that if it starts on Windows XP and not on 7, it means it's not a motherboard problem.

Well, the timings are on Auto (SPD). What I don't know is if they take the timings from the old Kingstons or the ones from the Corsairs; I didn't look into that. When I look into it, I'll comment on it.

Can't it be that Windows 7, being 64 bits, is more demanding with the memory parameters than Windows XP 32 bits?

Thanks, goodbye.

[gamingpy]

@colombox:

Well, the timings are in Auto (SPD). What I don't know is if they take the timings from the old Kingstons or the Corsairs; I didn't look into that. When I look into it, I'll comment on it.

Can't it be that Windows 7, being 64-bit, is more demanding with the memory parameters than Windows XP 32-bit?

Thanks, goodbye.

Supposedly, when it's in AUTO, it takes the timings from each ram you put in the socket, that is, the bios detects the timings that it uses, but the most preferable for me would be that you put it in manual mode, both the timings and the voltage, you're sure to find it in the ram itself, pre-printed, if not, check the technical specifications from its website, I had a similar problem and I solved it like I just told you, because you say that win7 can't be more demanding than winxp, since it's supposed to be an improvement of xp and therefore should consume a little more than the previous one, it's always like that, according to what I understand.

[colombox]

Okay, so I'll put it like this, let's see how it goes. Thanks.

[colombox]

Well, it seems that this motherboard does not support 4 GB memory modules, not even by setting them to 1333 MHz.

I bought 2 identical 2 GB Kingston 1333 MHz modules to the ones I had, and I already have 8 in total. Now everything works fine, the memories up to 1600 and the i3 to 3.8 without problems.

Greetings