What's new
  • Please do not post any links until you have 3 posts as they will automatically be rejected to prevent SPAM. Many words are also blocked due to being used in SPAM Messages. Thanks!

Is HPET at fault for image freeze or what else could it be?

vyxumemyc

Member
Joined
Mar 29, 2023
Messages
22
Hi there! Two months ago I bought a second hand kit consisting of:

- ASUS PRIME H310M-C
- i5 9400f + stock cooler
- 2 x 16 GB DDR4 Corsair

Previously to buying the kit I tested out remotely the RAM with memtest86 for 8 hours. After that I used Cinebench 23 for testing out the CPU for 30 minutes of stability testing for single core. The result I got was around the same value cpu-money shown for i5 9400 f (Cinebench 23). The temperature was normal. Hence, both tests ran succesfully.

This are the specs for my PC. The SSD and the PSU (Corsair RM550X Gold, 550W) were new. I borrowed the GPU from a friend - XFX R9 270x.

Since I bought the kit, while using a fresh Windows 10 Pro 64, BIOS mode, every 2-3 weeks some programs would slow down to the point the image would freeze up completely, without any BSOD screen. In some cases the image freeze would come together with a deafening buzzing of the speakers at maximum volume. The only way to recover was either power off or restart. After system power up there was no crash dump to be found.

XFX R9 270x went through a PSU frying while at that friend, but it seems the GPU wasn't affected by it, as it ran without any problems on a completely different system of that friend.

I've noticed that the latest CPU-Z (2.0.51 x64) version came with a lag when the window is dragged around. This has been noticed with 3 fresh (trial versions) installs of Windows 10 Pro 64, BIOS mode, Windows 10 Enterprise LTSC 64, UEFI mode and Windows 11 Pro 64, UEFI mode. After some searching related to this lag in CPU-Z I came across people saying that HPET could be responsible for this lag. At this point I was thinking HPET was also responsible for the image freeze I kept getting. Hence I followed up some tutorials for disabling HPET completely within Windows, which I managed to. But what I couldn't disable was HPET within the motherboard, since it doesn't have this feature.

Prior to disabling HPET within Windows I ran a couple more tests, namely:

memtest86:
- testing out RAM for 36 hours


No problems regarding RAM.


Cinebench 23:
- test throttling single core: 10 minutes
- test throttling multi core: 10 minutes
- test stability single core: 30 minutes
- test stability multi core: 30 minutes

The result I got was around the same value cpu-money shown for i5 9400 f (Cinebench 23). The temperature was normal. Hence, both tests ran succesfully.

OCCT:
- testing out VRAM for 30 minutes, for 95% of the memory

No problems regarding VRAM.

Conclusion: the image would freeze up, even if all tests were successful.

So far I haven't managed to test out if HPET is responsible for this. Before I'd go for that, I wanted to get your opinion on this, as it would be a lengthy process.

The 3 Windows I used were on up to date regrading updates, including optional updates. Drivers were installed from the official sites. The mobo and GPU are on the latest BIOS. SSDs are on the latest firmware. I forgot to mention, I used a second new SSD for testing, as well.

I have also used an Nvidia GeForce 9500 GT (this GPU has never been in any system where the PSU fried up, so it should've been working well) for testing out W10 Pro 64, BIOS mode. Unfortunately, last night after disabling hardware acceleration in Chrome and getting into fullscreen on Twitch, the image froze up yet again.

A friend has a completely new system with W10 64 Pro UEFI, Segotep 500W power supply, which uses an i5 9400f, with Nvidia GeForce GTX 1650 Super, and with a somewhat similar mobo, also from ASUS (Asus PRIME H310M-R R2.0), for which CPU-Z also lags, but never had any crashes.


In my mind, so far, it seems the mobo is at fault.


Where do you think image freezing could come from? Is it HPET? What else could it be?
Or which components could you exclude as being responsible for this problem?
Or what would you advise me to do next?




Thank you!

PS:

I noticed that if the XFX R9 270x was not positioned at a 90 degrees angle on the motherboard, the monitor wouldn't receive any signal. On the other hand, with that friend that I borrowed the XFX from, the GPU seemed to work even if the angle wasn't quite 90 degrees on his mobo.
 

Sagath

Moderator
Staff member
Folding Team
Joined
Feb 7, 2009
Messages
6,707
Location
Edmonton, AB
I feel like this is an incorrect driver, not hardware.

I would double check your motherboard & chipset drivers when reinstalling windows before exploring hardware issues.
 

vyxumemyc

Member
Joined
Mar 29, 2023
Messages
22
Mentioning about it, I have currently installed the drivers for W10 64 for ASUS PRIME H310M-C, but if you could please take a look at the images on the Overview tab for these two motherboards, on the Asus site:
- ASUS PRIME H310M-C
- ASUS PRIME H310M-C/CSM
, you could notice that both mobos have "ASUS PRIME H310M-C" printed on their PCB, which is really confusing.

Both CPU-Z and HWiNFO64 report the motherboard as being ASUS PRIME H310M-C, but what if ASUS PRIME H310M-C/CSM shows up as ASUS PRIME H310M-C?

Having that confusing I went ahead and used these commands in cmd (admin):

wmic baseboard get Manufacturer, Model, Name, PartNumber, serialnumber

, which returned:

Manufacturer Model Name PartNumber SerialNumber
ASUSTeK COMPUTER INC. Base Board 180425572600382


I also used this command in Powershell(admin):

Get-WmiObject win32_baseboard | Format-List Product,Manufacturer,SerialNumber,Version

, returning:

Product : PRIME H310M-C
Manufacturer : ASUSTeK COMPUTER INC.
SerialNumber : 180425572600382
Version : Rev X.0x


Furthermore, I have installed the ASUS software for installing drivers and there it has shown as being PRIME H310-C, it has also provided me with an S/N. Using that S/N I contacted ASUS tech support on Facebook to double check, and indeed it is a PRIME H310-C mobo.

The S/N I got in the ASUS software was J4M0CS216962.

I'm still wondering what if the Asus software reports ASUS PRIME H310M-C/CSM as being ASUS PRIME H310M-C, and what if the Asus tech support sees it the same as the software does?

What should I do in this case, should I go ahead and try to find people who have a ASUS PRIME H310M-C/CSM mobo and ask them if they could tell me what CPU-Z shows up for them?
In case I can't find anyone, would you advise in trying to install the drivers for ASUS PRIME H310M-C/CSM and see how that pans out, as today I learned that if you install the wrong drivers, the hardware won't fail?

-------------------------------
Edit:
I skipped on reading the other comments by mistake, and I've noticed there are chances for the hardware to fail as a result of installing the wrong drivers. Would this also apply to motherboards?
-------------------------------

Or what else would you advise?

Thank you!
 
Last edited:

vyxumemyc

Member
Joined
Mar 29, 2023
Messages
22
I think I might be right about ASUS PRIME H310M-C/CSM showing up as ASUS PRIME H310M-C, because if you could take a look at:


, where I looked for the term "PRIME H310M", there's no result having "ASUS PRIME H310M-C/CSM", which is really strange. I made sure to expand all results first.

I did a search on google using "PRIME H310M" restricted to "valid.x86.fr". Even if I got 226 results, none of them contained "CSM". I used Infinite Scroll for Google™ Chrome extension to get all pages as one page, and used "CSM" as the term for searching thought the page.
 

Latest posts

Top