Jump to content

Fiery

Administrators
  • Posts

    12479
  • Joined

  • Last visited

  • Days Won

    558

Posts posted by Fiery

  1. AIDA64 uses standard Windows internert access API (wininet.dll) to download updates information and update packages using HTTP protocol.  It uses standard Windows proxy configuration, but beyond that it has no control over the actual network adapter, network layer or network route Windows picks to download the necessary files from AIDA64 servers.  So I'm afraid currently we cannot limit AIDA64 NetUpdate to specific network connections.

     


    Regards,

    Fiery

    • Like 1
  2. 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.

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

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

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

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

×
×
  • Create New...