Jump to content

Pill

Members
  • Content Count

    26
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Pill

  • Rank
    Member
  1. Thanks but there is no confusion here. The 15GB of Virtual Memory reported by AIDA simply doesn't exist, If I have 8GB of RAM installed and no pagefile it means my total available Address Space is 8GB. It also means I have a Commit Limit of 8GB. There is no more memory anywhere.. Add an 8GB pagefile to the 8GB of i RAM and we get a total of 16GB Virtual Address space, made up of 8GB RAM and 8GB of Virtual Memory. Virtual Memory is the pagefile . Virtual Address Space is everything available to Windows This screenshot with Process Explorer might help clear things u
  2. Actually you almost have it right, all u need to do is rename Swap Space to Committed Memory then delete the Virtual Address Space part which is incorrect. What is listed as "swap space" is actually Address Space/Commit Limit. I have 8GB RAM + 2GB Page File so total available address space is about 10GB. I tho I have the PF turned off...
  3. Ah no I don't think the API is to blame as MSI Afterburner, Task Manager, Process Explorer and also RAM Map all report Virtual Address space correctly. You can see this in the screenshot I posted above where the PF is disabled. AIDA64 is the only app afaik which reports incorrectly. Windows doesn't manage swap space with the PF disabled, it manages Virtual Address Space. Swap Space is specifically the pagefile. With the pagefile disabled total Address Space is limited to RAM installed. AIDA should be reporting the same as Task Manager above which shows a 7.8GB comm
  4. This anomaly has been present in AIDA for years. Virtual Address Space is always twice the installed RAM, even with the pagefile disabled. Never really bothered me but since I was already browsing the forums figured I'd point it out. Keep up the good work.
  5. Confirmed, happens if sensor page is left open when AID64 is minimized to taskcbar. It only started to occur after installing the latest 13.6 AMD drivers, It may help you to know the latest 13.6 set require an updated VC runtime (included with package).
  6. OK thanks. I think they pulled those numbers out of a hat....or maybe that's just measuring 1 core/module lol.... Will let you know if I find out anything
  7. Hi, if the CPU Package displays current TDP why does it always read between 35W-45W, even when benchmarking at 4.8GHz? (HWiNFO64 also does this). Thanks.
  8. Hi is there any way for AIDA64 to display the actual CPU/NB voltage instead of just the VID? Thanks. ------[ AIDA64 v2.85.2447 Beta ]------ ------[ Microsoft Windows 7 Ultimate 6.1.7601.22137 Service Pack 1 (64-bit) ]------ ------[ Motherboard Info ]------ Motherboard ID : 63-0100-000001-00101111-122211-Chipset$1APEF003_BIOS DATE: 04/09/13 22:15:23 VER: 04.06.05 Motherboard Model : Asus Sabertooth 990FX R2.0 Motherboard Chipset : AMD 990FX, AMD K15 DMI MB Manufacturer : ASUSTeK COMPUTER INC. DMI MB Product : SABERTOOTH 990FX R2.0 DMI MB Version : Rev 1.xx DMI MB Se
  9. Yep this is true. I have 7950 with 8228G (VDDC_CHL8228_VIDReadback = 0 added to Afterburner). My results below:
  10. Hi this isn't really a bug but wanted to let you guys know that the sensors in my screenshot are for the motherboard VRM's (confirmed with ASUS Thermal Radar). An educated says one is the CPU and/or CPU/NB. The second is possibly the DRAM vrm but not 100% sure.
  11. Yep same here.I have 8GB ram installed with no page file, yet AIDA reports my total virtual address space as 16GB....
  12. Hi, I'm having the exact same problem described in a couple of other threads. The first thing that happens is the GPU VDD disappears in sensor page, then my G15 LCD screen displays 0.00v and completely freezes. On closer inspection with Process Explorer I could see aida64.exe was hung at 25% CPU load and using 115 threads. Not sure if this thread count is normal but it seems very high to me. I'm also getting access violation errors like this one: Not using AI Suite, not running RAID. No external devices except G15 keyboard and G500 mouse. Using latest AIDA64 build October 1. Specs:
×
×
  • Create New...