Thats great stuff nFo, will be very helpful.Quote:
Originally Posted by nFo
Do anyone know what is in the changelog for the 0502 bios?
Printable View
Thats great stuff nFo, will be very helpful.Quote:
Originally Posted by nFo
Do anyone know what is in the changelog for the 0502 bios?
Awsome nFo! :toast:Quote:
Originally Posted by nFo
I tried 502 as I have with every bios so far and I couldn't get rid of it fast enough. It almost killed my board. Something is not right with it, at least for me. Back to 408.
502 undervolts. 408 overvolts. the difference in actual vcore is huge (almost -0.1v), and it's probaby what doesnt seem right. besides the usb issue 408 is terrible, can't get it stable at 400 fsb. 0005 is still the best, but 502 is better than 408 as long as you up the vcore in the bios considerably.Quote:
Originally Posted by xgman
-mds
what USB issue with 0408
here is my latest OC on a P5B-dlx and e6300
http://upshizzle.com/gallery/albums/...on 3304ghz.jpg
running 2 hours ortho right now and counting...
http://upshizzle.com/gallery/albums/...3ghz_13006.jpg
http://upshizzle.com/gallery/albums/...006_orthos.jpg
Quote:
Originally Posted by ssabripo
What does this have to do with the P5WDG2 WS Pro???
Nothing. But he likes to post... :p:
He also post this same pic to the "Post your E6400 OC Results!" thread. Consider that he's using a 6300! :lol2:
Edit: Hopefully he posted it on the right thread... :clap:
I have put on the bios 0502, but it does not go well on overclocking....
I have had to replace the official 0408.
When will exit new bios the ufficile one?
By
I was wondering if someone could help me understand the new options that are available under the CPU configuration menu in the BIOS v0408. The new settings available there don't make too much sense to me :p:
Thanks in advance!
Quote:
Originally Posted by Natalia
Just a few additional questions:
Does everyone have a "long" delay after the USB devies are initialized, the memory about is displayed,.....(delay)....... and then the USB connected devices and Hard Drives /CD Drives are diplayed?
Also, when a boot fails and you get the black screen of death when the BIOS *tries* to boot, and after turning the computer on and off and the BIOS settings temproarily revert, does it take everyone 2-3 minutes to get through the Hard Drive recognition process?
One more thing, what does "Intel CPU uCode Loading Error" mean?
About the uCode error, I had this with the 0408 bios and the latest beta, 0502. I went back to 005 which I think is the most stable and the error went away.Quote:
Originally Posted by Natalia
About the HD recognition, Only time I have encountered this was with IDE drives not properly configured as master / slave ( but you are running a SATA drive) so you got me threre.
If you haven't tried this, just load all default values under the Bios and start from scratch. Maybe you disabled something important while playing around with other settings!
i get a dealy with USB recognition for about 10-20 seconds as the longest...if it hangs longer, i just push reset.
you can adjust the recognition time in the bios as long as the device is on when you post and then go into the bios...go into USB devices and you should see the device near the bottom of the USB page...enter the device and adjust time to recognize device...the longest delay setting is 40 seconds and the lowest is 10 seconds.
a black screen of death and then a reset taking 2-3 minutes to get through the hard drive recognition is excessive...i would either do a turn off and then on after 30 second delay with recognizing the drives or try using the reset button...pushing the reset button usually shuts down the computer for me unless i have exceeded the overclocking for the voltages that i am using at the time....a note: you can also adjust the IDE delay time under IDE settings on the first bios page.
my understanding about the intel cpu code loading error is the overclock is to severe due to not enough Vcore, Vmem and Vmch!...try adjusting the Vcore first.
Quote:
Originally Posted by Natalia
this is UNBELIEVABLE....
here i have the E6400 from my other computer...i switched out an E6700...i originally had the 6400 set to boot with 1.60 Vcore and just about max on everything else for voltage except for Vfsb.
NOW...i set the Vcore to "Auto," and vmch and vdimm to maximum (1.8 & 2.4)...still, FSB at 440 and the darn computer boots into windows...the memory is set to "SPD" for both scenarios of high/auto Vcore.
the system was never orthos stable even with 1.6 Vcore...look now...1.23v and temp is way less...before i was seeing 63C for idle conditions with 1.6 Vcore...i still think my Ultra 120 heatsink is not working optimally....going to change that out very soon....been waiting on memory to show up at newegg before making the purchase.
under CPU category in the bios, i have the following enabled or auto:
EXECUTE DISABLE LIMIT
C1 CONTROL
CPU INTERNAL THERMAL CONTROL
INTEL SPEEDSTEP
BUT...can you believe it....it seems normal...no BSOD, SO FAR!
nice work...so you set vcore to auto, and get lower vcore to cpu?
i just lowerer my vcore to 1.4 (400x9) atm...i wanna see how low i can keep my vcore, and still keep this oc at the same clock.
i wasn't happy with the high idle temp of 63C and 1.60 Vcore...i just started to experiment with the voltages and certain settings in CPU category.
my approach to overclock is to have a stable system for idle conditions...since i am not running any games, it is not important for me to have an orthos stable system.
yes, the Vcore is set to "AUTO."
PLUS...i have the PCIe bus set to 120 MHz...PCI bus to 33 MHz.
i am a HAPPY camper!:)
EDIT:...hyperpath has been disabled at all times.
nothing really....just sharing the news! :) :toast:Quote:
Originally Posted by fishingeek
i've experienced similar behaviour with my 0408 WS proQuote:
Originally Posted by Natalia
and i think its the ICH7R raid getting !@#^
occasionally i might get a master hard disk error followed by a series of numbers declaring the drives ID....after a minute or so
usually after pushing the clocks too high...
i think i'm gonna go with 005 bios to see what happens
Quote:
Originally Posted by SlackerXL
Interesting thoughts. Would not have thought to think of the ICH7R being the culprit.
could be the drive.
I have no issue's with what is described above on 0408, I have 2 raptors in raid 0, I did have problems with the marvel after boot though, that thing is a piece of shiznit, you cannot run to simultanious drives on it without experiencing severe throttle, cannot image what a raid array would do to the thing.
However with all the damn pci slots on this board, I just shoved 2 sata controller cards I had laying around in, and run my storage drives of independendent controllers, and use ide to sata adaptors for my optical drives, which are plugged into the other intel sata ports, and all is well, can read write and burn from both opticals and all the hard drives without slow down.
Do you guys have stuff hooked to the marvell adaptor? Is the bootrom on in the bios for the marvel? I would ditch that thing, and try another controller.
have you guys got pcie and pci freq on auto or manual?
I had a few issues crop up on higher fsbs when the pcie was on auto (sync with cpu clock). If so try locking pcie to around 100-105 at higher fsbs and pci to 33.33.
appologies if you've already tried this.
regards
Raja
Natalia
leave cpu microcode on (it recognises the cpu), that'll turn off the errors you are getting during post.
I also set ide timeout to 0 once you have a stable overclock and have stopped pushing fsb.
Can you stick a normal pci card in one of the pci-x slots. Have 3 pci cards (tv, wireless, x-fi) and need a good clocking board. Was going to wait for the new dfi rd600 but its going to cost a bomb when it comes out and its nor expected until next year + no evidence on how it clocks or if bugs yet etc.
Yup they're supposed to be backwards compatible with regular PCI.Quote:
Originally Posted by ted34
as HermS said, yse pci works just fine, has an issue with my x-fi in the pci-x slot, but just moved it to the normal position in the bottom pci slot and it is fine now.
Have a via controller card, a $10 one in the pci-x slot now, works fine