thanks, just flashed F7 and noticed the PLL override setting was gone, gonna try F7E
Printable View
thanks, just flashed F7 and noticed the PLL override setting was gone, gonna try F7E
Np and welcome. :) Nice looking rig, I use the white tubing myself.
Quote:
Originally Posted by dinos22
Sorry I meant the SATA2 ports.. I need to transfer the data off of my RAID0 which is 3x640 GB WD blacks to a 2TB that I just ordered.. I just want to make sure that having the 640's hooked up to the SATA2 wont cause any immediate damage.
Naa man I'm still using 1,2,3 & 4 noproblems...Quote:
Originally Posted by aver
Nice looking rig there, Nice job on the sleeving looks like you have experience and not a nooby :)
man sleeving those power cables is something else. really like that
oops think i killed my 2600k , mine needed a lot of v core 1.65 for 5.373mhz and ran all baenchies but tonight i had bsod a few times with something like failure to something signal on secondary processor , now all it tries to do is a permanent boot loop , so everything comes on as though its starting the boot process then clicks off and tries again and again, could be board but i think its the cpu myself
dont take long with that kind of voltage huh glen?
that sucks.
you need a better chip anyways
:D yeh mate got to look on the bright side :up:,can't see it being the motherboard . it tries to post but just loops and nothing on the led panel with the boot codes ,i'll get a cpu to try tomorrow
what cooling subzero? if subzero that really isn't promising.
LOL BTW nice cable sleeving i see them in microcenter for like 5-10 bucks per extension they are sleeved like that, I would do it if I kept this thing in a case. Or if my case had a window. I would do black, when get a gold plated waterblock black tubing, gold plated blocks for my GPUs and so on.
I will be interested to see if it was the chip. I just sent my board back as it was doing the exact same thing. I thought it was the board for me as it started after flashing the backup bios.Quote:
Originally Posted by GLENBOY
Aver,
If i recall, you *backflashed* the backup BIOS with an older version, is that right?
Maybe the main bios can be backflashed, but perhaps it was backflashing the backup that killed it?
I remember WAY back, with an Abit BH6 board (rev 1.1), they released some BIOS (around the time they broke CAS latency changes temporarily), I think it was version NK, and if you backflashed to an older version, it would brick the BIOS (the dos flasher would reach around 30%, then suddenly "insta-speed" 3x faster up to 100%, then the board wouldn't POST anymore. You could backflash successfully by hot flashing *twice* (the first hotflash would brick, the second one would succeed).
There was a 1.0 board BIOS version which did the exact same brick...I think it was two bios versions after the initial release of that board. I recall posting (maybe on the old ocforums?) about warning people NOT to backflash.
LOL I still have an old spare bios chip abit mailed me from back then...
Has ANYONE here successfully backflashed the backup BIOS with alt-f12 and NOT bricked their boards? (I don't suggest you try it until you get your RMA'd replacement from the recall...)
I've pestered Dinos22 in PM, but i thought i'd post these images here anyway. Is anyone else finding the Marvel SATA 3 ports are giving slow write speeds?
Intel SATA 3:
http://i24.photobucket.com/albums/c1.../Attointel.jpg
Marvell SATA 3:
http://i24.photobucket.com/albums/c1...ttoMarvell.jpg
You be one of the first to kill one if its the chip..... My 2500K has had the max the board can set 1.7V + the LL1 overvolt & 1.9v+ through the memory for days & she loves it :DQuote:
Originally Posted by GLENBOY
This is my max overclock for 24/7.
Using L1 4.0v set in bios with everything Auto.
If you notice under load = 1.356v max cpu clock 4.7
System is 100% stable, 30+ passes on LinX a few hours ago.
This time I left everthing enabled turbo ect. Running bios F7
No problem here flashing the backup, on UD4 or UD7?Quote:
Originally Posted by Falkentyne
Also have seen many users not have issues as well, here and other forums.
Marvell is always terrible like that :DQuote:
Originally Posted by jackbrennan2008
i'll report back this evening getting a new cpu to try i had flashed the backup bios to f6x but that was weeks ago and its been 100% sinceQuote:
Originally Posted by aver
i'll try new cpu tonight so will know whether its cpu or mboardQuote:
Originally Posted by C-N
I wonder why they limited Vcore at 1.7? Seems like 1.9-2.0 would be more of an ideal Vcore limit!
Not very extreme is it.... makes me wonder how much further these chips will go as I've just seen one run x58. Maybe its something I have done but my UD5 has no x58 multi x57 is the max you can set.Quote:
Originally Posted by Lsdmeasap
Edit: Think x57 is the limit of 2500K's ... 2600's go higher just waiting to see one go quicker than x58
There is no need for more volts. If you do need more I can give you a bios for 2.1vcore heh
I dont but someone might, Its good to know its not a hardware limitation :up:Quote:
Originally Posted by dinos22
lsd,Quote:
Originally Posted by Lsdmeasap
Remember, I was talking about BACKflashing the backup, meaning to an older BIOS, not forward to a newer one. I haven't seen anyone talk about flashing the backup to an older bios....
Done it both ways on my UD5... no problem, just pump F12 3 times to switch bios's & flash it.Quote:
Originally Posted by Falkentyne
Sorry I didn't catch that, but ya I have back flashed the backup as well when going back to F3 to test some things (From both being on newer F6x or above)
uf my friend thats very bad news gigabyte has been standing the flag "use our ports" i talked to them so if intels become degraded we are f*kd :down:Quote:
Originally Posted by Lsdmeasap