I have bluescreen(BUGCHECK 4A) use madhook dirver.
the problem started after the driver upgrade to 3.1.18
The following figure shows problematic thread information.
If you look at the current stack of that thread in memory,
you can see that the madhook driver has been called.
However, since there is no symbol information, it is difficult to analyze it any more.
Can you help me?
I've announced in May 2018 that madCodeHook 3.1.18 is the last 3.x build. After all, madCodeHook 4.0 was released mid 2016 already! You can't expect me to provide active support for very old/outdated madCodeHook builds forever for "free". So ideally you would upgrade to madCodeHook 4.0, then check if it has the same blue screen problem, and if it does, then we can try to get to the bottom of why it happens and how to fix it.