Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12004

  • Joined

  • Last visited

  • Days Won

    525

 Content Type 

Everything posted by Fiery

  1. Fiery
    We've just rolled out a new AIDA64 beta that supports LCDInfo and Aquaero 4 displays: http://forums.aida64.com/topic/2449-new-lcd-device-support-lcdinfo-usb13700-and-usbd480/
  2. Fiery
    We've added support for both LCDInfo LCD protocols, as described at: LCDInfo USB13700 LCDInfo USBD480 You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD. The only thing needed to enable this feature is having the LCD drivers (libusb0) installed, and the display to be connected to a USB port. You can verify if your device is compatible with AIDA64 by finding the device on the Devices / USB Devices page in AIDA64, and checking its Device ID. It should be one of the following IDs: 16C0-08A2 (USB13700) 16C0-08A6 (USBD480) It is recommended to use the latest firmware for your display. You can find the new AIDA64 beta update at: http://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD or VFD device that is currently unsupported by AIDA64. BTW, Crystalfontz LCD, POS VFD (customer display, pole display, table display), and Trefon LCD devices are also supported now by the latest AIDA64 beta. Regards, Fiery
  3. Fiery
    AIDA64 uses CPU MSR register to detect throttling activity. It is per core, so #1 from your list. I'm not sure if there's a register that one could use to detect throttling activity for other parts of the CPU package. Much quicker, typically just tens of milliseconds. AFAIK throttling kicks in when the CPU is overheating for 20 milliseconds (or more), so the whole thing is very sensitive and very sharp. It has to be, or else it wouldn't be able to prevent a critical overheating situation damaging the processor.
  4. Fiery
    There's a native method to read PCH Diode temperature, directly from the PCH. That's a different reading And it's not supported by many Intel systems.
  5. Fiery
    Thank you for the shot, it looks great. I'm glad you could make it work We'll try to get a SPF-87H that failed to work out for you, because there's a slim chance that particular DPF has some other tricks that AIDA64 doesn't handle properly yet. Although my gut instinct says that your particular SPF-87H part may just have some hardware flaw that isn't related to AIDA64 at all.
  6. Fiery
    Please note that AMD processors will not throttle, throttling is used by Intel processors. AMD processors use a different mechanism to protect themselves from overheating. As for the spikes, they could be because the CPU temporarily failed to provide the right CPU multiplier reading, or that the motherboard temporarily failed to provide the BCLK (FSB) clock speed via APIC. Such things could happen when the system is under extreme load (stress). You don't have to worry about such things as long as your processor isn't overheating while running the stress test. Regards, Fiery
  7. Fiery
    AIDA64 will not stress or load the system when you only use it for monitoring purposes. I'm afraid you haven't provided enough details on the issue to discuss it further. For example, it would be important to know what kind of computers are they, and whether you could see any actual CPU load (via e.g. Task Manager) when your processors were throttling while you were using AIDA64. And if you saw any actual CPU load, it would be important to know whether they were caused by the AIDA64 main process (aida64.exe) or some other process or service. Regards, Fiery
  8. Fiery
    No adjustment is necessary about TJMax on Intel Nehalem and Silvermont family processors. TJMax adjustment was only necessary in the LGA775-era. As for throttling, it may or may not kick in at TJMax. Please note that the on-die CPU temperature sensors aren't that accurate that one may expect them to be. Also, when any of the CPU cores momentarily hits TJMax, the CPU will start throttling immediately, and the reported DTS temperature will quickly drop down a few degrees Celsius. The whole thing overheating protection mechanism works very quickly, and the measured temperatures will fluctuate a lot.
  9. Fiery
    Thank you for the feedback
  10. Fiery
    Thank you for the feedback
  11. Fiery
    I'm sorry, that is just a pecularity of our implementation of the log closing. It doesn't put the footer there if you manually stop logging, since it treats the situation as you just suspend logging and may restart it again with the same log files. It will only put the footer there when AIDA64 itself stops the logging and closes the log file. We'll try to come up with a solution soon, although it's not easy, since there are many different issues colliding with each other in this case.
  12. Fiery
    Such things could happen when AIDA64 enables a certain chipset PCI device that is otherwise disabled by the BIOS at system bootup. Once the new device appears in Device Manager, try to reinstall Intel Chipset Device Software. It should take care of installing the drivers for the enabled device.
  13. Fiery
    We can only add that in case the BIOS Setup or Gigabyte's own software also shows the reading as PCH temperature. Otherwise it's just pure guessing
  14. Fiery
    It should be there But it's written there only when you close AIDA64 or it automatically opens a new log file.
  15. Fiery
    We've added support for all Trefon USB LCD and GLCD products, as listed at: Trefon USB-Displays You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD. The only thing needed to enable this feature is having the LCD drivers (libusb0) installed, and the display to be connected to a USB port. You can verify if your device is compatible with AIDA64 by finding the device on the Devices / USB Devices page in AIDA64, and checking its Device ID. It should be one of the following IDs: FFF0-FFFD FFF0-FFFE It is recommended to use the latest firmware (Version 2.1) for your display. You can find the new AIDA64 beta update at: http://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD or VFD device that is currently unsupported by AIDA64. BTW, Crystalfontz LCD, LCDInfo LCD and POS VFD (customer display, pole display, table display) devices are also supported now by the latest AIDA64 beta. Regards, Fiery
  16. Fiery
    We've just updated AIDA64 to include support for Samsung 800P, 800W, 1000P and 1000W DPF displays as well: http://www.aida64.com/downloads/latesta64xebeta This version also supports both Samsung's original SODI drivers and generic libusb0 drivers.
  17. Fiery
    We've implemented support for the new generation graphical Crystalfontz CFA-835 display in the following new AIDA64 Extreme beta update: http://www.aida64.com/downloads/latesta64xebeta
  18. Fiery
    We've fixed the clipboard locale (character set) issues in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3120dwjf9t3lcpzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery
  19. Fiery
    We've further tweaked the log files header/footer, as requested. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3120dwjf9t3lcpzip Let me know how it works
  20. Fiery
    We've fixed the sensor readings in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3120dwjf9t3lcpzip As for the PCH temperature, I'm not sure how HWiNFO64 reads it. Can you please post a screen shot that shows all HWiNFO64 readings and all AIDA64 readings side-by-side? As for the BIOS date, the emulated classic system BIOS apparently contains a wrong system BIOS date stamp. It's due to a BIOS bug, and not an AIDA64 issue.
  21. Fiery
    We've implemented the requested drag&drop LCD page reordering trick in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3120dwjf9t3lcpzip Let me know how it works. Please note that at the time you perform the reordering, the page captions will be reordered as well, to indicate that you've performed a reordering. So e.g. after swapping Page 1 and Page 3, the page captions will look like: "Page 3 / Page 2 / Page 1 / Page 4". But, after you press the OK button and close the Preferences window, and reopen it again, the page captions will be restored to the default order of "Page 1 / Page 2 / Page 3 / Page 4". The pages content will however be kept as it should, so the content will be kept swapped.
  22. Fiery
    Sounds great, thank you for letting us know about the resolution.
  23. Fiery
    In our first test run under Win8.1 we've also attempted to install Frame Manager, but the installer failed. Frame Manager doesn't seem to be compatible with Win8.x at all, but the drivers work fine under Win8.x -- at least for us. We've installed the Mini Monitor device drivers using the drivers copied to \Program Files\Samsung\FrameManager by Samsung Frame Manager installer, and it worked just fine. In one of your previous posts you seemed to have indicated that it didn't work for you under both Win7 and Win8, but now you say it works fine under Win7? Just to make sure it's not a driver issue, please try to change the Mini Monitor drivers to the ones we're using. The driver version is the same with yours, but we've already got two different Samsung SPF driver sets, both with the same version, so you never know with Samsung I'll send you the download link to our drivers in private message. BTW, our "Plan B" for the Samsung issue is that we would implement an alternative driver path in our code, to let you use generic LibUSB drivers with Samsung DPFs. That may or may not help in your situation though, since -- if I properly understand what you wrote -- the device keeps disconnecting after 5 seconds even if you don't start AIDA64 at all. It could well be a driver issue that may be resolved with the LibUSB driver, but it is also possible that it's a hardware flaw that will not be resolved by a driver change. Anyway, if you have time and energy left to hassle with your SPF-87H, you can try our LibUSB solution soon. I'll send you a message once the LibUSB driver and the AIDA64 beta with LibUSB Samsung SPF support is ready to be test-driven.
  24. Fiery
    In case the Mini Monitor device disappears from the system after that 5 seconds elapsed, even if you don't start AIDA64 at all, then it seems to be an issue that is related to the Samsung driver or the device itself. Have you tried to connect the device to another computer? Have you tried to check the Windows Event Logs, to see whether there's any reference to why the device gets disconnected? I'm starting to feel like your particular SPF-87H device has some hardware flaws... Maybe try updating the firmware. I'll soon run out of ideas
  25. Fiery
    It's quite puzzling. Have you tried to connect the DPF to another USB controller? Have you tried to power the DPF off, power it on again, and switch the device to Mini Monitor Mode on the DPF, and see what happens when you start AIDA64?
×
×
  • Create New...