Fiery

Thank you for your feedback. We will fix the reported issue in the next AIDA64 beta update.

It definitely shouldn't crash on a stable system. Can you check if it passes if you disable Turbo Boost?

Please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

@LeLoT3 Can you please try to disable Low-level SMBus operations in AIDA64 / main / File / Preferences / Stability, restart AIDA64, and check if it makes a difference?

Thank you! Can you please post a screenshot of the PC Monitoring page of the BIOS Setup (UEFI Setup) as well? That would help us to implement advanced sensor support for your motherboard and provide you with a lot more sensor readings than now.

I'm sorry for the late reply. Currently we're investigating the issue by working together with AMD. A temporary workaround that seems to work in most cases like yours is to disable Memory Integrity in Windows Settings / Core isolation.

Does the BSOD happen if you disable Memory Integrity in Windows Settings / Core isolation?

Make sure to enable Embedded Controller (EC) bank switching in AIDA64 / main menu / File / Preferences / Stability.

Thank you, we will fix the issue in the next AIDA64 beta update.

As I've stated, the new, adjusted price still doesn't include the inflation rate spikes of late. They are almost the same price as it were with a very steady 2% annual inflation rate, without spikes or drama. And even then our existing customers have already saved a lot by us not raising prices every year by 2%, but instead doing a single adjustment at the end of the mentioned 17 years period. Licensing differences are explained at https://www.aida64.com/licensing As for the basic edition, please note that we're not interested in offering lower-priced products in general. We may or may not lose market that way, but we're adamant that a lower priced product would simply cannibalize the market of the premium (Extreme) variant, and in the end it wouldn't be financially beneficial for us to maintain one more SKU.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

Please avoid posting a single issue in multiple topics. I've replied in your other topic. This topic closed.

Please avoid posting a single issue in multiple topics. I've replied in your other topic. This topic closed.

Yes, you need AIDA64 to be running to have the SensorPanel working.

While I understand your point, your actual system has no memory modules but instead BGA memory chips. Since BGA memory chips lack SPD support, we cannot count them. As for memory bus width in use, it's actually there: Quad Channel LPDDR4 means 4 channels, 32 bits each, so 4x32 = 128 bits of memory bandwidth.

Which voltage rails do you miss?

You're right, it is confusing to many of you guys, so we will revamp it in the next AIDA64 beta update.

Please avoid posting a single issue into multiple topics. I've replied in your other topic. This topic closed.

Can you see your Arc GPU listed on the Display / GPU page of AIDA64? Are you using the latest version of AIDA64 v6.90?

Can you see your Arc GPU listed on the Display / GPU page of AIDA64? Are you using the latest version of AIDA64 v6.90?

First of all, we've kept the same price of $39.95 for 17 looong years (for the Extreme edition). If you calculate with only 2 percent average annual inflation -- not counting the jump in the inflation rate recently -- the base price would already be $58.2 by now. The only issue is that we haven't followed the slow pace of inflation by slowly increasing our prices, but instead offered it for the same (IMHO by now quite low) price. The sharp jump in inflation forced us to alter our prices, but they're still lower than what simply by following inflation would bump them up by now. As for basic edition, no, we're not interested in cutting the features set and make a lower-priced edition for home users. We will do the opposite and offer more features for a higher price actually. The rest is well, it's your take on our prices, and I appreciate your input. But we have a different idea about our pricing scheme. You may also want to study the licensing scheme more thoroughly: the Engineer and Business editions target different type of use. So it makes little sense to compare their prices against each other (apples vs. oranges). Also, please note that you do not have to pay *whatever price* annually. We've designed the licensing scheme so that you only should (may need to) purchase a renewal license when the old version no longer serves your needs. You can skip 3 or 4 years and enjoy AIDA64 as long as it fulfills your needs. You do not need to renew AIDA64 every year if you e.g. don't upgrade to the latest Windows and don't upgrade to the latest hardware. Only those folks who live on the cutting edge of PC hardware+software are the ones that actually find it necessary to keep renewing their licenses regularly.

Please note that it's quite difficult to solve this issue on our side. To let you get a bit of insight into the problem: SensorPanel is a window, and a part of the AIDA64 main process. All windows belonging to the AIDA64 process share the same DPI configuration. So when you move a window (e.g. the SensorPanel) away from the main window, it will still keep (inherit) the same DPI setting that all AIDA64 windows share. So when your main monitor (where you launch AIDA64) has a 150% DPI setting, the SensorPanel will also use that. The SensorPanel will look and act the same on your main display and your secondary display even if the latter has a different DPI setting. It would require a lot of work on our part to make sure all AIDA64 windows (incl. the SensorPanel) can dynamically resize and follow DPI changes when they are moved from one display to another. We're committed to do the job, to make our homework, but sadly it will take more time than what we originally estimated on it

I understand your frustration. We're quite frustrated too, but it's because it's very-very difficult to solve this issue on our side. To let you get a bit of insight into the problem: SensorPanel is a window, and a part of the AIDA64 main process. All windows belonging to the AIDA64 process share the same DPI configuration. So when you move a window (e.g. the SensorPanel) away from the main window, it will still keep (inherit) the same DPI setting that all AIDA64 windows share. So when your main monitor (where you launch AIDA64) has a 150% DPI setting, the SensorPanel will also use that. The SensorPanel will look and act the same on your main display and your secondary display even if the latter has a different DPI setting. It would require a lot of work on our part to make sure all AIDA64 windows (incl. the SensorPanel) can dynamically resize and follow DPI changes when they are moved from one display to another. We're committed to do the job, to make our homework, but sadly it will take more time than what we originally estimated on it

Please avoid swearing if possible. I understand that you're very frustrated at this issue. Please know that you can kill the AIDA64.EXE process using the Task Manager in case you cannot find any "more gentle" ways to make it close or force it to close. And once you killed the process, you should be able to either uninstall it or update it to another version. Regarding the bug itself, based on your topic title I'm not sure if this issue can only be fixed by Asus or both Asus and us have to work together to get it resolved.