Problem with DFI Lanparty Board. Please Help!!

Dijonase

Gawd
Joined
Jun 4, 2004
Messages
946
I recently bought a new case, Athlon 64 3000+, and DFI Lanparty UT NF3 board. My plan was to move all existing parts from my current system to the new setup. I did just that and I'm getting a single long beep when I power on. Accordnig to the DFI website it's a DRAM error, but what exactly does this mean? Does it mean that my RAM isn't compatible with the board? I was previously using an Asus A7N8X Deluxe and my understanding was that my 2x512 sticks of Komusa PC3700 would be perfectly compatible with the DFI board. I pulled them out and I get the same long beep, so it seems that the board doesn't recognize the RAM. Am I going to need to pick up new RAM?
 
Have you tried just one stick? Make sure it is seated fully in slot. Push hard.
 
I tried one. Then I tried the other. Then I tried each one in each slot. Then I tried no RAM. Always the single long beep denoting a DRAM error.
 
RonB said:
Have you tried just one stick? Make sure it is seated fully in slot. Push hard.

umm that was my suggestion. as a P4 user, I've had problems with putting the 2 DIMMS in the wrong sockets. 1 Stick may fix this problem.

Are memory timings still a big issue with AMD 64 boards? I remember people had to manually modify memory timings for stability. I remember someone mentioning -11 timings were perrty stable. ::shrug:::
 
fore1337 said:
Are memory timings still a big issue with AMD 64 boards? I remember people had to manually modify memory timings for stability. I remember someone mentioning -11 timings were perrty stable. ::shrug:::

I don't even get to that point. I disconnected everything but my video card and my hard drive but I don't get the display to come up. It just emits that damn beep.
 
Dijonase said:
I tried one. Then I tried the other. Then I tried each one in each slot. Then I tried no RAM. Always the single long beep denoting a DRAM error.

mayonnaise.
Standard protocol on trouble shooting a MOBO is:
1. disconnect all extraneous devices: FDD, USB, Hard Drives, any PCI cards except for the video.
2. all you want hooked up is the CPU, RAM and Video. …if you get it to post… you know it’s one of your peripherals… if you’re still getting the beep keep tweaking with the RAM.
3. Try clearing your CMOS.
 
fore1337 said:
mayonnaise.
Standard protocol on trouble shooting a MOBO is:
1. disconnect all extraneous devices: FDD, USB, Hard Drives, any PCI cards except for the video.
2. all you want hooked up is the CPU, RAM and Video. …if you get it to post… you know it’s one of your peripherals… if you’re still getting the beep keep tweaking with the RAM.
3. Try clearing your CMOS.

I'll unhook the hard drive and try it all again. If nothing else I'll clear the CMOS. Thanks for the help. Hopefully I can make somtheing happen.
 
fore1337 said:
mayonnaise.
Standard protocol on trouble shooting a MOBO is:
1. disconnect all extraneous devices: FDD, USB, Hard Drives, any PCI cards except for the video.
2. all you want hooked up is the CPU, RAM and Video. …if you get it to post… you know it’s one of your peripherals… if you’re still getting the beep keep tweaking with the RAM.
3. Try clearing your CMOS.

I did all of the above and still nothing. I'm completely perplexed.
 
Does anyone else have any ideas what might be going on? I've tried every possible configuration I can think of and still nothing.

I also noticed the following: the CMOS reset jumper seems to be strangely labeled. Th manual has the pins labeled 1-3 from left to right. When I looked at the board intending to reset the CMOS, however, the label is on the board itself upside down, which would make the pins numbered 3-1 from left to right. If I had the jumper attached improperly and powered on could that have caused some sort of problem?
 
I bought new RAM yesterday and I'm still getting the same results. The old RAM was Komusa 2x512 PC3700. The new RAM is Kingston ValueRAM 2x512 PC3200. I'm thinking at the moment that it's a problem with the motherboard rather than the RAM but I'm hoping that I just have a jumper misplaced or something and I won't have to RMA it. If anyone has any thoughts they'll be greatly appreciated.
 
you can try this, but it's usually just a lot of useless work.

sorry the only other think I could suggest is pulling it out of your case.. sometimes people trap a screw under the MOBO or something. That could cause a short.

try:
Throwing the mobo on a wood table, jumper the power switch and put an LED on the jumpers for Power LED.
It sould boot on the table... if not, you may be dealing with a dead mobo/cpu or both.

This just happened to my Gigabyte 8KNXP motherboard ($200 USD) ouchy. Turns out it was Gigabyte's fault.. they wrote a bad BIOS and promptly changed it... I ran the bad BIOS for 1-2 months... then 1 day. dead. :-\

My replacement was a Lanparty 875P revB
guess that's why I responded to your thread.


I'd return that bad boy if I could.
 
I just noticed something strange. I was looking at the online manual for my board and there's an LED on the board labeled LED6, the DRAM power LED. It says this LED will be lit when the system's power is on. There's a second LED labeled LED1, the Standby power LED. It says this LED will be lit when the system is in standby mode. When I plug my system in both LEDs light up regardless of whether it is powered on or not. This doesn't seem right to me. Has anyone experienced anything similar or know what might be going on here?
 
Assuming it's not a defective motherboard (which it very well could be) this is what comes to mind after considering what you've already tried:

1) Clear CMOS (you said you did already, but since there was confusion I don't know if you were successful)

2) pull out the motherboard from the case and make sure you didn't get carried away with unused motherboard standoffs and that there's nothing metal shorting out the motherboard.

3) make sure you plugged in the 4pin ATX 12v connector to the motherboard.

4) make sure all plugs, connectors, and cards are seated completely.
 
Well, I somehow got past my DRAM error. I pulled the RAM, video card, and CPU out and reseated everything and i no longer get that nasty beep. Now I have a new problem. All the hardware seems to startup just fine.

The fans all spin, the hard drive spins, the DVD drive shows activity. The problem is that I don't get a display. I have my video card fully connected but the display doesn't come up. Any further suggestions?

Oh, and I appreciate all the help I've gotten so far. This is the single best hardware forum I've ever come across.
 
I've been able to make more headway. Now when I power on my display begins to come up, I see what looks like some sort of a logo (though I can't tell since it's only up for a fraction of a second), then the system emits a single short beep and appears to restart. The only beep error codes listed in the online manual for the Lanparty are a single long beep denoting a DRAM error and a single long beep followed by three short beeps, so I'm not sure what the single beep I'm hearing might be. Any suggestions?
 
Argh, I don't want to hear that. Everything I've found wrong so far can be chalked up to user error so I don't think it's RMA time yet. Most recently I found that my CMOS jumper was on the wrong pins. I've tried to clear it a few times over the last couple of days and I must have left the jumper on the wrong pins last time I cleared it. Can this damage the board?

Otherwise I seem to be making progress, so does anyone have any advice other than RMA? I'm not ready to concede defeat just yet.
 
Try a different video card, it sounds like you may have a problem in that area. I was going to have you check and make sure the AGP is locked at 66 but it doesn't sound like you have got that far yet. Also what power supply are you using does it have enought to run that board and cpu? Is the cpu installed properly? ie no bent pins. And is the heatsink making good contact. Thats about all I can think of to try. I just put that combo togeather last week and it is running great.
 
I'm at work at the moment so I can't check anything, but I can say this. The last thing I did was remove the CPU, make sure all the pins looked good, and reseated it. The heatsink is on there nice and tight and looks to be making good contact. The PSU is a brand new 420W Thermaltake I picked up from newegg so my guess is that it's fine. I've got a GeForce 4 MX 440 in an old box that I can try if nothing else works.

Seeing as how each problem I've had so far has had a solution I have to say that I'm probably doing something wrong. The trick is to figure out what the hell that is. I want to RMA it as a last resort rather than just get frustrated and give up.

I appreciate all the help! Anyone else have any ideas?
 
OK, I've very nearly got things working. I just seem to be having one more problem, but it's a strange one.

I powered on, got a single beep, and the DFI Lanparty logo came up just as the Asus logo came up on my old box. So far so good. The system then appeared ti restart. There was the same single beep and it booted up again. I was able to get to the BIOS before it restarted again. I left it go a couple of times and it appeared to restart at random points.

Does anyone have any idea what might cause my system to randomly restart as it boots up?
 
I was able to get a better look at things this time. It's saying there's a CMOS checksum error. The online manual says that this can be caused by a weak CMOS battery, but my battery is brand new (presumably). I'm stumped.
 
1.) Try running with only a single stick of RAM. If you've got the RAM plugged into the wrong sockets (easy to do on DUAL DDR setups) you'll get frequent restarts.

2.) Got a new PSU to try out? Maybe you're not getting enough voltage... tweaker's creedo... if it ain't stable? Over-volt baby! Too bad this doesn’t apply to relationships. ;)

3.) Cooling... if something is overheating it may be shutting you down after a short time. Pull up the HSK (check that it’s seated well), make sure the fan is running .... Actually! Make sure the CPU fan is plugged into the CPU fan connector on the MOBO. I've found that *some* MOBOs don't like to boot when you have NO fans connected correctly. heh heh This rule can apply to chipset and case fans as well.

4.) It still sounds like a short or something. …did you pull out the MOBO and check for loose screws?
 
I've actually got everything up and running. Well, not everything, but that's another story. Thanks for the help.
 
Interesting. You said you were using PC3700 memory? According to DFI's website the DFI Lanparty 250Gb UT does not support PC3700.

Three 184-pin DDR SDRAM DIMM sockets
Supports single channel (64-bit wide) memory interface
Supports up to 3GB memory when using DDR333
Supports up to 2GB memory when using DDR400
Supports PC2700 (DDR333) and PC3200 (DDR400)
DDR SDRAM DIMM

Supports x8/x16, non-ECC, up to 512Mb DDR devices
Supports unbuffered DIMM

Feel free to correct me if I'm wrong.
 
Gouda said:
Interesting. You said you were using PC3700 memory? According to DFI's website the DFI Lanparty 250Gb UT does not support PC3700.

Three 184-pin DDR SDRAM DIMM sockets
Supports single channel (64-bit wide) memory interface
Supports up to 3GB memory when using DDR333
Supports up to 2GB memory when using DDR400
Supports PC2700 (DDR333) and PC3200 (DDR400)
DDR SDRAM DIMM

Supports x8/x16, non-ECC, up to 512Mb DDR devices
Supports unbuffered DIMM

Feel free to correct me if I'm wrong.
There's no way higher-rated memory would cause a problem. Now, PC-1200 would definetly be a problem.

On the other hand, that Komusa RAM would be a compatibility issue. I mean, what was the last time you've heard of Komusa RAM? What chips does it have? And does it even work?
 
Dijonase said:
Well, I somehow got past my DRAM error. I pulled the RAM, video card, and CPU out and reseated everything and i no longer get that nasty beep. Now I have a new problem. All the hardware seems to startup just fine.

The fans all spin, the hard drive spins, the DVD drive shows activity. The problem is that I don't get a display. I have my video card fully connected but the display doesn't come up. Any further suggestions?

Oh, and I appreciate all the help I've gotten so far. This is the single best hardware forum I've ever come across.

may i ask how u got the display to work?
 
i jsut go the same board today, just wating on the new proc and dvd drive.

i would like to know if there are any suggestion u have when installing the components that arent too clear in the manual or just things to avoid. this is my first time putting together a cpmuter, and i would like to avoid any things i could do to mess it up.
 
fore1337 said:
you can try this, but it's usually just a lot of useless work.

sorry the only other think I could suggest is pulling it out of your case.. sometimes people trap a screw under the MOBO or something. That could cause a short.

try:
Throwing the mobo on a wood table, jumper the power switch and put an LED on the jumpers for Power LED.
It sould boot on the table... if not, you may be dealing with a dead mobo/cpu or both.

This just happened to my Gigabyte 8KNXP motherboard ($200 USD) ouchy. Turns out it was Gigabyte's fault.. they wrote a bad BIOS and promptly changed it... I ran the bad BIOS for 1-2 months... then 1 day. dead. :-\

My replacement was a Lanparty 875P revB
guess that's why I responded to your thread.


I'd return that bad boy if I could.

How did you get the replacement? Through manufacture or retailer rma? I'm curious because the Lanparty isn't a Gigabyte board.
 
Back
Top