gigioracing Posted July 6, 2013 Share Posted July 6, 2013 (edited) 1) I've tried different cpu but they are not seen 2)the monitor freezes when I open cpu.z (also default) . with 1.62 version work correctly.. http://hwbot.org/submission/2399257_gigioracing_cpu_frequency_athlon_xp_1900_palomino_2232.48_mhz Edited July 6, 2013 by gigioracing Quote Link to comment Share on other sites More sharing options...
Mr.Scott Posted July 6, 2013 Share Posted July 6, 2013 (edited) I have no issue. Here's a couple from today. http://valid.canardpc.com/show_oc.php?id=2855371 http://valid.canardpc.com/show_oc.php?id=2855862 It depends largely on the bios that's used. Edited July 7, 2013 by Mr.Scott Quote Link to comment Share on other sites More sharing options...
Bobnova Posted July 7, 2013 Share Posted July 7, 2013 What motherboard is that Mr. Scott? My AN7 hates modern CPUz. Quote Link to comment Share on other sites More sharing options...
Mr.Scott Posted July 7, 2013 Share Posted July 7, 2013 DFI Ultra B I'll have to dig out my AN7 and try it. Haven't run it in a while anyway. Quote Link to comment Share on other sites More sharing options...
Bones Posted July 7, 2013 Share Posted July 7, 2013 All versions of CPU-Z from 1.60 to present have this issue with Socket A, any versions from 1.59 down work OK. The changes made from 1.59 to 1.60 is the apparent issue but exacly how it's doing it I don't know, I too get the system lockup/freeze trying to open it up for a screenie after a run is done. It's done this with every Socket A board and CPU I have. It always locks the system up while CPU-Z is showing "Processors" during the program's startup. Quote Link to comment Share on other sites More sharing options...
Mr.Scott Posted July 8, 2013 Share Posted July 8, 2013 I don't understand. I've never had that issue on any version of CPUz or board. Quote Link to comment Share on other sites More sharing options...
I.nfraR.ed Posted July 8, 2013 Share Posted July 8, 2013 cpuz was fine with my Abit boards until 1.55 or 1.57, don't remember exactly. Then it was fixed in some of 1.6x versions. Haven't tried recently, but it seems to be broken again., however the issue in the past was wrong FSB detection. Quote Link to comment Share on other sites More sharing options...
Bobnova Posted July 8, 2013 Share Posted July 8, 2013 I don't understand. I've never had that issue on any version of CPUz or board. Guess you're special Quote Link to comment Share on other sites More sharing options...
I.nfraR.ed Posted July 8, 2013 Share Posted July 8, 2013 1.55: OK - http://hwbot.org/submission/1060504_i.nfrar.ed_cpu_frequency_athlon_xp_2500_barton_2767.85_mhz 1.57: NOK - http://hwbot.org/submission/2185244_i.nfrar.ed_cpu_frequency_athlon_xp_m_2800__3094.62_mhz 1.58: NOK - http://hwbot.org/submission/2220806_i.nfrar.ed_cpu_frequency_duron_1.6ghz_2750.85_mhz 1.60: NOK - http://hwbot.org/submission/2295507_i.nfrar.ed_cpu_frequency_athlon_xp_2000_thorton_3182.53_mhz 1.61: OK - http://hwbot.org/submission/2324603_i.nfrar.ed_cpu_frequency_athlon_xp_m_3000__2923.81_mhz 1.62: OK - http://hwbot.org/submission/2354919_i.nfrar.ed_cpu_frequency_athlon_xp_3200_2779.22_mhz 1.63: OK - http://hwbot.org/submission/2368188_i.nfrar.ed_cpu_frequency_athlon_xp_m_2500_3288.84_mhz Guess it might be setup dependent, but that's on my Abit NF7s. As I said, the problem was related to wrong FSB detection. Quote Link to comment Share on other sites More sharing options...
Mr.Scott Posted July 8, 2013 Share Posted July 8, 2013 Guess you're special Yeah.....I'm sure that's it. lol I did have the FSB detection problems that everyone else had, but that's fixed now. I still get no lockups or anything like that though. Quote Link to comment Share on other sites More sharing options...
I.nfraR.ed Posted July 8, 2013 Share Posted July 8, 2013 I get lockups and sometimes error on first start. Quote Link to comment Share on other sites More sharing options...
Mr.Scott Posted July 8, 2013 Share Posted July 8, 2013 Interesting. Wonder if it has to do with my stripped OS. Quote Link to comment Share on other sites More sharing options...
GENiEBEN Posted July 8, 2013 Share Posted July 8, 2013 P.O.S 1/65 refuses to validate a GL40 chipset motherboard that has no issue with 1/64. Quote Link to comment Share on other sites More sharing options...
gigioracing Posted July 9, 2013 Author Share Posted July 9, 2013 All versions of CPU-Z from 1.60 to present have this issue with Socket A, any versions from 1.59 down work OK. The changes made from 1.59 to 1.60 is the apparent issue but exacly how it's doing it I don't know, I too get the system lockup/freeze trying to open it up for a screenie after a run is done. It's done this with every Socket A board and CPU I have. It always locks the system up while CPU-Z is showing "Processors" during the program's startup. I have the same problem,the system freeze when i open cpu-z I also have found problem with slot 1 cpu's Quote Link to comment Share on other sites More sharing options...
attilorz Posted July 14, 2013 Share Posted July 14, 2013 i have no problem... maybe is a chipset problem because i'm using an a7v600. this evening i will try an a7n8x-x board 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.