(BSOD) tcpip.sys / Ntoskrnl.exe - Bad_Pool_Header

[BuBuBang]

I've built my own PC for the first time ever, and I've had nothing but BSOD's from the get-go. Very annoying as I can't do anything!

OS: Windows 7
Error: BAD_POOL_HEADER

I've ran RAM diagnostics, and I've ran HDD diagnostics. Both gave the all-clear, so I ran safe mode and there were no issues - bam! Software problem.

Ran bluescreenview - errors were Caused By Driver "tcpip.sys" / "ntoskrnl.exe".
I updated my Realtek LAN Driver and the problem still occurrs....

Can somebody please give me a fix or talk me through it? I'll be eternally grateful as this is the only PC in the house and we desperately need it to operate properly for basic computing needs

Thank you in advance <3

P.S. I installed all hardware / software in the same day or so, so I can't single out which hardware/software update caused the issue because I pretty much started getting issues as soon as I got the machine....But I'm starting to think it's the wifi dongle

 

[johnbl]

any bugcheck problem with tcpip.sys will be cause by your wireless drivers.
So you should update your Wired ethernet driver, your wireless ethernet driver and maybe a wireless bluetooth driver if you have one.

Note: this assumes your system is updated by windows update, and your system is not under malware attack and your memory is working correctly.

if you have updated the drivers already then run cmd.exe as an admin then run
sfc.exe /scannow
this will check for corrupted core files and attempt repair.

you might even want to do a malwarebytes scan ( but I do think you just have outdated network drivers)

the problem can also occur if you have another bad driver that is corrupting the data in memory of the driver next to it. Very common problem. Best to put a memory .dmp file on a server,make it public access and post a link. Sometimes people can spot bad versions of drivers.

 

[BuBuBang]

any bugcheck problem with tcpip.sys will be cause by your wireless drivers.
So you should update your Wired ethernet driver, your wireless ethernet driver and maybe a wireless bluetooth driver if you have one.

Note: this assumes your system is updated by windows update, and your system is not under malware attack and your memory is working correctly.

if you have updated the drivers already then run cmd.exe as an admin then run
sfc.exe /scannow
this will check for corrupted core files and attempt repair.

you might even want to do a malwarebytes scan ( but I do think you just have outdated network drivers)

the problem can also occur if you have another bad driver that is corrupting the data in memory of the driver next to it. Very common problem. Best to put a memory .dmp file on a server,make it public access and post a link. Sometimes people can spot bad versions of drivers.

I've updated the drivers 3 times and I still get those problems unfortunately, so I did the "sfc.exe" as you recommended and it's finished, but I don't know if it's made a difference haha. Haven't had the problem since, but it's come and go anyway.

I've done 4 malwarebytes scans, I get nothing.

How do I get the .dmp file sorry?

 

[johnbl]

search for files that end in .dmp
or look in c:\windows\minidump directory

you would locate the files, they are large and they are binary files so you would have to copy to a cloud server like microsoft onedrive and make them public access and then post a link to them here.

 

[BuBuBang]

I've put them on the cloud called copy.

https://copy.com/KoUJTk3HKfv4qvGz

What now mate? 😛

Thank you for the support so far by the way.

 

[johnbl]

overall,
- remove the overclocking driver (I don't think it is the cause of the problem)
- update the USB wireless driver (again, most likely not the cause. mostly the 2012 and older versions corrupt memory)

I would suspect the wired ethernet driver form 2009 as being the most likely cause of the corruption. I would remove the driver or update it from your motherboard vendor.

if you still get this bugcheck, something is corrupting your memory.
-This can be caused by bad BIOS memory timings. Update the BIOS and run memtest. (again not a likely cause of this failure)
if all else fails you have to run verifier.exe and set debug flags to force driver error checking. When a driver overwrites its own memory area. Windows will detect it and bugcheck at the time of the memory corruption and It will name the driver that corrupted memory. how to run verifier.exe :http://www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html
after you get a bugcheck you can turn use verifier.exe /reset to turn off verifier error checking to make your machine run at its normal speed. Then copy the new memory dump to a server and post a link.


================

third bugcheck is also like the first 2.
----------
second bugcheck file = 030115-25818-01.dmp is like the first, Malwarebytes Web Access Control was running and something corrupted memory and it caused a bugcheck in networking code.

-------
looked at the first bugcheck file=030115-20030-01.dmp
something corrupted the memory and cause a crash in networking code.
(the driver is most likely the victim of the corruption not the cause.)

-remove AODDriver2.sys Wed Sep 11 20:36:40 2013 this is a overclocking driver.

you have a USB wireless adaper: Ralink RT2870 series USB802.11n Wireless Adapter Driver
get the newest driver here: http://www.mediatek.com/en/downloads/
is should be the fist on the list. rt2870 chip.


Your wired ethernet driver should be updated:
RtNdPt60.sys Sun Jul 19 19:27:32 2009 ( go to your mother board vendor to get an update)
it is Realtek NDIS User mode I/O Driver - Ethernet
if you know what the chip is you can maybe get the driver here:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=7&PFid=10&Level=3&Conn=2
(it is hard to figure out the chip without looking at the motherboard spec)

 

[BuBuBang]

I downloaded the newest Ralink RT2870 series USB802.11n Wireless Adapter Driver.

I deleted RtNdPt60.sys.

I deleted AODDriver2.sys.

My internet speeds are going slower now, but if it's for the general good of not having a bluescreen, I can deal with that

I'm very grateful for your help, thank you very much!!! Have a good day now. And I'll let you know if (god forbid) this happens again.

 

[BuBuBang]

A few months have gone past and this hasn't happened. I have picked the solution. Thank you very much.