I would use the pheverstool to scan your hacks. Anything pink means you have dupes. Sort by MD5 and delete the dupes.
Anything red means they are hacks. Select all hacks and disable them. Then, do a binary search. Binary search is faster than going through your hacks one by one.
Here's how:
10 create new subfolder named <Insert name here> ex. "Hacks that need checking" or "CH3CKD33ZHAXF00"
20 create new subfolder named <Insert name here> ex. "Hacks that actually work" or "ZOMGD33ZHAXW3RK"
30 Place all your disabled hacks in here (if you used the pheverstool, they will have a .off file extension)
40 Enable half of your hacks.
50 Load game
60 If no error occurs: go to 70; else go to 80
70 place your "good" hacks in your "working" folder; go to 30 and repeat
80 REM: Your error obviously lies in this set of hacks
90 disable half of these hacks
100 load game
110 if no error occurs: go to 40; else go to 120
120 if one hack left: congratultions, you have found the culprit, go to END; else go to 90 and repeat
Hope that all makes sense. Who knew you'd need an easy 12 step program to sort your hacks.
Ste
PS. Extra credit for bonus step after you determine which hack it is:
END: actually reporting it
here to let everyone else know what the problem was,
and reporting it back to the creator.
ETA: Edited to remove typos, make the
pseudocode much clearer, and change the numbering to
BASIC format.