• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

New build problems, BSOD

M

marcnapier

n00b
Joined
Dec 29, 2008
Messages
51
Guys,

Not quite understanding what's happening here: Just built Msi p55-gd65 with i7 860, 2x2gb GSkill Ripjaws CL7, GTX 295, Corsair 650 watt psu, x-fi titanium, velociraptor 150.

So I start to install Win 7 Ultimate 64, delete old partition and it's starts to install. It gets to about 9% expanding files then I get irq_not_less_or_equal BSOD. Temps are fine, CPU at 28C.

But in BIOS RAM is recognized as 1333 not 1600. Tried changing it to proper speed, no difference, still BSOD. Raid is set to IDE not AHCI. Have tried changing to different SATA ports and when I do that, it wont boot from DVD says BOOTMGR is missing. Haven't tried removing any cards or RAM sticks yet. All components other than board processor and ram were all working fine in previous build.

What the heck is going here?

Marc
 
Well I have a similar build and I get BSOD from time to time in Win 7 64bit.

I have removed the X-Fi Titanium from my system and I haven't got any BSOD yet. I am still researching the issue and when I have time I maybe install again my X - Fi card in a different pci - express slot.

Btw I also had problems when I was trying to install windows 7 and I just removed my usb mouse ( I used only my ps/2 keyboard ) and the installation completed successfully!
 
use 1 stick of ram, and set vdimm manually in bios to the default voltage for your particular ram.
if this doesnt work, try using a different optical drive, with different cable and in different channel.
i used to get this error during win xp installs at approx same point. microsoft documentation says it is usually a memory problem, but i found that it was almost always the optical drive, sometimes the hard drive, ie bad hdd, bad cable, set up wrong in bios, etc. try doing the install with only your boot drive and the optical with win7 dvd connected to mb.
 
You must log in or register to reply here.
Back
Top