Ok, well I have been trying for a few weeks now to get this DFI LanParty mobo that I have to work, and simply am not getting it to work. Random lockups and other issue. I'm pretty disappointed. So I'm thinking about sending it back.So I need some suggestions on some good NF4 boards Socket 939 with a PCI-E slot and at least 3 PCI slots. Something fast, but something STABLE, which this DFI board seems to be anything but!Or if anybody wants to take a stab at fixing my DFI board setup.
4/9/2006 9:27:02 AM
I use Biostar (the best all-around brand IMO and well packaged, well labeled, etc.), MSI (very good almost equal to biostar), Gigabyte, and sometimes ECS (no frills but solid). A lot of people swear by Asus but I find them to be overpriced. Run far, far away from Tul and stay away from "no name" brands... check the manufacturer web site and make sure there is good documentation, bios updates, drivers, etc.With that info, just pick the one with the features you need. I suggest newegg.com.
4/9/2006 10:13:25 AM
i just got a dfi lanparty board (brand new pc) and i have random lockups as well. i have no idea what is causing them, but maybe it's the mobo.is this a common issue with DFI?
4/9/2006 12:30:10 PM
i think lanparty mobos require a lot of power if I remember correctly when i was researching new mobos.. make sure your PSU is sufficient.. as in at least 480W..
4/9/2006 1:40:07 PM
define what is the random lockupsI had a asus a8n that randomly blue screened, until i figured out that the stupid nvidia firewall was causing it.
4/9/2006 1:43:16 PM
I just purchased a DFI LanParty UT Ultra-D mobo. All DFI NF4 mobos require at least 480W.There are a couple of known stability issues on certain sticks of memory. You may try updating your BIOS and make sure it is configured to suit your needs.Otherwise, if you had to purchase another NF4 board, I would go with the following:Asus A8N-EEpox EP-9NPA+UltraMSI K8N Neo4 PlatinumMSI K8N Neo4-F (non-ultra north bridge...great board @ bargain price)
4/9/2006 3:11:00 PM
my psu is 520 watts
4/9/2006 5:06:39 PM
i have a chaintech nf4 ultra that has been quite stable on a Venice (can't remember, maybe 3200?). I have 4 1g modules at ddr400 in it with no issues.
4/9/2006 5:10:54 PM
I have a 500W PSU unit so power isn't my problem.The board runs fine with a couple sticks of my old Crucial RAM, but I have a nice new stick of Mushkin that it won't run, unless I have the Crucial in there with it to slow it down to the Crucial RAM speed.One other question though. I have XP on my computer a legit version I got at a conference. If I can't find the CD, and need it to repair my install of XP or to reinstall XP, what do I do? Will MS offer a replacement XP.
4/9/2006 7:12:30 PM
I'm using an Asus A8N-E and I haven't had a problem with stability.
4/9/2006 7:23:02 PM
ok i tested the memory, it's not that. it isn't overheating... i really have no idea why the computer is randomly locking up.probably the same problem Nighthawk was seeing. any ideas on fixes?
4/9/2006 8:46:29 PM
Yea apparently the RAM I have is PC4000 and the board only supports up to PC3200 speed.So you have to boot up with another stick of RAM, change the RAM limitor or multipler (called something like that) from auto, to whatever the highest speed the mobo can support. Otherwise, it simply tries to run at whatever speed the faster RAM is set to run at, and will fux0r.At least, that how its been explained to me. I'm about to try it now to see if it works or not.
4/9/2006 9:55:52 PM
bttt was that the problem?how can i check and see if that's my problem?
4/11/2006 12:32:57 PM
once I got my bios straight on my dfi, all the lockups went away. I'm only using a 450w ocz modstream and I'm overclocking a good bit. a good brand psu with solid 12v amps is more important than an inflated wattage rating. I've had months of uptime on this board, I wouldn't right it off just yet.
>uptime13:04:31 up 18 days, 21:07, 1 user, load average: 0.00, 0.00, 0.00
4/11/2006 1:03:44 PM
i tried to update my bios and after i did the comp wouldn't even start up. i had to clear the CMOS just to get it back to the initial problem of locking up all the time
4/11/2006 1:08:45 PM