cbjaust

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.

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?

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.

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.

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.

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. cbjaust_GPUPI_for CPU_100M_12m-49.578s.result

Yeah true, GPU-z identifies R9 390X as Hawaii though. I consider them to be Hawaii. that's what I said, didn't I? ?

Of Course, why would they not? R9 280X is Tahiti as well.

thanks Strunkenbold for your tireless efforts over the years. You've been nothing but fair and it's a shame some in the community can't see past their self importance and recognise this. Here's hoping you have a change of heart and the whingers learn to take it on the chin for the good of the community, the hwbot database and overclocking in general. hwbot is a great project let's hope it continues.

SanDiego and Denmark too.

Well that rules out socket 754 then.

yes, but could you save the data file / submit without gpupi crashing?

yep, I wonder why the others are using 3.1.1

I am using Windows 7 x86... I wanted to run it in Server 2003 R2 x86 (Windows XP kernal) but I couldn't find an OpenCL that would install...

This platform - s478 P4 Prescott-1024M is a stage in Team Cup this year, (this result) seems OK but I have no idea what they're doing different, it looks like Windows 7... I can get a result fine just can't get the result file or upload directly, in both cases GPUPI crashes.

It still crashes when trying to save the result to a file, even with hwinfo disabled...