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

Windows Vista BSOD TCPIP.SYS error?


  • Please log in to reply

#1
ragingjello

ragingjello

    New Member

  • Member
  • Pip
  • 2 posts
Hi, recently I've been getting the BSOD with the normal text and the error: tcpip.sys or something along those lines. I've attached the dump file for anyone willing to help. I am running Vista SP2, and the BSOD occurs everytime I boot in normal mode (about 3 minutes in) but safe mode is always stable.

Edited by ragingjello, 14 February 2011 - 04:29 PM.

  • 0

Advertisements


#2
ragingjello

ragingjello

    New Member

  • Topic Starter
  • Member
  • Pip
  • 2 posts
Here's the dump file:
Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [J:\Mini021411-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:/symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`0340a000 PsLoadedModuleList = 0xfffff800`035cedd0
Debug session time: Mon Feb 14 20:04:52.026 2011 (UTC + 1:00)
System Uptime: 0 days 0:02:44.682
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffffa6004e6dace}

Probably caused by : tcpip.sys ( tcpip!WfpAleMatchStatefulEndpoint+9e )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffffa6004e6dace

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff8000346422e to fffff80003464490

STACK_TEXT:
fffffa60`01768a68 fffff800`0346422e : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffffa60`01768a70 fffff800`03462a78 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
fffffa60`01768bb0 fffffa60`04e6dace : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb8
fffffa60`085f6fa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpAleMatchStatefulEndpoint+0x9e


STACK_COMMAND: kb

FOLLOWUP_IP:
tcpip!WfpAleMatchStatefulEndpoint+9e
fffffa60`04e6dace e86d8dffff call tcpip!memset (fffffa60`04e66840)

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: tcpip!WfpAleMatchStatefulEndpoint+9e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME: tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c18e50c

FAILURE_BUCKET_ID: X64_0x7f_8_tcpip!WfpAleMatchStatefulEndpoint+9e

BUCKET_ID: X64_0x7f_8_tcpip!WfpAleMatchStatefulEndpoint+9e

Followup: MachineOwner
---------
  • 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