View Full Version : Debugger problem on XP SP2
k-libre
April 30th, 2005, 09:57
hi everybody...
i'm not speaking good english but i'm going try to explain my problems.
i'm realy newbie about cracking. I downloaded many programs and i start to keep some tutorials.
it was good at the begining. Than, in ollydbg after the breakpoints my computer is blocked. I couldn't understand why.. anyway i tried with other crackme's but it was same. Each time just after breakpoint my computer is blocked.
So i tried to make breakpoint with w32dasm, gobug and ida. But the results was same. I tried many crackme's in different debuggers but it was everytime same.
And now i don't know what i must do? How can i make to work one debugger on my pc?
i have
Xp pro Service Pack 2
Amd Athlon 2400 Xp 2.00 ghz 512 mb
Geforce mx 5200
help me please.
thanks
naides
April 30th, 2005, 10:53
Explain a little bit:
When you say my computer is blocked you mean it freezes, meaning no response from the mouse, keyboard, or Ctrl Alt Del?
or is it the debugger that freezes, but you can run other things on the side,
or is it the application, the crackme that freezes?
k-libre
April 30th, 2005, 13:40
when i said is blocked its mean no response from pc.
mouse : i can move it but when i want to click somewhere it's not working.
keyboard : it's working. But when i make Ctrl+Alt+Del i have to wait long time or i must make it two or tree times for see task manager. When i see task manager i can't make anything because computer is still freeze.
(i would like to capture my screen for to show to you but i can't because pc is freezes)
There is not problem with crackme. Because i tried many crackme's. There was same problem.
i tried different crackmes with different debuggers (w32dasm, olydbg, ida, gobug) There was same problem.
I have not virus and spy.
Since two days i working on this subject and i couldn't find solution yet. I dont know exactly but maybe problem is about DLL files. I have this idea because, i have same problem with all debuggers. it's mean my system who have problems? but where....
Thanks for any help...
nikolatesla20
April 30th, 2005, 14:11
Well just for grins then, open a file called boot.ini on the root of your C:\ drive, (change it to non-read only first), and then find some text that says "OptIn", and change it to "AlwaysOff", and reboot (this turns off the system's data execution protection - part of SP2). Then try debugging again...
-nt20
k-libre
May 1st, 2005, 13:05
thanks for help...
i did it what u said but nothing is changed!
But
i tried to start my computer with safe mod. in safe mod all debuggers worked good. it's mean i have problem with my system but where?

naides
May 1st, 2005, 13:20
Well, you just showed yourself the method to figure that out.
What is the difference between safe mod and normal mod? in safe mode only a minimum of drivers get loaded, so some of the drivers and services that get loaded in normal mod are fucking up your debuggers
If you read the "start up and shutdown troubleshooter" in windows help and support you will learn how to selectively boot your computer with some but not all sevices.
Systematically boot your computer with an increasing number of drivers and services and check if the debuggers are working as expected, until you find the one or ones that mess with your debugger capabilities. Get rid of them, and PLEASE PUBLISH HERE WHO IS FUCKING UP YOUR DEBUGGER.
My gut feeling is that one of the applications or softwares that you have installed in your computer is protected with a service that sabotages the normal function of debuggers in general.
laola
May 3rd, 2005, 11:27
Please run msinfo32 (click on the "Start" button, then "Run...", enter msinfo32 into requester box, hit enter) and save the output. Attach it to a post here so I can have a look at it - maybe it's one of the "usual suspects"

Powered by vBulletin® Version 4.2.2 Copyright © 2018 vBulletin Solutions, Inc. All rights reserved.