Access violation

[needsupport22]

Hey there, this popped up while around 100 players were online and caused the server to freeze and require force shutdown and restart. https://gyazo.com/d6723e9bff527463fbb7aae94edb815a Any page where all these error codes are listed with explanation? Or can someone tell me the fix for this specific one please, thanks for your time.

[Kent Briggs]

Do you have larger images? You only posted thumbnails. I can sometimes trace raw addresses back to source code lines using the .map file created by my compiler. Were there any entries recorded in your Error Log file around that same time?

[Kent Briggs]

Also, which version and edition are you running?

[needsupport22]

This was on PM 4.43 gold, 64 bit, I could not access the error codes as the client was frozen upon opening on the tournaments tab, those code pop ups in the gyazo is all I could see

[needsupport22]

I think it says " 000000000040E875 "

[Kent Briggs]

Everything that appears on the Logs tab gets written to daily Error log files and Event log files in the data folder so you can always check those after the fact. And you should definitely patch up to 4.50, the last version 4 update:

http://www.briggsoft.com/patches.htm

[needsupport22]

Ok so I found it in the error logs, it says

2017-10-28 18:16:50|Invalid account file found: C:\Users\root\AppData\Roaming\Poker Mavens 4\Accounts\unsunghero.dat which appears on various error logs, any way for me to delete this account as it doesn't show in the poker mavens client

[needsupport22]

2017-10-29 18:36:46|Invalid account file found: C:\Users\root\AppData\Roaming\Poker Mavens 4\Accounts\unsunghero.dat here it shows again after the site crashed once more

[Kent Briggs]

2017-10-29 18:36:46|Invalid account file found: C:\Users\root\AppData\Roaming\Poker Mavens 4\Accounts\unsunghero.dat here it shows again after the site crashed once more

You can just delete that file directly.

[Kent Briggs]

You can just delete that file directly.

That will of course kill the account. You might first try loading it into NotePad and see if there is any recoverable information in it.