i7 Build: Win7 32-bit ok, 64-bit BSODs on install

foop

foop

foop

Associate
Joined
11 May 2004
Posts
131
I'm upgrading to an i7-based machine. Windows 7 Home Premium 32-bit Retail will install fine. 64-bit BSODs just after the first "Starting Windows" as it boots from the install CD with

STOP: 0x00000124 (0x0000000000000000, 0xFFFFFA8001DD8028, 0x00000000B2000000, 0x0000000000030005)

I've got

i7 930 at stock speed
Gigabyte X85A-UD5
3 x 2GB Kingston HyperX 1600
EVGA GTX260 Core216
Corsair H50 cooler
Intel X2-M 160GB

I've disabled all onboard devices in the BIOS, and changed performance to standard. Memory is on auto settings.

I read that Win 7 doesn't like some nVidia cards on install and gives 0x124 errors, so I've tried it with an old 8800GTX and a Radeon HD4650. Same BSOD.

I've tried setting QPI up to 1.335V in steps.

The 32-bit install is rock-solid. It runs IntelBurn for hours quite happily. Similarly, Memtest86 will run for hours with no problems.

What's going on?
 
dodgy ram / ram slot? maybe as the 32bit will only get 2 of the ram to function fully, and 64 uses all.
 
that would be my guess.

try running memtest and see if it comes up with any errors for your ram.

also try to install both with just 1 stick in
 
Cycrow said:
try running memtest and see if it comes up with any errors for your ram.

also try to install both with just 1 stick in
Click to expand...

I've tried each of the three sticks on its own in each of the slots - which took a while - and got the same 0x124 STOP with all of them. I've run memtest for a couple of hours and it hasn't found anything.

I'm about to try flashing the BIOS next, although I'm only one away from the latest version and the list of fixes doesn't look very useful.
 
I tried Ubuntu 10.04 64-bit on it, and that crashes at the start of install too, with a machine check exception. This is the same as a Windows STOP: 0x124 BSOD.

Interestingly, the MCi_STATUS reported by Ubuntu is exactly the same as with Windows and when you decode it, the MCA error is "internal parity error". I don't think this helps me work out whether it's the processor or the motherboard, though.

I guess it's RMA time anyway.
 
You must log in or register to reply here.
Back
Top Bottom