Hi there,
I used to play around with OllyDbg since a year. All went well until one day a proper debugging wasn't possible.

I always receive a Thread 000000XXX terminated exit code 0 message at the bottom of OllyDbg.

Can anyone tell me what can be done in this case ?

Thanks in advance

Hi,
Do you mean that OllyDbg isn't running anymore ? Did you played with it files (.dll or .exe) ?
Did you tried to reinstall it ? (or redownload it ?) It is maybe a malicious program that modified your favourite debugger..?
Regards.

OllyDbg runs like Forest. But after attaching any process and pressing F9 (Run) the thread is terminated with exit code 0.

All Dlls are clean ones. I tried to re-install the application and OllyDbg, but the effect stays the same.

We need more information. Is it doing this with *all* executables, or just this one? Try loading notepad.exe. If it's just this one program, it's probably an anti-debugging trick.

Sorry, I thought I said it happens with all applications. Maybe this is caused by some broken windows library ?

That is odd.

My gut feeling: You installed an app that has a process persistently running in memory which in turn sabotages Olly, every time you try to run it.

you could go in a wild geese chase stopping one by one all the processes and testing Olly in between, until you isolate the offending proc/thread.

I doubt one of the Windows Libraries got corrupted. I would doubt very much that the damage would be limited to the Debug API's and would expect your system to be more unstable.
Can you run other debuggers? Windbg, Sice other??

Try reinstalling windows, or installing a VM with windows in it. It should allow you to debug there.

I experienced something similar a while back after trying to analyze a file, which I cann't recall what was it. But after that file, it didn't matter what I tried to open, it always gave me the thread error too. At the end, I ended up reinstalling ollydbg and that seems to have taken care of whatever the problem was.

first point to try unzip ollydbg in a new folder and load some exe on it and see if problem persists if yes then it could be serious
maybe like naides suggests sabotage by some bs running in backgorund

if it indeed worked then next try is to copy the udd folder to some other place ( i assume you have a seperate udd folder ) and delete the existing one and try out again if the former worked this should work too

if it worked then it is a problem of one of corrupt udd files drag drop one by one into and isolate the corrupt one

or simply if you dont need any older analysis

start --> run --> cmd --> cd path to udd folder --> del *.udd del *.bak

or get the cleanupex plugin and delete udds by choice