This is one of the reasons why i use a BIOS Savior. Do you think the corruption happened after you forced a CMOS Reset after you moved the jumper over?
This is one of the reasons why i use a BIOS Savior. Do you think the corruption happened after you forced a CMOS Reset after you moved the jumper over?
:D Yep - because using BH-5 on 5V rail before the Vdimm was set to 3,72 when I turned the rig off.Quote:
Originally Posted by The Mofo
Then I swiched the jumper to the 3,3V rail and remebered my last setting 3,72. That was the reason I cleared the CMOS to prevent the TCCD from gettin' 3.2 volts and within that all somethin' went wrong.
:toast:
I hope to get my RMA dfi back this week. I came home one day from work and found any load on my cpu caused it to crash. I went into the bios to check this out and the bios was garbled up. I tried to flash it but each time I would flash and save optimal setting and go back in to make chages it would garble up afain tried a few different bios - same thing until it hung up during a flash. then I got the 3 rid lights and the power light on the front of case flashing and it would freeze before it boot or run a floppy.
I wonder if forcing the CMOS reset fubar'd everything up.. Ive had a similar problem once and traced it back to not pulling the power connector from the psu/mb out before forcing cmos reset.
--- HCC ---
Did you try to reflash the "bad" BIOS chip after getting things working?
I would agree and "preach" to always push the pwr button a couple times after disconnecting pwr, before changing any hardware.
The deal with the mem change over... use those multiple settings stores ("BIOS reload" screen) to store good working settings and a "default" super slow setting (like 2.7 Vmem, 1.4 Vcore, 100Mhz FSB, 6x multi, 2.5,4,4,8 mem) for change overs and recover mode. Assign function keys to them. Then before changing mem types out, go into the BIOS and do a "load from this setting" the super slow setting to insure you can boot up afterwards.
Also, turn off the "auto save last good boot" in the same menu immediately after you have booted the "super slow" setting. That way your default "safe setting" is sure to boot anything safely, and the CMOS won't get written to during a bad OC setting boot. You can also select the "safe setting" with a jumper without having to clear the CMOS supposedly (say supposedly because the only time I tried it was before I had my CMOS set up as described, lol).
Peace :toast:
So do you think that the 'auto save last good boot' feature could be the cause/final straw of the numerous DFI SDS? I say 'the last straw' because I guess if the board starts to fail, becoming more and more unstable on each boot, once it gets criminaly unstable then it tries to rewrite 'good' settings on a bad boot, and because the system is unstable it borks the bios. Interesting....
Edit: To elaborate, could this feature also cause compleatly sudden death, ie. user trys highly overclocked settings, bios panics due to instability and trys to 'flash' good settings and borks itself??
I too use a BIOS Savior... ever since my Abit AN7 had a corrupted BIOS and I had no way to restore it without RMA'ing the board at the time, I bought one for my main rig. For $20-30, and the fact that it can be used with newer motherboards (the model I have works fine on a DFI Lanparty NF4-Ultra D too, as they both use the same BIOS chip capacities/types), it's a very good investment. When overclocking, things can go wrong quickly with the wrong settings regarding the BIOS... it's a good backup.
yea i do that all the time (turn power on with cord undone) works like a charm
:D No - did not try a hotflash, if somethin' goes wrong I have no BIOS anymore, ordered a new BIOS chip for 15 bucks, not really expensive.Quote:
Originally Posted by EMC2
I always set manually save settings before changing anythin' - here not the problem because I often replaced RAMs before. This issue was caused by some bad voltage I think, has to do somethin' with the Vdimm jumper.
It doesent matter if I push the start button after turning off the rig, there is the MACH II GT within the boot circiut and only the MACH gives a signal to the board, so it only would cause that the MACH is free from electricity....
:toast:
HCC, I think we need to get to know each other better...
... because now we're both on the same boat :D
Just made approximately the same mistake.
Wanted to see how some TCCD borrowed from a friend clock on my DFI.
Vdimm for my VX was set to 3.4 with the 5v jumper, of course.
Loaded optimized defaults first, though.
Took VX out, put TCCD in, moved the jumper... and cleared cmos simultaneously as well.
A note for others: power cord was unplugged and power switch was pressed at least for a couple of times to remove any excess power remaining in the circuits.
Pulled everything back, pressed the power button...
... BANG! 3 red lights and nothing. NO POST.
I guess, I need to refresh my hotflashing skills... my nF2 rig is still running :D
:banana: Ha - I'm not the only one !!! Bad luck often comes twice - though it hit two different people this time........ :p:Quote:
Originally Posted by mrlobber
So what do You think about it? Has somethin' to do with the jumper, heh ?
Maybe we should report OSKAR - not all user have a second BIOS chip like myself or a second rig to do a hotflash....... :slapass:
BTW within all that trouble I noticed that there even is no use to move the jumper back to the 3.3V rail - I had the same temps with 2,8 Vdimm on 3.3V as on 5V rail, but have 2 x 120mm fans blowing straight to that area....
:toast:
Yeah, definitely the jumper is involved somehow. All I know is Oskar warned that when changing the jumper, you should act almost as when clearing bios - with all that power unplugging and so on. Obviously, there is a connection between the two (naturally, should be so that the board knew when it has the high Vdimm available), but it has some nasty backdoors and these links are getting opened if they (bios and the jumper) are reset simultaneously...Quote:
Originally Posted by HARDCORECLOCKER
The most stupid thing is, I read this thread already, but somehow thought it doesn't apply to me :p: :stick: At least now we have 2 cases proving a theory :D
;) Yep - think that's the point here. Sorry to hear You even read my thread before it happened to You.......... :(Quote:
Originally Posted by mrlobber
BTW...., never ever change Your avatar - I love it !!!
:toast:
Maybe if you didnt force a clear on the BIOS, it wouldnt cause the corruption? Only thing i can think of is there is some kind of voltage spiking the BIOS chip when you force a cmos clear.
How come everyone is moving the +5V jumper back over to default? You dont have to crank it up if you dont have to.
This is pretty funny how everyone is RMAing their DFI boards this week. Mine died on me last week LOL
GO DFI
its obvious because youre too hardcore :nono:
Never thought of myself that way :DQuote:
Originally Posted by Voodoo|Minion
Ok, update on my situation:
my DFI is half dead.
That is, it posts with memory in memory slots 1 or 2, and it doesnt post with memory in slots 3 or 4 (closest to the cpu). Tested with 3 different memories (VX, BH-5, TCCD), 2 bios chips (beta 3.26 and official 3.10), both Vdimm jumper configurations.
Apparently, it seems that something in the Vdimm circuit is damaged.
So long for this DFI. Was a pretty good board for me. Time for another one...
:D Also update: Got a new 2nd BIOS chip now, who knows whal will happen in future........ :stick:
:toast:
Quote:
Originally Posted by HARDCORECLOCKER
I"ve been looking into this, as it happened to me on 2 seperate occasions. First time, brand new build using Mushkin TCCD 1gb pack. The good stuff, lvl2 black. Board failed memtest, next day bios chip died. Or so I thought. I rma'd my memory too and scored a deal on bh5 to hold me over on RMA. reflahsed bios, bh5 works flawlessley with it. Tried TCCD again, failed memtest. I didnt leave it in long enough to kill the bios.
Second time, building a system for a friend who already had mushkin tccd, same memory as me. I warned him about the bios thing, he wanted to try it because he didnt wana get new memory. Worked fine for 3 days, then became windows unstable, still passed memtest though. Then got the bios checksum error, no amount of reflashing fixes it. Tried my bh5, reflashed, works fine. Hes going to buy bh5, but in the mean time, I haev him 100% stable for a week now with a SINGLE stick of 512mb mushkin tccd.
You also had tccd, and do a search, 99% of the people that killed their dfi's had TCCD. Interestingly enough, this boards bios was specially optimized from the get-go to run TCCD super fast; I believe oskar or bigtoe said that (dunno who, it was someone that knows their bios...). My theory is that one of these optimizations is simply running too aggressive for some of the TCCD memory out there, and corrupting the bios as a result.
Seriously, do a search, its scary how many people have the dead bios/tccd combo. I don't know why or even if memory could corrupt bios, but I'd put money on there being SOME kind of link there.
:D Indeed very interesting facts here - had some problems with TCCD right from the start with this board - booting into windows at 10 x 334 1:1 but no matter what settings I tried - didn't get it stable.
And the BH-5 running like charme......... :p:
:toast:
more from the 3400 @ 3.2ghz thread.....
Quote:
we corrupted our bench drive right away, then we had alot of system problems. we thought the mobo was dead for over an hour. tried everything.. then eshbach threw in one of my sticks of bh5 and BOOM! it worked! put his ram back and it fired right up!
in the end we learned alot, but didnt run any 3d.
Not me... BH-5 is running horribly with mine with OCZ's new BH-5. I've done EVERYTHING anyone else in this thread would have done.
I first tried seeing how far I would get without enabling the 4v option, and I only got to 235 Mhz. So I did usual (turn it off, pull plug, wait a minute, clear cmos, change jumpers to 4v and then restart). When it restarts, it just turns on for about 10 seconds, then shuts off and the vdimm light goes off. So I do the same thing, and it finally restarts. I test with Memtest only at 200 Mhz and at 3.3v (just to check for instability at stock speeds), and I get Memtest errors galore.
Right now I am trying different bioses and timings and nothing seems to help. Odd... I never had this problem with VX's.
now that sounds like bad memory, I havent heard of any cases of limitied overclocking with memtest errors, hell, my TCCD was superpi stable at 280mhz before it went. Check it in another machine
Hm, some news kinda on this topic by OPB here:
http://www.xtremesystems.org/forums/...ad.php?t=59414