Windows 10: Constant BSOD - BAD_POOL_CALLER/HEADER

I've been getting this BSOD for quite a while now, I've re-seated my RAM, lowered my CPU overclock back to stock, updated my drivers and removed my killer network driver and replaced it with a more stable one. Pretty much ran out of options on my end & find this pretty difficult to fix as I've never had such problem with my other computers I've built before. Thanks in advance!

:)

 

Constant BSOD's on Windows 10, when trying to play League of Legends game. errors, like "Bad Pool Header," "Faulty Hardware Corrupted Page," and "Attempted Write to ReadOnly Memory".

Everytime I try to play a game of League of Legends, I either blue screen loading in, during the game, or right before the game ends. I get a couple of random errors, like "Bad Pool Header," "Faulty Hardware Corrupted Page," and "Attempted Write to ReadOnly
Memory". I have an Nvidia Geforce GT 730 Graphics Card, and not only did I constantly try to fix if it was a driver issue, but I even clean installed new drivers twice and updated it. I still get constant BSOD's. :/

OP - Constant BSOD's on Windows 10

 

Recurring BSOD crashes after using specific software (Axure RP Pro)

The causes of the BSOD's are related to BAD_POOL_CALLER and SYSTEM_SERVICE_EXCEPTION related to the drivers; ntoskrnl.exe+16c560 and win32kbase.sys

 

The latest dump indicates a problem with mwac.sys which belongs to Malwarebytes Anti-malware.

Code: *** WARNING: Unable to verify timestamp for mwac.sys *** ERROR: Module load completed but symbols could not be loaded for mwac.sys[/quote] What anti-virus are you using? If it's BitDefender, see here: BSOD - BSOD, Crashes, Kernel Debugging - Malwarebytes Forums, see if that resolves the problem.

If not, uninstall Malwarebytes Anti-malware following Maurice's instructions here: BSOD - BSOD, Crashes, Kernel Debugging - Malwarebytes Forums

 

You also have Driver Verifier enabled, why?

Code: Verify Flags Level 0x000209bb STANDARD FLAGS: [X] (0x00000000) Automatic Checks [X] (0x00000001) Special pool [X] (0x00000002) Force IRQL checking [X] (0x00000008) Pool tracking [X] (0x00000010) I/O verification [X] (0x00000020) Deadlock detection [X] (0x00000080) DMA checking [X] (0x00000100) Security checks [X] (0x00000800) Miscellaneous checks [X] (0x00020000) DDI compliance checking ADDITIONAL FLAGS: [ ] (0x00000004) Randomized low resources simulation [ ] (0x00000200) Force pending I/O requests [ ] (0x00000400) IRP logging [ ] (0x00002000) Invariant MDL checking for stack [ ] (0x00004000) Invariant MDL checking for driver [ ] (0x00008000) Power framework delay fuzzing [ ] (0x00040000) Systematic low resources simulation [ ] (0x00080000) DDI compliance checking (additional) [ ] (0x00200000) NDIS/WIFI verification [ ] (0x00800000) Kernel synchronization delay fuzzing [ ] (0x01000000) VM switch verification [X] Indicates flag is enabled Summary of All Verifier Statistics RaiseIrqls 0x0 AcquireSpinLocks 0x0 Synch Executions 0x0 Trims 0x0 Pool Allocations Attempted 0x9ab905 Pool Allocations Succeeded 0x9ab905 Pool Allocations Succeeded SpecialPool 0x9ab905 Pool Allocations With NO TAG 0x0 Pool Allocations Failed 0x0[/quote]

 

[/quote] One of the "fixes" I found online was doing that, when I saw it wasn't successful I didn't know how to revert the change.
Thanks so much for the mwac.sys fix! I really appreciate it, you're a life saver!

 

See Part 3 here:
Driver Verifier - Enable and Disable in Windows 10