New beta version: memset34beta2
-Fix a bug with tREF on some P35/X38, when "0" value is show after apply.
Sorry for this inconvenience.
New beta version: memset34beta2
-Fix a bug with tREF on some P35/X38, when "0" value is show after apply.
Sorry for this inconvenience.
FELIXOriginally Posted by FELIX
New beta version: memset34beta2
-Fix a bug with tREF on some P35/X38, when "0" value is show after apply.
Sorry for this inconvenience.
Again want to thanks for your work and dedication, memset is a great program. Although I feel depressed when I think I have to change DPI settings and reboot each time when I want to use it. Would you fix that BUG and allow running it with various DPI scales ?
Thanks
i3770K@ 4.4 - 1.25v - TR120 Black+ Scythe GT AP-14
Crucial Ballistix Tracer 4x4096 DDR3 1866Mhz
Asus P8Z77-v Deluxe
PowerColor HD R290 moded to X
Samsung SSD 256GB 840 Pro
Samsung HDD 7200RPM 2TB (2x1TB) SA(N)TA
Corsair HX 650W
Antec P182 +3x Scythe -800-1200RPM
Asus 27" VN279QLB
Logitech G100S, CM Storm Quick Fire TK
Win 8.1
FELIX
PLEASE add command rate in there again (testing different mobos that don't have the CMD rate selection means that we are in the dark what's selected as CPUz doesn't reliably show it still)
Command Rate is detected by a single bit in MCHBAR registers.
The value is either 0 or 1.
CPU-Z can read the command rate on any current Intel chipset.
the thing is stilt it wasn't reading properly on the Gigabyte P35T-DQ6
Too old version of CPU-Z, nothing else.
Or maybe the bios is bugged.
But CPU-Z reads it correctly, period.
the P5K3-Dlx also switches back and forth from reading ir correctly and not reading it correctly FWIW. most of the time it is correct but every few reboots it goes back to 2T then after a reboot or two, CPU-Z starts picking it up as 1T again.
i don't quote in my signature, but best WR ever...i can't even make that shyt up ^^^
Posting Permissions
Reply With Quote
Bookmarks