Jump to content

davidm71

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by davidm71

  1. Well I uninstalled the recently purchased Aida64 and removed the PKey file. Then I installed the oem version and was told by the dialogue that this is a Trial version. Not the full version. So apparently MSI did not spring for the full version with this Godlike motherboard you would think they would have considering the cost. Also it was just a few versions too old to support the processor. So I upgraded to latest and copied the pkey file back and have the full version once again.

     

    The only thing is after upgrading lost the nice dragon MSI logo within the previous version. Wonder if there is anyway to restore that logo?

     

    Thank you

  2. Hi,

    Recently used my insider preview feature to update to 1903 May update and having a problem with AIDA64 not loading at all.

    I click the icon and nothing happens. Tried it on the portable version with same results.

    Not sure whats going on.

    Edit: After some more testing its kind of weird in that if it runs it will run minimized to taskbar on right hand side or take a very very long time to run but thats rare. 

    Right now not running!

    Thanks

  3. Please choose your words more carefully.

    It's not our fault that AMD implemented the ULPS feature in a way that causes issues to 3rd party software vendors like us and many other guys who work on diagnostic and monitoring software. We've talked to a developer close to AMD about this, and even he admitted the way AMD implemented ULPS in their drivers is very unwise. It simply turns off the secondary GPU when it's not used, and a simple MMIO readout -- a standard Windows method to read registers from various type of hardware -- causes a hard lock on the computer. Please note that I'm talking about readout, not writing to any registers.

    If you know what MMIO is, how kernel drivers work, and what should happen when a system component goes to sleep, then it should be obvious to you that this method is unacceptable. We've tried to implement workarounds, in fact, we did implement 3 different workarounds to overcome the ULPS nightmare, but it doesn't work in some cases.

    If you want to blame anyone or ban anyone, it should be AMD Catalyst developers, and not AIDA64 or any other 3rd party applications.

    Fair enough. But how about doing a check and warning AMD crossfire folks that going any further may lock your system up?

    I have to agree to disagree with your answer.

  4. I got another suggestion. You could pull out the second gpu just to use their software! Its unacceptable to disable a key system power saving feature just to use this software. I can't believe they haven't fixed this issue at version 1.85 already!

    I say AMD/ATI users ban AIDA64 until they fix this issue!

    BS.

    Edit: Why I'm pissed: Risking data loss due to an unexpected reboot is not pleasant...

  5. I found a fix. You need to make a registry change and then reboot. Also not a bad idea to disable and then enable crossfire first but this step may not be neccessary. Anyhow worked for me. I put it into a reg file that your going to have to run...

    Good luck.

    File is attached to this post.

    Or you can follow the instructions to edit your registry on this link to the Evga site:

    ULPS crash fix ...

  6. I am also getting freezing or full system lockup requiring reboot when in crossfire mode on an Asus Crosshair IV 890FX board as soon as I hit the sensor button.

    Thanks.

    BTW, That disabling multi-gpu feature in preferences did nothing....

    thanks.

  7. It may be the infamous ULPS issue ;) Please try to disable Multi-GPU support in AIDA64 / main menu / File / Preferences / Stability. Let me know if it helps.

    Thanks,

    Fiery

    I am also getting freezing or full system lockup requiring reboot when in crossfire mode on an Asus Crosshair IV 890FX board as soon as I hit the sensor button.

    Thanks.

×
×
  • Create New...