Jump to content

Squall Leonhart

  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by Squall Leonhart

  1. I've seen it mentioned on a number of occasions that SpeedFan is safe to use with Aida64, however on Asus boards this isn't exactly the case.


    When I have both running there is a high degree of chance that all the devices indicated to be accessed via ATK vanish.


    Is aida64 and Speedfan accessing these  via the ATK0 driver (ASACPI.sys)?

    Systems in question are Rampage 3 and Rampage 4 extreme boards.

  2. Sensor and GPU Sensor info latency is massive, report the issue to nvidia, I'll notify ManuelG of this thread and to be on the watch for the feedback.



    You might also go further and perform the following

    Use nsight to analyze your system for causes of hitching and stutters

    Then follow on with these if it doesn't display a trigger or theres evidence the issue is in the nvidia driver.

    Performance reports require the user to submit a gpuview or gpu-z log.

    How to generating an event trace log for GPUView to troubleshoot performance issues/low FPS/game stutter

    Collecting GPU logs using GPU-Z

    extended logs can be put on a filestorage host like google drive and their share link mailed to driverfeedback@nvidia.com


    For the LM78 sensor, disable EC (Embedded Controller) monitoring and iirc for this mainboard you turn Asus WMI on?


    Your issue is basically caused by multiple utilities on the system hitting the same sensors at the same time which is neither a safe or performant thing to do.

    Ie, don't run aida64 at the samet time as Hwinfo64, speedfan, corsair link etc.

    • Like 1
  3. Easy, here you go.

    The drive is currently on the ASUS UASP driver, but Smart was also missing on the mass storage driver, regardless both could pass through smart to Crystaldisk, and I can also see the data in HD Tune, SSD-Z, etc.





    I also have a cable based on the ASM1351 on order so i can get trim working on this ssd, so i'll likely be back with dumps for that too after it arrives lol.

  4. Fiery, the feature this user wanted is possible.

    The drive itself can report what SATA mode it is in, but not all do so and seems more likely when the Drive is Sata Rev3 / 6Gb with some exceptions being ODD's

    The utility SSD-Z implements it.

    Attached to Intel ICH10 sata








    Attached to Marvel SATA 6G



    Attached to JMI E-Sata


  5. On 8/29/2018 at 12:09 PM, birdgg said:

    I take your response that I shouldn't assume AIDA64 causing BSOD?  I thought this is a bug reports forum and I was reporting a BSOD that is reproducible, if I can not report that I doubt why this forum ever exists.  On the other hand, have you read all posts that concludes anything and would you shed some light?

    Aida64 is just a victim to nvidia's unstable NVAPI code at the present time.

  6. On 8/21/2018 at 12:22 AM, vabchgent said:

    So I have this Blue screen and it points directly at AIDA 64 . It only happens when my monitor is in sleep mode, am I in the right place. looks like it is being worked on and may be a Nvidia problem. Just making sure I am following.




    PROCESS_NAME:  aida64.exe


    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

    it doesn't point directly at anything.

    otherwise it would be FAULTING_PROCESS:

    Nvidia has made no mention of whether they have reproduced the issue with the reproduction steps so far.


    On 8/23/2018 at 4:41 AM, adriant42 said:

    Hi Fiery,

    I tried Google but could not locate a forum/announcement that talked specifically about the BSOD monitor power management issue. I would like to keep track of this issue to see if there has been a fix. Do you happen to have a link that you can share?




    There is no announcement.

    12 hours ago, birdgg said:

    Hi Developers,

    I saw this thread yesterday and was hoping the beta version will address the BSOD that I've experienced.  However I got a BSOD in about 1 hour, I wasn't very sure that the BSOD in my case was relating to Windows 10 update that has been mentioned in other posts in this thread but what I can be sure is that whenever I have my computer idle with AIDA64 running, I will get BSOD within 1-4 hours.  I'm not very sure what to provide to keep this issue on track but here's some basic information of my system and hopefully this can be fixed in coming stable version update.

    MB: Asus B350 prime plus
    CPU: Ryzen 1600
    SSD: Samsung Sm961 and Evo 850
    VGA: Nvidia GTX 980 Ti

    You should read all posts within a thread before assuming something.

    There will not be a fix for this bsod coming from Fiery's side.


  • Create New...