Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD tcpip.sys XP AND wireless issue


  • Please log in to reply

#1
storageman

storageman

    New Member

  • Member
  • Pip
  • 2 posts
Latest minidump attached.
Receiving "unattended" -meaning- I am not sitting or doing anything at the Dell Latitude D8930 when BSOD TCPIP.sys occurrs.

Additional information:
When traveling a few months back, was forced to upgrade my Minicard-wireless-DW1395 4312BG-drivers to support WPA2 and while at that location had no problems. Since returning home I have been unable to connect to my Linksys WRT300N (wired connection is fine).
Boblevy@storageman.com
Attached File  Mini031411-01.zip   24.1KB   48 downloads
  • 0

Advertisements


#2
noknojon

noknojon

    Member

  • Member
  • PipPipPip
  • 531 posts
Hi storageman and Welcome -
Please do the following as it will provide us with more information than the mini dump.

Please download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thank You -
  • 0

#3
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Your crash dump analysis

On Mon 3/14/2011 06:49:39 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini031411-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x38FA9)
Bugcheck code: 0x100000D1 (0xC, 0x2, 0x0, 0xFFFFFFFFA8478FA9)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Protocol Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


FIRSTLY still do as first advised so that if any more BSOD occurs you can then paste the report from the utility that Noknojon sent you.


1. Go device Manager , click the view tab, click to show hidden devices
Are there any warnings pls. This will be a yellow or red mark at the side of the driver entry.
If so click to open the driver and either go from there following the prompts or post the details. if you cannot deal with the issue.

2. Check especially pls the entry for the network adaptor.
Wireless and on that entry - Roll back the driver.
Check after this how the situation is.

3. If still blue screening OR no connection on Linskys remembering of course that you will presumably have to re-enter your PRESENT connection wireless key on the Linskys, as presumably that is NOT the same as when you were away.
Continue as below.

4. Uninstall the driver for the Linskys. Shut down and reboot.
Wait for the new hardware found and follow any prompts.

5. What is being used for the Wireless connection repair, that is open the wireless connection on the taskbar - right click - repair or in Control Panel. please - Windows Wireless Zero - Linksys - a Hub program ie: BT wireless connection . If you click repair you will probably see a report indicating such.

GUIDANCE
Device Manager is Start, Right click My Computer, click properties, click the hardware tab, click Device Manager.
Roll back Driver - click to open the device , then click the driver tab. - then click the Roll back. - button.
Uninstall the driver is on the same and the entry below the roll back.
To see details of devices, click the + sign by the side of the entry - ie: Network adaptors.
Post back please with details of what done and further help required with any messages received.

Edited by Macboatmaster, 14 March 2011 - 07:34 PM.

  • 0

#4
storageman

storageman

    New Member

  • Topic Starter
  • Member
  • Pip
  • 2 posts
==================================================
Dump File : Mini031411-01.dmp
Crash Time : 3/14/2011 4:56:28 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x0000000c
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0xa8478fa9
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+38fa9
File Description : TCP/IP Protocol Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5625 (xpsp_sp3_gdr.080620-1249)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini031411-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================
boblevy@storageman.com
  • 0

#5
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Storageman
All the information has already been posted for you.
I analysed your crash dump for you. and provided the guidance as to how to proceed.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP