DFI NF4 Ultra/SLi-D BUGS and Fixes Thread

Printable View

Show 100 post(s) from this thread on one page

08-21-2005, 03:25 AM
OneyedK

Quote:

Originally Posted by largon

btw. Where is the CMOS Reloaded stored? If I use another bios chip, the settings that were saved while the other chip was seated, are still there.

The CMOS Reloaded is stored into the main memory...
So if you cannot change setting, that means the access to the memory is not ok (OC too high?)...
Normal working procedure:
Bios is loaded into memory upon boot
Changing bios setting happens in memory (different area than old settings)
pressing F10 saves them onto the bios chip

That's the reason why after pressing F10 you need a reboot,
so settings on bioschip are identical to those in memory.

Hope the explanation is a bit clear...
08-21-2005, 03:26 AM
njkid32

Quote:

Originally Posted by largon

I think my DFI's CMOS Reloaded is borked. None of the fields can be renamed:
I can still type what I want to the fields but the text just don't appear there after pressing enter in the 3rd row. :confused:
The strange thing is that the last row from the 1st slot's description (excluding the 1st letter) apppears to the 1st row of the 4th slot IF I save settings to the 4th slot. :D

I've tried reflashing and clear CMOS - no effect.

btw. Where is the CMOS Reloaded stored? If I use another bios chip, the settings that were saved while the other chip was seated, are still there.

Hey largon, I had the same problem and I thought it was done. But how you fix it is load optimized defaults and then go and save over everything. Save to each bank then overwrite each description with nothing. Then reboot and try to save. I emailed DFI about this and they said that its stored somewhere on the mobo and the only way to fix it is to do it this way. So I tried it and it worked. So give it a try... I bet it works LOL
08-21-2005, 04:46 AM
largon

njkid32,
That didn't work. At least in the first time I tried it.

Symptoms getting weirder:
http://www.xtremesystems.org/forums/...id=36012&stc=1

The "01MHz / 1.6 vCore" is only visible for a fraction of a second, I had to shoot 25 pics to capture it. Normally this row reads
"┌──────Description──────┐"

"01MHz / 1.6 vCore" should be 1 row lower and read "2601MHz / 1.6 vCore"

"3-2-7 2.5 vDimm" should be 2 rows lower and read "2-3-2-7 2.5 vDimm"
08-21-2005, 05:12 AM
njkid32

Quote:

Originally Posted by largon

njkid32,
That didn't work. At least in the first time I tried it.

Symptoms getting weirder:
http://www.xtremesystems.org/forums/...id=36012&stc=1

The "01MHz / 1.6 vCore" is only visible for a fraction of a second, I had to shoot 25 pics to capture it. Normally this row reads
"┌──────Description──────┐"

"01MHz / 1.6 vCore" should be 1 row lower and read "2601MHz / 1.6 vCore"

"3-2-7 2.5 vDimm" should be 2 rows lower and read "2-3-2-7 2.5 vDimm"

Ok, so you cleared your cmos, loaded optimized defaults, saved to every bank and then saved a blank description on each bank?

The one thing I was told from DFI was that if you have anything saved in the cmos reloaded from a different bios and load them to a new bios it will mess things up for you.

So make sure you do a good cmos clear. Pull the battery then set the jumper to clear for like 10 min at least then put the jumper back to normal and put the battery back in. This has saved me many times. Then when you are done with this do the above save optimized defaults to every bank.
08-22-2005, 01:09 PM
[G.N.U.]Fragman

Quote:

Originally Posted by arrarro

Hi

I have a SLI-DR, can anyone tell me if the four sata slots of Silicon Image Raid controller are fixed so that is it possible to overclock without troubles at any fsb? is silicon image controller better than built in nforce4 nVidia one?

:confused:

silicon AND nvidia controller both works fine also when OCing....nvidis also have sata300 (sata 2) support, which the silicon doesnt have....
08-22-2005, 02:36 PM
Quanticles

I was running memtest on my 4400+, it didnt seem as stable lately and i was trying to figure out why. After I ran memtest for ~5 hours I rebooted, increased vcore a little bit (to 1.45 * 1.10) and rebooted again. This time I got 3 lights... "CPU Detected" according to the manual, which would mean the memory is bad..? I try the memory in another computer and it's fine. Put it back in after clearing cmos repeatedly and still 3 lights. I try putting in my 3500+ winchester and I get one light this time... "System boot-up". Not sure what that one means. Clear again, still nothing.

I'm using the bigtoe modded 704 bios, 2.8v on ram, and not particularly high clocks (i was memtesting).

Any Ideas? I'm hosting a LAN here tomorrow and it's gonna suck if I cant get this rig running.
08-22-2005, 02:41 PM
njkid32

Quote:

Originally Posted by Quanticles

I was running memtest on my 4400+, it didnt seem as stable lately and i was trying to figure out why. After I ran memtest for ~5 hours I rebooted, increased vcore a little bit (to 1.45 * 1.10) and rebooted again. This time I got 3 lights... "CPU Detected" according to the manual, which would mean the memory is bad..? I try the memory in another computer and it's fine. Put it back in after clearing cmos repeatedly and still 3 lights. I try putting in my 3500+ winchester and I get one light this time... "System boot-up". Not sure what that one means. Clear again, still nothing.

I'm using the bigtoe modded 704 bios, 2.8v on ram, and not particularly high clocks (i was memtesting).

Any Ideas? I'm hosting a LAN here tomorrow and it's gonna suck if I cant get this rig running.

Are you getting bios beeps? If so try this--Just put 1 stick in the second orange slot! That will fix it (I think). I have had this problem several time. If you are able to boot with the 1 stick then set all your settings then save. After it posts shut it down and put the other stick in. If you are using a new bios and have stuff saved in the cmos reloaded then load optimized defaults and save over each bank in the cmos reloaded. NEVER use settings from another bios on your new one cuz it will cause problems for you.. Hope this helps!
08-22-2005, 02:46 PM
OneyedK

Bios 704-2BT worked fine with me using OCZ VX4000...

Now I've changed back to my tccd 431 and have about the same problem as quanticles (cleared cmos several times and finally got it to boot with one stick)...
So I'm going to give the 623-3 another go...
08-22-2005, 02:52 PM
njkid32

You guys can get it to work if you try the second orange slot.
08-22-2005, 03:02 PM
Quanticles

I tried using the second orange slot but that didnt seem to work. The system was able to boot using the 3500+ just fine. I had the 4400+ running before... could it possibly be dead now? Or would it be a bios setting?
08-22-2005, 03:16 PM
Quanticles

It still wont POST even with one stick in slot 2. It looks like the 4400+'s memory controller is toast... =(
08-22-2005, 03:32 PM
njkid32

Quote:

Originally Posted by Quanticles

It still wont POST even with one stick in slot 2. It looks like the 4400+'s memory controller is toast... =(

Its prolly a stupid question but did you pull the battery out and set the jumper to clear and leave it for awhile. Then try to boot with the ram in the second orange slot. Did you try the X2 in another computer? Also do you have a second set of ram to try in the DFI.

I had a similar problem with my TCCD's and what I did was take my CH-5 and put it in the second orange slot and it booted just fine. It looks like the X2's dont really play nice with TCCD.

You never said--are you getting bios beeps?
08-22-2005, 04:21 PM
Quanticles

Quote:

Originally Posted by njkid32

Its prolly a stupid question but did you pull the battery out and set the jumper to clear and leave it for awhile. Then try to boot with the ram in the second orange slot. Did you try the X2 in another computer? Also do you have a second set of ram to try in the DFI.

I had a similar problem with my TCCD's and what I did was take my CH-5 and put it in the second orange slot and it booted just fine. It looks like the X2's dont really play nice with TCCD.

You never said--are you getting bios beeps?

I just enabled the buzzer jumper, and it isnt making any sounds as far as I can tell.

I just set the jumper to clear and pulled out the battery. I dont have another 939 system available to try the part in, unfortunately. The other available memory is some samsung tccd 3200. =/
08-22-2005, 04:46 PM
njkid32

Quote:

Originally Posted by Quanticles

I just enabled the buzzer jumper, and it isnt making any sounds as far as I can tell.

I just set the jumper to clear and pulled out the battery. I dont have another 939 system available to try the part in, unfortunately. The other available memory is some samsung tccd 3200. =/

Yeah just let it clear for awhile. Try all your ram just to rule out anything else. Are you using the 3500 or the 4400? I would just clear the bios for at least an hour or so then try the 4400 and your 1 stick in the second orange slot. If it still doesnt work try different sticks of ram. Now if that still doesnt work put the 3500 in and see if you can get it to post.
08-22-2005, 04:48 PM
Quanticles

Quote:

Originally Posted by njkid32

Yeah just let it clear for awhile. Try all your ram just to rule out anything else. Are you using the 3500 or the 4400? I would just clear the bios for at least an hour or so then try the 4400 and your 1 stick in the second orange slot. If it still doesnt work try different sticks of ram. Now if that still doesnt work put the 3500 in and see if you can get it to post.

I was able to get the 3500 to boot earlier. One light means it's booting, I just had the vga disconnected (silly mistake).

Using the 3500 I was able to also use cmos reloaded to pull up a bootable set of bios i had saved for the 4400 (it worked for the 3500 as well). The 4400 didnt boot with that either.

The cmos is still clearing... x.x
08-22-2005, 04:55 PM
njkid32

Quote:

Originally Posted by Quanticles

I was able to get the 3500 to boot earlier. One light means it's booting, I just had the vga disconnected (silly mistake).

Using the 3500 I was able to also use cmos reloaded to pull up a bootable set of bios i had saved for the 4400 (it worked for the 3500 as well). The 4400 didnt boot with that either.

The cmos is still clearing... x.x

OK question the settings you have saved in the cmos reloaded are they from another bios? If they are you need to load optimized defaults and save over each bank. Then reboot and reset all your settings and save them again. You should never mix and match settings with different bios's. This came straight from DFI. I dont think you killed your X2 its just that they are really picky with these TCCD!
08-22-2005, 05:35 PM
Quanticles

Quote:

Originally Posted by njkid32

OK question the settings you have saved in the cmos reloaded are they from another bios? If they are you need to load optimized defaults and save over each bank. Then reboot and reset all your settings and save them again. You should never mix and match settings with different bios's. This came straight from DFI. I dont think you killed your X2 its just that they are really picky with these TCCD!

No, those were from the same 704, when it was booting before.
08-22-2005, 05:36 PM
Quanticles

I had the 704 bios running with this memory, hardware config, etc etc, and was running memtest earlier today. I did a slight voltage change to the CPU and it stopped posting. =/

The saved bios were a bootable 704 settings.
08-22-2005, 06:05 PM
njkid32

Quote:

Originally Posted by Quanticles

I had the 704 bios running with this memory, hardware config, etc etc, and was running memtest earlier today. I did a slight voltage change to the CPU and it stopped posting. =/

The saved bios were a bootable 704 settings.

OK one more question--- the bios you are using is it the 704 or 704-2BT? If you were using the 704 and the special 123% you could have killed your chip!
08-22-2005, 06:27 PM
Quanticles

Quote:

Originally Posted by njkid32

OK one more question--- the bios you are using is it the 704 or 704-2BT? If you were using the 704 and the special 123% you could have killed your chip!

704-2BT. I was using special 110%.
08-22-2005, 10:03 PM
Quanticles

Left clear-cmos jumper in clear state for well over an hour with the battery out and compy unplugged... nothing.
08-22-2005, 10:16 PM
njkid32

Quote:

Originally Posted by Quanticles

Left clear-cmos jumper in clear state for well over an hour with the battery out and compy unplugged... nothing.

I am all out of solutions sorry! The only thing I would say to do now is take your chip to a local shop and see if they can test it. I wish you luck man! Sorry I couldnt have been of more help.
08-23-2005, 07:18 AM
Quanticles

Maybe someone else will have a 939 system at the LAN today... x.x
08-24-2005, 05:01 PM
[G.N.U.]Fragman

be careful with thos 704 bios ffs..somehow the vcore calc. is messed up......saw someone fried a venice because of it......

above VID 123% and more CAN make the bios just fire all avalieble volts on the CPU....and then you should be able to smell the cpu...............

something about it here:

http://www.dfi-street.com/forum/show...0&page=1&pp=15
08-27-2005, 08:14 AM
sponge bob

hi, i have sli-dr
i just buyed it, and i cant to post
only 4 red leds burning, all other parts are fine (tested)
what sould i do? :stick:
or just RMA it?

Show 100 post(s) from this thread on one page

All times are GMT -8. The time now is 11:22 AM.

XtremeSystems