View previous topic :: View next topic |
Author |
Message |
Davethewave Expert Cheater Reputation: 0
Joined: 06 Mar 2005 Posts: 210
|
Posted: Thu Aug 25, 2005 1:14 pm Post subject: Crashes |
|
|
some times when I am in the code window and I click a code, then I click "Find out what addresses this code accesses" it will attatch the debugger, when I go back into the game, the game quickly crashes or locks up, then crashes.. A specific example is Dungeon Siege II, I searched for some code and found "code: 004016f8 - 89 37 - mov [edi],esi" so when I try to find out what that code accesses the game crashes always. I have the stealth modes disabled.
|
|
Back to top |
|
|
Dark Byte Site Admin Reputation: 458
Joined: 09 May 2003 Posts: 25296 Location: The netherlands
|
Posted: Thu Aug 25, 2005 2:44 pm Post subject: |
|
|
disable debugger detection prevention
and dont use hyperscan
and use debug registers, not exceptions
Thats the only thing I can come up with, because when I did it it never crashed on me and those are the settings I usually use.
(the only times it crashed was when I modified a part of the code which caused a bug and finally made the game crash)
_________________
Do not ask me about online cheats. I don't know any and wont help finding them.
Like my help? Join me on Patreon so i can keep helping |
|
Back to top |
|
|
Davethewave Expert Cheater Reputation: 0
Joined: 06 Mar 2005 Posts: 210
|
Posted: Tue Aug 30, 2005 1:21 am Post subject: |
|
|
Ok right on, also another note: If you open 00000000-Physical Memory in 5.0 you may not want to attempt to read data before address 00400000... it causes the computer to reboot itself as if it tries to get outside the physical memory and gets confused because it can't?
*never mind, maybe it's just my ram? I can goto address 00300000, but it reboots between 003F0000 and 00400000 for some reason.*
|
|
Back to top |
|
|
Leonidas Advanced Cheater Reputation: 0
Joined: 07 Mar 2005 Posts: 98
|
Posted: Tue Aug 30, 2005 1:52 am Post subject: |
|
|
Another thing regarding the crashes when doing to "find what addresses this code accesses", if you have the memory browser open it'll break and will wait to continue. and when full screen, thats hard
as for crashes for accessing ram, that is device/ram dependent. it may be a device is trying to lock that ram, but fails because you are watching it.
e.g a example of device memory: look at address c0000 (or c00000?) for the bios of your videocard
Also, does it really spontaniously reboot, or first shows a blue screen of death before rebooting? (if so, you can disable the reboot in your windows settings, so you can read the error message)
|
|
Back to top |
|
|
|