Solved Random BSOD Windows 8.1 64 bit

[zmint]

I am facing Random BSOD. The most common reason shown are Bad_pool_header (tcpip.sys) and dpc_watchdog_violation
The frequency of BSOD is not in a fixed pattern. sometime it shows 2 times a day and some time it wont show even in 3 days.
I updated all the drivers but cant figure out the cause.
As per thread instructions I have attached he file generated by the tool mentioned.
Please help ....

Thanks

View attachment 67774

 

[lifetec]

The latest 5 dumpfiles are all

   *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {e, ffffd000a59b12b0, fffff8003594ab84, ff648856b516b281}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+dac )
Followup: Pool_corruption
---------
2: 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 of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Debugging Details:
------------------

BUGCHECK_STR:  0x19_e
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  [COLOR=#ff0000]chrome.exe[/COLOR]
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
LAST_CONTROL_TRANSFER:  from fffff8024a4ae61c to fffff8024a35d3a0
STACK_TEXT:  
ffffd000`ba44d1a8 fffff802`4a4ae61c : 00000000`00000019 00000000`0000000e ffffd000`a59b12b0 fffff800`3594ab84 : nt!KeBugCheckEx
ffffd000`ba44d1b0 fffff800`3582e10d : ffffffff`ffffffff ffffc000`6fd5f7a0 ac08e933`d11c00c7 ffffffff`ffffffff : nt!ExDeferredFreePool+0xdac
ffffd000`ba44d280 fffff800`3677c732 : ffffc000`736cdd20 00000000`0000000f 00000000`0000000f ffffe001`469291c0 : [COLOR=#ff0000]tcpip![/COLOR]UdpTlProviderEndpoint+0xed
ffffd000`ba44d330 fffff800`3678b74b : 00000000`00000000 ffffe001`41b17010 ffffe001`46a13010 00000000`00000000 : [COLOR=#ff0000]afd![/COLOR]AfdCreate+0x5712
ffffd000`ba44d480 fffff802`4a5fa641 : 00000000`00000005 ffffd000`ba44d7e1 00000000`00000000 00000000`00000000 : afd!AfdDispatch+0x8b
ffffd000`ba44d4e0 fffff802`4a6b0114 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe001`4235b030 : nt!IopParseDevice+0x6c1
ffffd000`ba44d700 fffff802`4a607203 : 00000000`00000000 ffffd000`ba44d8a8 00000000`00000042 ffffe001`40900b00 : nt!ObpLookupObjectName+0x784
ffffd000`ba44d830 fffff802`4a66e95b : 000100e0`00000001 ffffe001`41721ba8 00000000`00000001 00000000`00000020 : nt!ObOpenObjectByName+0x1e3
ffffd000`ba44d960 fffff802`4a66e5e8 : 0000005e`0cfbe3e0 ffffd000`c0140000 0000005e`0cfbe410 ffffe001`416998c0 : nt!IopCreateFile+0x36b
ffffd000`ba44da00 fffff802`4a368bb3 : 00000000`00000102 ffffd000`ba44dad8 00000000`00000000 0000005e`00000001 : nt!NtCreateFile+0x78
ffffd000`ba44da90 00007ff8`ed660c0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000005e`0cfbe308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`ed660c0a

info:
STOP 0x00000019: BAD_POOL_HEADER
Usual causes: Device driver

tcpip.sys
Driver Description: Microsoft TCP/IP Driver (networking related)
Driver Update Site: Windows Update
afd.sys
Driver Description: Ancillary Function Driver for WinSock
Driver Update Site: Windows Update

As you can see the dumpfiles are not blaming a specific driver as the cause, but it is all network related.
Also in all the dumpfiles Chrome.exe is mentioned in the process

Looking through the driver modules i found that your VMWare has driver from early 2013 (prewindows 8.1).
Please update and report.

The other dumpfile with

    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, 0, 0}
*** WARNING: Unable to verify timestamp for networx.sys
*** ERROR: Module load completed but symbols could not be loaded for networx.sys
Probably caused by : tdx.sys ( tdx!TdxSendDatagramTransportAddress+2db )

The dumpfile names networx.sys.

Driver Description: NetWorx
Driver Update Site: http://www.softperfect.com/products/networx/
Please update to the latest version.

 

[zmint]

Thanks for the help.
So you mean I need to update VMware and Networx only ? Nothing else need to be done ?
I am on my way to update these 2 programs. ......

 

[zmint]

As you suggested ... I have updated Vmware and Networx ..... Let us hope this resolves the issue ...

 

[zmint]

it happened again with error dpc_watchdog_violation
should I remove VMware and Networx ?
I can do without them.

here is the latest crash report generated ....
View attachment 67802
Pleases help ...

 

[lifetec]

The latest dumpfile blames again networx.

So i would first only remove networx and see if this stops the BSOD.

 

[zmint]

Yes I removed that ... Fingers Crossed ....

 

[zmint]

It is calm most of the time.... just got one today driver_irql_not_less_or_equal (ndis.sys)
Latest report attached

View attachment 67815

 

[lifetec]

Both dumpfiles blames

 *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {29, 2, 0, fffff801260e4a6a}

*** WARNING: Unable to verify timestamp for Rtnic64.sys
*** ERROR: Module load completed but symbols could not be loaded for Rtnic64.sys
Probably caused by : raspppoe.sys ( raspppoe!DerefPppoePacket+123 )

Rtnic64 Thu Jan 23 10:01:19 2014
You have a Realtek RTL8139/810x Family Fast Ethernet NIC


Driver Description: Realtek Ethernet NIC driver

Driver Update Site: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=7&PFid=10&Level=3&Conn=2

 

[axe0]

Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.

  <ActivePartialProductKey>[COLOR="#FF0000"]9D6T9[/COLOR]</ActivePartialProductKey>
  <ActiveProductKeyPid2>[COLOR="#FF0000"]00261-50000-00000-AA497[/COLOR]</ActiveProductKeyPid2>
  <OSVersion>6.3.9600.2.00010100.0.0.048</OSVersion>
  <ProductName>Windows 8.1 Pro</ProductName>
  <ProcessorArchitecture>x64</ProcessorArchitecture>
  <EditionId>Professional</EditionId>
  <BuildLab>9600.winblue_ltsb.160303-0600</BuildLab>
  <TimeZone>India Standard Time(GMT+05:30)</TimeZone>
  <ActiveSkuId>c06b6981-d7fd-4a35-b7b4-054742b7af67</ActiveSkuId>
  <ActiveSkuDescription>Windows(R) Operating System, [COLOR="#FF0000"]VOLUME_KMSCLIENT[/COLOR] channel</ActiveSkuDescription>
  <ProductUniquenessGroups>55c92734-d682-4d71-983e-d6ec3f16059f</ProductUniquenessGroups>
  <ActiveProductKeyPKeyId>ace182fe-75fe-ee4b-31e7-9fb20a237002</ActiveProductKeyPKeyId>
  <ActiveProductKeyPidEx>06401-02615-000-000000-03-16393-9600.0000-3022013</ActiveProductKeyPidEx>
  <ActiveProductKeyChannel>[COLOR="#FF0000"]Volume:GVLK[/COLOR]</ActiveProductKeyChannel>
  <ActiveVolumeCustomerPid>06401-00152-312-957543-03-1033-9600.0000-0862016</ActiveVolumeCustomerPid>
  <OfflineInstallationId>096032320082238400286837987572300828913063394023583976548681524</OfflineInstallationId>
  <DomainJoined>false</DomainJoined>

Forum rules

4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).

 

[zmint]

The Problem is gone ......No more crashes ... peace and only peace ....
Will report back after waiting few more days ....

Thanks

 

[zmint]

The Problems is SOLVED .... No more crashes at all .... It was Networx doing all this ...
Thanks Everyone who helped me ...

 

[lifetec]

Great to hear.