ntkrnlmp.exe and tcpip.sys Bsods Help? windows 7

bizzarefoods · Aug 17, 2011

Hello.. Im sorry but i cannot follow the posted posting for BSODs. Reason I don't have access to the computer right now. only the dumps.

I have posted this elsewhere but it seems people are less likely to check minidumps for people

i have looked a the first to and they say ntkrnlmp.exe and the other the tcpip.sys file. So please can anyone help ?

I havent gone through most of the basics. An update might help but i dont see the computer all the time and havent been able to yet.

" Hello I'm attaching the dumps from my girlfriends computer. Its a lenovo Thinkpad (not sure model)... has an i5 though. I didn't look at it that much. I grabbed these and said i would look at them.

i see that this comes up in the first tcpip.sys ( tcpip!Ipv6pRouterSolicitationTimeout+41

the 2nd seems to be ntkrnlmp.exe

bsv report View attachment 170687 change to html lol

i haven't looked at the others will after posting this.

I will note that she has windows updates including sp1 (windows 7 btw..) to do. there might be a network update... heard that might help
lauren crash.zip
Any help would be great! Thank you !"

wish · Aug 17, 2011

Hello,
Uninstall McAfee then replace it with MSE for troubleshooting purpose.
Virus, Spyware & Malware Protection | Microsoft Security Essentials

Then update these drivers:

Code:

Tppwr64v.sys Wed Oct 18 00:40:21 2006 (4535E875) → [URL="http://support.lenovo.com/en_US/default.page?"]ThinkPad Pwr Mgmt Port[/URL]
PTUMLBUS.sys Tue Nov 02 06:58:39 2010 
PTUMLCVsp.sys Tue Nov 02 06:59:55 2010 → [URL="http://www.vzam.net/download/supported.aspx"]PANTECH  Connection Manager[/URL]
PTUMLMdm.sys Tue Nov 02 06:59:17 2010

Then we'll see how it goes.

Log

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03404000 PsLoadedModuleList = 0xfffff800`03641e70
Debug session time: Mon Aug 15 08:01:45.918 2011 (GMT-8)
System Uptime: 0 days 0:23:31.510
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : tcpip.sys ( tcpip!Ipv6pRouterSolicitationTimeout+41 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6782952f0263dec0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  a[Ì

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff80000b9c178 -- (.exr 0xfffff80000b9c178)
ExceptionAddress: fffff88002c5b691 (tcpip!Ipv6pRouterSolicitationTimeout+0x0000000000000041)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000b9c220 -- (.trap 0xfffff80000b9c220)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800806f338 rbx=0000000000000000 rcx=fffffa8008328ca0
rdx=fffff80000b9c420 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002c5b691 rsp=fffff80000b9c3b0 rbp=fffffa8007043b00
 r8=fffff80000b9c400  r9=ffeffa8008328e38 r10=fffffa8008328e38
r11=fffffa800b1c9510 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
tcpip!Ipv6pRouterSolicitationTimeout+0x41:
fffff880`02c5b691 418b4114        mov     eax,dword ptr [r9+14h] ds:c3e0:ffeffa80`08328e4c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000346c2ee to fffff80003474590

STACK_TEXT:  
fffff800`00b9b268 fffff800`0346c2ee : 00000000`0002278c fffff880`02c784c4 fffff800`00b9b9e0 fffff800`034a1524 : nt!KeBugCheck
fffff800`00b9b270 fffff800`0349a2dd : fffff800`03682b7c  fffff800`035bce68 fffff800`03404000 fffff800`00b9c178 :  nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b2a0 fffff800`034a1950 : fffff800`035c3b0c  fffff800`00b9b318 fffff800`00b9c178 fffff800`03404000 :  nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b2d0 fffff800`034ae8cf : fffff800`00b9c178  fffff800`00b9b9e0 fffff800`00000000 fffffa80`00000006 :  nt!RtlDispatchException+0x410
fffff800`00b9b9b0 fffff800`03473c02 : fffff800`00b9c178  00000000`00000000 fffff800`00b9c220 fffff800`00b9c400 :  nt!KiDispatchException+0x16f
fffff800`00b9c040 fffff800`0347250a : fffffa01`00000001  00000000`00000002 fffffa80`080d4048 fffffa80`080d4010 :  nt!KiExceptionDispatch+0xc2
fffff800`00b9c220 fffff880`02c5b691 : fffff800`00b9c678  fffffa80`0703aa30 00000000`00000000 fffffa80`07043b00 :  nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c3b0 fffff880`02c5aed2 : 00000000`00000000  fffffa80`07043b00 fffffa80`08328ca0 fffff800`00b9c3f0 :  tcpip!Ipv6pRouterSolicitationTimeout+0x41
fffff800`00b9c3e0 fffff880`02c5ad63 : 00000000`00000000  00000000`00000000 fffffa80`07043bc0 fffffa80`07043b58 :  tcpip!Ipv6pRouterDiscoveryTimeout+0x72
fffff800`00b9c460 fffff880`02c5b808 : fffffa80`07043bb8  fffffa80`07043b58 00000000`00000000 fffff800`00b9c678 :  tcpip!Ipv6pInterfaceSetTimeout+0x158
fffff800`00b9c4d0 fffff880`02c5a6b9 : 00000000`00000000  fffff800`00b9c678 00000000`00000001 fffff800`035fcc40 :  tcpip!IppCompartmentSetTimeout+0x88
fffff800`00b9c540 fffff800`0348012e : fffff800`00b9c660  00000000`000128cd 00000000`00000002 00000000`00000000 :  tcpip!IppTimeout+0x89
fffff800`00b9c570 fffff800`0347fc76 : fffffa80`0476bc68  fffffa80`0476bc68 00000000`00000000 00000000`00000000 :  nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`0348034e : 00000003`49536aba  fffff800`00b9cc58 00000000`00016170 fffff800`035f2088 :  nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`0347fb57 : 00000000`da9f4fc8  00000000`00016170 00000000`da9f4fab 00000000`00000070 :  nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`0347cd8a : fffff800`035eee80  fffff800`035fcc40 00000000`00000002 fffff880`00000000 :  nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000  fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 :  nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!Ipv6pRouterSolicitationTimeout+41
fffff880`02c5b691 418b4114        mov     eax,dword ptr [r9+14h]

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  tcpip!Ipv6pRouterSolicitationTimeout+41

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e0013b7

FAILURE_BUCKET_ID:  X64_0x1E_tcpip!Ipv6pRouterSolicitationTimeout+41

BUCKET_ID:  X64_0x1E_tcpip!Ipv6pRouterSolicitationTimeout+41

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

ntkrnlmp.exe and tcpip.sys Bsods Help? windows 7

bizzarefoods

New member

My Computer

wish

New member

My Computer