Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11554

  • Joined

  • Last visited

  • Days Won

    489

 Content Type 

Everything posted by Fiery

  1. Fiery
    Please check post #9 on the first page of this topic
  2. Fiery
    Yes, it must be a collision between AIDA64 and Corsair Link Software. Are you using the latest beta version of AIDA64 (v5.70.3854), and also the latest version of Corsair Link Software? (v4.2.3.41) We're now in discussion with Corsair, trying to figure out the best way to synchronize their software with our software. From now on, you will see constant improvements on both sides, so soon the collisions will be gone. Till then, make sure to enable automatic updates to AIDA64 beta packages (AIDA64 / main menu / File / Preferences / General / NetUpdate), and also keep Corsair Link Software up-to-date.
  3. Fiery
    RemoteSensor port is set in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / RemoteSensor. I mean the firewall software that's running on your Windows computer. In your firewall software you have to make sure to open the TCP/IP port you use for RemoteSensor. Otherwise the firewall software will block the RemoteSensor network traffic.
  4. Fiery
    Are you sure your phone uses the same IP address range (e.g. 192.168.0.xxx) as your main computer? Do you have the TCP/IP port that you use for RemoteSensor open on the firewall software running on your computer? Maybe you not only changed the router but also switched firewall software? Localhost doesn't count about firewall issues
  5. Fiery
    We don't have plans to enable that, since you can achieve the same goal by using the SensorPanel: You can have the System Stability Test and SensorPanel windows open next to each other.
  6. Fiery
    The issue will be fixed in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new beta is available for download.
  7. Fiery
    It should be possible to turn the device on in mini-monitor mode, or change the operation mode while it's on, using the buttons of the SPF device. Once the device is switched to mini-monitor mode, you should be able to install the SPF drivers we've put together. BTW, when you start AIDA64 and enable Samsung SPF LCD support, and it detects a SPF device in mass-storage mode, it should initiate the transition into mini-monitor mode, to ease the process of installing the driver. However, for your device maybe that transition cannot be initiated by a Windows software
  8. Fiery
    CPU IA Cores and CPU GT Cores temperatures are read from the CPU, and not from the iGPU. Hence, it's quite possible that the CPU provides the iGPU (GT Cores) temperature even when the iGPU is disabled. The iGPU may be disabled, but its thermal sensor would still continue to operate. You can verify if the iGPU is really disabled by checking the list of GPUs on the Display / GPU page in AIDA64. Regards, Fiery
  9. Fiery
    Ever wondered how big the new nVIDIA Pascal GPU family would turn out to be? Here's the whole list of Pascal SKUs, with their respective PCI device IDs. Enjoy! Note: The list contains a few Maxwell IDs as well, in order to clarify the difference between GMxxx-A and GMxxx-B PCI device regions. Note #2: GM200-B may have been a second iteration, an optimized variant of the original GM200, but never reached the market. Could have been a plan B in case Pascal slips to late 2016 or 2017. [...] 15F0 Graphics Device [GP100GL-A] 15F1 Graphics Device [GP100GL-A] [...] 1725 Graphics Device [GP100-B] 172E Graphics Device [GP100-B] [...] 1B6F Graphics Device [GP102-B] [...] 1B80 GeForce GTX 1080 [GP104-A] [...] 1C02 Graphics Device [GP106-A] [...] 1CC2 Graphics Device [GP107-B] [...] 1D01 Graphics Device [GP108-A] [...] Click for the full list of PCI IDs here.
  10. Fiery
    We've contacted Corsair to ask for their assistance on this issue. I'll let you know in this topic once we have an update to this issue
  11. Fiery
    We don't have a list of affected devices. Refer to the following forum topic, especially the last few pages: https://forums.aida64.com/topic/2424-new-lcd-device-support-samsung-spf-digital-photo-frames/page-16
  12. Fiery
    Thank you for the feedback and your kind words
  13. Fiery
    That's great news, thank you for your feedback!
  14. Fiery
    We've fixed the copy-paste issue in the latest AIDA64 beta update available at: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works Thanks, Fiery
  15. Fiery
    Please try it with the latest AIDA64 beta available at: http://www.aida64.com/downloads/latesta64xebeta Let me know if it helps
  16. Fiery
    We've implemented Corsair's synchronization semaphore in the latest AIDA64 beta update available at: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works Feel free to re-enable both Asetek LC sensor support and Corsair Link sensor support in Preferences / Stability, they should work from now on too.
  17. 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
  18. Fiery
    In such situations the usual order of business is to update the motherboard flash BIOS, re-check all memory timing settings to conform what the memory modules dictate, and check if the CPU Turbo ratios are properly configured by the BIOS. If none of those help, you may want to lower the memory clock (if it's overclocked), and loosen up a bit on the memory timings. Changing Command Rate (tCR or tCMD) from 1T to 2T could do wonders in the quest of reaching 100% system stability Regards, Fiery
  19. Fiery
    Samsung SPF picture frames would work fine, although a few users complain about the device overheating under constant communication with AIDA64 -- clearly a hardware issue. As for Odroid, we support Odroid-Show natively in AIDA64, but those are small displays VU7 seems to support direct HDMI connection, so it would work as a secondary monitor. In other words, you can expand your Windows Desktop to that display, and you won't even need to use the AIDA64 LCD module. You can instead use the AIDA64 SensorPanel feature, and import your previous LCD layout to there. Those true monitor displays are the best devices out there, although some could cost a lot of $$. You can also use virtually any DSub, DVI, HDMI or USB connected monitors in the same way as the VU7. Sometimes you can pick up 2nd hand 17-inch LCD monitors for as low as US$20. They could provide a huge space to place your sensor readings as well
  20. Fiery
    Yes, but ideally, we would like to synchronize AIDA64 with Corsair Link Software about any device access, not just when it comes to AXi, HXi and RMi Series PSUs. That way, you would be able to re-enable the 2 other, currently disabled options too. Or at least we have high hopes about being able to access any Corsair hardware by implementing Corsair's own synchronization technique If they did it the right way, and we implement it the right way, it should work fine.
  21. Fiery
    The root cause of the issue is that for some reason Corsair refuse to use the industry standard synchronization mutexes that would ensure AIDA64 and other monitoring software (like AMD OverDrive, CoreTemp, CPU-Z, EVGA E-LEET, GPU-Z, HWiNFO, HWMonitor, MSI AfterBurner, RivaTuner, SIV, SpeedFan, etc) work properly next to a running Corsair Link Software instance. Corsair came up with their own solution, and now we have to implement it in AIDA64. We'll try to do that in the upcoming days, and hopefully I'll be able to send you a new AIDA64 beta download link in this topic in a few days from now. Thank you for your patience about this issue.
  22. Fiery
    Thank you for the updated dump. We'll do some further improvements in the next AIDA64 beta update. I'll post a download link for the new beta update into this topic soon.
  23. Fiery
    Do you have a SDK for the keyboard, or any other technical details on how to talk to the keyboard? Here they didn't seem to find one, but maybe things have changed since then: https://github.com/SpoinkyNL/Artemis/issues/55
  24. Fiery
    You can try the following to resolve the issue, which seems to be related to the memory or cache subsystem: 1) Update the motherboard BIOS 2) Re-check all memory timings to make sure they match the values G.Skill recommends 3) If none above helps, it may be best to lower the memory clock and/or to use more relaxed memory timings. Sometimes a simple change like upping the Command Rate (tCR) from 1T to 2T can do magic I personally would never trust a setup that generates hardware failure errors in any stress test software.
  25. Fiery
    That unfortunately is normal for mobile systems since the introduction of Haswell CPUs. The processor is designed to not overheat and not throttle under "regular load" scenarios -- but it will overheat and throttle when running a very demanding task like AIDA64 System Stability Test. As long as the throttling doesn't affect the way you can use your computer, it's not a big deal. If you however can find hiccups while gaming, and you're certain it's because of overheating, then try to improve the cooling of your system. Regards, Fiery
×
×
  • Create New...