Find the code in the main thread that is responsible for spawning a certain thread?

I'm trying to stop the PS Remote Play program from detecting and/or connecting a controller that is plugged into my PC. In ollydbg when I plug in the controller it spawns a new thread and when I unplug the controller it terminates that thread. To my understanding, if I'm able to find where it checks if a controller is plugged in I could use an unconditional jump or 0x90 opcodes to stop the program from either checking if the controller is plugged in. This would stop the thread from ever spawning. How can I trace the thread back to the function that spawned it?

Read more here:

Content Attribution

This content was originally published by Anthony Leone at Recent Questions - Stack Overflow, and is syndicated here via their RSS feed. You can read the original post over there.

%d bloggers like this: