Jump to content
AIDA64 Discussion Forum
goaftw

fixed: AIDA64 and freeze screen (MSI B350 Tomahawk + Ryzen 5 1600 + GTX1080) [Win10 1803 timer collision]

Recommended Posts

Hello. After upgrading the Windows to the latest version of 1803, I have a strange problem. When monitoring programs(AIDA64 or HWiNFO64) are launched after a while my screen freezes and I can not do anything, and after it freezes PC and helps only reboot. I wrote to the forum HWiNFO64 and I was helped there.

https://www.hwinfo.com/forum/Thread-Windows-10-1803-freeze-screen

The problem was in "Periodic polling" for calculation CPU Bus Clock. After I turned off "Periodic polling" I did not have a screen freeze for 5 days when using HWiNFO64. But when I start AIDA64 after a while I have a freeze screen and PC. Tell me please what setting I should turn off in AIDA64, so that the program ceased to check periodically CPU Bus Clock.

Thank you.

Share this post


Link to post
Share on other sites
On ‎5‎/‎26‎/‎2018 at 12:11 PM, goaftw said:

Hello. After upgrading the Windows to the latest version of 1803, I have a strange problem. When monitoring programs(AIDA64 or HWiNFO64) are launched after a while my screen freezes and I can not do anything, and after it freezes PC and helps only reboot. I wrote to the forum HWiNFO64 and I was helped there.

https://www.hwinfo.com/forum/Thread-Windows-10-1803-freeze-screen

The problem was in "Periodic polling" for calculation CPU Bus Clock. After I turned off "Periodic polling" I did not have a screen freeze for 5 days when using HWiNFO64. But when I start AIDA64 after a while I have a freeze screen and PC. Tell me please what setting I should turn off in AIDA64, so that the program ceased to check periodically CPU Bus Clock.

Thank you.
 

We've done extensive test runs with Ryzen 1000 and Ryzen 2000 Series processors, and couldn't reproduce the issue :(  Have you tried to use the latest AIDA64 beta build?

https://www.aida64.com/downloads/latesta64xebeta

Also, do you still have the MSI B350 Tomahawk motherboard and AMD Ryzen 5 1600 CPU?  Do you have any nVIDIA video cards in your system?

Share this post


Link to post
Share on other sites

Thanks for your reply. I'm using AIDA64 Extreme 5.97.4600, but I'll definitely try the latest beta version. Yes, I still have MSI B350 Tomahawk, AMD Ryzen 5 1600  and GeForce GTX 1080 (latest driver 397.93). Since I disabled "Periodic polling" in HWiNFO64 this problem no longer appeared. But the problem does exist. Here are a few topics from the forum HWiNFO64 and all helped turn off the "Periodic polling":

https://www.hwinfo.com/forum/Thread-Solved-system-crash

https://www.hwinfo.com/forum/Thread-Solved-hwinfo64-hanging-freezing-windows-10-1803

Tell me please what setting in AIDA64 periodically checks CPU Bus Clock, as "Periodic polling" in HWiNFO64.

Share this post


Link to post
Share on other sites

I have been having an issue for the last 2 driver releases 397.93+397.64 where Windows is hanging/freezing constantly. 30 seconds after I log into Windows, roughly around the time Aida64 loads,  it will hang for like 5 minutes. Then it will be fine, but it will freeze again and again later for a few minutes each time.

There does not seem to be anything related to the drivers in the event viewer at the time of the hang. 391.35 works perfectly and I keep having to roll back to it. I have done the driver upgrades with DDU, and also without my SLI bridge. Nothing is helping. I have 2x 1080 TI in SLI.

Share this post


Link to post
Share on other sites
On ‎5‎/‎30‎/‎2018 at 9:57 PM, goaftw said:

Thanks for your reply. I'm using AIDA64 Extreme 5.97.4600, but I'll definitely try the latest beta version. Yes, I still have MSI B350 Tomahawk, AMD Ryzen 5 1600  and GeForce GTX 1080 (latest driver 397.93). Since I disabled "Periodic polling" in HWiNFO64 this problem no longer appeared. But the problem does exist. Here are a few topics from the forum HWiNFO64 and all helped turn off the "Periodic polling":

https://www.hwinfo.com/forum/Thread-Solved-system-crash

https://www.hwinfo.com/forum/Thread-Solved-hwinfo64-hanging-freezing-windows-10-1803

Tell me please what setting in AIDA64 periodically checks CPU Bus Clock, as "Periodic polling" in HWiNFO64.

We believe we've found the root cause of the issues concerning Windows 10 April 2018 Update (Version 1803 / Build 17134) based systems.  The timer that AIDA64 uses for BCLK measurement is also used by a new Win10 component.  Most likely that component is used for GPU profiling.  And when AIDA64 and Win10 both use the timer for their own purposes in the same time, the system could become unstable.  We've had to disable polling for BCLK, so from now on AIDA64 will only measure BCLK once, and then use the last value until AIDA64 gets restarted.  Here's the new AIDA64 beta build that includes the workaround:

https://www.aida64.com/downloads/latesta64xebeta

  • Thanks 1

Share this post


Link to post
Share on other sites
On ‎6‎/‎22‎/‎2018 at 12:57 AM, pbcopter said:

Thank you Fiery.  This work-around has eliminated the freezing for me in my system.

Thank you for your feedback!

Share this post


Link to post
Share on other sites

Testing 4652 under 17134, none of the clocks under Overclock update, everything under CPU Speed is now a static number

 

I'm creating a feedback so Microsoft can follow up and implement a safe mutex for accessing the timer, Microsoft shouldn't be adding unsafe 'features' that cripple existing utilities.

https://aka.ms/AA1ovm3

Share this post


Link to post
Share on other sites
On ‎6‎/‎26‎/‎2018 at 5:34 PM, kaotik said:

Working here too. Wanted to give it a few days before posting. No more freezing in windows 10 .. Great job :)

Thank you ;) 

Share this post


Link to post
Share on other sites
On ‎6‎/‎26‎/‎2018 at 9:01 PM, Squall Leonhart said:

Testing 4652 under 17134, none of the clocks under Overclock update, everything under CPU Speed is now a static number

 

I'm creating a feedback so Microsoft can follow up and implement a safe mutex for accessing the timer, Microsoft shouldn't be adding unsafe 'features' that cripple existing utilities.

https://aka.ms/AA1ovm3

Clocks: It's normal, since the BCLK is now measured only once, to avoid collisions with the Win10 RS4 kernel.

Feedback: Thank you.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...