BSOD when closing a certain program BAD_POOL_HEADER ntoskrnl.exe

[solcluster3]

Hello I'm new on this forum so I'll go straight to the point to ask
I'm always get a BSOD everytime I close a game client since 2 days ago (September 17th about 10 pm +8 GMT)
The game is Elsword Online on private server (VOID Elsword)
All the BSOD I got only happen whenever I close the game client / end the game
And I had 8 BSOD so far all with the same problem

Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter : 00000000`00000020, fffff800`03647860, fffff800`03647ce0, 00000000`8548c38b
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0

I also happen to test the official server client with nothing happen whatsoever when I close the client
So I just want to know what happen to my laptop as didn't install anything before the BSOD happen
So what cause the BSOD? my antivirus or the client is faulty? but before that I can play the game normally without BSOD. So please help me and thank you.

 

[solcluster3]

no reply at all
someone please reply

 

[Golden]

Please be patient.......you've only waited a day. This section is very busy.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffff80003647860, fffff80003647ce0, 8548c38b}

*** WARNING: Unable to verify timestamp for EagleX64.sys
*** ERROR: Module load completed but symbols could not be loaded for EagleX64.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

Either update or uninstall AhnLab HackShield.

 

[solcluster3]

Ah thank you for the reply and I'm sorry for being impatient
So it the hackshield that cause the BSOD
Then seems like I have to take this problem to the game forum then

BTW is there no other choice beside update or uninstall?
I mean is it not driver conflict problem or compatibility problem?
Because there is no BSOD before that day and the game maintenance was at Thursday 18

 

[solcluster3]

A little noob question here.
Will it damage the system if I cause the BSOD intentionally?

 

[Golden]

It depends on the BSOD, but generally speaking, no it won't.

 

[solcluster3]

It depends on the BSOD, but generally speaking, no it won't.

So generally speaking will my BSOD damage my system or even my hardware?
And I want to try to run it in compatibility mode so which file should I change? The game.exe or the hack shield?

 

[Golden]

As I said, it depends on the BSOD. If it was me, I would uninstall the software to avoid system instability.

I don't know what you mean by compatibility - I suggest checking with the game developer, they will be able to advise better.

 

[solcluster3]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffff80003647860, fffff80003647ce0, 8548c38b}

*** WARNING: Unable to verify timestamp for EagleX64.sys
*** ERROR: Module load completed but symbols could not be loaded for EagleX64.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

Either update or uninstall AhnLab HackShield.

Above you said that Eaglex64.sys was the cause of BSOD but why the dump said ntoskrnl.exe cause the BSOD.
Just for a note what ntoskrnl.exe use for? I read it is the kernel for NT system.
And on above bugcheck analysis said memory_corruption. Should I check my RAM for error?

 

[Golden]

The cause is clearly identified in the. Dmp file.

You are welcome to test your RAM if you like.