techPowerUp! Forums - View Single Post - CPU-Z 1.6x.x

Daz1967 · Apr 30, 2012, 03:43 PM

Same here.

I have a CPUZ.ini file, Readme.txt and Whatsnew.txt files in the CPU-Z folder along with the executable and uninstaller but even if I run CPUZ v1.60.1 outside that folder in, say, my otherwise empty download folder then it still misreports the BCLK, multiplier and, thus, clock and RAM speeds. CPUZ v1.60 and earlier versions work fine, however.

The release notes for v1.60.1 mention a fix for misreported clock speeds under Windows 8 and it seems to me that it is this particular fix which may be the cause of the bug under Windows 7, though I confess I'm no expert. Seems a bit of a coincidence that the error occurs under Windows 7 for the very thing that is supposed to fixed under Windows 8.

Not that it matters that much as I can just continue using v1.60 for now as it works absolutely fine.

Processor:	Intel Core i7-920 @ 3.8 GHz
Motherboard:	ASUS P6T Deluxe v2209
Cooling:	Thermaltake Frio
Memory:	12 GB G.Skill Ripjaws 1,600 MHz DDR3
Video Card:	Point of View NVIDIA GeForce GTX 680
Hard Disk:	256 GB Crucial M4 SSD (boot) + 3 TB Samsung Spinpoint F3 hard drives
Optical Drive:	2 x Samsung BD-ROM/DVD rewriters
CRT/LCD Model:	24" HP LP2475w (HDMI)
Case:	Cooler Master 932 HAF Advanced
Sound Card:	Creative X-Fi Titanium HD
PSU:	Cooler Master Silent Pro M850
Software:	Windows 7 Home Edition SP1 (64-bit)

Apr 30, 2012, 03:43 PM	#103
Daz1967 Join Date: Apr 2012 Posts: 4 (0.01/day) Thanks: 0 Thanked 0 Times in 0 Posts	Same here. I have a CPUZ.ini file, Readme.txt and Whatsnew.txt files in the CPU-Z folder along with the executable and uninstaller but even if I run CPUZ v1.60.1 outside that folder in, say, my otherwise empty download folder then it still misreports the BCLK, multiplier and, thus, clock and RAM speeds. CPUZ v1.60 and earlier versions work fine, however. The release notes for v1.60.1 mention a fix for misreported clock speeds under Windows 8 and it seems to me that it is this particular fix which may be the cause of the bug under Windows 7, though I confess I'm no expert. Seems a bit of a coincidence that the error occurs under Windows 7 for the very thing that is supposed to fixed under Windows 8. Not that it matters that much as I can just continue using v1.60 for now as it works absolutely fine.