Windows 7 - BSOD with tcpip.sys on EP45-UD3R (Rev 1.1)

DBH · 02-06-2010

About 2 months ago I reformatted to Win 7 and ever since have been getting this problem. Somewhat frequently (2-3 times a week) my computer will BSOD with the following information

Stop: 0x000000D1
error in process: tcpip.sys

I looked into the problem and from what I could figure out from Google, I have faulty chipset drivers (my motherboard is a Gigabyte EP45-UD3R (Rev 1.1), Intel p45 Express chipset (series 4)). After reading this forum for a bit I learned that Intel is apparently not supporting Series 4 chipsets for Windows 7 and the only drivers Gigabyte has released for Win7 are the ones I'm using.

My question is, is there anyway to remove these BSOD's without hoping that some reliable new drivers will be eventually released? If not what reliable and safe sites should I watch for non-official drivers? The lastest .dmp file from the crash is attached.

**usasma** · 02-06-2010

Please show us the links that conclude this is a chipset driver issue.
Intel Windows 7 chipset drivers listed here: http://downloadcenter.intel.com/Sear...lation+Utility

The dump file (stack text) suggests that rt86win7.sys is the likely cause. This driver belongs to your Realtek network driver.

Please:
- download a new, Windows 7 compatible driver from Realtek: Realtek
- uninstall the currently installed Realtek driver from your system
- install the freshly downloaded driver and see if that fixes the BSOD's.

Also, please remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available Windows 7 drivers to replace the one's that you uninstall OR remove:

Quote:

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- some driver links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:

Code:

3xHybrid.sys Tue Dec 04 06:34:12 2007 -  ASUS Hybrid TV Tuner by Philips Semiconductors GmbH
COMMONFX.DLL Mon Apr 09 08:23:31 2007 - Creative Common FX Plug-in
ctaud2k.sys  Mon Apr 09 08:22:04 2007 -  Creative Audio Driver (WDM) by Creative Technology Ltd (Creative Labs Online Store)
CTAUDFX.DLL  Mon Apr 09 08:23:41 2007 -  Creative Audio Driver (WDM) by Creative Technology Ltd (Creative Labs Online Store)
ctoss2k.sys  Mon Apr 09 08:21:48 2007 - Creative OS Services Driver or Creative Audio Product by Creative Technology Ltd (Creative Labs Online Store)
ctprxy2k.sys Mon Apr 09 08:22:05 2007 - Creative Audio Driver (WDM) by Creative Technology Ltd (Creative Labs Online Store)
CTSBLFX.DLL  Mon Apr 09 08:23:53 2007 - Creative SB FX Plug-in
ctsfm2k.sys  Mon Apr 09 08:21:44 2007 - Creative SoundFont Management Device Driver or Creative Audio Product by Creative Technology Ltd (Creative Labs Online Store)
emupia2k.sys Mon Apr 09 08:21:43 2007 -  E-mu Plug-in Architecture Driver by Creative Technology Ltd (Creative Labs Online Store).
ha10kx2k.sys Mon Apr 09 08:21:50 2007 - Creative Hardware Abstract Layer Driver by Creative Technology Ltd (Creative Labs Online Store).

Summary of the BSOD:

Code:

Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Feb  6 12:49:25.638 2010 (GMT-5)
System Uptime: 0 days 16:35:06.623
BugCheck D1, {b2209000, 2, 0, 899007f8}
*** WARNING: Unable to verify timestamp for inspect.sys
*** ERROR: Module load completed but symbols could not be loaded for inspect.sys
*** WARNING: Unable to verify timestamp for Rt86win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt86win7.sys
Probably caused by : tcpip.sys ( tcpip!IN6_IS_ADDR_ISATAP+18 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System