Registry Cleaner access violation on 64 bit system

clydeman wrote

I just installed this version and tried to run the Registry Cleaner on a 64 bit system and it keeps freezing on me. The first time I tried to install it I didn't delete the old version. This time it was a clean install.Any thoughts?

1. Do you get a 'freeze application error' or does jv16PT just stop processing (freeze)?

2. During the 'scan' process or during 'fixing' of the found errors?

Same problem on my system. I submitted a bug report.

It freezes when it seems close to being finished "analyzing" data on the registry cleaner. It does not reach the point where it lists any found errors. It always seems to freeze at the same place. It only says "not responding" and then in a little while it will go to a page asking to continue the program, restart it or close it.

It only freezes itself, not the entire computer. Windows 7 x64. ,1032 and .1039.

floydgrant wrote

Same problem on my system. I submitted a bug report.

It freezes when it seems close to being finished "analyzing" data on the registry cleaner. It does not reach the point where it lists any found errors. It always seems to freeze at the same place. It only says "not responding" and then in a little while it will go to a page asking to continue the program, restart it or close it.

It only freezes itself, not the entire computer. Windows 7 x64. ,1032 and .1039.

Are you using Alwil/Avast software?

No, I am not using that software.

clydeman wrote

I hope these images are useful.

Yes, usefull. The picture shows an access violation NOT a application freeze error.

It shows you are running jv16PT build 1132 and build 1141 was released late today.

Suggestions:

1. What happens if you click 'continue application' after you get the access violation error

2. Can you try the same with build 1141, the latest jv16PT version released today.

3. In the jv16PT installation folder there is a file bugreport.txt, containing detailed info on the occured application errors (e.g. access violation).

Can you .zip this file and attach this zipped file to this forum thread? Zip is mandatory because .txt files are not allowed to upload to the forum.

clydeman wrote

I hope these images are useful.

When you see this dialog, a file called BugReport.txt is automatically generated to the program's installation directory (e.g. C:\Program files (x86)\jv16 PowerTools 2012\). Could you open the BugReport.txt and copy/paste its content here? You can censor out any information that you consider too private (like computer name, Windows login name etc).

Sending this file would allow me to see exactly what happens before the problem occurs.

same freeze on version .1141.

clydeman wrote

bugreport.zip

Thank you! However, this BugReport.txt contains information about "program seems to be frozen" and not about the Access Violation problem that your screenshot contains. Can you try to run the Registry Cleaner again in order to get a BugReport.txt of the Access Violation?

clydeman wrote

New Compressed (zipped) Folder.zip

I let this run for about 10 mins and it kept freezing and stopped working.Should I leave it running for a longer period of time?

According to the BugReport.txt, it seems that:

1) The problem occurs only after you have clicked the Fix button, not during the actual scan. Am I correct?

2) You are using an anti-virus product as well as some other security related software. In theory, these products can intercept all registry and file system calls made by jv16 PowerTools which can cause delay and make the program seem to have frozen. To rule this out, could you try to replicate the problem in Windows Safe Mode? In Safe Mode, all the security products will be disabled.

For me, it freezes before it even lists the problems it has found. I have Norton Internet Security, but I turned it off and jv16 Registry Cleaner still froze.

floydgrant wrote

For me, it freezes before it even lists the problems it has found. I have Norton Internet Security, but I turned it off and jv16 Registry Cleaner still froze.

Does the program produce the BugReport.txt file? If yes, could you send that over?