Jump to content

WinXP x64 - Defraggler crashes after 4GB -> 8GB RAM upgrade


Edge

Recommended Posts

I've been a happy user of Piriform's software for a long time now, but I just ran into a strange problem.

 

I work with multiple OSes on my computer, but my "main" OS is Windows XP Professional x64 Edition. Until yesterday, I had no problems with Defraggler on it... but as soon as I upgraded from 4GB of RAM to 8GB of RAM, Defraggler crashes as soon as it loads, with the typical "app crash" Windows error message:

 

---------------------------------------------------------------------------------------------------------------------

 

 

 

Defraggler has encountered a problem and needs to close. We are sorry for the inconvenience.

 

 

 

If you were in the middle of something, the information you were working on might be lost.

 

 

 

Please tell Microsoft about this problem.

 

 

 

We have created an error report that you can send to us. We will treat this report as confidential and anonymous.

 

 

 

To see what data this error report contains,
click here.

 

 

---------------------------------------------------------------------------------------------------------------------

 

...which is of course followed by the usual buttons: Debug, Send Error Report and Don't Send. If I click on the "click here" link, here is what it shows:

 

---------------------------------------------------------------------------------------------------------------------

 

 

Error signature

 

 

 

AppName: defraggler.exe AppVer: 1.14.0.159 ModName: defraggler.exe

 

ModVer: 1.14.0.159 Offset: 000c7fcd

 

---------------------------------------------------------------------------------------------------------------------

 

There is of course an option to "view technical information about the error report", but for some reason I can't cut and paste from those results.

 

Perhaps there a bug in Defraggler that does not like to work with systems with > 4GB of RAM?

 

The strange thing is that if I don't acknowledge the error in any way (i.e. just move the dialog box off to the side and don't click any buttons), Defraggler appears to continue to operate just fine... so the error doesn't seem to be a total showstopper. If I do acknowledge the error though, it immediately closes Defraggler regardless of what it's doing.

Link to comment
Share on other sites

  • 3 weeks later...

Sorry, I had not checked the forums in a while so I just saw your reply, Romanoff.

 

However, before running the "debug" test, I went ahead and updated to 1.15... and it appears to have solved the problem. :)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.