BSOD Bad Pool Caller

[Elite2014]

I am suddenly getting a BSOD that happens a couple times a week with the error, BAD_POOL_CALLER. I tried updating as much drivers as I could and ran the SFC Scanner in the Command Prompt, but that did not find anything. Can someone please help me figure out what is wrong with my computer? I'm uploading my most recent dmp file (happened earlier today).

dmp file: http://s000.tinyupload.com/?file_id=67213486148873096976

 

[Laptop_Nerd]

Hi,

Please do try these troubleshooting steps that may help.
- First is to run Windows Update and install all the update available.
- Once done, do run SFC Scanner.
- Search for Command Prompt, right click on it and select Run as Administrator.
- Once open, type sfc/scannow then press Enter. While until it finish the scan and see if it will solve the issue or not.
- If these steps will not work, proceed with doing a clean install of the graphics card driver.
- Go to Device Manager and uninstall the graphics driver.
- Next is to open Programs and Features then uninstall anything related to the graphics card.
- Once done, download and install the latest driver.
- Reboot the laptop once the latest driver has been installed then test it again.
- If the same problem will persist, do also run a memory test just to make sure everything is working properly.
- If all test will pass, last option would be to reinstall Windows 10.

 

[johnbl]

first, you have 3 copies of overclocking software, remove them:
C:\Program Files (x86)\MSI\Command Center\DDR\NTIOLib_X64.sys Mon Nov 26 02:11:53 2012
C:\Program Files (x86)\MSI\Fast Boot\NTIOLib_X64.sys Thu Oct 25 18:46:44 2012
C:\Program Files (x86)\MSI\Super Charger\NTIOLib_X64.sys Thu Oct 25 03:27:58 2012

these are running out of different directories at the same time, it is a old version that does not understand the new voltage tweaking
requirements of your new cpu (Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz)
IE they are applying the incorrect voltages to the CPU (too high voltages)

the actual bugcheck was in networking code called by your McAfee virus scanner.
It looks like it resulted in an attempt to free the same memory twice. the first time was ok, but the second time the driver was no longer the owner so the system bugchecked. This can be a bug in the virus driver or may be a bug in one of the ethernet drivers (or timing related to the overclock driver)

if I were to guess you have some other problem going on with your system sleeping

your key device drivers look like they are relatively current. I would remove the overclocking software and just see if you can get another bugcheck.
typically though you would not get this bugcheck being caused by a overclocking driver. Ie, I still think you have 2 more problems to resolve after you fix the overclock driver problem.

 

[Elite2014]

first, you have 3 copies of overclocking software, remove them:
C:\Program Files (x86)\MSI\Command Center\DDR\NTIOLib_X64.sys Mon Nov 26 02:11:53 2012
C:\Program Files (x86)\MSI\Fast Boot\NTIOLib_X64.sys Thu Oct 25 18:46:44 2012
C:\Program Files (x86)\MSI\Super Charger\NTIOLib_X64.sys Thu Oct 25 03:27:58 2012

these are running out of different directories at the same time, it is a old version that does not understand the new voltage tweaking
requirements of your new cpu (Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz)
IE they are applying the incorrect voltages to the CPU (too high voltages)

the actual bugcheck was in networking code called by your McAfee virus scanner.
It looks like it resulted in an attempt to free the same memory twice. the first time was ok, but the second time the driver was no longer the owner so the system bugchecked. This can be a bug in the virus driver or may be a bug in one of the ethernet drivers (or timing related to the overclock driver)

if I were to guess you have some other problem going on with your system sleeping

your key device drivers look like they are relatively current. I would remove the overclocking software and just see if you can get another bugcheck.
typically though you would not get this bugcheck being caused by a overclocking driver. Ie, I still think you have 2 more problems to resolve after you fix the overclock driver problem.

Okay, I removed the overclock software and will see if this might solve it. I will update if the problem happens again.