Achill3uS Posted August 27, 2015 Share Posted August 27, 2015 hey guys, i experienced something weird with latest 1.73 cpuz when trying to save validation files even with Gigabyte or Asus mobos. i was benching 6700k on ln2, and above ~5.5G when i press F7 or the validate button from cpuz tab (extreme oc feature on or off doesnt change about that) got immediately blackscreen and system restart. i guess this new cpuz generates bigger cpuz load during validation process like older versions. anyway since you cannot validate with older cpuz versions anymore you have to modify cpuz.ini file. here are my settings below what i used to take valids succesfully cpu and mobo tab activated only. [CPU-Z] VERSION=1.7.3.0 TextFontName= TextFontSize=14 TextFontColor=000080 LabelFontName= LabelFontSize=14 ACPI=1 PCI=0 MaxPCIBus=256 DMI=1 Sensor=0 SMBus=0 Display=0 UseDisplayAPI=0 BusClock=0 Chipset=0 SPD=0 XOC=1 CheckUpdates=0 after this, i was able to succesfully save and upload valids up to 6.4G+ anyway, i know its nothing new here but i've lost about an hour+ to figure this out while benching. hope it helps anyone who is chasing max clock. cheers, bala Quote Link to comment Share on other sites More sharing options...
xxbassplayerxx Posted August 27, 2015 Share Posted August 27, 2015 You can also find the XOC setting in the CPU-Z Validate tab. Quote Link to comment Share on other sites More sharing options...
trodas Posted August 27, 2015 Share Posted August 27, 2015 ...makes me wonder, if all the other that XOC settings, are also important to disable... Quote Link to comment Share on other sites More sharing options...
Achill3uS Posted August 27, 2015 Author Share Posted August 27, 2015 You can also find the XOC setting in the CPU-Z Validate tab. i started with that, XOC enable did not worked for me still need to figure out exactly what couse this, but did anyone experience similar issue/bug? Quote Link to comment Share on other sites More sharing options...
Massman Posted August 31, 2015 Share Posted August 31, 2015 Thanks for sharing! Quote Link to comment Share on other sites More sharing options...
trodas Posted August 31, 2015 Share Posted August 31, 2015 I experienced similar bug, but on the other "end"... Pentium 90 overclocked past 66MHz it report wrong FSB and CPU clock... and same P90 underclocked to 10.7MHz result in no CPU frequency shown, hence no validation. Bug since v1.70... because earlier versions have no problemo. Quote Link to comment Share on other sites More sharing options...
sin0822 Posted September 3, 2015 Share Posted September 3, 2015 I am also not able to validate like before, it does seem that the program is putting more load on the system, I think if you enable the XOC it is less, but still I can't get the same validations I could before. 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.