Bluescreen tcpip.sys

tranced · November 11, 2009

astept sa raspunda si vdragosh pe aici , ca doar de la start.exe e buba

LiNU · November 11, 2009

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Nov 11 12:04:40.338 2009 (GMT+2)
System Uptime: 3 days 22:32:41.496
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {c, 2, 0, b68acc66}

Probably caused by : tcpip.sys ( tcpip!TCPAbortAndIndicateDisconnect+23 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b68acc66, address which referenced memory

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


READ_ADDRESS:  0000000c 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!TCPAbortAndIndicateDisconnect+23
b68acc66 8b400c          mov     eax,dword ptr [eax+0Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  start.exe

LAST_CONTROL_TRANSFER:  from b689d9e9 to b68acc66

STACK_TEXT:  
a66fc8f0 b689d9e9 027430e0 a66fca90 856989c0 tcpip!TCPAbortAndIndicateDisconnect+0x23
a66fcb40 b687aa55 0000000e 00000003 804f0cf3 tcpip!TdiSetInformationEx+0x27f
a66fcbec b687a07c 856989c0 85698a30 85698a30 tcpip!IPSGetTotalCounts+0x24
a66fcc08 b687a034 856989c0 85698a30 882fe608 tcpip!ARPQueryInfo+0x78
a66fccd4 00000000 89a1fbd8 887e0820 a66fcd48 tcpip!ARPQueryInfo+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!TCPAbortAndIndicateDisconnect+23
b68acc66 8b400c          mov     eax,dword ptr [eax+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  tcpip!TCPAbortAndIndicateDisconnect+23

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  44477c19

FAILURE_BUCKET_ID:  0xD1_tcpip!TCPAbortAndIndicateDisconnect+23

BUCKET_ID:  0xD1_tcpip!TCPAbortAndIndicateDisconnect+23

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

1: kd> lmvm tcpip
start    end        module name
b6874000 b68cc080   tcpip    M (pdb symbols)          c:\windows\symbols\sys\tcpip.pdb
    Loaded symbol image file: tcpip.sys
    Image path: tcpip.sys
    Image name: tcpip.sys
    Timestamp:        Thu Apr 20 15:18:33 2006 (44477C19)
    CheckSum:         0005ED86
    ImageSize:        00058080
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Unul fresh si de la mine, cu toate ca mi-a fost dor de albastru ala :comp1:

bunny · November 11, 2009

Se pare ca doar pe XP da bluescreen, nu? :-?

LiNU · November 11, 2009

Da, doar pe XP face chestia asta, indiferent de SP 1, 2 sau 3...

bunny · November 11, 2009

Am cautat pe zeci de forumuri, eu mai mult decat v-am scris pe-aici, nu am cu ce sa va ajut, pare rau. :( Initial ar fi bine sa mai cautati si voi, poate mi-a scapat si mie cateceva, dar mie sincer nu-mi mai da bluescreen, am bagat patch-ul ala de la microsoft, am facut chestia aia cu reset din cmd, dar oricum eu nu stau mai mult de o ora in joc ca sa ajung sa primesc eroarea, poate ca as primi-o, god knows. :-??

tranced · November 11, 2009

pai tu nu , dragos poate ar putea

LiNU · November 13, 2009

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Nov 13 22:40:18.484 2009 (GMT+2)
System Uptime: 2 days 10:34:50.213
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
.........................................................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {c, 2, 0, b68acc66}

Probably caused by : tcpip.sys ( tcpip!TCPAbortAndIndicateDisconnect+23 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b68acc66, address which referenced memory

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


READ_ADDRESS:  0000000c 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!TCPAbortAndIndicateDisconnect+23
b68acc66 8b400c          mov     eax,dword ptr [eax+0Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  start.exe

LAST_CONTROL_TRANSFER:  from b689d9e9 to b68acc66

STACK_TEXT:  
b42158f0 b689d9e9 021dea28 b4215a90 862c0930 tcpip!TCPAbortAndIndicateDisconnect+0x23
b4215b40 b687aa55 0000000e 00000005 804f0cf3 tcpip!TdiSetInformationEx+0x27f
b4215bec b687a07c 862c0930 862c09a0 862c09a0 tcpip!IPSGetTotalCounts+0x24
b4215c08 b687a034 862c0930 862c09a0 877fe230 tcpip!ARPQueryInfo+0x78
b4215cd4 00000000 886a04f0 89961f58 b4215d48 tcpip!ARPQueryInfo+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!TCPAbortAndIndicateDisconnect+23
b68acc66 8b400c          mov     eax,dword ptr [eax+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  tcpip!TCPAbortAndIndicateDisconnect+23

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  44477c19

FAILURE_BUCKET_ID:  0xD1_tcpip!TCPAbortAndIndicateDisconnect+23

BUCKET_ID:  0xD1_tcpip!TCPAbortAndIndicateDisconnect+23

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

1: kd> lmvm tcpip
start    end        module name
b6874000 b68cc080   tcpip    M (pdb symbols)          c:\windows\symbols\sys\tcpip.pdb
    Loaded symbol image file: tcpip.sys
    Image path: tcpip.sys
    Image name: tcpip.sys
    Timestamp:        Thu Apr 20 15:18:33 2006 (44477C19)
    CheckSum:         0005ED86
    ImageSize:        00058080
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Un raspuns de la Dragos ?

Venom07 · November 14, 2009

exista o versiune de windows xp modificat de niste "Baietasi" ca sa arate frumos,care nu are problema cu acest tcpip.sys...

Ada XP Blue se numeste

Il am de cateva saptamani si n-am luat nici un BSOD

tranced · November 14, 2009

exista o versiune de windows xp modificat de niste "Baietasi" ca sa arate frumos,care nu are problema cu acest tcpip.sys...
Ada XP Blue se numeste
Il am de cateva saptamani si n-am luat nici un BSOD

nu e de la windows , ia cauta prin topicul asta sa vezi ce solutii s-au incercat si tot asa

nu vezi unde crapa? in start.exe care stim cu totii ce e

AngelDust · November 16, 2009

Am uitat sa postez.Am facut cum a zis bunny ultima data.Same shit.Nici nu ma asteptam la altceva.Problema e clara si ne invartim degeaba in jurul cozii.Bunny multumesc macar ca ai incercat.

bunny · November 16, 2009

Daca v-as spune sa va puneti windows 7, v-as injura? :-s Stiu ca unii aveti licenta, dar daca asta ar fi singura solutie de a va putea juca linistiti, altceva nu stiu.

tranced · November 16, 2009

Daca v-as spune sa va puneti windows 7, v-as injura? :-s Stiu ca unii aveti licenta, dar daca asta ar fi singura solutie de a va putea juca linistiti, altceva nu stiu.

pentru mine momentan nu e asta solutia , astept sa mai scoata creative un driver pentru placa de sunet pentru ca sunt ceva probleme cel putin la mine.... si oricum prefer xp nu am un sistem asa performant

si oricum sa schimb windows doar pentru mu mi se pare ciudat , doar noi trebuie sa incercam diverse chestii dar oare dragos a incercat sa faca ceva in sensul asta launcher-ului ca sa nu mai crape ?! poate ca nu toti pot sa faca upgrade la win 7 , ce facem in situatia asta?

LiNU · November 17, 2009

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Nov 17 10:36:57.139 2009 (GMT+2)
System Uptime: 1 days 16:36:07.418
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {c, 2, 0, b68acc66}

Probably caused by : tcpip.sys ( tcpip!TCPAbortAndIndicateDisconnect+23 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b68acc66, address which referenced memory

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


READ_ADDRESS:  0000000c 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!TCPAbortAndIndicateDisconnect+23
b68acc66 8b400c          mov     eax,dword ptr [eax+0Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  start.exe

LAST_CONTROL_TRANSFER:  from b689d9e9 to b68acc66

STACK_TEXT:  
b36678f0 b689d9e9 02ed5a68 b3667a90 887a2928 tcpip!TCPAbortAndIndicateDisconnect+0x23
b3667b40 b687aa55 0000000e 00000003 804f0cf3 tcpip!TdiSetInformationEx+0x27f
b3667bec b687a07c 887a2928 887a2998 887a2998 tcpip!IPSGetTotalCounts+0x24
b3667c08 b687a034 887a2928 887a2998 887a9fb8 tcpip!ARPQueryInfo+0x78
b3667cd4 00000000 899dd8b0 89edb388 b3667d48 tcpip!ARPQueryInfo+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!TCPAbortAndIndicateDisconnect+23
b68acc66 8b400c          mov     eax,dword ptr [eax+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  tcpip!TCPAbortAndIndicateDisconnect+23

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  44477c19

FAILURE_BUCKET_ID:  0xD1_tcpip!TCPAbortAndIndicateDisconnect+23

BUCKET_ID:  0xD1_tcpip!TCPAbortAndIndicateDisconnect+23

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

1: kd> lmvm tcpip
start    end        module name
b6874000 b68cc080   tcpip    M (pdb symbols)          c:\windows\symbols\sys\tcpip.pdb
    Loaded symbol image file: tcpip.sys
    Image path: tcpip.sys
    Image name: tcpip.sys
    Timestamp:        Thu Apr 20 15:18:33 2006 (44477C19)
    CheckSum:         0005ED86
    ImageSize:        00058080
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Dragos, vre`o idee? :beer:

theogritzi · November 19, 2009

si eu am problema asta

procesor intel e2180

2 gb ram

video : 8800 gt

placa de baza :mx-p5n

bunny · November 19, 2009

In primul rand scoate-ti quote-ul de la semnatura, nu facem pe nimeni vedete pe toate gardurile. In al doilea rand citeste topicul, nu exista rezolvare.

AngelDust · November 19, 2009

Azi de dimineata am patit-o iar.Cel mai nasol a fost ca eram singur pe spot.BSOD.Fericire suprema.Cateodata imi vine sa sterg jocul asta din 2 mutari.F8+enter.

AngelDust · November 23, 2009

Ieri 1 bsod , azi 2.Am pierdut iar spot.

bitzy · November 24, 2009

Pe Windows 7 nu iei bluescreen, dar nu toti isi permit Win 7... altii poate au lucenta pe XP...

LiNU cum nu iei blue screen pe win7 , eu am luat o data cand tocmai ce iesisem dintr-un joc:D

LiNU · November 24, 2009

Ai vreun Minidump sa-l analizam ? Poate nu e de la MU

tranced · November 26, 2009

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini112609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Thu Nov 26 13:17:51.738 2009 (GMT+2)
System Uptime: 12 days 2:17:17.311
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image tcpip.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tcpip.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {c, 2, 0, ab700fa9}
Probably caused by : tcpip.sys ( tcpip!ReadNextTCB+152 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: ab700fa9, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 0000000c
CURRENT_IRQL: 2
FAULTING_IP:
tcpip!ReadNextTCB+152
ab700fa9 8b400c mov eax,dword ptr [eax+0Ch]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: start.exe
LAST_CONTROL_TRANSFER: from ab6f1b5e to ab700fa9
STACK_TEXT:
a5ad88f0 ab6f1b5e 0255efd0 a5ad8a90 892d3640 tcpip!ReadNextTCB+0x152
a5ad8b24 00000000 82701020 c0300000 00204000 tcpip!TdiQueryInformationEx+0x865
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip!ReadNextTCB+152
ab700fa9 8b400c mov eax,dword ptr [eax+0Ch]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: tcpip!ReadNextTCB+152
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tcpip
IMAGE_NAME: tcpip.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 485b99ad
FAILURE_BUCKET_ID: 0xD1_tcpip!ReadNextTCB+152
BUCKET_ID: 0xD1_tcpip!ReadNextTCB+152
Followup: MachineOwner
---------

dupa 12 zile uptime s-a produs inevitabilul

S1KA · November 27, 2009

aceasi ploblema si eu .... BSOD

de fiecare data cnd aprind pC primesc bsod .... trebe sa ii dau repair la windows ca sa mearga ... apoi daca iara ii dau rr | sau sting pc . din nou BSOD .... deci de fiecare data cnd apare BSOD trebe sa ii dau repair :(( si daca vreun sofware cere rr ; ii dau rr si iara BSOD :|

pLS helP me :(

am incercat multe din sugestiile voastre dar deloc :(

dracy21 · November 27, 2009

la fel si eu si multi dupa server

bunny · November 28, 2009

Ok, S1 e history. Bluescreen pe S2, careva?

LiNU · November 28, 2009

Stai ca inca nici nu am facut shorcut la start.exe pe desktop. Revenimi noi cu vren Bluescreen daca e cazul :P

:beer:

bunny · November 28, 2009

Ah, scuze. ^^ Sper sa nu, m-am saturat de topicul asta fara solutie. :)

Companie	Domeniu	Politica de confidenţialitate
RCS&RDS S.A.	linkmania.ro	Vezi politica de confidenţialitate
ips4_hasJS, ips4_ipsTimezone, ips4_IPSSessionFront, ips4_member_id, ips4_pass_hash, ips4_language, ips4_anon_login, ips4_theme, ips4_forum_view, ips4_recentEmoji
Google LLC	google.com	Vezi politica de confidenţialitate
_ga, _gid, _gat, AMP_TOKEN, _gac_, __utma, __utmt, __utmb, __utmc, __utmz

Sign In

Archived

Bluescreen tcpip.sys

Recommended Posts

tranced

LiNU

bunny

LiNU

bunny

tranced

LiNU

Venom07

tranced

AngelDust

bunny

tranced

LiNU

theogritzi

bunny

AngelDust

AngelDust

bitzy

LiNU

tranced

S1KA

dracy21

bunny

LiNU

bunny

Recently Browsing 0 members

Browse

Activity