Hyperless Havoc by TAGG, Ground and ShaggySVK

[Leeghoofd]

 

Welcome to Hyperless Havoc by TAGG, ShaggySVK and Ground

 

Hardware: 

• any CPU that fits into 1366
• any RAM except Elpida Hyper (TAGG and Ground will be checking plausibility - Mem Kit pics required) DIY sticks are allowed (as long as not Elpida Hyper)
• no populated second CPU socket allowed

 

Rules:

• Standard Hwbot verification rules apply + SPD Tab
• Legacy CPU-Z allowed
• no cooling restrictions
• Verification screenshots must contain official Hyperless Havoc wallpaper
• All scores must include a picture of the benching rig as well as a picture of the memory sticks used with labels or IC text visible if OEM / DIY sticks
• judges may request video proof
• In case of a tie SuperPi 32M stage is the tiebreaker

 

BenchMate Submissions only:  Max Core Frequency AND Max Effective clock must have a check mark
 

 

The following benchers are exempt from prices: Ground, ShaggySVK, TAGG, Tapakah

 

Benchmarks:

• Stage 1: 65P Superpi 32M with Benchmate 4505MHz/4505MHz
• Stage 2: 65P Pyprime 2B with Benchmate 4505MHz/4505MHz
• Stage 3: 65P Y-cruncher 1B with Benchmate 4505MHz/4505MHz
• Stage 4: 15P Mem Clock x58a-oc banned (Bonus Round)

 

[skulstation]

A question about 

• no populated second CPU socket allowed

 

The EVGA sr-2 have jumpers to disable the cpu's.

Ar we alowed to populatie the second cpu when the other socket is disabled by switching thé Jumper around?

Edited March 12 by skulstation

[ground]

8 minutes ago, skulstation said:

A question about 

• no populated second CPU socket allowed

 

The EVGA sr-2 have jumpers to disable the cpu's.

Ar we alowed to populatie the second cpu when the other socket is disabled by switching thé Jumper around?

The rule was added specifically with SR-2 in mind to avoid dual socket scores for ycruncher. Given it would be run as single socket in that case, I don't see it breaking the spirit of the rule, so sure.

[ground]

If anyone has issues with CPUz 2.15, you are not alone. Without any changes to the OS, its not showing changes to BCLK. Given that clocking up after boot is relevant for memory frequency, the followinng fixes have been found: 

for modern OS: bcdedit /set useplatformclock true
for legacy OS (win XP): edit C:\boot.ini and add "/usepmtimer"

Edited April 2 by ground

[Leeghoofd]

New updated rule from the organizers

 

BenchMate Submissions only:  Max Core Frequency AND Max Effective clock must have a check mark