Jump to content

AIDA64 SensorPanel freezes the machine (5x GTX1070) [Win10 1803 timer collision]


Recommended Posts

Hi,

Nicehash2 freezes when aida64 sensor panel is running.

It occurs within 5 min when using google chrome together with nicehashv2 using equihash for the GPU and cryptonightv7 for the CPU

, using Nvidia drivers 391.35.

When using nvidia drivers 397.64, this is even worst, there are BSOD generated.

Using win10 home 64 bits, latest aida64 5.97.4633 beta

5 GTX1070 and 1950X CPU.

 

My sensor panel config is attached.

Sensor panel Refresh speed set to 2 seconds.

 

aida64_xixou_config.png

2018-05-20.sensorpanel

Link to post
Share on other sites

I see 4 low level settings under aida64 stability settings preferences:

MSR

PCI

SMBUS

SENSOR

They are all ticked active.

For my sensor panel, the PCI and SMBus are not relevant, so I disabled them(unticked).

So far I was not experiencing the freeze anymore using combination of nicehash v2 and google chrome using Nvidia drivers 391.35.

Could you try at your side sblantipodi and Forceflow ?

 

Link to post
Share on other sites
20 hours ago, xixou said:

Someone on nvidia forum stated that nicehash uses low level access to the GPU.

 

https://forums.geforce.com/default/topic/1052670/geforce-drivers/official-397-64-game-ready-whql-display-driver-feedback-thread-released-5-9-18-/27/

 

Can the low level access of aida64 be changed into an indirect level access?

not nicehash itself, the claymore binary and a few others have nvapi interaction to monitor card thermals and disable p2 cuda.

Link to post
Share on other sites

Do you know how to disable nicehash v2 low level accesses? I twitted nicehash but got no answer.

BTW, on aida64 restart, my gpu sensors were gone, so I had to also select PCI low level access to make it work,

so only the low level SMB is unticked at the moment.

I will try and see if it is still stable

 

Link to post
Share on other sites
Quote

HeavyHemi wrote:

On Wed 5/23/2018 10:54:52 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: aida64.sys (0x0000000000000000)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aida64.sys .
Google query: aida64.sys KMODE_EXCEPTION_NOT_HANDLED

 

A couple of hours of leaving AIDA64 open which was entirely accidental.

 

 

https://forums.evga.com/FindPost/2823774

Link to post
Share on other sites

I'm sorry for the late reply.  We've already got a few topics about the same bug of the recent ForceWare drivers.  The issue is not related to AIDA64 at all -- which can be considered a problem since we cannot fix it in our end.  Downgrading ForceWare to 388.31 solved the issue:

 

 

Link to post
Share on other sites
On ‎6‎/‎2‎/‎2018 at 8:33 AM, xixou said:

Can you help Nvidia to reproduce it such that they fix the issue at their end?

Downgrading to such old driver is not an option as programs like nicehash2 and miners don't support it anymore.

Since the issue affects any software that uses NVAPI (nVIDIA's own API), it should be pretty easy to reproduce it in nVIDIA's own labs.  We can however be of assistance if asked.  We're always open to work with hardware manufacturers, but nVIDIA is not famous for being open to such cooperations I'm afraid.

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.

 

 
Link to post
Share on other sites
On 6/11/2018 at 1:24 PM, p1r473 said:

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.

Totally different problem.

Link to post
Share on other sites
On 6/11/2018 at 5:24 AM, p1r473 said:

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.

Yes, I get the same.
When BSOD comes, this is when it freezes longer.
No issue with driver 391.35

 

 

Link to post
Share on other sites

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

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...