• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Bug: GTX 260 Clock Monitoring Incorrect Since 0.3.9

Joined
Sep 27, 2012
Messages
4 (0.00/day)
Likes
0
#1
I got a GTX 260 and noticed that it's clocks were being misrepresented in the sensors page with 0.7.4.

I rolled back until I discovered that 0.3.8 was the last version of GPU-Z to report them correctly.



EVGA Precision also misreports the same core clock.
 

Solaris17

Creator Solaris Utility DVD
Joined
Aug 16, 2005
Messages
19,389 (4.27/day)
Likes
6,300
Location
Florida
System Name Venslar
Processor I9 7980XE
Motherboard MSI x299 Tomahawk Arctic
Cooling EKWB L360 R2.0
Memory 32GB Corsair DDR4 3000mhz
Video Card(s) Gigabyte 1080TI
Storage 2x SG 3TB HDDs (RAID 0) | 1x ADATA 128 SSD (Cache) | 1x Drevo 256 SSD | 1x 1TB Samsung 850 EVO (OS)
Display(s) 3x AOC Q2577PWQ (2k IPS)
Case Inwin 303 White (Thermaltake Ring 120mm Purple accent)
Audio Device(s) Realtek ALC 1220 on Audio-Technica ATH-AG1
Power Supply Seasonic 1050W Snow
Mouse Roccat Tyon White
Keyboard Ducky Shine 6 Snow White
Software Windows 10 x64 Pro
#2
thats because of the clock controller the PLL crystal cannot make even clock rations like 10 20 30 40 its always been a few mhz off IIRC at one point they all "leveled" the readings, I believe mine uses a 27mhz crystal so 1 step is a 27mhz jump IIRC.
 

Kursah

Moderator
Staff member
Joined
Oct 15, 2006
Messages
11,066 (2.69/day)
Likes
5,160
Location
Missoula, MT, USA
System Name Kursah's Gaming Rig - Haswell Edition | Spartan Home Server 2015
Processor i7 4790k 4.0/4.8 @ 1.26v | i7 4790k 4.0/4.4 @ 1.18v - Both delidded w/CLU
Motherboard Asus Z87-Pro - BIOS 2103 | Asus Z87-Pro - BIOS 2103
Cooling Noctua NH-U14S Push-Pull | Cooler Master 212 EVO Stock - Using NT-H1 and AC MX-4
Memory 16GB (2x8) Corsair Dominator DDR3 2400 CL11 | 32GB (4x8) G.Skill DDR3-1600 CL9
Video Card(s) MSI GTX980 Ti Gaming 6G LE @ Stock | Onboard Intel HD 4600
Storage 850EVO 250GB SSD, 960GB SSD, 1x2TB | 840 120GB SSD, RAID10 6x2TB (6TB) + 8TB Backup
Display(s) Samsung 32" TV IPS 1080p, Dell 23" U2312HM IPS 1080p | 19" 4:3 Dell LCD..mostly RDP.
Case Corsair 600C - Stock Fans on Low | Lian Li Lancool PC-K7 - Cougar fans
Audio Device(s) Aune T1 mk1 > AKG K553 Pro + HiFiMAN HE-350 (Equalizer APO + PeaceUI) | Realtek ALC1150
Power Supply EVGA 750G2 Modular + APC 1500VA UPS | EVGA KR500 80+ Bronze + CyberPowerPC 1000VA UPS
Mouse Logitech G502 | Dell USB Laser Mouse
Keyboard Logitech G15 rv2 | Dell USB Keyboard
Software Windows 10 Pro x64 | Windows Server 2012 R2 (GUI Core,Hyper-V + VMs)
#3
Yep, that is reading correct. It's not a misreport, it's the hardware clocked value verses the software rounding it to a nice and smooth number.
 
Joined
Sep 27, 2012
Messages
4 (0.00/day)
Likes
0
#4
OK, thanks for the clarification. I guess it's XFX's fault for not setting and advertising a clock that the card was actually capable of running at.