Submission details

avatar

- Elite League

5min 9sec 374ms with AMD K6-2 450MHz at 720MHz

Ranking position

n/a

Global rank:

2nd

K6-2 450MHz rank:

Cup Silver 2nd out of 28

Points earned for overclocker league

Points earned for team league

Media gallery

Screenshots
SuperPi - 1M screenshot
screenshot
screenshot
screenshot

Hardware details

CPU details

  • Model: AMD K6-2 450MHz 'Chomper'
  • Cooling: Liquid Nitrogen
  • Speed: 720MHz (+60.00%)
  • buy on amazon

Memory details

  • Product: PC-150
  • Type: 256MB SDR SDRAM
  • Speed: @ 120MHz
  • Timings: 2-2-2-5

VGA details

  • Speed: MHz / MHz (Stock)

Mainboard details

Disk details

Power details

Recent Comments

NoMS commented on his own score:

K6-2 450 @ 720 2.4V - No CB/CBB - Thanks iandiniz48 for the pot - Recapped motherboard VRM - Using old CPU-Z 1.47 because newer have issues with clock detection even after ACPI=0.

Ukraine moi_kot_lybit_moloko says:

you can use cpu-z vintage edition

NoMS says:

48 minutes ago, moi_kot_lybit_moloko said:

you can use cpu-z vintage edition

It does not work here. 😢
V
ideo attached.

Italy GRIFF says:

Great work.

Russian Federation Antinomy says:

What clock detection issues, clock jumping? Which version where you using? We've fixed this with Franck Delattre about 2-3 years ago specifically for P5A. Versions 1.9x should be fine.

NoMS says:

2 hours ago, Antinomy said:

What clock detection issues, clock jumping? Which version where you using? We've fixed this with Franck Delattre about 2-3 years ago specifically for P5A. Versions 1.9x should be fine.

Yes, clock jumping. 1.03.0 Vintage Edition is broken as you can see in the video i posted on this thread, tbh, even the old 1.47 I used sometimes got issues with this, it's only a bit more manageable than newer versions. 🥺

If I remember well from my previous testing, same issue as 1.03.0 on CPU-Z 1.98. Any ideas to fix that?

Russian Federation Antinomy says:

5 minutes ago, NoMS said:

same issue as 1.03.0 on CPU-Z 1.98

Should be fixed since 1.86. I've reported it on 1.85. Try versions from 1.86 to current and let me know. If you don't have them, I can send you.

NoMS says:

45 minutes ago, Antinomy said:

Should be fixed since 1.86. I've reported it on 1.85. Try versions from 1.86 to current and let me know. If you don't have them, I can send you.

Downloaded all of them since 1.86 from here, is there any other version you want me to try?
1.86 is broken here and all the other versions looks the same, attached is one video showing the issue with 1.86 and a report.txt from 1.98 which you can also spot the issue.

Here is a validation with 1.98, apart from the fact that the image looks correct, the 5.6MHz on memory clock is very wrong.

Also I don't know if it helps but my board is a P5A rev 1.03.

TOCP-2B025FEAE8.txt

Russian Federation Antinomy says:

O.K. Looks like I got the test build where this was fixed, I checked it but Franck didn't apply it to release versions. I'll remind him of this issue.
If your P5A rev. 1.03 with Phaselink PLL? Or is it the newer ICS version?

NoMS says:

Just now, Antinomy said:

O.K. Looks like I got the test build where this was fixed, I checked it but Franck didn't apply it to release versions. I'll remind him of this issue.
If your P5A rev. 1.03 with Phaselink PLL? Or is it the newer ICS version?

It's Phaselink PLL52C66-28

Russian Federation Antinomy says:

Just now, NoMS said:

Phaselink PLL52C66-28

Yeah, that's the one that gives most terrible fluctuations. I've reminded Franck of this issue.

Ukraine moi_kot_lybit_moloko says:

6 hours ago, NoMS said:

It's Phaselink PLL52C66-28

oooh, i have p5a-b with phaselink - its bugged clocker. when i put jumpers on 140 fsb - mobo didnt start, and after reboot i get 128(!!)mhz. i see here validation on p5a 128 mhz, may be @max1024

Ukraine moi_kot_lybit_moloko says:

ooh, sorry Max, its not you😁
its @Gumanoid, there is link on valid with bugged phaselink

Russian Federation Antinomy says:

3 hours ago, moi_kot_lybit_moloko said:

link on valid with bugged phaselink

It's not mostly the PLL that is bugged, it's the system timer. But on 1.03 the fluctuations were wild like down to 4-5MHz FSB. This began after a certain version of CPU-Z, I think Gumanoid was using one that wasn't yet affected. Got broken later.

Please log in or register to comment.