cbjaust
-
Posts
646 -
Joined
-
Last visited
-
Days Won
6
Content Type
Profiles
Forums
Events
Blogs
Posts posted by cbjaust
-
-
Thanks. Re-benched.
-
Cheers. It was a lucky strike from a scumtree haul (Lian-Li PC-71, Geil DDR 1GB, San Diego 4000+, more DDR and a couple of 775 office boxes for AUD$30!)
-
your dual core version http://hwbot.org/submission/3953898_optytrooper_cinebench___r11.5_phenom_ii_x2_b59_2.78_points/ has the same problem.
-
6 hours ago, Tech Tweaker said:
I don't actually see that anywhere in the benchmark rules (they say it's optional), and couldn't find it in the official competition rules. *shoulder shrug*
it's in the thread here
-
the dual core optimiser is a driver for windows, and nothing to do with the chipset.
-
would the AMD Dual Core Optimizer be required? AMD utilities page
-
apparently Opty has a habit of reporting subs at the drop of a hat and yet posts up this debacle. ?
-
Have an even number of stages between AMD/Intel and AMD/nVidia
-
1
-
-
1 minute ago, yosarianilives said:
Just disable hwinfo, it won't fill in anything.
GPUPI 3.1.1 does not have the option. Next time I run it I'll delete the hwinfo.dll, I think I remember doing that before, thanks for reminding me...
-
It's this one: http://hwbot.org/submission/3939629_cbjaust_gpupi_for_cpu___100m_pentium_4_3.2ghz_(prescott)_12min_37sec_485ms and the problem is GPUPI 3.1.1 picks up my mainboard as something it is not. (DH100 or something...) It should be a LanParty Pro 875B and I think that once the result goes in the chipset gets hard coded or something and so amount of adding the correct name gets the dropdown box to show up with the correct selection. Anyway thanks in advance.
-
as per title I'm getting "not able to connect" errors for any page on hwbot.org...
-
Looks like CPUz is spazzing out and reporting the bus speed as double the real speed of what I'm guessing is 128MHz. The changelog on the CPUz page doesn't go back to v1.59 but it's obvious CPUz fixed the bug sometime post v1.59.
Edit: staus on CPUID Validator is Rejected anyway so technically the entry should be removed anyway.
-
1
-
-
it's the first line in the detail thread for the DDR2 stage: https://community.hwbot.org/topic/185165-the-official-team-cup-2018-ddr2-stage-thread/
-
Surely flashing a BIOS on a semi-modern FM1 board is not beyond the majority of the participants of Team Cup 2018?
-
2
-
-
11 minutes ago, yosarianilives said:
Don't forget the Athlon x4's 640 (zosma) and 645t. although those are already listed as zosma
Yeah, I was only referring to the Phenom II x4 CPUs and I saw the Athlon II E0 CPUs were already listed as Zosma (or @Antinomy already fixed them if necessary) ?
-
As per title, Phenom II x4 650T as per this page http://hwbot.org/hardware/processor/phenom_ii_x4_650t/ is mis-categorised as a Thuban core where it should be Zosma. All the chip harvested Thuban E0 stepping quad cores were given the Zosma moniker even though they share the same CPUID as Thuban and as such are reported as Thuban by CPUz.
-
1
-
-
Of the four Phenom II CPUs in the hwbot database that are chip harvested Thuban cores: x4 650T, x4 840T, x4 960T Black Edition and x4 970 Black Edition, only two are categorised as Zosma (960T and 970 BE) the other two are categorised as Thuban. Obviously this leads to ambiguity, either all the above mentioned CPUs are classed as Zosma or they are classed as Thuban but not both. Now I know our erstwhile database caretaker has recently resigned which leads to a bit of a dilemma.
-
1
-
-
38 minutes ago, Strunkenbold said:
Yes I remember there was something similar with those unlocked Haswell mobile CPUs. You have to prevent that Windows loads the intel firmware on boot.
I dont think that you need to implement the fix in GPUPI. All needed is the patch exe from the passmark guys.
To quote their readme:
This is reminds me of The Stilts Bulldozer Conditioner...
All we need is someone to test if it really works.
I think I have somewhere a board and a CPU both from scrap and not known to work maybe its time to test this bundle now.The patch when implemented immediately sets the performance back to "normal"
Rerunning the patch and selecting no to the workaround gets back the mad performance. 
-
1
-
-
6 hours ago, unityofsaints said:
Thanks for all the time you spent investigating this! ? It would be funny to submit a bug report with AMD just to see their reaction.
Are you using Win 7 64-bit SP1, AMD SDK 2.91 and GPUpi 3.2 non-legacy with HPET off?
Not sure if it's HPET or some Windows Update making the performance "Normal" but a fresh 2008 R2 install and the F2 BIOS on the GA-A75-D3H did the trick. I was using a pretty much up to date Windows 7 x64 install before and had HPET on. So yeah. Interesting that you stumbled on to this mad performance and great work by _mat_ verifying his softwares.
-
Well I probably need some kind of guide for newbies because with older CPU's that should be supported by OpenCL and AMD's APP I can never get them recognised, not to mention the difficulty locating AMD's earlier SDK versions. Most of the time I'm just glad GPUPI recognises the CPU and runs. You've got a neat benchmark but it's annoyingly frustrating to just get working.
-
Yeah, I was always in Windows 7
-
There must be some other voodoo at play because I saw zero difference with pre 1.1.0.3 AGESA BIOS on GA-A75M-UD2H and GA-A75-D3H. ?
-
I tried my socket 478 system again for Team Cup DDR Stage 3 and this time I tried 3.1.1 but it has the same issues with crashing on the HWINFO.dll module when starting the benchmark. So I deleted HWINFO.dll and the bench ran fine but at the end it had the same crash as 3.2 on module "StackHash_0a9e".
I also tried 3.2 again but trying to save still crashed with the "StackHash_0a9e" module.
Help!
Cheers
Edit: 2.3.4 works just fine, result file attached.
-
3 hours ago, yosarianilives said:
In the database they are listed as Grenada even though they're Hawaii. As there would need to be hw purchased I'd like to verify before hand.
Yeah true, GPU-z identifies R9 390X as Hawaii though. I consider them to be Hawaii.
2 hours ago, ozzie said:280 is tahiti, not hawaii, 285 is tonga, 290 is hawaii, ,
that's what I said, didn't I? ?
avalanche - Core i7 8700K @ 5470MHz - 3043 marks XTU
in Result Discussions
Posted