Memtest86 Stable But XP BSODs

[poopyman67]

I just got my new system, and here are the specs:

DFI NF4 SLI-DR Expert
2*512 OCZ 3200 Platinum Rev. 2

It works @ stock(I get one after coming off an OC, but that could be residual or something)

Well I got my sytem to run at these settings:

RAM: 2.5-5-3-3-5 @ 250Mhz
LDT X:4
CPU:9(can't get it to run any higher)

These settings are rock solid in memtest, but when I try to boot into or install windows, i get a blue screen, saying Driver IRQ less than or Equal or something of the sort. I know that this can be due to bad RAM, but this stuff works fine.... any suggestions?

It also fails to boot sometimes.... when it tries to boot from the HD, I get this:
L 99 99 99 99.....

I've seen it before, and it usually refers to a bad MBR or so I thought, cuz when I go back to stock settings, it'll usually work. I'm totally confused here, any thoughts?

 

[themusgrat]

Probably a CPU problem. Install at stock, no matter what. Always.

 

[poopyman67]

ok, thanks.

I was running an older version of memteset86(the dfi board came w/1.6 installed, and so now i'm running the new 3.2, and I found out that it wasnt as stable as I had previously thought... so now I'm retesting it... seems like my voltage may have been too high... anand was running the same ram @ 1.65, and I was running it at 1.77, and I know that tccd chips dont respond too much to voltage, so I brought it down, and so far, so good.... I'll haev to run it much longer tho b4 i can try it out again...

thanks for the advice!

also: i just turned on SMART HD, and seems like my extra hd is crapping out on me..... man....western digital...... never again(2nd time!)

 

[poopyman67]

ok, well, my system is running stable at stock, but when i oc, I can't get into windows, even tho its totally rock stable in memtest86(this time im positive).

any suggestions??

Heres what I'm running:
RAM: 2.5-4-3-7 @ 250Mhz
LDT X:4 (1000mhz)
CPU X:9 (2250mhz)

 

[lopri]

It's a VERY common problem with A64 CPUs thanks to its built-in on-die memory controller. While CPU and memory are stable at certain speeds, respectively, once you get them to run together it just doesn't work because the memory controller can't keep up with the speed of memory. Especially if you're near your CPU's limit. Try using divider (DDR166) so that the memory runs at stock speed (CPU still overclocked). If it runs fine, then your CPU's memory controller is borked.

Other possibilities: Memory timings or your motherboard (BIOS) is not behaving well. Try updating the BIOS.

 

[poopyman67]

I've been fooling around with the settings, and I've found that I can't boot into windows if i change my timings. I've tried running 2.5-4-3-7 at stock speeds, and I'm unable to boot. So I'm not quite sure what to make of that....

Could it really be my CPU?

 

[Unkno]

always run your memory at a lower speed when testing cpu. If it works and then you increase your memory and it BSODs, then you know it's the memory.

 

[poopyman67]

I should be able to run my memory @ 2.5-4-3-7 @ 200mhz tho... the SPD settings are 2-2-2-5 @ 200....

if i keep it at the same timings, i can oc, but with limited results(205), as the timings are really tight so I dont have much room....

I think some of the extra memory settings that DFI has are screwing me up...

 

[the cobbler]

memtest stable does not mean Windows stable

memtest will show a few extra MHZ than you will be able to run in Windows, and even more MHZ than 3D stable memory clocks

 

[cubeless]

just had this same issue going to 4 x512 from 2x512 in lanparty nf4 d... onboard memtest was fine, xp puked... set everything to auto, it boots up, find out what all the settings are, go back to bios and set them, start playing...

 

[lopri]

Try a different BIOS? It's mostly likely the BIOS/motherboard if the memory is memtest stable AND can't run at stock.

 

[poopyman67]

it runs fine at stock timings, but not at any other timings.

 

[poopyman67]

i've found that i can run it @ 2-3-3-6, so it seems taht my problem is that I can't run at anything else than CL2. Any idea as to what could be causing this?