CoSMOS Gamehacking Tool

The newest version of CoSMOS has been randomly crashing (5 times this morning). I've had a value locked during each crash but that's the only thing they have had in common.

I've cleared my registry of any remnants of older versions, I've re-installed and it still occurs.

The issue doesn't occur with the previous version using the same game.

From my event logs-

Application: CoSMOS.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 0000000000000000

Faulting application name: CoSMOS.exe, version: 4.0.0.0, time stamp: 0x59ca86dd
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x25fc
Faulting application start time: 0x01d3385f5dac8f27
Faulting application path: C:\Program Files\CoSMOS\CoSMOS.exe
Faulting module path: unknown
Report Id: d45e42e4-7c00-4435-903f-b2618ab7de06
Faulting package full name:
Faulting package-relative application ID:

Any ideas what would be causing this?

Can you tell me which value you have locked? What data type it was? Have you added this item manually or from scanning results?

The locked value was a double from a scan.

I've scanned for double and frozen the values without any crash. Is there anything else you can remember you did before it crashed? Is that issue reproduceable or rather happens randomly (but frequently in your case) ?

I've been able to reproduce it three times in the last 20 minutes.

The game is AquaNimble on Steam (it's a shmup).

I scan and lock "Lives" at 5 (double). I reset scan and scan for "highest chain" (double). First scan no issues, second scan will crash CoSMOS.

The game isn't crashing but I'll jump into another game and see if I can reproduce it just to make sure it's not an issue with that specific game.

The crashes aren't isolated to that one game.

CoSMOS crashed twice in about 30 minutes with Asteroid Bounty Hunter, locked was a "float" this time and crashes varied in the number of scans on the second value (first time it was 4, second was 9 and I was searching "all"

So the only thing the crashes have in common is I have a value locked. It's never crashed while doing the initial scans for the first value.

Error info from event log is the same as the previous game.

[Edited by Criel, 9/28/2017 3:00:25 PM]

[Edited by Criel, 9/28/2017 3:00:45 PM]

Anything you did different than me in this video?

The only thing different I've done is change the locked values.

For instance with AquaNimble I started with 5 lives, searched for value and found it with 2 or 3 lives left and changed it back to 5, locked it.

The second game was under the same circumstances. I changed the value I found prior to locking it.

If you can't reproduce it on your end I'm leaning towards it being an issue with my .Net being damaged/corrupted but it's strange that I haven't had issues with other applications if that's the case.