Windows 10: Blue Screen Since Anniversary Update

I keep getting the odd blue screen since the anniversary update. I think it's network related, the network driver. I've uninstalled it and reinstalled it but it keeps happening. Any ideas? Attached is the zip file as per rules of posting on this section.

:)

 

Black screen issues after the Anniversary Update on Windows 10

Prior to Anniversary addition update My Win 10 computer booted somewhere between 30 and 40 seconds. Since the Anniversary addition it takes anywhere fro Two to Three minutes to Boot. On start up I get the black screen with the blue box and the dots going
in circles for a few seconds, then it changes to a black screen without the blue box and the dots going in circles for a couple minuets (like it's installing updates) before the computer starts.

Should I try to uninstall the update?

This is driving me up a wall with the excessive boot times.

Aloha

Dave

Original title: Windows 10 Anniversary addition Boot problem

 

Blue screen seems worse since anniversary update

Mines a Dell laptop.

 

Correct, except for the network drivers part.

See if McAfee has software updates, or remove it as a test.
Driver Reference Table - mfewfpk.sys
Uninstall *Arrow Solved Anti Virus (AV) stand alone removal tools - Windows 10 Forums

Per the parameters it is that a pool was double freed, in this case by a McAfee driver.
However, the thing is I don't see the first freeing being happening, we can only see a pool being allocated.
Unfortunately investigation is impossible with a minidump, if you don't mind please upload a kernel dump (C:\Windows\MEMORY.dmp) to a 3rd party uploader like onedrive, google drive, dropbox and post a share link in your next reply.

Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_CALLER (c2) The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc. Arguments: Arg1: 0000000000000007, Attempt to free pool which was already freed Arg2: 0000000000000000, (reserved) Arg3: 0000000000000074, Memory contents of the pool block Arg4: ffffe70d0ec54eb8, Address of the block of pool being deallocated 2: kd> k # Child-SP RetAddr Call Site 00 ffff9580`99071068 fffff800`15cd9ced nt!KeBugCheckEx 01 ffff9580`99071070 fffff804`ed9817f8 nt!ExAllocatePoolWithTag+0xf1d 02 ffff9580`99071150 fffff804`edb04890 NETIO! ?? ::FNODOBFM::`string'+0x9d98 03 ffff9580`990711a0 fffff804`ed95fcee tcpip+0x104890 04 ffff9580`990711f0 fffff804`ed95fa9b NETIO!NetioDereferenceNetBufferList+0x10e 05 ffff9580`99071270 fffff804`eda26440 NETIO!NetioDereferenceNetBufferListChain+0x29b 06 ffff9580`99071330 fffff804`eda28335 tcpip+0x26440 07 ffff9580`99071430 fffff804`edb611e8 tcpip+0x28335 08 ffff9580`99071550 fffff804`edc94fb6 tcpip+0x1611e8 09 ffff9580`99071590 fffff800`15af1e75 fwpkclnt!FwppInjectionStackCallout+0x116 0a ffff9580`99071620 fffff804`edc968e6 nt!KeExpandKernelStackAndCalloutInternal+0x85 0b ffff9580`99071670 fffff804`edc96543 fwpkclnt!NetioExpandKernelStackAndCallout+0x52 0c ffff9580`990716b0 fffff804`edd30e3b fwpkclnt!FwpsInjectTransportReceiveAsync0+0x2d3 0d ffff9580`990717f0 ffffe70d`0d81d950 mfewfpk+0x10e3b 0e ffff9580`990717f8 00000000`00000000 0xffffe70d`0d81d950[/quote]

 

[/quote] Can't seem to find
(C:\Windows\MEMORY.dmp).

 

How is your recovery settings configured? *Arrow BSOD Minidump - Configure to Create in Windows 10 - Windows 10 Forums

 

OK, no problem. Please follow my suggestion for McAfee.

 

Okay will do. Thanks for your help.