Drivers BSOD bad pool caller (c2) Windows10

Morning, My PC got BSOD as the tittle says, a couple of time while playing games and browsing the internet, maybe for loading image or video on website. I am not familiar with the debugging system and cant recognize any way to prevent or solve. Perhaps anyone could help me here.

This is my PC Specs

Motherboard : Gigabyte 945GCM-S2L (Rev 1)
Processor : Intel Dual Core E2180 2Ghz
VGA : Shappire AMD ATI Radeon HD5670
WLan/Portable Wifi : TPLink WN7200ND


Here is debugging analyze from windows debugger (I also upload the minibumb at rar file)

1: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000001254, (reserved)
Arg3: 0000000000000000, Memory contents of the pool block
Arg4: ffffe000dc1dc9c8, Address of the block of pool being deallocated

Debugging Details:
------------------


POOL_ADDRESS: ffffe000dc1dc9c8

FREED_POOL_TAG: Mdl

BUGCHECK_STR: 0xc2_7_Mdl

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER: from fffff80078889f05 to fffff80078762c20

STACK_TEXT:
ffffd000`d8739088 fffff800`78889f05 : 00000000`000000c2 00000000`00000007 00000000`00001254 00000000`00000000 : nt!KeBugCheckEx
ffffd000`d8739090 fffff801`c7d891bf : ffffe000`dc3f0ea0 00000000`b9111e95 00000000`00000001 00000000`00000001 : nt!ExFreePool+0x23d
ffffd000`d8739170 fffff801`c7f01cda : 00000000`00000002 fffff801`cba02202 00000000`00000000 00000000`00000000 : NETIO! ?? ::FNODOBFM::`string'+0x76f
ffffd000`d87391c0 fffff801`c7d61257 : 00000000`00000000 00000000`00000001 fffff801`c7e738a0 00000000`00000000 : tcpip! ?? ::FNODOBFM::`string'+0x3aaaa
ffffd000`d8739210 fffff801`c7e6661a : 00000000`00000002 ffffe000`dc419001 ffffe000`dd6a8b60 ffffe000`de087380 : NETIO!NetioDereferenceNetBufferListChain+0xe7
ffffd000`d87392c0 fffff801`c7e22bad : ffffe000`dc41fc50 00000000`03342eae ffffe000`dd02004c 0000007d`2640d73c : tcpip!TcpFlushDelay+0x7a
ffffd000`d8739350 fffff801`c7e21b99 : ffffe000`dc43b960 ffffd000`d87337c7 ffffd000`d873bb01 ffffe000`00000001 : tcpip!TcpPreValidatedReceive+0x3ad
ffffd000`d8739440 fffff801`c7e21792 : 00000002`ffffffff 00000000`00000000 00000000`00000000 00000000`00000006 : tcpip!IppDeliverListToProtocol+0x59
ffffd000`d87394f0 fffff801`c7e20be4 : 00000000`00000006 fffff800`78e6a46b ffffd000`d87395f9 00000000`00000000 : tcpip!IppProcessDeliverList+0x62
ffffd000`d8739560 fffff801`c7e21f28 : fffff801`c7fc9310 ffffe000`dc45f010 00000000`00000001 00000000`00000001 : tcpip!IppReceiveHeaderBatch+0x214
ffffd000`d8739660 fffff801`c7e8342f : ffffe000`dd76a4f0 ffffe000`dd6a8b60 ffffd000`d8739801 00000000`00000000 : tcpip!IppFlcReceivePacketsCore+0x338
ffffd000`d8739780 fffff801`c7e82a90 : 00000000`00000002 ffffd000`00000001 fffff801`c7e738a0 00000000`00000001 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x25f
ffffd000`d8739860 fffff800`786922f5 : 00000000`00000002 00000000`00000000 ffffe000`dc39d040 fffff801`c7e829d0 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xc0
ffffd000`d8739990 fffff801`c7e73cf6 : ffffe000`dc452c60 00000000`00000001 ffffe000`dc452ba0 ffffe000`dd6a8b00 : nt!KeExpandKernelStackAndCalloutInternal+0x85
ffffd000`d87399e0 fffff801`c7c395d3 : 00000000`00000000 ffffd000`d8739ae0 ffffe000`00000001 ffffe000`dd28e010 : tcpip!FlReceiveNetBufferListChain+0xb6
ffffd000`d8739a60 fffff801`c7c91e59 : ffffe000`dc39d001 fffff800`78650000 ffffd000`00000000 00000000`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x133
ffffd000`d8739b20 fffff801`c7c94023 : ffffe000`dd2601a0 00000000`00000000 ffffe000`db239001 00000000`00000002 : ndis!ndisDoPeriodicReceivesIndication+0x3bd
ffffd000`d8739c40 fffff801`c7c4d1cb : ffffe000`dc010350 ffffe000`dc3a3930 ffffd000`d8739cd9 ffffe000`db239000 : ndis!ndisPeriodicReceivesWorker+0x63
ffffd000`d8739c70 fffff800`786fb6d8 : ffffe000`db239040 ffffe000`dc39d040 ffffe000`db239040 ffffe000`db354040 : ndis!ndisReceiveWorkerThread+0x15b
ffffd000`d8739d40 fffff800`78767d06 : fffff800`78979180 ffffe000`dc39d040 ffffe000`db354040 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`d8739da0 00000000`00000000 : ffffd000`d873a000 ffffd000`d8734000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
NETIO! ?? ::FNODOBFM::`string'+76f
fffff801`c7d891bf 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: NETIO! ?? ::FNODOBFM::`string'+76f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 559f3890

IMAGE_VERSION: 10.0.10240.16384

BUCKET_ID_FUNC_OFFSET: 76f

FAILURE_BUCKET_ID: 0xc2_7_Mdl__NETIO!_??_::FNODOBFM::_string_

BUCKET_ID: 0xc2_7_Mdl__NETIO!_??_::FNODOBFM::_string_

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xc2_7_mdl__netio!_??_::fnodobfm::_string_

FAILURE_ID_HASH: {dd744697-930e-32ed-5dd0-069db36dc066}

Followup: MachineOwner
 

Attachments

  • Minidump.zip
    104.1 KB · Views: 2
This is caused by an ATI video driver

Thank you for ur respond. How do you know that the ATI caused the problems?
Btw, my ATI driver is already uptodate, by the system information given, yet the BSOD still occurred.

I hope we can find the solution once more.
Thx bfore
 

Attachments

  • AMD.jpg
    AMD.jpg
    164 KB · Views: 0
  • Minidump.zip
    54.1 KB · Views: 0

Tmagic650

Posts: 17,233   +234
Okay, pull out the ATI card and clean the gold contacts using a pencil eraser. Make sure that the video card is clean and free of dust