📎 AI Summary:
The thread discusses a user experiencing frequent BSODs after upgrading from Windows 8 to Windows 10, primarily with BAD_POOL_CALLER errors. A responder analyzes a bugcheck report, suggesting that McAfee security software may be causing the crashes and recommends uninstalling it using its removal tool, while also checking network drivers and uninstalling potentially problematic software like DAEMON Tools Lite. Overall, the troubleshooting focuses on driver conflicts and security software issues as potential causes of the BSODs.
L

LIl Sludgedog

New Member
Member details
Joined
Sep 9, 2015
Messages
1
Thread Author #1
After upgrading to windows 10 from windows 8 a few days ago I started getting BSODs every day at random times. Most of them have been the BAD_POOL_CALLER but the latest one was a SYSTEM_SERVICE_EXCEPTION (nvlddmkm.sys). Any help would be appreciated.
 

Attachments

Solution
kemical
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 1254, 416000c, ffffe00175acd9b0}

*** WARNING: Unable to verify timestamp for mfewfpk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfewfpk.sys
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get...
Sort by date Sort by votes
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#2
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 1254, 416000c, ffffe00175acd9b0}

*** WARNING: Unable to verify timestamp for mfewfpk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfewfpk.sys
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsCompleteOperation0+24 )

Followup: MachineOwner
Hi,
the above bugcheck means either a driver, system service or application is making a bad request and it seems the common denominator is McAfee. I can see in the Call stack (a blow by blow account of the last sub routines) that McAfee was involved.
Please uninstall McAfee for the moment and use the onboard Defender. Use McAfee's own removal tool found here:
Link Removed

Driver wise you don't look in too bad a shape although I notice an Atheros network driver on the system when your support page has drivers for a Realtek network component. Is this something you've added yourself?

athwbx.sys Wed Nov 13 08:05:17 2013: Qualcomm Atheros AR9485WB-EG Wireless Network Adapter update driver if one is available:
Link Removed

You can find other Windows 10 drivers on your support page:
http://www.gigabyte.com/products/product-page.aspx?pid=4714#driver

I also noticed this application:
dtlitescsibus.sys Mon Dec 08 10:13:10 2014: DAEMON Tools Lite Virtual SCSI Bus Driver. A known cause of bsods in some systems I would recommend uninstalling to test.

Please post any new dump files.
 
Upvote 1 Downvote
Solution
You must log in or register to reply here.