Formula350
Members-
Posts
34 -
Joined
-
Last visited
About Formula350
- Birthday 04/17/1983
Converted
-
Location
UNITED STATES
Converted
-
Occupation
www.Pro-Clockers.com
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
Formula350's Achievements
Newbie (1/14)
10
Reputation
-
Yea, honestly though, that doesn't really surprise me given that I think CPUTweaker was probably the last fan made/third party utility that did memory timings on AMD chips other than Overdrive, and as far as I know it had ceased to support AMD after Thuban (not even my Thuban-based Stars core A8-3850 is supported by it, which was a real bummer). For that matter, short of being either really good with figuring our registers along with having the tools to manipulate them, or the industry connections to have the awesome insider-programs, then seems like you're basically SOL these days (especially when it comes to AMD ). I remember when the OC record was set on Bulldozer and I was looking at that screenshot wondering "Man, I've not heard of PSCheck, it looks awesome!", then much to my surprise managed to actually find it on AMD's site (along with a couple other programs that I nabbed, but long since outdatted lol), I was one happy camper! Sadly, I couldn't contain that excitement and shared it with everyone... thus, that area of AMD's site once again getting closed to the public Oh well, right? I did see a thread on, I think Overclock.Net, where someone had said they had updated MSRTweaker for Carrizo, but for the life of me I can't find that thread again :\ If anyone happens to know what I'm referring to and can point me to it, I'd love to try to message the guy. Or *cough* better yet... if someone with coding savvy is able to update it themselves for us all, hell that'd be even better!! :ws:
-
Desperate times call for desperate measures... in a manner of speaking While I'm indeed in the neverending pursuit of more performance, in this instance I'm looking to take the "Polaris Approach" with less=better, as what I'm sporting is the mobile FX-9800P The most I've been able to come up with for anything tweaking related is an unreleased program made (modified?) by The Stilt, which he (understandably) is unwilling to release publicly. I've tried the most recent AMDMSRTweaker I was able to dig up which is v1.1 (and another one similar version, but is curiously much smaller file size [no, not 32b vs 64b heh]), but from what I've been able to tell the changes applied do not 'physically' result in any changes. The readings are reflected MSRTweaker, but nothing seems to actually take hold, at least as far as CPUz (and similar read-out software) or benchmarks detail. I know that the Kaveri and later models have issues with support, namely voltage related which is present of course, but even when dialing back that number which was provided there doesn't seem to be any changes. Thermals under stress testing seem to be the exact same as before making any voltage adjustments. Also, the PStates don't appear to be holding the multipliers either, as I've tried to make the Boost multis a lot lower in order to keep a more consistent clock, but everything appears to indicate that clocks are unchanged. Reasoning? Well beyond the obvious of increasing battery life, and lower heat output, thus hopefully increasing graphics clocks in games, it's also because the way that AMD chips are setup and in turn handled by Windows power policies... sucks. :\ For example the vast majority of the percentage values do not function at all, due to a large range covering most PStates, such as with the lowest PState covering pretty much everything from 0% to 55% Or the fact that 100% = boosting, regardless, and 99% = not full-speed but the next PState down, which is like 2.2GHz instead of 2.7GHz. Beyond that, I sure do miss the days of in-windows RAM Timing tweaks What I wouldn't give for something like A64Info again! At any rate, I doubt anything will come from this, but I honestly couldn't think of anywhere else TO look. Thanks :celebration:
-
No prob. Seems that the other A75 motherboard BIOSes are waiting on my testing of this one's, so I don't have anything to upload as I originally though. So I'll fire word over and let him know of the issues I've came across, but that the CPU-NB divisors work up to 900MHz at least.
- 3 replies
-
- a75-ud4h beta bios
- fm1 tips
-
(and 1 more)
Tagged with:
-
Note: As far as I'm aware, this is only for the A75-UD4H. I titled this thread with only "A75" as I am hoping to get the same Beta for the -UD2H (no guarantees). Please read the included Disclaimer text. It includes what has changed, and what I've so far discovered as bugs.
- 3 replies
-
- a75-ud4h beta bios
- fm1 tips
-
(and 1 more)
Tagged with:
-
Free 2000-4000MB/s Memory Write perf boost (at least on Gigabyte A75)
Formula350 replied to Formula350's topic in Llano OC
Hmm... <_> Well, alright, but I'm including a disclaimer!! lol -
Noticed a hugeeee difference in memory performance between the ASRock A55 Pro3 and it's replacement, Gigabyte A75-UD4H. The ASRock was getting anywhere from 2000-3000MB/s better Write speeds, around 10,000MB/s to 11,000MB/s. The UD4H was only managing 6,000MB/s to 8,500MB/s (I did break 9,000MB/s in an unstable config though). Initially I thought it was a problem with the CPU-NB (Mem Controller) in the BIOS, which I discovered was not running at it's full 900MHz at any DDR3 speed, which it should auto configure it 900MHz when running at DDR3-1866. Instead it was stuck on 720MHz, which is what DDR3-1600 auto configs to, and that's a healthy speed difference! Informed Gigabyte and they got a beta BIOS out to me, which it now provides manual NClk (CPU-NB) divisor control, but Auto is still bugged and not running at 900MHz. Regardless, you can select a divisor of 4.00 and that is 900MHz, so everything is peachy there! Hopefully they'll release that BIOS soon (my board may have died though so I can't continue testing it ) However, that unfortunately didn't resolve the problem with the Write performance. While tinkering with the F7 release, I had decided to "Enabled" the "C6 Support" option (Default is "Disabled") and what do you know... FIXED WRITE SPEEDS! Overclocks don't seem to be effected by Enabling C6 either, so that's good. To enable C6 Support, just go into the Advanced Chipset BIOS menu and it's the second option in the list Simply cursor down to it, and press the + key on the keypad or hit Enter and select "Enabled". Back out and goto "Save Changes and Exit" (or Press F10 from any menu) and that's it, right as rain (To those wondering about the Beta BIOS. There are a couple new bugs in it that could cause problems for some. The biggest, which will result in your system not POSTing and requiring a CMOS clear, is the selection of any NClk Divisor lower than 4.00 (900Mhz) -- IOW selecting even 3.75 (960MHz) will require you to clear it. Also, the Memory Timing Menu's Proc ODT's "Auto" option does not work, not sure if it's broken any further, but it jumps to 60Ohms and doesn't display as "Auto" if you select it. So as a result, and not knowing Gigabyte's policy, I don't feel right with uploading it anywhere, I'm sorry. )
-
Been testing a Beta BIOS (F8b) for Gigabyte to fix a huge issue I discovered: CPU-NB (NClk) not running at full speed (runs at 720MHz, even when set to DDR3-1866, instead of 900MHz like it should) and effects what I assume to be the whole A75 line. For sure the UD4H and UD2H. Anyways... There is now the option to select the NClk divisors, up to quite an extreme level, though unfortunately anything lower than 4.00 (900MHz) results in the system not posting, and not recovering via Backup BIOS. But still, it's so much nicer! I'd attach it, but I'm not sure how GB would feel, and also I think the rather early (slightly broken) NClk adjustments might cause some undue tech support tickets Oh forgot, the memory Proc ODT is either glitched or broken too, with AUTO completely not working.
-
Tried it with the latest version? CPU-Z 1.59.4 just got posted on Stasio's list of tools today. I haven't had my desktop connected to the network lately so I can't tell you if it's approving results.
-
ASRock A55 Pro3, A55iCafe, A55M-HVS. ASUS F1A75-V, F1A55, F1A55-M LE, F1A55-M LX, F1A55-M LX PLUS, F1A55-V, F1A55-V PLUS MSI A75MA-P35, A55-G45, A55-G35, A55M-P35 Just if you want a more-complete list of boards that are out there, that's all
-
Last post of images for now, unless someone has any requests. (long pics, sorry, had to combine 2 into one) MaxxPi2 Pro (internal beta) "Memory" bandwidth scores, highlighting again the vast difference in memory performance between the two boards. This time I went and configured the Gigabyte to the same settings as the ASRock. The only thing different (from what I can change) is that the Gigabyte has IMC Ohm, Drive Strengths and Drive Timing options, which I leave at Auto. --------- MaxxPi2 Pro "Overall" memory score, same as above. --------- Best Sandra I achieved with the ASRock, and at the same (stable) speeds as the above (3.58GHz, DDR3-2300). I've yet to reinstall it to run on the 3870K (went all screwy, won't run) while overclocked, but the default config only net like 16GB/s on the Gigabyte --------- Sandra, again, but just outlining the change in performance on the ASRock board between the default NB speed of 900MHz when you set DDR3-1866(which I listed as it's rated 1800MHz) and the 742MHz (1500MHz) that the system selects at 1333. Also is the 2300Mhz which results in 1112MHz (2224MHz). This was before having done the subtiming tweaks in the above results. --------- ASRock's BIOS showing the option for CPU-NB speed options. It's a drop down listing a whole bunch, but no screenshot of that, sorry.
-
Random Cache-Mem results of the 3870K on the Gigabyte. The second one is the mate to the previous post's 1866 6-8-6 results. -------- 3.9ghz cachemem.png Results on the Giga with 3870K@3.9GHz, which I dropped the DDR speed down to in turn lower the CPU-NB (which sadly I have no choice over) to rule them out. Interestingly, despite those drops the Write performance isn't as bad as expected. Couple more left, YAY 5 pics-per-post! :banana:
-
A55 Pro3 - AIDA64-3850@3.58+NB@1107+DDR3-2300.png This is the best, stable results with that board. It's only a 3+1+1 phase config by the looks of it, which after having the GB board my suspicions that it was limiting the overclocks is confirmed. I can bench the 3850 at 3.9GHz and DDR3-2445, nothing that ASRock A55 board could ever dream of doing. ---- AIDA64-3850@3.8+NB@943+DDR3-2445.png Memory score for the Gigabyte, the best I've been able to manage so far. Quite good, but it's Write performance sucks, which again, is inline with what I experienced on the ASRock board when I disabled the ASMedia SATA-III controller . Not sure why that would occur, but it was consistent, and even then the Write was about 700+MB/s faster than this (fastest) Gigabyte result :\ ---- AIDA64-3870K@3.0+NB@720+DDR3-1866.png Defaults on the 3870K in the Gigabyte using the timings I've been using as "default". This is using the foolishly low CPU-NB speed of 720MHz, which doesn't help performance as you can see... ---- AIDA64-3870K@3.0+NB@720+DDR3-1866 6-8-6-34 CR2.png Defaults on the 3870K in the Gigabyte, lower timings (forgot to adjust the Command Rate and tRAS lower) and crappier than expected performance ---- AIDA64-3850@2.9+NB@900-DDR3-1866.png 3850 on the ASRock, as you can see, Write performing much better at defaults with NB@900 than the Gigabyte does at any NB and DDR3 speed combination ---- On all the AIDA64 compilation results you can see that the board doesn't much effect any of the benchmarks which have to deal with just the CPU, which some are only impacted by CPU speed, and so the higher NB or DDR3 speed doesn't make a difference.
-
It is Hidden, but it still doesn't work after restoring it That's what I mentioned having already done by restoring it in F7 (which PM me if anyone wants that, not that it seems to function). I'll try rolling back to F3 and see if it's able to control the CPU-NB. Fingers crossed, because I don't like having one of the best boards and not having such a key option/setting to change... Going to gather screenshots, I'll post them in a separate reply.
-
ALRIGHT! We're back in action thanks to a thread Stasio linked me to Holding the power when turning it on so that it'll then turn right back off in 4 seconds, then powering it back on, will trigger the second BIOS to engage (After it shut off I left the power button held in for a few more seconds just to make sure) There is not a multiplier, but it's a speed on that board. It is only selectable up to a certain MHz at a specifc memory speed. So at 1333 for example it'd limit to 720Mhz (which the Gigabyte runs at under DDR3-1866!), and at 1866 it runs at ~900MHz I've got screenshots (which are in my review I linked to earlier), but it's almost 2:30AM, so I need to get to sleep. I'll post up a bunch of stuff tomorrow.
-
I let it sit powered on for about an hour and I could hear it (in the background) in a reboot loop ever 5 seconds or so, which coincided with a flicker of the HDD LED. I tried everything to get the system working, but the USB slots don't get any power to do a Recovery Flash via thumb drive, the Optical drive isn't being accessed for a Recovery Flash on a Bootable CD and the shorting of BIOS pins I tried but I have no idea which pin/s to do since it's far different from the board the original trick worked on :\ Yea it was a borked flash, which I know it should auto recover, as my 890GX has done it for me but it isn't doing it on this board Didn't help mine any. That is just for helping memory overclocks, at least from everything I've been reading. Eitherway, the Pro3 was always enabled, and it was the Disabling of the add-in SATA-III chip (ASMedia) that is what caused the system to exhibit crappy memory Write performance. I went through every setting I could, even going so far as to disabling SBGPP, but even that didn't help :\ Anyways, I did manage to get some benchmarks ran to illustrate the difference in performance, so I'll plug that system's HDD into a USB adapter to grab them. If anyone has any thoughts on which pin to short to trick a recovery, and perhaps WHEN to short it, here is the pinout: