Jump to content

BAD_POOL_HEADER caused by afd.sys

IvanC123
By IvanC123
in Troubleshooting
 Share
Posted

So I just bought a new PC and its like 2 months old.
When I installed the windows (8.1) for the first time I was getting 2 BSOD'S.
First I got the MEMORY_MANAGEMENT BSOD and later I got PFN_LIST_CORRUPT BSOD.
I thought reinstalling Windows may solve the problem so I installed a fresh Windows 8.1 and now I'm getting the BAD_POOL_HEADER BSOD.
The interesting thing is that all 3 are potentially caused by bad RAM and I have a single DIMM of Corsair ValueSelect 8GB DDR3-1600MHz.
Is it possible that I bought faulty RAM or is it caused by something else ?

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

So I just bought a new PC and its like 2 months old.

When I installed the windows (8.1) for the first time I was getting 2 BSOD'S.

First I got the MEMORY_MANAGEMENT BSOD and later I got PFN_LIST_CORRUPT BSOD.

I thought reinstalling Windows may solve the problem so I installed a fresh Windows 8.1 and now I'm getting the BAD_POOL_HEADER BSOD.

The interesting thing is that all 3 are potentially caused by bad RAM and I have a single DIMM of Corsair ValueSelect 8GB DDR3-1600MHz.

Is it possible that I bought faulty RAM or is it caused by something else ?

Follow the BSOD posting instructions pinned at the top of the troubleshooting subforum: http://linustechtips.com/main/topic/354634-bsod-posting-instructions-please-read/

 

Once we get the dump files, we'll be able to take a look at what drivers or Windows' components are being problematic.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

When i try to run the "perfmon /report" command in cmd, it opens the resource and performance monitor and then i get the error message 
"The operator or administrator has refused the request."

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

When i try to run the "perfmon /report" command in cmd, it opens the resource and performance monitor and then i get the error message 

"The operator or administrator has refused the request."

We don't necessarily need that now, it would be handy though. For now, skip that step.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

So you want me to just give you the dump file from the minidump folder ?

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

So you want me to just give you the dump file from the minidump folder ?

Yup, that should be enough for now.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

So, how do I do that ?

By following the instructions here: http://linustechtips.com/main/topic/354634-bsod-posting-instructions-please-read/

Method A should still work. just skip the perfmon section.

Or do method B and skip the perfmon section.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted (edited)

So, I took a look.

What version Nvidia driver are you running at the moment? "NvStreamKms" belongs to nVidia Streaming Kernel service and it managed to overlap some memory (possible memory leak) which caused the BSOD.

 

You're best bet would be to use Dsplay Driver Uninstaller from here: http://www.guru3d.com/files-details/display-driver-uninstaller-download.html to remove your nVidia driver and then re-install the latest nVidia driver from here: http://www.nvidia.com/Download/index.aspx

 

While you're at it, you have no devices in device manager that show up as unknown or have a yellow triangle next to it? (Just want to verify that you have all your needed drivers installed.)

********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 19, {25, 20, 1, ffffe00008c84dc0}Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cd6 )Followup: Pool_corruption---------3: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************BAD_POOL_HEADER (19)The pool is already corrupt at the time of the current request.This may or may not be due to the caller.The internal pool links must be walked to figure out a possible cause ofthe problem, and then special pool applied to the suspect tags or the driververifier to a suspect driver.Arguments:Arg1: 0000000000000025, Arg2: 0000000000000020Arg3: 0000000000000001Arg4: ffffe00008c84dc0Debugging Details:------------------OVERLAPPED_MODULE: Address regions for 'NvStreamKms' and 'WUDFRd.sys' overlapBUGCHECK_STR:  0x19_25CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  svchost.exeCURRENT_IRQL:  2ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freLAST_CONTROL_TRANSFER:  from fffff8016f716456 to fffff8016f5d10a0STACK_TEXT:  ffffd000`242c3ed8 fffff801`6f716456 : 00000000`00000019 00000000`00000025 00000000`00000020 00000000`00000001 : nt!KeBugCheckExffffd000`242c3ee0 fffff800`0179c50e : ffffe000`08c84dd0 00000000`00000006 00000000`00000000 00000000`206c644d : nt!ExDeferredFreePool+0xcd6ffffd000`242c3fb0 fffff800`01754c79 : ffffe000`046ed200 00610063`00002300 00000000`00000000 ffffe000`03df3b10 : afd!AfdSetupReceiveDatagramIrp+0x39effffd000`242c4070 fffff800`0179a033 : ffffe000`04112540 006b0072`00000028 ffffe000`03df3b10 fffff800`00d09734 : afd!AfdReceiveDatagramEventCommonHandler+0x309ffffd000`242c41e0 fffff800`00d29361 : 00000000`00000000 fffff800`0000004c 00000000`00000000 ffffe000`04112540 : afd!AfdTLDgramReceiveEventHandler+0x123ffffd000`242c42b0 fffff800`00d26dbc : ffffe000`04897300 00000000`00000028 ffffd000`00000000 ffffd000`242c44d0 : tcpip!UdpDeliverDatagrams+0x181ffffd000`242c4450 fffff800`00d268ff : ffffc000`00239d30 ffffad3d`6158170c ffffd000`242c4ac8 fffff801`6fb2a1d8 : tcpip!UdpReceiveDatagrams+0x223ffffd000`242c48f0 fffff800`00d25ad3 : ffffc000`00239d30 00000000`005f0380 00000000`00000001 ffffffff`ffffffff : tcpip!IppDeliverListToProtocol+0x4fffffd000`242c49b0 fffff800`00d261ac : 00000000`00000000 ffffe000`04112500 a9824c25`59eb7418 ffffd000`242c4ab8 : tcpip!IppProcessDeliverList+0x63ffffd000`242c4a50 fffff800`00cd4b20 : ffffe000`04112540 ffffe000`02ef8010 00000000`00000002 ffffd000`242c4c68 : tcpip!IppReceiveHeaderBatch+0x1fcffffd000`242c4b80 fffff800`00cd37fe : 00000000`00000000 00000000`00000011 00000000`00000000 00000000`00000000 : tcpip!IppLoopbackIndicatePackets+0x330ffffd000`242c4c60 fffff800`00ceeb7c : 00000000`00000500 00000000`00000000 00000000`00000002 ffffe000`0a0e0670 : tcpip!IppLoopbackEnqueue+0x3beffffd000`242c53a0 fffff800`00cefa6d : fffff800`00e87370 ffffe000`0a0e0600 00000000`00000000 ffffe000`0a0e07b0 : tcpip!IppDispatchSendPacketHelper+0x39cffffd000`242c5530 fffff800`00ced722 : 00000000`00000000 00000000`00000017 ffffd000`242c5a40 ffffe000`0151fa58 : tcpip!IppPacketizeDatagrams+0x2ddffffd000`242c56d0 fffff800`00cfe312 : 00000000`00000000 ffffe000`032df204 fffff800`00e87370 ffffe000`0465f010 : tcpip!IppSendDatagramsCommon+0x4a2ffffd000`242c58b0 fffff800`00cdc35e : 00000000`00000000 00000000`0000d40d 00000000`0000d40d 00000000`0000080a : tcpip!IpNlpSendDatagrams+0x42ffffd000`242c58f0 fffff800`00cdc9ba : ffffe000`04e326a0 ffffe000`047a9868 ffffd000`242c5e10 fffff800`00e87370 : tcpip!UdpSendMessagesOnPathCreation+0x42effffd000`242c5d10 fffff800`00cdf9cc : 00000000`206c0000 00010101`011fffff ffffe000`0fa9e880 00000000`00000000 : tcpip!UdpSendMessages+0x1daffffd000`242c6140 fffff801`6f51dfa9 : 00000000`00000000 e9fe1463`00000000 ffffc000`08b66020 00000000`00000000 : tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x15ffffd000`242c6170 fffff800`00cdf92c : fffff800`00cdf9b8 ffffd000`242c62f0 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0xe9ffffd000`242c62c0 fffff800`0179a629 : ffffe000`047a95a0 ffffd000`242c6b80 ffffe000`047a95a0 ffffe000`047a95a0 : tcpip!UdpTlProviderSendMessages+0x6cffffd000`242c6340 fffff800`017820ca : ffffe000`04431140 00000000`00000000 00000000`000000c8 ffffd000`242c6660 : afd!AfdFastDatagramSend+0x579ffffd000`242c6500 fffff801`6f84af47 : ffffe000`04897070 00000000`00000000 ffffd000`242c6880 ffffd000`242c6880 : afd!AfdFastIoDeviceControl+0x10bbffffd000`242c6870 fffff801`6f84bd2a : ffffd000`001f0003 00000000`00000000 00000000`00000000 00000063`8cd68a18 : nt!IopXxxControlFile+0x3f7ffffd000`242c6a20 fffff801`6f5dc8b3 : ffffe000`746c6644 ffffd000`242c6b08 00000000`00000000 00007ff7`cdb48710 : nt!NtDeviceIoControlFile+0x56ffffd000`242c6a90 00007ffc`51b07b4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000063`b282d7b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`51b07b4aSTACK_COMMAND:  kbFOLLOWUP_IP: nt!ExDeferredFreePool+cd6fffff801`6f716456 cc              int     3SYMBOL_STACK_INDEX:  1SYMBOL_NAME:  nt!ExDeferredFreePool+cd6FOLLOWUP_NAME:  Pool_corruptionIMAGE_NAME:  Pool_CorruptionDEBUG_FLR_IMAGE_TIMESTAMP:  0IMAGE_VERSION:  6.3.9600.16384MODULE_NAME: Pool_CorruptionBUCKET_ID_FUNC_OFFSET:  cd6FAILURE_BUCKET_ID:  0x19_25_nt!ExDeferredFreePoolBUCKET_ID:  0x19_25_nt!ExDeferredFreePoolANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:0x19_25_nt!exdeferredfreepoolFAILURE_ID_HASH:  {680ab642-66fb-4ff9-27f7-315ec4127c9b}Followup: Pool_corruption---------3: kd> lmvm Pool_Corruptionstart             end                 module name3: kd> !threadGetPointerFromAddress: unable to read from fffff8016f7d1000THREAD ffffe0000fa9e880  Cid 02ec.08c0  Teb: 00007ff7cdb47000 Win32Thread: 0000000000000000 RUNNING on processor 3Not impersonatingGetUlongFromAddress: unable to read from fffff8016f720310Owning Process            ffffe00004431140       Image:         svchost.exeAttached Process          N/A            Image:         N/Afffff78000000000: Unable to get shared dataWait Start TickCount      6226816      Context Switch Count      9982           IdealProcessor: 0             ReadMemory error: Cannot get nt!KeMaximumIncrement value.UserTime                  00:00:00.000KernelTime                00:00:00.000Win32 Start Address 0x00007ffc51a92850Stack Init ffffd000242c6c90 Current ffffd000242c6440Base ffffd000242c7000 Limit ffffd000242c1000 Call 0Priority 9 BasePriority 8 UnusualBoost 1 ForegroundBoost 0 IoPriority 2 PagePriority 5Child-SP          RetAddr           : Args to Child                                                           : Call Siteffffd000`242c3ed8 fffff801`6f716456 : 00000000`00000019 00000000`00000025 00000000`00000020 00000000`00000001 : nt!KeBugCheckExffffd000`242c3ee0 fffff800`0179c50e : ffffe000`08c84dd0 00000000`00000006 00000000`00000000 00000000`206c644d : nt!ExDeferredFreePool+0xcd6ffffd000`242c3fb0 fffff800`01754c79 : ffffe000`046ed200 00610063`00002300 00000000`00000000 ffffe000`03df3b10 : afd!AfdSetupReceiveDatagramIrp+0x39effffd000`242c4070 fffff800`0179a033 : ffffe000`04112540 006b0072`00000028 ffffe000`03df3b10 fffff800`00d09734 : afd!AfdReceiveDatagramEventCommonHandler+0x309ffffd000`242c41e0 fffff800`00d29361 : 00000000`00000000 fffff800`0000004c 00000000`00000000 ffffe000`04112540 : afd!AfdTLDgramReceiveEventHandler+0x123ffffd000`242c42b0 fffff800`00d26dbc : ffffe000`04897300 00000000`00000028 ffffd000`00000000 ffffd000`242c44d0 : tcpip!UdpDeliverDatagrams+0x181ffffd000`242c4450 fffff800`00d268ff : ffffc000`00239d30 ffffad3d`6158170c ffffd000`242c4ac8 fffff801`6fb2a1d8 : tcpip!UdpReceiveDatagrams+0x223ffffd000`242c48f0 fffff800`00d25ad3 : ffffc000`00239d30 00000000`005f0380 00000000`00000001 ffffffff`ffffffff : tcpip!IppDeliverListToProtocol+0x4fffffd000`242c49b0 fffff800`00d261ac : 00000000`00000000 ffffe000`04112500 a9824c25`59eb7418 ffffd000`242c4ab8 : tcpip!IppProcessDeliverList+0x63ffffd000`242c4a50 fffff800`00cd4b20 : ffffe000`04112540 ffffe000`02ef8010 00000000`00000002 ffffd000`242c4c68 : tcpip!IppReceiveHeaderBatch+0x1fcffffd000`242c4b80 fffff800`00cd37fe : 00000000`00000000 00000000`00000011 00000000`00000000 00000000`00000000 : tcpip!IppLoopbackIndicatePackets+0x330ffffd000`242c4c60 fffff800`00ceeb7c : 00000000`00000500 00000000`00000000 00000000`00000002 ffffe000`0a0e0670 : tcpip!IppLoopbackEnqueue+0x3beffffd000`242c53a0 fffff800`00cefa6d : fffff800`00e87370 ffffe000`0a0e0600 00000000`00000000 ffffe000`0a0e07b0 : tcpip!IppDispatchSendPacketHelper+0x39cffffd000`242c5530 fffff800`00ced722 : 00000000`00000000 00000000`00000017 ffffd000`242c5a40 ffffe000`0151fa58 : tcpip!IppPacketizeDatagrams+0x2ddffffd000`242c56d0 fffff800`00cfe312 : 00000000`00000000 ffffe000`032df204 fffff800`00e87370 ffffe000`0465f010 : tcpip!IppSendDatagramsCommon+0x4a2ffffd000`242c58b0 fffff800`00cdc35e : 00000000`00000000 00000000`0000d40d 00000000`0000d40d 00000000`0000080a : tcpip!IpNlpSendDatagrams+0x42ffffd000`242c58f0 fffff800`00cdc9ba : ffffe000`04e326a0 ffffe000`047a9868 ffffd000`242c5e10 fffff800`00e87370 : tcpip!UdpSendMessagesOnPathCreation+0x42effffd000`242c5d10 fffff800`00cdf9cc : 00000000`206c0000 00010101`011fffff ffffe000`0fa9e880 00000000`00000000 : tcpip!UdpSendMessages+0x1daffffd000`242c6140 fffff801`6f51dfa9 : 00000000`00000000 e9fe1463`00000000 ffffc000`08b66020 00000000`00000000 : tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x15ffffd000`242c6170 fffff800`00cdf92c : fffff800`00cdf9b8 ffffd000`242c62f0 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0xe9ffffd000`242c62c0 fffff800`0179a629 : ffffe000`047a95a0 ffffd000`242c6b80 ffffe000`047a95a0 ffffe000`047a95a0 : tcpip!UdpTlProviderSendMessages+0x6cffffd000`242c6340 fffff800`017820ca : ffffe000`04431140 00000000`00000000 00000000`000000c8 ffffd000`242c6660 : afd!AfdFastDatagramSend+0x579ffffd000`242c6500 fffff801`6f84af47 : ffffe000`04897070 00000000`00000000 ffffd000`242c6880 ffffd000`242c6880 : afd!AfdFastIoDeviceControl+0x10bbffffd000`242c6870 fffff801`6f84bd2a : ffffd000`001f0003 00000000`00000000 00000000`00000000 00000063`8cd68a18 : nt!IopXxxControlFile+0x3f7ffffd000`242c6a20 fffff801`6f5dc8b3 : ffffe000`746c6644 ffffd000`242c6b08 00000000`00000000 00007ff7`cdb48710 : nt!NtDeviceIoControlFile+0x56ffffd000`242c6a90 00007ffc`51b07b4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ ffffd000`242c6b00)00000063`b282d7b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`51b07b4a 
Edited by ionbasa

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

I'm currently running the latest version which is the 355.60 
But I don't get it, gpu drivers are the first thing I installed when I reinstalled Windows and I'm pretty sure that's a clean install.
I'll try to uninstall drivers with the program you suggested me, then reinstall them. And I have no yellow triangles in the device manager :D

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

I'm currently running the latest version which is the 355.60 

But I don't get it, gpu drivers are the first thing I installed when I reinstalled Windows and I'm pretty sure that's a clean install.

I'll try to uninstall drivers with the program you suggested me, then reinstall them. And I have no yellow triangles in the device manager :D

If you already have the latest driver, you could also try a previous driver revision. Just in case the current one is buggy.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Okay, I uninstalled the drivers with the "display driver uninstaller" and I reinstalled them. For now, everything seems to work perfectly fine and I had no BSOD's 

Link to comment
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×