Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

BSOD TCPIP error


  • Please log in to reply

#1
fortybiggens

fortybiggens

    New Member

  • Member
  • Pip
  • 1 posts
Just installed Windows 8.1 and started having this issue of bsod and check the dump file and it said it was a TCPIP error. I would love some help with this cause its so annoying.

Here is my dump file. Thanks in advance



Microsoft ® Windows Debugger Version 6.3.9600.16384 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\032014-5359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*your local symbol folder*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*your local symbol folder*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0xfffff802`2740e000 PsLoadedModuleList = 0xfffff802`276d59b0
Debug session time: Thu Mar 20 00:16:37.089 2014 (UTC - 7:00)
System Uptime: 0 days 0:54:30.825
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8022b6ff020, 0, fffff8022748cccf, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PpmIdleExecuteTransition+40f )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8022b6ff020, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8022748cccf, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8022775e150
GetUlongFromAddress: unable to read from fffff8022775e208
fffff8022b6ff020

FAULTING_IP:
nt!PpmIdleExecuteTransition+40f
fffff802`2748cccf 65488b042520000000 mov rax,qword ptr gs:[20h]

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

DPC_STACK_BASE: FFFFF80228E2CFB0

TRAP_FRAME: fffff80228e24710 -- (.trap 0xfffff80228e24710)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000008
rdx=0000000000000815 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8022748cccf rsp=fffff80228e248a0 rbp=fffff80228e249a0
r8=0000000000000001 r9=0000000000028654 r10=0000048263badb25
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
nt!PpmIdleExecuteTransition+0x40f:
fffff802`2748cccf 65488b042520000000 mov rax,qword ptr gs:[20h] gs:00000000`00000020=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80227577615 to fffff8022755e0a0

STACK_TEXT:
fffff802`28e24528 fffff802`27577615 : 00000000`00000050 fffff802`2b6ff020 00000000`00000000 fffff802`28e24710 : nt!KeBugCheckEx
fffff802`28e24530 fffff802`27476ffd : 00000000`00000000 fffff802`27757a80 fffff802`28e24710 fffff802`28e24648 : nt! ?? ::FNODOBFM::`string'+0x9085
fffff802`28e245d0 fffff802`2756832f : 00000000`00000000 fffff802`276ff180 00000000`00000000 fffff802`28e24710 : nt!MmAccessFault+0x7ed
fffff802`28e24710 fffff802`2748cccf : fffff802`276ff180 fffff802`28e24900 0000000a`e770242f ffffe000`01a23450 : nt!KiPageFault+0x12f
fffff802`28e248a0 fffff802`2748c660 : fffff802`276ff180 fffff802`28e24acc fffff802`28e24ad0 fffff802`28e24ad8 : nt!PpmIdleExecuteTransition+0x40f
fffff802`28e24a90 fffff802`27561bbc : fffff802`276ff180 fffff802`276ff180 fffff802`27757a80 00000000`00000000 : nt!PoIdle+0x270
fffff802`28e24be0 00000000`00000000 : fffff802`28e25000 fffff802`28e1e000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!PpmIdleExecuteTransition+40f
fffff802`2748cccf 65488b042520000000 mov rax,qword ptr gs:[20h]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!PpmIdleExecuteTransition+40f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5215d156

IMAGE_VERSION: 6.3.9600.16384

BUCKET_ID_FUNC_OFFSET: 40f

FAILURE_BUCKET_ID: AV_nt!PpmIdleExecuteTransition

BUCKET_ID: AV_nt!PpmIdleExecuteTransition

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!ppmidleexecutetransition

FAILURE_ID_HASH: {0ced0187-972d-f83e-de87-663d75806c32}

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

Edited by fortybiggens, 20 March 2014 - 01:49 AM.

  • 0

Advertisements


#2
jcgriff2

jcgriff2

    Member

  • Expert
  • 92 posts
  • MVP

Hi -

 

Sounds like networking drivers may be an issue.

 

See if Driver Verifier  flags any 3rd party drivers -

 

http://www.sysnative...dows-vista.html

 

Update networking drivers as well!

 

Regards. . .

 

jcgriff2


  • 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