If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
It fixes my graphics card errors (The description for Event ID 14 from source nvlddmkm...... ) im over the moon with that :) It seems all fine and stable with the same overclock I was using on f5x ,however it still has the bug when you leave the bus to auto it goes to 99.77. if you manually set it to 100 it works perfectly.
i5 4670k
gigabyte GA-Z87-D3HP motherboard
MSi twin forza 770gtx 2gb
Soundblaster X fi xtremegamer
8gb Kingston ddr3
Hi, noticed something with the Z87X-OC F7g BIOS, in windows 8.1 it no longer reports the correct mem speed, it just stays at 1600MHz even though I'm OC'd to 2200MHz with F7d it worked. Not really a major thing, CPU-Z still reports my mem at the correct speed :)
It's hard to call that an excuse with the thread named like it is.
1) You can always revert to older release BIOSses.
2) It's BETA. What definition do you need of this?
3) Unless the BIOS physically breaks your board you got no reason to complain. If these bugs and missing features annoy you, stay away from beta BIOSses or get a different board from a "better" maker....
4) One exception: X79 boards and being forced to use betas for IVB-E CPUs...
Hi what stuff are you talking of ? I've not really looked at the bios much just set same options as on f5j and booted, only issue i saw was 99.77 bus.
For example the CPU voltage settings doesn't work properly anymore when I disable CPU turbo mode - Offset voltage setting is completely broken and has no effect. Furthermore Bios F6f causes restarts very often when I start or restart my PC while booting.
Then it's a USER ISSUE. Why do you assume I didn't ? The truth is I had a screenshot of CPU-Z on my HD but Tweaktown refused to have it uploaded for no apparent reason, so I am trying again. Currently using F14b with VirtualFred's mod and iRST SATA RAID option ROM 13.1 modded in by myself.
Looks like someone else overlooked something there. Either did not know how to set the multipliers by typing the numbers in or just not knowing that the memory multiplier needs to be reduced because it is linked to the BCLK.
ALSO, I ran Cinebench 11.5 CPU test. The result was 8.45 at 102.33x43 and 8,42 at 125x35! At par with my old results.
It's not a user issue, the BIOs is flawed. I figured it out after seeing you post your overclock at x35. Tried the same multiplier as yourself, it works. Tried every multiplier (x34,x35, x37,x38) BUT x36 and it worked. x36 in F14b on the X79-UD5 doesn't. Try running x36 multiplier. It reverts to 28x for me.
So the issue is, x36 multiplier reverts to x28 multiplier when using 1.25 strap on the X79-UD5 using F14b . Every other multiplier works.
1) You can always revert to older release BIOSses.
2) It's BETA. What definition do you need of this?
3) Unless the BIOS physically breaks your board you got no reason to complain. If these bugs and missing features annoy you, stay away from beta BIOSses or get a different board from a "better" maker....
4) One exception: X79 boards and being forced to use betas for IVB-E CPUs...
Sorry guys I was misunderstood. I was taking up for Stasio. The original comment that I was responding to was an unappreciative user stating something to the effect of "Why did you post this BIOS. It's not perfect, it has bugs. Don't you test this stuff?"
There was a post stating that it said in the OP that this software was for testing and problems were to be expected. I replied to that meaning "Yes exactly, but even if he didn't read the OP that's not an excuse. The thread says BETA in the title so people should know it's to be tested. It's not Stasio's fault that people aren't familiar with fundamental terms or know the etiquette of not coming into a beta testing build and ranting about the software not having been tested. The whole purpose if the thread is for US to test it. Sheesh.
Anyway, I'm sorry for the confusion. There was another post several days before that I ignored but I realized with this one that my post had the opposite effect of why I wrote it.
Thank you stasio for all that you do. Sorry about you guys thinking my message was negative instead of the other way around.
@deathelement: That's not what I read but okay. There are still options when setting 36x. like enforcing it via turbo mode settings etc. Just a thought. IMHO still more a minor issue...and no sorry I won't mess with my current settings now. I am at 43x102.33 again. You could also try 128.6x35 to get 4500 MHz....
Comment