Jump to content

Featured Replies

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.

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.

I don't understand. I've never had that issue on any version of CPUz or board. :confused:

 

Guess you're special :D

Guess you're special :D

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.

  • Author
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

i have no problem... maybe is a chipset problem because i'm using an a7v600. this evening i will try an a7n8x-x board

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...