Printable View
i get the same problem with my vx. i rma'd my vx to monarch....
running great 2 2 2 5 at 250. change something or just reboot. then all hell breaks loose. get long beep and no post. nothing can bring it back as long as vx is loaded. even boot with extra bh-5 sticks and set all timings and such, put vx back in and still no post.....just a long beep....
change bh-5 buffalo sticks and starts right up, every time......
hope the new set of vx stick fix the problem.....
max
Yeah, I'm gonna try more bios' and then do a similar thing.... dare fate by getting same type of ram again. In my case TCCD on Brainpower. Gonna have to take a step down and go with PDP. No offense to the PDP guys, these Gskill LE's are just binned higher. Well, if I keep having issues, I'll report. I think I can help this thread by trying all the same hardware in another board and reporting. So 1. try to fix with bios.. 2. Get annoyed and break down the rig. I got a chaintech with a winnie sitting in it already.
I have 2 sets of Ram to try, and they both do the same thing.
2x256 XMS3500 and 2x256 GSkill LE ( 431 chips).
It is NOT my ram.
I have been having issues for the past week or so regarding this board.
I could NOT get it to boot last night or this morning regardless of cmos clears/ ram swapping etc..
I just put my X800L in the 2nd pci-e slot ( running 2x), and it booted NP.
I did this B4, and it worked for awhile, and even that wouldn't work a day later.
Well the looks of it we can rule out BH die. BH seems to run fine.
Pretty sure VX is UTT and UTT is a modded CH die. AND we all know how CH die did on our intels vs the BH on intel.
As far as other peps and TCCD prblems, bet theres something they got wrong some where, cause most of us are comming to the same thing. "BOOT WITH 1 STICK, THEN POWER DOWN, THEN SHOVE THE OTHER ONE IN, AND BOOT" then dont shut your PSU down or you have to go all thro this again.
Here is a guys post about what happen after he RMA'd his broke'n CH die lol
http://www.bleedinedge.com/forum/sho...1&postcount=52
Read the whole thread lol
Anyways
Peace Nugz
Well bad news, my new sticks are toast as well now.
After a lengthy burn in, the reboot issue has returned.
2 days of stress free computing, now im back to being a no-post wonder.
The bottom line is that i dont think these chips can hack the voltage, or require liquid cooling in order to function for any length of time.
Something is causing a change in them after they chew on the juice for awhile...the mem works fine once up and running...so i dont think chips are defective....but after they got some high voltage it causes them to be hard to detect.
I dont know, maybe i should switch to some BH5, or go the other end of the spectrum and aim for high fsb.
BOTTOM LINE IS THIS:
OCZ KNOWS THERE IS A PROBLEM AND THEY NEED OUR HELP TO FIGURE IT OUT. LETS WORK TOGETHER, FIND THE ISSUE, AND FIGURE OUT THE SOLUTION.
lets try and find the common variable here as to why this is happening:
my system is as so:
evga 6800gt
dfi sli-dr revision AA0
2x512mb pc4000 VX
enermax 600watt sli ready PSU
2 x maxtor 80 gig SATA raid 0 on nforce diamond max 9
1 x 300 gig SATA maxtor diamond max 10
lg dvd/cdrw combo
DELL 2405fpw monitor
bios 414-2
After all my research and trials at home here I have come to a conclusion...
Alot of fanboys wont like this, but I RDGAS.......
I have NEVER seen a mobo with so many quirky issues....
EVER.
This mobo, when it runs, is great......
but the bugs make it a SERIOUS POS.
Thats reality, ask around.
Fanboys, I don't really care. I've already been there.
Good Day.
You guys should start checking your voltage rails and also try to measure the memory module voltage. Apperantly the board has some issues with higher voltages at start up. This problem(cold boot) is also known with the NF2 DFI boards(i had one back then). If you do some research over the net youll find it. My opinion is to try some TCCD chips since they are very sensible to voltage and see whats going on. Also try some of the OCZ PowerStream PSUs since they have the rail adjustments at the back. That way when you adjust the rails you will know for sure that you provide the "perfect" amount of volts to the motherboard. Also what abot the chipset voltage? I heard the DFi NF4 has some chipset voltage adjustments.. Maybe play with those too...? :rolleyes:
PS. I forgot to mention that you also need to play with the timings. I know most of you want some crazy tight timings from the VX modules but try to lose them and see whats up...
Good luck to you guys
D
the only reason most of us can accualy get them running is cause WE KNOW WHAT WE ARE DOING, to acculy get that far. Most people would just say it's dead and RMA the stuff.
OCZ Powestream 520
Iv adjuststed my rails from the red light to orange. when orange less stable. witha DMM reading it.
Timmings. YOU HAVE TO HAVE THEM SET RIGHT befor the 2 sticks boot. allmost down to exact timming. if ones off mine dont boot with 2 sticks.
Dont think its the MB. as CH die had big problems with intel. And it acts the same on my intel rig as the old CH die IC's did.
More or less it's the crappy die on the IC's. And now after a few months, it's starting to show that CH/UTT die can't handle the volts as OCZ thought.
It's the ram in sertain boards, just like kingstone CH-5 i have. works in the IC7, But not in my P4C800-E. IC7 you can ues the 5:4 divider with CH5 but not on the P4C800-e i have. It's strange. But o well.
Peace Nugz
Thanks everyone for the tips and advice! When I get my OCZ 600W back I'll try changing some rails and then seeing the results. :)
Quote:
Originally Posted by Nugz
I agree, seems that its not just NF4, I know of at least two NF3 users that now have boot problems with these sticks (VX)
First off I thought it was an OVP issue but I now know its the memory as Im getting boot issues at default timings with 2.8/2.9/ 3.0/3.1 volts
Bad news guys, the reboot problem has resumed...worse than ever. The Sticks "slowly died" on me.
i had about 2 days of glorious normal operation then it went all crazy on me again, there is a hug tjhread over at dfi street on this issue, no one knows what is going on yet.
Well I got my new PSU back today and the usual steps required to boot (you know using 1 stick, then changing to 2) now works again. Computers are strange things. :P
I believe it is rather tricky issue. My first 4 Mushikin blue had problem occasionally until it died.
My new 4 sticks of mushikin blue seems to have no problem using all else same. There must be slight difference between even each memory. If you do have cold boot issues as mentioned, I suggest grabbing new memory... (be it RMA or what not)
Okay I lied about earlier, I switched the power supply off to change cables on the motherboard and now the other stick doesn't want to know me.
the board is great for me with tccd - just hates vx/utt etc etc....
I have this problem occassionally too...But while a slight inconveniance it's nothing for me to lose sleep over.
While my VX runs fine at 260 with 3.45v, occassionally when I cold boot I get that lovely bios beeping noise (ram error). No matter what I do at this point I've found it will only boot from the FIRST orange slot in my case when this happens...I have to take the other stick out. What I do is just boot windows with the one stick...it freezes while loading windows after I log in and can see my wallpaper and such...I then power off the system and insert the other stick and it works fine. I know it's weird, but it works. It doesn't happen that often, but it does happen.
While it sucks this happens, it's good to know i'm not alone and my ram isn't dying. I was starting to think as much...Almost RMA'ed until I saw this thread.
It is worth noting this has only happened (I believe) since I started using the latest bios. I havn't flashed back to an earlier version yet...but might that be it? I'm starting to think I should go back to 3/10 or 3/(26?). Those seemed to be the most stable...although I could be wrong.
i tried every available bios and it still did it.......every combo of timing / setting - it is deeper than that
everything runs preety well here
2/18 bios, twinmos mtec "value" 512x2 250 2-2-2-5-7-15 3.2v
I was have intermittent problems with cold booting. Just got me a new venice 3200, so had to flash to newer bios, was running 2/18. Flash to 4/14-3, everyhting goes well, restart then :censored: long beep and nothing. Switch to a stick of some old value crap I have, boots fine. Then change to my twinmoss, get into bios, set how it has been running for over a month, and again, just long beep no boot :cussing: :cussing: :cussing: Flash back to 2/18, still can't get the twinmoss to boot. The ram is fine. Tried it in my son's computer, boots up just fine. I think that I've had enough with this ram. Love being able to run at 260 2-2-2-6 though. Does the BH-5 UTT have this issue also? Or is it that this damn board is just too picky with ram? Maybe I should try some TCCD. Any suggestions? Sorry for the rant, but this is just damn frusrating.
I had a litte trouble when I first got the board, but have found that high vdimm will cause the board to take a while booting... Then my board just quit, and before I RMA'ed it I found that it would boot fine (fast) when using the 3.3v line to feed the vdimm (using the pin trick, and adjusting your 3.3v supply up)....
And, now after I got my new back, I did not even try using the 5v supply and went straight to the 3.3v line mod and no problems at all... Boots cold, warm, restarts fine etc... and it is fast to make it's first beep ~2sec, as before it could take it ~10 - 20sec to finally make it's first beep..
I also noticed that when I first booted with this board I used EB memory and it booted w/o problem, but as soon as I installed the VX memory it did not boot. I then had to flash to the 310 bios and change the memory settings and never had no boot problems besides the long wait....
4x4n: i think it is limited to utt/ch......i havent read anywhere of ppl having issues with old style bh or even new style bh......just plain utt has issues..
jasonxxx: ya i miss 265 @ 2-2-2 but having to wrestle with the board day in and day out gets old real fast...
oh well tccd @ 300 will have to do ;)
I just ordered some of the OCZ Platinum Rev 2. I think I'm done with utt.
Quote:
Originally Posted by dsumanik
Hi, realize that there was another issue that came up before the DFI NF4 was used to test VX. We used MSI Neo2 NF3 boards with a booster and later found that some sticks would not boot consistently on the DFI NF4 (cause it's cranky). We have taken care of those with an RMA.
The "cold boot issue" is something entirley different. If you noticed, guys with Winbond based RAM from other manufacturers, and guys with TCCD are having this problem.
OCZ does have awsome RMA support, but an RMA won't fix this if its' spread out over all manufacturers, new and old RAM and Winbond and TCCD.
If I were looking to solve this I would be asking about boards revisions, CPU steppings and week codes and the like to find some that iyou all have in common, not your memory, as we can see it's not a certain type of memory or a certain brand.
What do you think?
How about posting your DFI mobo type (UT unmodded, UT modded to SLI, SLI) revision (located on the sticker on the bottom side of the last PCI slot, like AA0 or A02), PSU model and size, and whatever els you can come up with to find something in common with all of you. ;)
BTW, try holding down the Insert key while booting up, as this always gets me booted right up when I have had this happen (yes, even me with TCCD when heavily overclocked :))
If you read back in the thread some, including myself have had cold boot issues with TCCD also. I have always had the 5v jumper on though, from day 1. Maybe it really is the jumper and putting it back to 3.3v will fix this.Quote:
Originally Posted by arctic-k20