CoSMOS Gamehacking Tool
Page 1 of 1
Signup or Login to Post
Error: Couldn't get the thread context
  • Current rank: 1 Star. Next Rank at 100 Posts.
    Send a message to mroshaw99
    VETERAN
    mroshaw99 posted on Feb 22, 2020 12:48:20 PM - Report post
     
    Frequently, when I try to "Find out what writes to this address", I get an error:

    Couldn't get the thread context. Failed at SuspendThread with 0x5

    This happens for all games / processes at the moment. CoSMOS doesn't return any pointers to accessing addresses. Sometimes if I close everthing down and start again, it works.

    I've tried running as administrator but same behaviour.

    Any ideas what's happening?
  • Moderator
    Send a message to CyPHeR369
    MODERATOR
    CyPHeR369 posted on Feb 22, 2020 1:19:21 PM - Report post
     
    What game?
    32 or 64 bit?
    Any security software running?
    Can u post the error log?
    "Light travels faster than sound. This is why some people appear bright until you hear them speak."
  • Trainer Maker
    Send a message to 0x90
    STAFF
    0x90 posted on Feb 22, 2020 2:59:18 PM - Report post
     
    Wait for v6 getting posted in a couple of days
  • Current rank: 1 Star. Next Rank at 100 Posts.
    Send a message to mroshaw99
    VETERAN
    mroshaw99 posted on Feb 22, 2020 5:32:14 PM - Report post
     
    quote:
    originally posted by CyPHeR369

    What game?
    32 or 64 bit?
    Any security software running?
    Can u post the error log?

    I'm using the Cheat Engine 64-bit tutorial EXE to learn how to use CoSMOS
    64-bit
    Windows Defender and Malware Bytes
    Will do - though that's the only line in the "Log" tab

  • Current rank: 1 Star. Next Rank at 100 Posts.
    Send a message to mroshaw99
    VETERAN
    mroshaw99 posted on Feb 22, 2020 5:32:52 PM - Report post
     
    quote:
    originally posted by 0x90

    Wait for v6 getting posted in a couple of days

    Okay, awesome! Looking forward to the new version!

  • Current rank: 1 Star. Next Rank at 100 Posts.
    Send a message to mroshaw99
    VETERAN
    mroshaw99 posted on Feb 27, 2020 6:07:38 AM - Report post
     
    quote:
    originally posted by 0x90

    Wait for v6 getting posted in a couple of days

    Still getting the same issue, unfortunately. Using CoSMOS Advanced 6.0.1, running as Administrator.

    Using "Cheat Engine Tutorial (v3.4)", 64-bit version, as target process.

    11:04:36: Cosmos loading finished in: 00:00:02.2276096
    11:04:36: Failed checking for updates...
    11:04:41: Process Handler: Enumerating processes...
    11:04:42: Process Handler: Time enumerating processes: 697ms
    11:04:50: Successfully attached to Tutorial-x86_64
    11:04:50: Time enumerating modules: 3ms
    11:04:50: Time enumerating memory regions: 2ms
    11:04:50: Symbolhandler: Enumerating symbols...
    11:04:51: Symbolhandler: Finished! Time enumerating symbols: 267ms
    11:04:56: New scan started
    11:04:56: Scan finished in: 00m 00s 081ms
    11:04:56: Time preparing scan results: 2ms
    11:05:02: New scan started
    11:05:02: Scan finished in: 00m 00s 004ms
    11:05:02: Time preparing scan results: 0ms
    11:05:10: Time enumerating modules: 1ms
    11:05:10: DEBUG -> Initial BP!
    11:05:11: Couldn't get the thread context. Failed at SuspendThread with 0xERROR_ACCESS_DENIED (0x5)

  • Trainer Maker
    Send a message to 0x90
    STAFF
    0x90 posted on Feb 27, 2020 7:25:26 AM - Report post
     
    There is nothing wrong with this. There can always be (for us unimportant) threads running where suspend and calling getthreadcontext will fail. Other debuggers will silently continue on this. I can also see the initial breakpoint got hit.

    On Cosmos v5 it may have failed to retrieve thread context of ALL threads so the debugger failed to work completely. For you I see only one error, which can be completely ignored as long as the breakpoints get hit. So except of the log displaying an error, which is by design, what exactly is the issue?
  • Current rank: 1 Star. Next Rank at 100 Posts.
    Send a message to mroshaw99
    VETERAN
    mroshaw99 posted on Feb 27, 2020 2:11:10 PM - Report post
     
    quote:
    originally posted by 0x90

    There is nothing wrong with this. There can always be (for us unimportant) threads running where suspend and calling getthreadcontext will fail. Other debuggers will silently continue on this. I can also see the initial breakpoint got hit.

    On Cosmos v5 it may have failed to retrieve thread context of ALL threads so the debugger failed to work completely. For you I see only one error, which can be completely ignored as long as the breakpoints get hit. So except of the log displaying an error, which is by design, what exactly is the issue?

    Gotcha. Sorry, I see now that that breakpoint is indeed hit in 6.0.1, whereas it wasn't doing so at all in 5.x. All good, then! Thank you for your help!

Page 1 of 1
Signup or Login to Post
All times are (GMT -06:00) Central Time (US & Canada). Current time is 8:02:05 AM