I don't recall such behavior in the 2.4.3 client from back when it was live, is the executable itself modified by your private server?
I don't recall such behavior in the 2.4.3 client from back when it was live, is the executable itself modified by your private server?
"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live." - Martin Golding
"I cried a little earlier when I had to poop" - Sku
Am I missing something here? Is there a reason he cannot post the stack trace/error report given by WowError.exe? That should make it fairly clear what the issue is...
I had the same issue until I replaced my RAM (some of them were defect). A lot of games were just crashing (also got a wide array of bluescreens, even some I never heard from before ). This might not be your problem, but should consider a hardware defect if everything else fails.
"Threads should always commit suicide - they should never be murdered" - DirectX SDK
I've had the same dilemma/problem a while ago, came up with the following ideas, but I didn't implement it.
1st idea.) Look for WowError, read the crash log from memory that contains the PID:
2nd idea.) Find a function that will only be called upon crashing. Hook it in every running instance.Code:This application has encountered a critical error: ERROR #132 (0x85100084) Fatal exception! Program: C:\Program Files (x86)\World of Warcraft\Wow.exe ProcessID: 5948
Funcs worth looking into in 3.3.5a
- 0x771D10
- 0x772B20
- 0x772760
3rd idea.) Find a static memory location that will hold a specific value that indicates that the client crashed.
For example, 0xCAD804 in 3.3.5a is always equals 1 for me upon crash. I did not look into this variable so I don't know what it is exactly.
I feel like there must be an easier, more obvious solution for this though...
Last edited by homer91; 03-02-2014 at 04:02 AM.
when client crashes,it's MainWindow Title will be "Wow", if i remember