jumper Posted January 16, 2015 Author Share Posted January 16, 2015 Avoiding the problem is of no help in solving the problem! Please try to reproduce the "MPREXE caused an invalid page fault inmodule KERNELEX.DLL" problem with first release.0 and then release.4. The latter should detect the NULL pointer before the crash and display first a "storage #x is NULL" messagebox and then a deep stack dump messagebox. I need to know the value of #x and the contents of the stack dump (should be on the clipboard). Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now