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

Defraggler Defraggler Bug Reporting
1

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.

2

Thanks, we'll have a look at this.

3

Hi,

Can anyone else confirm this issue?

Edge, can you post the debug log and exception.txt file?

To run Defraggler in debug log: http://docs.piriform.com/defraggler/troubl...r-in-debug-mode

The exception.txt file should be located in the executable directory after the crash.

Thank you,

Best regards

Romanoff

4

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. :)