Jump to content

Fiery

Administrators
  • Posts

    12473
  • Joined

  • Last visited

  • Days Won

    557

Posts posted by Fiery

  1. Bitdefender Total Secuity 2013 indicates "Driver Agent" is bad for your computer's health!!!   So bad, in fact, it quaratined it!!!!   (The "Web Scan" to be exact)

     

    I'm pretty sure that's just a false alarm.  Many security software tend to get too sensitive these days.  We've notified eSupport about this issue though, so they will look into it and contact BitDefender to have Total Security 2013 fixed up.

  2. I'm getting this too now, for every empty slot in my cardreader the 'no disk' dialog pops up 3 times on addin new item to the panel or sensor osd prefs. The cardreader is is a scythe card&floppy, identified as Y-E Data, Silicon Media R/W, device-id: 057B-0020

     

    In windows disk manager the drives do show as removable/no media.

    mobo happens to be asus too, this time M5G with latest bios(1707)

     

    image of the error:

    PLxUDIM.jpg

     

    any way to solve this?

     

    Regards, Darkje

     

    Can you please post a full Scythe part number for your card reader?  We'll try to purchase one to perform test runs in our labs.

  3. Problem not solved for everyone! I just installed Aida 62, ver. 2.85.2400, on my Lenovo Y500, and have the same issue. When I check the BIOS information, it says "unknown." New computer, Windows 8, firmware and OS up to date. 8GB memory, 1TB HDD. Screen shot attached.

     

    I'm afraid that may happen in such cases when the UEFI BIOS refuses to emulate the classic system BIOS region with valid data.  The System BIOS Date field shows that the system BIOS is invalid.  We haven't yet found a proper workaround to fix such issues :(

  4. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at:

     

    http://www.aida64.com/downloads/aida64extremebuild2412dt8hwjrp4mzip

     

    After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

     

    If it still doesn't work as expected, then please try to disable SMBus access in AIDA64 / main menu / File / Preferences / Stability, and let us know if it makes a difference.  After altering the SMBus option, make sure to restart Windows.

     


    Thanks,

    Fiery

  5. It sounds a lot like a PSU (Power Supply Unit) failure to me.  If it's possible, try to get a new PSU.  Borrow it from a friend to make sure you don't spend too much on this issue if the PSU is not at fault afterall.  If the PSU is fine, then my second guess would be the motherboard: one of the capacitors may have given in.

     

    But, before you start dealing with hardware issues, make sure to update the motherboard to the latest BIOS version, restore your settings to factory defaults (make sure your system is not overclocked), apply all Windows updates/hotfixes, and update your video driver to the latest version.

     


    Regards,

    Fiery

  6. As for command-line, while doing our test runs we used the following one:

     

    "F:\tweak\nVIDIA Inspector 1.9.7.0 Beta\nvidiaInspector.exe" -setMemoryClock:0,2,444 -setShaderClock:0,2,1222

     

    It worked flawlessly for us, so I'm sure that the command-line handling of AIDA64 Alerting facilty works fine.

     

    ---

     

    "Number of ours between sending repetitive alerts" means after firing an alert, how much time AIDA64 should wait before firing another alert for the same condition.

     

    "Update Frequency/Alerting" means the polling frequency of the alerting items, to check whether they are inside or outside the configured limits.

  7. We've tested it with an Asus GeForce GT 520 (GF108-based) card, and memory clock can be adjusted via a similar command-line using AIDA64 Alerting facility, so the command-line handling definitely works fine in AIDA64. Setting GPU clock from command-line doesn't work though, but it also doesn't work from the GUI of nVIDIA Inspector.  I suppose it's due to the fact that GPU and shader clocks are linked together, so you need to adjust shader clock instead of GPU clock, and GPU clock will follow the change as 50% of shader clock.

  8. If the default core temperature values are always zero, then it may be due to the ACC (Advanced Clock Calibration) feature of AMD processors.  When you activate ACC in the BIOS Setup, then core temperature measurement will be impossible by any software.  They will always appear as zero Celsius.

  9. Thank you for the data.  Your motherboard uses the usual ASRock fan mux logic, so only one of the CPU fans can be monitored by AIDA64.  If you connect the fan to the other CPU fan connector, AIDA64 will show the RPM for it.

     

    As for core temperatures and GPU diode temperature, they are quite low, and it is due to the common hardware issue of modern AMD processors (e.g. FX, Llano, Trinity, Richland).  They measure unrealistically low temperatures at idle, but the measurements get much closer to real when the system is under heavy load.  Unfortunately this is a hardware issue that cannot be fixed from software.

     


    Regards,

    Fiery

×
×
  • Create New...