Jump to content

BSOD or hard hang with dump 0x116 or 0xEA when AIDA64 logging or BurnIn stress with AIDA64 logging or after BunrIn 8hrs stress pass then idle with AIDA64 with high F/R


Recommended Posts

 

Hello Sir,

 

Would you please help to confirm if any AIDA64 logging compatibility issue with AMD Renoir platform (UMA)?

Is it possible to solve by AIDA64?

Thank you.

 

We found high F/R BSOD or hard hang with 0xEA or 0x116 when running Burnin with AIDA64 logging or idle for a period of time after Burnin 8hrs pass with AIDA64 logging on AMD Renoir platform. 

After confirmed, only AIDA64 logging for a period of time can reproduce, no need to run other APPs.

And ever found BSOD 0xEA just when AIDA64 was detecting sensor information.

Steps and log files of hang with dump 0x116 are as the attached files for the reference.

Full dump please refer to download link: https://wetransfer.com/downloads/b30b6b2d51919809840bb14f8681e86d20200814161731/ccd94a25b5779c27897a6bdf19d921b720200814161833/3e7b99

 

Other checked:

1. BURNIN+AIDA64 log_update frequency 1s: Fail

2. BURNIN+AIDA64 log_update frequency 10s: Pass

3. Furmark+AIDA64 benchmark: Pass

 

AIDA64: 6.25.5400.0

OS: Win10 20H1

AMD platform: Renoir FP6 UMA

 

AMD's feedback:

Found PCI Configuration Space that BAR5 is empty when BSOD 0x116 occurred. But, GFX driver should not save and restore PCI configure.

Not sure why AIDA64 tool could be save/restore PCI configure?

AIDA64 log steps.7z AIDA64_3.5hrs_hang_0x116_minidump.7z

Link to post
Share on other sites
On 8/14/2020 at 6:26 PM, sea said:

 

Hello Sir,

 

Would you please help to confirm if any AIDA64 logging compatibility issue with AMD Renoir platform (UMA)?

Is it possible to solve by AIDA64?

Thank you.

 

We found high F/R BSOD or hard hang with 0xEA or 0x116 when running Burnin with AIDA64 logging or idle for a period of time after Burnin 8hrs pass with AIDA64 logging on AMD Renoir platform. 

After confirmed, only AIDA64 logging for a period of time can reproduce, no need to run other APPs.

And ever found BSOD 0xEA just when AIDA64 was detecting sensor information.

Steps and log files of hang with dump 0x116 are as the attached files for the reference.

Full dump please refer to download link: https://wetransfer.com/downloads/b30b6b2d51919809840bb14f8681e86d20200814161731/ccd94a25b5779c27897a6bdf19d921b720200814161833/3e7b99

 

Other checked:

1. BURNIN+AIDA64 log_update frequency 1s: Fail

2. BURNIN+AIDA64 log_update frequency 10s: Pass

3. Furmark+AIDA64 benchmark: Pass

 

AIDA64: 6.25.5400.0

OS: Win10 20H1

AMD platform: Renoir FP6 UMA

 

AMD's feedback:

Found PCI Configuration Space that BAR5 is empty when BSOD 0x116 occurred. But, GFX driver should not save and restore PCI configure.

Not sure why AIDA64 tool could be save/restore PCI configure?

It's odd, since AIDA64 doesn't write/alter BAR5, but only reads it.  We're in contact with AMD about this issue, which seems to be due to a collision between AMD video drivers and the part of AIDA64 that detects unified shader count on AMD GCN and RDNA GPUs.  I hope AMD can come up with a solution to this issue that was never a problem before.  They must have changed something in one of the recent video driver updates that made the collision happen.

Link to post
Share on other sites

Hello Sir,

Many thanks for the reply. I will try to inform AMD your suggestion, but not sure if they will modify GFX driver. Until now, they think it is tool issue. Is it possible that you could share your discussion mail with AMD for the reference? Or other suggestion? Thank you.

Link to post
Share on other sites
  • 1 month later...
  • 2 weeks later...
  • 3 weeks later...
  • 2 weeks later...

Hello Fiery,

Sorry correct finial result after more experiments. Do you have any idea about below items? Thank you.

Result: Fail if select any one of below items

Fail items:
1. GPU Clock
2. GPU Used Dedicated Memory
3. GPU Used Dynamic Memory
4. GPU Power Control

Link to post
Share on other sites
  • 3 weeks later...
  • 4 weeks later...
On 12/21/2020 at 2:13 AM, sea said:

Hello Fiery,

Would you please advise if you still check these fail items?

Thank you.

Our conclusion is that it's due to a video driver bug.  We're waiting for the new generation (Adrenalin 2021) AMD video drivers and expect the issue to be resolved in there.

Link to post
Share on other sites
On 12/21/2020 at 2:13 AM, sea said:

Hello Fiery,

Would you please advise if you still check these fail items?

Thank you.

We've implemented further tweakings about AMD GPUs in the latest beta version of AIDA64 Extreme available at:

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

After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Let me know if it helps.

Link to post
Share on other sites
  • 1 month later...
On 1/18/2021 at 11:55 PM, Fiery said:

We've implemented further tweakings about AMD GPUs in the latest beta version of AIDA64 Extreme available at:

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

After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Let me know if it helps.

Hello Fiery,

Currently, no enough units to check. I will test the beta once units are ready.

Thank you.

Link to post
Share on other sites
On 2/23/2021 at 9:37 PM, sea said:

Hello Fiery,

Currently, no enough units to check. I will test the beta once units are ready.

Thank you.

The beta version still hang with F/R 5/7 units. 

Link to post
Share on other sites
On 1/18/2021 at 11:55 PM, Fiery said:

We've implemented further tweakings about AMD GPUs in the latest beta version of AIDA64 Extreme available at:

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

After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Let me know if it helps.

Hello Fiery,

The beta version still hang with F/R 5/7 units. 

 
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...
  • Similar Content

    • By Miku
      My phone is at 144Hz, but it shows 120Hz instead

      report-2020-11-05-21-18-22.txt
    • By Razvan
      I am encountering this very strange bug. If I use Aida64 Cache&Memory Benchmark in Windows 10 I get a specific Ram benchmark result, let's say 48100 MB/s read / 53600 MB/s write /  47700 MB/s copy and 52 ns latency. However, if I am booting from an USB live Windows 10 CD (WinPE), I am getting drastically better results, such as 55000 MB/s read / 61300 MB/s write / 55000 MB/s copy / 45 ns latency.
      I am not changing any bios / RAM XMP / Ram memory timings settings between reboots, only booting from either main Win 10 installation or WinPE 10 live usb.  I am using the same Aida64 version in both cases.
      I am scratching my head, what can explain the huge difference between the results? In both cases, cpu usage is idle and no other background programs are running when doing the tests.
    • By Soul--Reaver
      System:
      Asus Sabertooth Z77
      Intel 3770K
      Nvidia Geforce 1070
      Logitech Keyboard G510S
       
      Aida64 version: 6.25.5400
       
      I'm using the LCD in my keyboard and Aida64 to monitor certain system values.
      I've noticed that the CPU util percentages are not correct on the LCD display.
      The most obvious is that when the system is completely idle (CPU util.png), The LCD will never show a lower number then 28% for CPU7 Utilization (LCD CPU util.png) on the LCD.
      The other numbers are also weird or incorrect but that is more of a feeling i have. The other CPU utils feel weird because i never see 1% or 2%. It's always 10%, 11%, 12%, 14%, 22%, 28% etc. but never below 10% except 0%
      As shown in "CPU util.png" Aida64 is capable of getting the correct percentages, it just does not show them on the LCD display in my keyboard
      Kind regards
      Swen Kruiper


    • By Moarty
      The CPU Temperature on the AsRock B550M Steel Series is incorrectly reported.
      Ryzen Master reports 86C while AIDA64 reports 46C
      MSI AfterBurner (RTSS) reports it correctly.
      I know its a brand new chipset, I'm not worried about it, just wanted you to know

    • By Erm Ermi
      Hi all, I created a new pc with GEFORCE GTX 1650 SUPER VENTUS XS OC graphics card but when I start aida64 in the gpu section it tells me that it is a GEFORCE GTX 1650 SUPER AERO ITX OC. I just wanted to report this little bug hoping it will be fixed in the future. thanks and good job.
×
×
  • Create New...