"A problem caused the program to stop working..." upon Spybot termination

[PaulWood]

When Spybot SD finishes, it abruptly terminates with the oft-seen message: "A problem caused the program to stop working..."
I ran SpyBot by executing MHPCTSEXSFKE.scr due to reading on this forum about a similar error on start up. Same thing occurs when running SpybotSD.exe.

I checked for application errors and found one. It referenced "ntdll.dll".

Faulting application name: MHPCTSEXSFKE.scr, version: 1.6.2.46, time stamp: 0x2a425e19
Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea8e7
Exception code: 0xc0000374
Fault offset: 0x000ce753
Faulting process id: 0x1420
Faulting application start time: 0x01cf41237767380b
Faulting application path: C:\Program Files (x86)\Spybot - Search & Destroy\MHPCTSEXSFKE.scr
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 6c71dd5d-ad18-11e3-98f5-bf324080aa3e
I'm at a loss - any suggestions?

[Zenobia]

I'm seeing on Google that Exception code: 0xc0000374 most likely means heap corruption.
This page has more on it,if it helps any:
http://www.qnx.com/developers/docs/6.4.0/neutrino/prog/hat.html#ProblemsWithHeapCorruption

As a more general,simpler,try it and hope for the best way of going about it,you could try uninstalling and then reinstalling Spybot and seeing how it goes.
The 1.6.2 version is available from this page,and there is also the newer 2.2 version of Spybot,if you would like to try that instead:
http://www.safer-networking.org/dl/
The operating system compatibility is listed here:
http://www.safer-networking.org/about/compatibility/

[PaulWood]

Zenobia,

Thanks for the info and suggestion. Having done some programming, I understood the comments regarding heap corruption on the qnx.com site. However, it's moot since I do not have the source code to compile with the malloc library. I have already reinstalled 1.6.2 and the error persists.

As an aside: I booted in SAFE mode and SpyBot SD completed without error. Apparently, some service or other application in memory is contributing to the memory error.

[Zenobia]

You might want to continue running the Spybot scan only after booting into safe mode instead of in normal mode for the next couple of times,since it was able to complete the scan.

And then,if/as you have any extra time to try to troubleshoot,you might want to try running Spybot in normal mode,and shutting down one or two applications that are running at the time of the scan,to see if the Spybot scan might complete.I'd go with anything non-essential at first,and work my way through shutting down any programs that usually run when I ran the Spybot scan until the scan completes.
If shutting down any programs usually running while Spybot scans didn't work,I'd probably look at Services next.Myself,I'd look those up to be sure it was something I could safely temporarily stop,and do it much the same way as when I was shutting down programs during a Spybot scan,one or two at a time,so I could try to narrow it down.
Services can be looked up here:
http://www.systemlookup.com/lists.php?list=8
Or here:
http://www.blackviper.com/windows-services/
Tedious and time consuming,I know,but about the only thing I can think of to troubleshoot,to start. :)

[PaulWood]

Zenobia,

Thanks for your suggestion. I was thinking along those lines also. You're right, it will be time consuming. I'll post results here if I have any success.

[Zenobia]

Thanks.Good luck,I hope you can get Spybot to complete the scan. :)