no, the closest u can get is by looking at the opcode errors and the address with instruction that caused the crash
with the opcode, u can deduce which cleo caused the problem(the cleo used that opcode)
with the address u can know which module crashed the game (gta_sa.exe, d3d9.dll, samp.dll) etc...
and then if u know / have analyzed / reversed the game, you would know which address region contains which functions, by that u can know what caused the crash (what function caused it, camera crash, position crash, texture drawing, sound etc...)