Bluescreen tcpip.sys

Phant0m · October 29, 2009

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

macar asta scoate din discutie ca ar fi de la cv hardware....

tranced · October 29, 2009

macar asta scoate din discutie ca ar fi de la cv hardware....

ai vrut sa zici software cred :-?

LiNU · October 30, 2009

Eu unul am dat DISABLE la placa de retea din bios, am pus una separat PCI si am reinstalat windows`ul si vad ca cel putin in ultimele 2 saptamani nu am mai avut probleme pe PC... Dar pe laptop ce fac ? :D

Phant0m · October 30, 2009

ai vrut sa zici software cred :-?

cred ca nu ai citit bn

tranced · November 6, 2009

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright ? Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini110609-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: Fri Nov 6 16:42:54.232 2009 (GMT+2)
System Uptime: 1 days 21:12:53.420
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, ad1dafa9}
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: ad1dafa9, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 0000000c
CURRENT_IRQL: 2
FAULTING_IP:
tcpip!ReadNextTCB+152
ad1dafa9 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 ad1cbb5e to ad1dafa9
STACK_TEXT:
a91448f0 ad1cbb5e 02882428 a9144a90 87a86f68 tcpip!ReadNextTCB+0x152
a9144b24 00000000 87497a60 c0300000 001fb000 tcpip!TdiQueryInformationEx+0x865
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip!ReadNextTCB+152
ad1dafa9 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
---------

dovada suprema ca cel putin in cazul meu bluescreen-urile sunt din cauza launcherului :hair:

LiNU · November 6, 2009

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


Loading Dump File [C:\WINDOWS\Minidump\Mini101809-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: Sun Oct 18 12:01:25.809 2009 (GMT+2)
System Uptime: 0 days 22:07:56.609
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, b6cbcc66}

Probably caused by : tcpip.sys ( tcpip!GPCcfInfoRemoveNotifyQoS+21 )

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: b6cbcc66, address which referenced memory

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


READ_ADDRESS:  0000000c 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!GPCcfInfoRemoveNotifyQoS+21
b6cbcc66 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 b6cad9e9 to b6cbcc66

STACK_TEXT:  
b59e38f0 b6cad9e9 0292b188 b59e3a90 87f164c0 tcpip!GPCcfInfoRemoveNotifyQoS+0x21
b59e3b01 dd000000 0077d489 d7000000 0077d496 tcpip!TdiQueryInformationEx+0x6f0
WARNING: Frame IP not in any known module. Following frames may be wrong.
b59e3bec b6c8a07c 87f164c0 87f16530 87f16530 0xdd000000
b59e3c08 b6c8a034 87f164c0 87f16530 866be548 tcpip!IPTransmit+0x1314
b59e3c40 804eeec5 8a040f18 87f164c0 806e4410 tcpip!OpenRCE+0xae
b59e3c64 8057f4e3 8a040f18 87f164c0 87aedac0 nt!CcAcquireByteRangeForWrite+0x2e
b59e3d00 80578038 00000038 0000fbcc 00000000 nt!NtQueryObject+0x37
b59e3d34 8054061c 00000038 0000fbcc 00000000 nt!NtCreateMutant+0x1
b59e3d64 7c90eb94 badb0d00 038aeab4 00000000 nt!RtlIpv4AddressToStringW+0x36
b59e3d70 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!GPCcfInfoRemoveNotifyQoS+21
b6cbcc66 8b400c          mov     eax,dword ptr [eax+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  tcpip!GPCcfInfoRemoveNotifyQoS+21

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  44477c19

FAILURE_BUCKET_ID:  0xD1_tcpip!GPCcfInfoRemoveNotifyQoS+21

BUCKET_ID:  0xD1_tcpip!GPCcfInfoRemoveNotifyQoS+21

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

Unul si de la mine. Se pare ca am banuit bine ca e de la Start.exe problema.

Asteptam rezolvarea :tiphat:

bunny · November 6, 2009

Asteptam rezolvarea :tiphat:

Aprob, si eu o astept. :)) God knows why. :)

pinned again.

tranced · November 6, 2009

pentru cine are dubii in legatura cu bsod tcpip.sys rog sa ataseze fisierul minidump care se afla in C:/WINDOWS/Minidump si va voi spune daca crash-urile sunt din cauza procesului start.exe (launcher-ul mu linkmania s1)

P.S. trebuie sa aveti activat "write debbuging information"

right click My Computer , properties , advanced , la startup and recovery dati advanced si la write debbuging information selectati small memory dump 64k

bunny · November 6, 2009

Ce antivirus folositi? :-?

Am mai cautat pe google, tcpip.sys e de la torrente. o_O Nu stiu cum, de ce si in ce fel.

tranced · November 6, 2009

Ce antivirus folositi? :-?
Am mai cautat pe google, tcpip.sys e de la torrente. o_O Nu stiu cum, de ce si in ce fel.

eu am nod32 v2.7

cand mi-a dat aparut bsod-ul de la logul de mai sus aveam doar skype si mu deschis , no utorrent

si n-are cum sa fie de la torrente din moment ce apare clar la process name start.exe aka linkmania launcher

http://fbx.ro/7npex5i6erzbkurh

bunny · November 6, 2009

Am gasit o chestie:

Start>Run, type in:
devmgmt.msc
Click OK.

In Device Manager, go View, click on Show hidden devices
Non-Plug, and Play Deivce folder will expand.
Find following drivers:
TCP/IP Protocol Driver
right click on the entry, click Properties
Click Driver tab, and change Startup type from whatever it is now to Demand.
OK your way out.
Restart computer.[/code]

tranced · November 7, 2009

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini110709-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: Sat Nov 7 12:19:33.140 2009 (GMT+2)

System Uptime: 0 days 19:34:01.859

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, ad1dafa9}

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: ad1dafa9, address which referenced memory

Debugging Details:

------------------

READ_ADDRESS: 0000000c

CURRENT_IRQL: 2

FAULTING_IP:

tcpip!ReadNextTCB+152

ad1dafa9 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 ad1cbb5e to ad1dafa9

STACK_TEXT:

a9c4a8f0 ad1cbb5e 028591d8 a9c4aa90 863aeb30 tcpip!ReadNextTCB+0x152

a9c4ab24 00000000 863103c0 c0300000 00235000 tcpip!TdiQueryInformationEx+0x865

STACK_COMMAND: kb

FOLLOWUP_IP:

tcpip!ReadNextTCB+152

ad1dafa9 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

---------

inca unul , e fresh are 7 minute

bunny · November 7, 2009

Ai facut aia de sus?

tranced · November 7, 2009

Ai facut aia de sus?

adineauri am facut... sa vedem si rezultate

bunny · November 8, 2009

Well? A mers? :D

tranced · November 8, 2009

Well? A mers? :D

momentan e liniste , standing by...

bunny · November 8, 2009

Se pare ca ceilalti care au eroarea asta n-au de gand sa testeze singuri. Fratilor, n-o sa vin la voi acasa sa va fac calculatorul, sunteti buni de plans, dar sa incercati sa vi-l rezolvati nu vreti, chiar si cu sfaturi. Treaba voastra, eu nu va bag lingura pe gat ca la copii.

AngelDust · November 8, 2009

O sa incerc si eu ce a zis bunny sa vedem ce o sa se intample.Am mai luat un BSOD fara utorrent.Aveam doar MU si firefox pornite.

PS bunny s-ar rezolva multe daca cineva s-ar ocupa de launcher.Cred ca sti si tu cum e cu tratarea simptomelor si nu a problemei.

tranced · November 8, 2009

O sa incerc si eu ce a zis bunny sa vedem ce o sa se intample.Am mai luat un BSOD fara utorrent.Aveam doar MU si firefox pornite.
PS bunny s-ar rezolva multe daca cineva s-ar ocupa de launcher.Cred ca sti si tu cum e cu tratarea simptomelor si nu a problemei.

eu unul am tot incercat atatea variante de win si nimic , am schimbat si sursa si placa de retea totul in zadar

cand colo ce sa vad : crapa in start.exe #-o

AngelDust daca ai fisierul minidump uploadeaza-l te rog

AngelDust · November 8, 2009

Nu am.Imi pare rau.Am mai scris si scriu iar.Calculatorul meu merge absolut perfect cat timp nu ma joc MU.

bunny · November 9, 2009

O sa incerc si eu ce a zis bunny sa vedem ce o sa se intample.Am mai luat un BSOD fara utorrent.Aveam doar MU si firefox pornite.
PS bunny s-ar rezolva multe daca cineva s-ar ocupa de launcher.Cred ca sti si tu cum e cu tratarea simptomelor si nu a problemei.

Odata cu S2, va disparea problema cu bluescreen, sper. >.<

AngelDust · November 9, 2009

Ce bine ar fi.O sa anunt cum merge treaba cu ce ai indicat.Mai mult de juma de ora nu merge MU cu utorrent pornit.Fara utorrent imi da foarte rar bsod.Maine sigur revin cu un raspuns.

tranced · November 9, 2009

Odata cu S2, va disparea problema cu bluescreen, sper. >.<

eu nu cred , launcherul S2 pare sa fie facut dupa cel de la S1

in practica vom vedea daca mai exista problema asta pe S2...

tranced · November 10, 2009

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © 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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Wed Nov 11 01:08:22.125 2009 (GMT+2)
System Uptime: 0 days 2:37:01.844
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, ab728fa9}
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: ab728fa9, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 0000000c
CURRENT_IRQL: 2
FAULTING_IP:
tcpip!ReadNextTCB+152
ab728fa9 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 ab719b5e to ab728fa9
STACK_TEXT:
aacb08f0 ab719b5e 029ca6c0 aacb0a90 88e55768 tcpip!ReadNextTCB+0x152
aacb0b24 00000000 87abc338 c0300000 00200000 tcpip!TdiQueryInformationEx+0x865
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip!ReadNextTCB+152
ab728fa9 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
---------

degeaba , tot iau ... asta e de acum 8 minute

JustAnotherPlayer · November 11, 2009

Eu primesc BSOD-uri mai des cand am BSplayeru pornit.

Cam 30 de minute si bam...

Am lasat afk toata noaptea,doar cu MU si nu am luat nimic.

Daca-l las linistit da foarte rar

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

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Recently Browsing 0 members