dfi nf4 cold boot problem

[arctic-k20]

I am starting this thread to get an idea of how many people are having cold boot issues with their dfi nf4 ultra / sli boards.

I think the cold boot problem is limited to VX / UTT / BH5 / CH5 but there may be others...

In my instance - the ram can be rock solid stable - run any benchmark and go for weeks on end. As soon as i power down ie) cold boot - turn everything off the board will NOT post with 2 sticks of vx in. It will only post with 1 stick in the second orange slot or second yellow slot.

I can flash the board until I am blue in the face but all it takes to bring the system to its feet is to turn it off.

[cupra]

I am starting this thread to get an idea of how many people are having cold boot issues with their dfi nf4 ultra / sli boards.

I think the cold boot problem is limited to VX / UTT / BH5 / CH5 but there may be others...

In my instance - the ram can be rock solid stable - run any benchmark and go for weeks on end. As soon as i power down ie) cold boot - turn everything off the board will NOT post with 2 sticks of vx in. It will only post with 1 stick in the second orange slot or second yellow slot.

I can flash the board until I am blue in the face but all it takes to bring the system to its feet is to turn it off.

i can boot my sli-dr jest fine with vx and bh...

[REDKEN]

Hmmm! Wasn't already stated by AMD that it was a mem controller issue?

[enduracell]

no problem here, I never heard such think before.

[ADM]

I have this problem, anyone know how to get around it?

[arctic-k20]

nothing i have tried yet has worked short of running 1 stick...

[ADM]

I've been told it could be something to do with the memory controller on the CPU.

[[XC] leviathan18]

is the memory controller on the cpu not mobo problem....

[[XC] 4X4N]

I have this problem sometimes too. I can shutdown for the night and it will come back on in the morning no problem. If I shutdown to mess with something, and unplug it from the wall, then no boot and I have to go through the whole boot with one stick process. Definitely gets frustrating.

[pershoot]

it happened once to me (while being off for like a day or so; psu switched off, power plu still in). turn on, no signal to mon., turn off and back on and booted right up. i reflashed, and it hasnt happened since.

[Cranox]

I got BH5 ( 2x 512mb and 2x 256mb )
Got a mach II and a venice 3800+

No problems here ( bios 03/10 )

[muzz]

I have the dreaded 3 light syndrome everyday now.

Do the other NF4 boards have these issues too, or is it just the DFI ?

[ADM]

I was told it was all the NF4 range of mobos that have this problem.

[THunDA]

Ive never had this problem.. well not without me causing it..hehe..

[sr4470]

No problems here so far, using the setup in my sig.

[Sucka]

I have 2 boards, no problems on either.

[whizkid]

Had this problem before w/ UTT using shipping BIOS. Flashed it to 310P and all was good!

[magg]

I have a similar problem, but it's actually with TCCD. I'll be fine, 3d stable, OCCT / SuperPi stable for years, but then every once in a while the mobo decides to just not boot. It will hit windows logo, then reboot :repeat:

Even returning it to all stock [load optimized], it still does it. I don't quiet know how to fix it yet, because sometimes it just fixes itself, and other times it loads up after I choose to boot with "last known working settings".

Arg, damn tempermental DFI boards.

[Onepagebook]

I tried, No problem at all.

[Apocalipsis]

No problems whatsoever, although with bios 3xx I was having some issues now with 218 all runs perfect, mem is BH5.

[texuspete00]

Well...bookmarked thread. I knocked a cap off my Gskill thats been running fine in my work rigs. Now I get my second DFI in, and I'm about to buy new ram... but only because my DFI does a mix of everybody's things!!

I gamed on it for 2 hours no problem. While it was sleeping.... it just up and SHUT OFF! It doesn't always need it to be cold either. Messing with anything in the bios is like teasing it to happen. One boot I'm gaming no problem... next turn the fan monitoring off and I'm dropping boots before windows! 3200+ Venice, Slightly damaged GSKill, and my DFI. I will find out though... I got a chaintech and some things I can compare.

I think I have the same thing as others though because 1 stick is the cure all. Good stick or bad one... though I need to test more.

[texuspete00]

Now I know my problem could be ram, but to the people not having problems with there's it's hard to diagnose. I mean mem controller issue? I'm sorry but both AMD and Intel's reps and standard's are towers next to shacks in this regard. Maybe a teething problem with bios's, but odds makers would have this 5000:1. I love my DFI mobos too but sometimes I need a second less possessed one.

Their are a lot of DFI loyalists these days, but everyone knows they are quirky. Go to their support forum and they'll be like flash to xxx bios, but first load optimized defaults, then flash, then load optimized defaults, then turn off the power, press the power button a couple fo times, clear the cmos, sing "how I love you for all time," cross your fingers and wait for the best. If something goes wrong, well it must be because you are a lousy singer!!! Anyways no offense anybody... it's not like some other forums that will place all the blame on your "noobishness" on their precious DFI's if you don't know it's lullaby yet.

[dsumanik]

I was having the issues too, i had to RMA my VX4000 to cure the problem.

The situation i got from speaking with all the OCZ guys and their communication with DFI is this:

It is an IC issue, the VX is designed to take high voltages and can make certain mobo/cpu combos have a tough time detecting the memory.

The temp cure:

Get your rig to boot off the one "GOOD STICK" in slot 2 then set the voltage to 3.2 in bios and fsb to 200mhz and on VX 2-3-3-8 timings (manually select spd)

Then pop in the other stick, it should post...from here you can overclock away but DO NOT power down the system, resetting is fine but hard reboot will cause the mem to not be detected.

After this....go call OCZ and get an RMA going, my new stick are clocking higher and i can turn my computer on and off at will (what a luxury!!)

The ram isnt defective, its just incompatible in certain situations.

Good luck guys, dont worry OCZ has awesome RMA support you can read my post on the OCZ forums
here:

http://www.bleedinedge.com/forum/showthread.php?t=9573
Forums on the BleedinEdge - Is this a candidate for RMA?

[arctic-k20]

thanks for the post dsumanik !! good info there

[texuspete00]

I was having the issues too, i had to RMA my VX4000 to cure the problem.

The situation i got from speaking with all the OCZ guys and their communication with DFI is this:

It is an IC issue, the VX is designed to take high voltages and can make certain mobo/cpu combos have a tough time detecting the memory.

The temp cure:

Get your rig to boot off the one "GOOD STICK" in slot 2 then set the voltage to 3.2 in bios and fsb to 200mhz and on VX 2-3-3-8 timings (manually select spd)

Then pop in the other stick, it should post...from here you can overclock away but DO NOT power down the system, resetting is fine but hard reboot will cause the mem to not be detected.

After this....go call OCZ and get an RMA going, my new stick are clocking higher and i can turn my computer on and off at will (what a luxury!!)

The ram isnt defective, its just incompatible in certain situations.

Good luck guys, dont worry OCZ has awesome RMA support you can read my post on the OCZ forums
here:

http://www.bleedinedge.com/forum/showthread.php?t=9573
Forums on the BleedinEdge - Is this a candidate for RMA?

hehehe... see what I mean. Don't you wonder when they are going to ask you to click your heels and find the secret mana? Now I've got a "date" with my DFI tonight.