balane Posted April 2, 2011 Share Posted April 2, 2011 AIDA64 Extreme Edition Beta 1.60.1314 Laptop is an HP Mini 311-1000NR. GPU is nVidia ion. Under Sidebar Items regarding GPU clock speeds I have two items available; GPU Clock GPU Shader Clock Both show 100MHz constantly while monitoring which is honestly useless information and I really have no idea to what it's referring. Neither of the GPU clock speed items available under Sidebar are helpful because both constantly show 100MHz as their readings. 1.) On the main page of AIDA64 under Display/GPU I see RAMDAC clock which honestly reports the GPU Core Speed. (Currently at 400MHz as I type this.) 2.) Under Display/GPGPU/Device Properties I see a Clock Rate item correctly listing the GPU Shader Clock speed currently at 1100MHz. 3.) I can not locate a working report of GPU Memory Clock anywhere although both GPU-Z and CPU-Z both show the memory clock (And core and shader) correctly. Is there a way I can add RAMDAC and Clock Rate listed above (And GPU Memory Clock if possible.) to the items I can monitor in the Sidebar? These are the items I would like to monitor on my desktop via the Sidebar Gadget. Thank you for your assistance. EDIT: I have just downloaded and tested the latest beta, 1.60.1339, and the problem persists. Quote Link to comment Share on other sites More sharing options...
Fiery Posted April 3, 2011 Share Posted April 3, 2011 100 MHz clock is reported because at idle your GPU is running at PCI Express nominal clock speed (100 MHz) to save power. It is a common power management technique of nVIDIA IGP GPUs. 1) That is a pure coincidence. All modern GPUs are equipped with a 400 MHz capable RAMDAC, but that doesn't mean it has any relation with the GPU core clock at all. 2) GPGPU device properties reflect the capability of the GPU, and not the actual speed it is running at. The actual speed is 100 MHz at idle, as reported on the GPU page. 3) IGP chips (like nVIDIA Ion) usually use the system memory as frame buffer and texture memory, and so it makes no sense to display memory speed or memory properties on the GPU page. Instead, AIDA64 shows the system memory type and clock rates on the Computer / Overclock and Motherboard / Motherboard[/b] pages. You can also have the system memory clock speed and timings displayed on the Sidebar Gadget. Regards, Fiery Quote Link to comment Share on other sites More sharing options...
balane Posted April 3, 2011 Author Share Posted April 3, 2011 Sorry but I'm just having a really hard time understanding that. Can you please look at this image? http://mysite.ncnetwork.net/res89pejl/furmark.jpg You can clearly see and agree that while Furmark is running my core and memory speeds should be ramped up from 100MHz. In fact they are being reported by every software monitoring tool I use (Furmark, GPUZ, CPUZ, HWiNFO32, Nvidia Tools, etc.) as 450MHz and 1064MHz. Yet AIDA64 always, no matter the load, reports my GPU speeds at 100MHz. To add even more to this no other software monitoring tool, not one single time, will ever report any of these speeds at 100MHz. Even further, when looking at the possible clocks speeds in my VBIOS under a multitude of conditions running at 100MHz is not even an option. Unless I'm missing something here it definitely appears as if AIDA64 is incorrectly reporting these speeds. Can you please shed any light on this? Thank you for your time. Quote Link to comment Share on other sites More sharing options...
Fiery Posted April 4, 2011 Share Posted April 4, 2011 You're right, that is not normal. Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic. Thanks, Fiery Quote Link to comment Share on other sites More sharing options...
balane Posted April 4, 2011 Author Share Posted April 4, 2011 Certainly. Thank you. ------[ AIDA64 v1.60.1339 Beta ]------ ------[ Microsoft Windows 7 Home Premium 6.1.7601 (32-bit) ]------ ------[ Video Adapters ]------ nVIDIA Ion [10DE-0876 / 103C-3651] ------[ Video Driver ]------ nvapi.dll: 8.17.12.7051 nvd3dum||8.17.12.7051 - nVIDIA ForceWare 270.51|||nvwgf2um||8.17.12.7051|||nvwgf2um||8.17.12.7051 nvd3dum||8.17.12.7051 - nVIDIA ForceWare 270.51|||nvwgf2um||8.17.12.7051|||nvwgf2um||8.17.12.7051 ------[ nVIDIA GPU #1 @ mem D2000000 ]------ GPU Clocks = 100 / 100 / 0 MHz Memory Clock = 0 MHz GPU Base Clock = 27000 kHz Shader Base Clock = 27000 kHz Memory Base Clock = 27000 kHz nvidia-000000 = 0ACB00B1 nvidia-0010F0 = 00000000 nvidia-001218 = 00000000 nvidia-001540 = F3010001 nvidia-0015F4 = 00000000 nvidia-0015F8 = 00000000 nvidia-0015FC = 00000000 nvidia-001600 = 00000000 nvidia-001850 = 00000000 nvidia-004000 = 00000000 nvidia-004004 = 00000000 nvidia-004008 = 00000000 nvidia-00400C = 00000000 nvidia-004018 = 00000000 nvidia-00401C = 00000000 nvidia-004020 = 80000000 nvidia-004024 = 00001001 nvidia-004028 = 00010000 nvidia-00402C = 00001203 nvidia-00C040 = 2EE11008 nvidia-00E114 = 00000001 nvidia-00E118 = 00000000 nvidia-00E11C = 00000001 nvidia-00E120 = 00000000 nvidia-020014 = FA2D0399 nvidia-020400 = 00000030 nvidia-100000 = 0000C042 nvidia-100200 = 00000000 nvidia-10020C = 10000000 nvidia-100214 = 00000000 nvidia-100474 = 00000000 nvidia-100714 = 00000000 nvidia-100914 = 00000000 nvidia-101000 = 9FC098C0 nvidia-300000 = B342BE3E nvidia-310000 = B342BE3E nvidia-700000 = 0420B104 nvidia-7E0000 = EB7CAA55 ------[ nVIDIA GPU #1 / ForceWare Properties ]------ Memory Type = 3 (DDR2) Memory Bank Count = 1 Memory Bus Width = 128-bit GPU / MC / VE Load = 0 / 0 / 0 VPE Count = 0 Shader Pipe Count = 1 Shader SubPipe Count = 2 Total SP Count = 16 Total TPC Count = 1 Total SM Count = 2 Core Count = 16 Partition Count = 2 Fan RPM = <unknown> Core Voltage = 900 mV Current Pstate = 12 Ventura State = 0 (unsupported) Physical Frame Buffer Size = 262144 KB Virtual Frame Buffer Size = 1441792 KB Total / Free Video Memory = 262144 KB / 208668 KB ------[ nVIDIA GPU #1 / ForceWare Clocks ]------ Perf. Levels = 4 Active Profile = 0 curr-core/shader/mem-0 = 200 MHz / 400 MHz / 1064 MHz [Active] curr-core/shader/mem-1 = 300 MHz / 600 MHz / 1064 MHz curr-core/shader/mem-2 = 350 MHz / 800 MHz / 1064 MHz curr-core/shader/mem-3 = 450 MHz / 1100 MHz / 1064 MHz orig-core/shader/mem-0 = 200 MHz / 400 MHz / 1064 MHz [Active] orig-core/shader/mem-1 = 300 MHz / 600 MHz / 1064 MHz orig-core/shader/mem-2 = 350 MHz / 800 MHz / 1064 MHz orig-core/shader/mem-3 = 450 MHz / 1100 MHz / 1064 MHz ------[ NVAPI GPU Handles ]------ GPU Count = 1 GPU #1 = BB000200 ------[ nVIDIA GPU #1 / Thermal Settings ]------ Sensor Count = 1 Sensor #0 / Controller = GPU Internal Sensor #0 / Target = GPU Core Sensor #0 / Current Temp = 49 Celsius Quote Link to comment Share on other sites More sharing options...
balane Posted April 12, 2011 Author Share Posted April 12, 2011 I'm not sure what a typical time frame on something like this is but do you expect any progress to happen? I've been checking back once a day. Thanks. Quote Link to comment Share on other sites More sharing options...
Fiery Posted April 12, 2011 Share Posted April 12, 2011 The bug fix will be implemented in the next beta release. Which is due in a couple of days. I'll let you know in this topic once the new beta is available. Thank you for your patience. Quote Link to comment Share on other sites More sharing options...
balane Posted April 12, 2011 Author Share Posted April 12, 2011 Fantastic. Thank you very much. I'll be looking forward to it. Quote Link to comment Share on other sites More sharing options...
Fiery Posted April 16, 2011 Share Posted April 16, 2011 We've fixed the Ion clocks in the following new beta version of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1358s7dm2qvrgbzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery Quote Link to comment Share on other sites More sharing options...
balane Posted April 16, 2011 Author Share Posted April 16, 2011 Works perfect now! Thanks much. Quote Link to comment Share on other sites More sharing options...
Fiery Posted April 16, 2011 Share Posted April 16, 2011 Thank you for the feedback Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.