Anyone else having issues when HPET is enable?, it causes my system to turn off after a few blackscreens even when i am doing nothing, just sitting in desk moving files. GPUPI and HWBOT x265 benchmark uses it so they ask me to enable it to be able to run the benchmarks. This seems to be new (at least on GPUPI) since i never had this problem before with GPUPI.

I'm using Windows 10 x64.

Any advice?

What's your system hardware?

Hi,

I jump in regarding gpupi 3.3 and hpet activation in Win7 Pro 64 bits.

Gpupi 3.3 detects a potential drift for my system and asks to activate HPET. I say Yes and reboot, but the HPET is inactive...
hence remains a 3.58 Mhz timer written in x265, and RTC 1 ms in gpupi

 

MB is MSI K8N Neo4 Platinum (also called Neo-F or MS 7125), nforce 4 chipset

Cpu is Amd Dual Core Opteron 175

 

On the same setup, I had no issues with single cores Opteron 144 and 155, and no messages of a potential drift.
What is happening...?

I am using gpupi 3.3.2 legacy.

 

cheers

 

Edited October 4, 20186 yr by bolc

I have removed the opteron 175 and put a 3700+ single core, and no pb, rtc 1ms, no display of possible drift
hpet is not active but it allows benchmarking.

 

58 minutes ago, bolc said:

I have removed the opteron 175 and put a 3700+ single core, and no pb, rtc 1ms, no display of possible drift
hpet is not active but it allows benchmarking.

 

Did you make sure that HPET is also enabled in BIOS? 

I'm not really sure... but isn't s939 too old to support HPET? AM2+ boards definitely support it, never tried it on older platforms.

would the AMD Dual Core Optimizer be required? AMD utilities page

On 10/4/2018 at 10:42 PM, yosarianilives said:

Did you make sure that HPET is also enabled in BIOS? 

there is no such option in the bios

On 10/5/2018 at 5:05 AM, cbjaust said:

would the AMD Dual Core Optimizer be required? AMD utilities page

to be tried

i used clockgen and memset but no amd software since AOD was not supporting nfroce4.

I am unsure that AMD DCO will support nfroce4 chipset though...

the dual core optimiser is a driver for windows, and nothing to do with the chipset.

Pending the OS used, it may or may not be needed. I believe the optimizer was included in XP SP2 on up.

thanks but no imprivement with dco.

and on a am2 / 790x chipset, gpupi 3.1 or 3.3.2 legacy will simply not start (appcrash)...
existing scores were made on 2.x only. no gpupi then
and yep. 2.3.4 runs fine. ok so no more gpupi on am2 (but on 939 is fine... perhaps I should put hpet off and see if gpupi 3.x starts on am2...)

Edited October 6, 20186 yr by bolc

GPUPI 3.x is a hit or miss it seems. Today I was running it on C2D and always appcrash when saving data file. On the other hand, A64 AM2 was running just fine http://hwbot.org/submission/3927537_havli_gpupi_for_cpu___100m_athlon_64_le_1640_(orleans)_8min_27sec_791ms

the appcrash on saving, I had this too ibeleive on 3.1.x or 3.2 but not on 3.1

hence i stuck with 3.1 for the 3.x and with 3.3.2 legacy for the 3.3.x...
u tried 3.1 i guess?

I
still have to try this : put hpet off in the bios and the os and see if gpupi 3. xcan start on am2...

Edited October 10, 20186 yr by bolc

Actualy I didn't try versions other than 3.2 and 3.3.2. Those behaved the same - appcrash.

Thanks fro the tip, I'll try the 3.1 next time.

Use Windows 7 for old hardware, it will allow RTC because there is no drift possible there. GPUPI follows the rules of HWBOT there.

As for the hardware detection bug on old hardware, I will look into it.