Jump to content

p1r473

Members
  • Posts

    29
  • Joined

  • Last visited

Posts posted by p1r473

  1. On 8/31/2020 at 5:24 AM, Fiery said:

    Our iCUE Nexus device hasn't arrived yet.  As soon as it hits our lab, we start researching how can we support it.  I have high hopes of fully supporting it as long as you close iCUE (software) since it notoriously collides with any other hardware monitoring software that is trying to access Corsair hardware.

    As for El Gato, the support is quite basic.  You can place a single image on the last key and that's it.  We're hoping that someone can develop a plugin for it that would allow more flexibility and greater interaction with other plugins.  Currently we cannot allocate more development time on that project.

    I cannot recommend either, since El Gato support is too basic, and without a test device I cannot confirm that iCUE Nexus would work with AIDA64.

     

    Any update on iCue nexus support? Doesnt seen to be any option in Preferences->LCD

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

     

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

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

  5. I am quoting JazJon, he said

    "I've tested the Mediasonic ProBox 3.5" SATA Hard Drive Enclosure - USB 3.0 SuperSpeed (K32-SU3) and have added the necessary data to BitFlock.com.
    Just restart the StableBit Scanner service (or reboot) and you should now have full IDENTIFY and SMART data.
    (and so will everyone else)
    This is better than Unsafe, because it doesn't have to "probe" the enclosure which could crash it. It simply asks our cloud for the correct method to use."

     

    You had said you wanted an AIDA64 tester to test if it works but... it looks like it only works if I use aida64 with StableBit Scanner rather than using the unsafe method that is causing crashes? I want to be able to monitor my enclosure temperature with aida64 without needing a 2nd application, in this case StableBit Scanner

     

    I am responding to the last 2 posts. the guy said he got aida64 to work with the enclosure if he used stablebit scanner, but I dont want to use that. I only want to use aida64. So I was wondering if you were able to use the method they use to get it to work (the method: It simply asks our cloud for the correct method to use.)

  6. Well I just had a dismount with disable_cypress so Im back to square one now. Ive had dismounts on everything but oxford, and oxford just causes the drives to not show up in the storage->smart screen

    So I have no idea at this point. Im probably having issues with 2+ of these guys, and I think this level of testing is beyond me. I'd emplore you to buy the unit but from a better retailer this time :)

  7. Ok here are my findings about the existence of each file

    disable_atapt- dismount

    disable_jmicron- dismount

    disable_sunplus- dismount

    disable_oxford- drive doesnt show up in aida64

    disable_cypress- no dismount

    So basically, atapt, jmicron, and sunplus methods being disabled have no effect and I still dismount. Disabling oxford prevents the drive from showing up in the storage->smart screen, which I think makes it stable but only because it cant see the drove. Disabling cypress caused no dismount, and drive was visible

    So i >>THINK<< cypress is the culprit. Im going to leave SMART on for now and have cypress disabled, and see throughout the week if there are any dismounts while having only cypress disabled

  8. I will test them all out and will report back soon as my testing is done

    Is there anything that might help generate a dismount? I tried a RAID dump with the option enabled but did not produce a dismount. It is sometimes stable, sometimes not, and right now its being very stable

    Should I have them disabled only one at a time, or once one is disabled, I contrinue with the rest of the disabled ones?

    Also, could a few of them being cuasing the issue, or is it only one? Like once I find one that doesnt dismount, can I stop the tests or do I keep going?

×
×
  • Create New...