problems with the ultra-d?

A

aoX|qL

n00b
Joined
Jul 3, 2005
Messages
20
Hey guys,

Recently I had the chance to purchase my new rig, here are the specs;

3500+ venice
DFI lanparty Ultra-D
crucial 2x1GB 184-Pin DDR SDRAM Unbuffered DDR 400 (PC 3200)
Powercolor x800XL
Antec Neopower
Western Digital Caviar SE 80GB 3.5" IDE Ultra ATA100 Hard Drive

okay now heres the problem, i dont know if its more of a hardware or software issue,
but me and my friend properly installed everything, it boots up just fine.
But then when we reformat then install XP, things turn sour.

Reformating was okay, no problems found, but then
in the middle of XP installing it freezes, so we reboot then reformat and install again.
now it pops up that blue screen of death.
we tried using different hard drives and different XP install CD's.
still no luck, and its still popping up the blue screen.

if there is any help please let me know! thank you
 
hey rhino,

im using the stock bios that came with the system, i guess.
(sorry im at work, which is no where near my computer =[ )
im guessing if i remember correctly, Phoenix something..
anyways could it be a motherboard issue?
i mean i got it to boot, its just installing XP it freezes
but everytime i restart it, it gives me that blue screen. =[

thanks!, more help is needed!
and oh yea, im lookin at these newpost that came out,
and it seems that ultra-d is way over my head =[.
 
You're using a Venice core. You have to reflash to bios 6-23 first for it to work correctly. Secondly, have you tried running memtest 86 that's built on to the board first? I got BSOD during Windows install too, and found out it was because one stick of my OCZ ram was bad. If those don't answer your questions, they have a thread listing the best stable settings to run at dfi-street.com

Oh, also, make sure your PSU is at least 480W with 28A down the +12V line with a native 24 pin connector, and connect all four power leads into the board (24 pin, 4 pin, 3 pin, floppy connector). The ultra-d is a power hungry beast.
 
ceng-phil said:
You're using a Venice core. You have to reflash to bios 6-23 first for it to work correctly. Secondly, have you tried running memtest 86 that's built on to the board first? I got BSOD during Windows install too, and found out it was because one stick of my OCZ ram was bad. If those don't answer your questions, they have a thread listing the best stable settings to run at dfi-street.com

Oh, also, make sure your PSU is at least 480W with 28A down the +12V line with a native 24 pin connector, and connect all four power leads into the board (24 pin, 4 pin, 3 pin, floppy connector). The ultra-d is a power hungry beast.
Click to expand...
actually thats not true...i have a san diego core (same as venice but with 1mb cache) and it worked fine with the stock 3-10 bios. His problem is that his memory is not configured correctly go to www.dfi-street.com and list your exact system specs and ask someone if the can give you your exact extended ram timings then input them manually in the bios
 
arite guys,

i took out one of the ram sticks, and it booted up and installed xp with no problem. :)
now, wen i put in the other ram stick, it crashed agen and agen.
any idea? i have not updated bios yet, would that fix the problem?
il give those memory timings a shot at dfi street also.

any more ideas? thanks!
 
aoX|qL said:
arite guys,

i took out one of the ram sticks, and it booted up and installed xp with no problem. :)
now, wen i put in the other ram stick, it crashed agen and agen.
any idea? i have not updated bios yet, would that fix the problem?
il give those memory timings a shot at dfi street also.

any more ideas? thanks!
Click to expand...
memory timings GUARANTEED bro....its a very common issue with DFi boards....find the right timings and it will be all peachy
 
GreenGoose said:
Up the voltage on the ram a notch or two.
Click to expand...
that wont do much to help if the ram timings are wrong...unless the ram is supposed to run at a higher voltage
 
arite guys,

wen i get off work, il go fiddle + post around dfi street for those timings,
thanks guys + cell !!
 
Ok, well I had the EXACT same symptoms until I updated my bios to the 510 bios (San Diego 3700).

The 310 bios could identify new revision cores and let my PC boot, but it would do exactly what yours is doing. After trying to re-install windows like 6 times, I discovered that I needed a bios update.

Do it and be happy.

This page has all that you need

I suggest downloading the ISO version and burning it to a CD. Just boot off the CD and flash from there. It's got some nice menus too.

510 is what I'm using. 704 is the newest release, but can kill your cpu if you use the 123% vcore (and higher) settings. There might be an official release between 510 (615 I think) that is safe. Personally, just flash the 510 and you'll be good to go.
 
bubblethumper said:
Ok, well I had the EXACT same symptoms until I updated my bios to the 510 bios (San Diego 3700).

The 310 bios could identify new revision cores and let my PC boot, but it would do exactly what yours is doing. After trying to re-install windows like 6 times, I discovered that I needed a bios update.

Do it and be happy.

This page has all that you need

I suggest downloading the ISO version and burning it to a CD. Just boot off the CD and flash from there. It's got some nice menus too.

510 is what I'm using. 704 is the newest release, but can kill your cpu if you use the 123% vcore (and higher) settings. There might be an official release between 510 (615 I think) that is safe. Personally, just flash the 510 and you'll be good to go.
Click to expand...

he is still going to have to have the correct ram timings...also why use an outdated bios if anything grab the previous official release 6-23 which is what im using
 
You must log in or register to reply here.
Back
Top