Jump to content

Luc

Members
  • Posts

    8
  • Joined

  • Last visited

Luc's Achievements

Newbie

Newbie (1/14)

  1. OK, update. Well, I started an RMA form for Centon memory because it is indeed faulty. In this computer, I now happen to have a generic 256 stick of pc2700. This is the ram that was in my computer before the upgrade and has worked through hell and high-water. I forgot to turn off prime95 at start up and as soon as it started running, instant restart. Granted, the centon 3200 ram failed memtest and is going back for RMA but I need to know what else could it be? I'm going to run memtest tonight on the 2700 just to be safe but aside from that i'm stumped. Idle CPU temp is 52.5 C Full CPU load temp is 57 C, I can't get it higher than that. As for voltage readings: VCORE 1.6 +3.3V 3.25 +5V 5 +12V 11.76 -12V -12.55 5VSB 4.94 VBAT 3.2 When monitoring, VBAT gives me an error saying that it hit its threshold (which is 3.2) my 12v +- readings look way off, but I never pay much attention to them. My PSU is a 420 ANTEC SmartPower. That is really the only thing I could see as being the problem. Any feedback would be appreciated.
  2. Two different sticks....someone is going to die. I bought these from the same manufacturer...I'm going to send them back. I'm usign the most current BIOS for my mobo so that isn't the case. I'm going to run the memtest again tonight on one of my sticks to see witch one is faulty. Both are covered by a Centon lifetime warranty so If both are bad then they're going back one at a time. Thanks for all your help people, I appreciate it even if it doesn't sound so.
  3. Holy crap...OK, I just ran CPU-Z out of ...(well I should be doing work but seeing as how English essays and Logic gate manipulation isn't too exciting) um...my ram timings don't jive. I completely assume that this isn't normal? I'm going to look up information about my ram manufacturer, i know they offer a lifetime warranty and I could just send in one stick at a time (if they're both bad) Going to do that tonight. can someone tell me, that isn' normal correct?
  4. no no no, I'm not blaming the motherboard, I know its the ram now. I just thought that if the 1394 port could cause a conflict with the ram that a repair request could fix it. Don't get the wrong impression, I love DFI. Whenever i get the funds to upgrade to amd64 I'm getting a DFI LANParty mobo to accompy it. Now that I know the mobo doesn't like my ram, what can I do now? I'm literally 100 miles from the place of purchase and i'm w/o a car. The only thing I haven't done yet (and I'm going to do sometime tonight when I finish homework) is change to the 6/19 BIOS like everyone suggested. In the event that this does not fix it, can anyone suggest a DFI motherboard that will be a little nicer to my RAM?
  5. Posting from a friends computer. OK, ran memtest overnight....that is a lot of fails....a whole lot of fails....What information should i need to take note of? Test 5 is where the fails are at btw...if that could mean anything. i'll switch sticks tonight and try, I seriously can't go without a computer, so if an RMA is needed for my mobo and I have to ship mine to get a fixed one then I kinda..can't. Have to go to class soon. Be back later. Thanks everyone.
  6. Just checked to double confirm, yes i have a lanparty NFII Ultra A version, I do not have the gigabit lan port or CMOS reloaded like the other and I have two seperate IDE connections for the RAID array, as well as only 1 SATA slot. uninstalled SP2 and same s*** still happens. I can play halo for as long as i want though...as for viewing adobe reader / word dox online...i'm kinda SOL. Earlier today my comp restarted when I had it underclocked to 266 fsb. I was pretty p***ed to say the least. Haven't looked at your thread yet legacy but from what you're telling me it sounds about the same. Windows reports a problem caused by device/display driver. I'll let the memtest run overnight, but if it is the memory I'm going to have to buy a new mobo. If it is the memory type that is the problem then there would be no point in sending it back in for another stick or two of the same stuff. Let's hope that's not the case though. If it is....urgh..... Update~ removed unnecessary swearwords and checked your post Legacy. Sounds very much alike, I'm going to run memtest overnight with both sticks and if errors, over the next two nights one by one. I'm operating in Dual Channel mode at the moment. Wish me luck.
  7. Ok.. the ram is running 1:1 and cas is 2.5, swapped the ram with a reluctant roommate and it works fine in his computer. CPU voltage is 1.65 ram is 2.6 and i didn't change voltage to AGP because I didn't know what is safe. Idle, processor is at 43.5 C. I'm running Hardware doctor and it is giving me a warning about VBAT being too high. ranges from 3.1 to 3.2, never higher. I'm going to test it real quick, if it last more than 1 second in halo, I'll be convinced.
  8. Hi all, first time poster long time DFI lanparty owner. After searching around the internet for help with my problem(s) I came upon this site. Seeing as how most owners of DFI mobos have successful results, I was hoping I could join the masses. I've owned my mobo for about a year now and everything had been great. Until I upgraded. With the coming of college I got a few presents. Particularly a 6800 GT, two sticks of 512 pc3200, and a shiny new AMD 3200+. Then bad things started happening. Ever since I've had this new system, I would get random crashes, like...really random crashes. For instance; after just starting up my computer and trying to access this site. As soon as the banner loads, computer restarts. Viewing an Adobe acrobat file over the internet through internet explorer, boom restart. Other times it happens an hour into gameplay of games such as Neverwinter Nights and Farcry. Halo for some reason never gets past the loading screen...Anyway. After said crashes, windows pops a screen saying "windows recovered from a critical error" I send a report and get one of three solutions. (I don't know exactly what they said, I can't access that right now) 1. The CPU detected an error and forced shut down to prevent damage. 2. Error caused by a Display Driver (I assumed graphics so I updated graphics driver which started its own set of problems) 3. Error caused by a Device Driver (I did recently install a new soundcard but these errors were here before I installed it.) I did a little tweaking and I found a way to make it stable, thing is I'm taking a performance hit. The computer can't run at 400 fsb, I have it underclocked to 266 atm and albeit nothing noticable is different, games run slower. While the processor is clocked this low, I can do anything with no errors. I am not an avid overclocker, I don't know what I'm doing and I've always been content with the way my games have looked under safe, stock conditions. This case is different though. I paid for some awesome parts and I want to use them to their full stock extent. I know a fairly decent amount of information about computers. The one i'm using was built by me and i've been paid to build for others before. There are many things I've not done to test, simply because at the moment I don't have the means to swap out and test parts. I was wondering if you guys here could give me a hand. Oh, running prime95 with my CPU at 400 fsb causes a crash within minutes. I assume it could be one of a few things. (in order of probability) 1. Bad Power Supply ~ The needed power for these new parts may be more than what my Antec 420W can handle, though I doubt it. But I had the PSU for about 2 years now so I dunno..) 2. Bad Memory ~ Very Rarely I'd get an error instead of a straight restart that says "insert crap and digits here....the memory could not be "read" " I had ran memtest before with no problems for the first hour so I assume thats not the case, but I'm not entirely sure. 3. Bad Processor ~ God I hope not because I need a computer to get work done and the process of sending the processor to AMD for a new one would take time that i can't afford. 4. Bad Video Card ~ I pray...PRAY that this isn't the case, although eVGA has an RMA policy that is still in effect, again, I don't have the time to not have a fully functioning computer. 5. Overheating ~ room temp is around 70 deg F in the room, Hardware Doc gives me 31 C in the case, 47C CPU idle, and 54C CPU load. (Prime 95 is running) I head the processors can run at speeds of up to around 85C w/o damage but I also heard that the readings for processor temp are off by about 10 degrees C give or take. These are my thoughts and my specs are listed below, I'm sorry to have wrote so much but I wanted to explain as much as I could.
×
×
  • Create New...