Which background program is making my games crash

lenni.michel

Prominent
Sep 1, 2017
34
0
540
Hi,
multiple games I play right now (R6S, GTA5, BO3) crash frequently and since I couldn´t find a way to fix that I contacted the support of the game developers.

After some back and forth, all of the customer services figured there is a background program causing the issue.
No one could tell me which one it is and everyone recommended I disable ALL autostart programs and do a clean boot of windows.

While that does help, I don´t want to have all of them disabled as I run them for a good reason (antivirus, bluelight filter etc...)
Now how do I tell which program is making all of my games crash?

Windows 10 64-bit self-built
GTX 1050ti - Core i3-7100 - 8GB 2133mhz RAM - AsRockH110itx/ac - 1TB HDD - 450 Watt PSU
...and yes, my GPU drivers ARE updated
 
Solution

They should have told you to disable them one at a time and test run the game after each one you disable. It's called deductive reasoning. You eliminate each one as a suspect if disabling it doesn't solve the problem. That said, there may be more than one causing it, so I suggest you keep going down the list until you've tested all of them one at a time.


They should have told you to disable them one at a time and test run the game after each one you disable. It's called deductive reasoning. You eliminate each one as a suspect if disabling it doesn't solve the problem. That said, there may be more than one causing it, so I suggest you keep going down the list until you've tested all of them one at a time.

 
Solution
Assuming it's a single program causing the problem, disabling them one at a time actually isn't the quickest way to find the problem.

First disable them all, so you can verify that one of them is in fact causing the problem.

Next re-enable half of them. If the problem returns, it's one of the programs in the half you re-enabled. If the problem doesn't return, it's one of the programs in the half you didn't re-enable.

Take the half of your programs that you've determined contains the culprit. Divide that half into half again (a quarter), and re-enable / disable that quarter (depending on which half the program program was in in the previous step). As before, if the problem returns, it's one of the programs in the quarter you re-enabled. If the problem doesn't return, it's one of the programs in the quarter you didn't re-enable.

Repeat until you've narrowed it down to the one program which is causing the problem. Repeatedly dividing in half this way will let you find the culprit program in sqrt(N) tries (where N is the number of programs). Disabling them one at a time takes N/2 tries on average to locate the culprit, so will on average take longer if you have more than 4 programs installed.
 
Well, honestly, he's being too vague by saying "While that does help". We don't know if it's a situation where each program is either a severe problem, or no problem at all as you assume. If you don't test each one, you have no way of knowing what level of problem if at all it is.

My rule of thumb with startups is to enable as few as possible, and I mean at all times, not just while gaming. I have like one enabled, that's it. I think what happens is far too many people assume just because it's something they use they need it enabled as a startup, which is almost always not the case.