Bluescreen tcpip.sys

[AngelDust]

Traim si vedem.Pana acum niciun BSOD , dar mai e timp.Am avut si 5-6 zile fara BSOD.

[AngelDust]

Revin cu noi info.BSOD din nou.Aia e.

[LiNU]

pune si tu minidump aici sa ti-l analizam :beer:

C:\Windows\MiniDump\

[AngelDust]

Vrei sa repet ce am repetat pana acum?Calculatorul meu merge absolut perfect cat nu ruleaza MU pe el. Ma joc orice la rezolutie si detalii maxim , filme in format hd , am avut si 4 jocuri pornite simultan.Atata timp cat am doar MU si firefox deschise ce mai e de adaugat?

Eu ma las pagubas.

[Biggles]

problema asta era pe S1... cand incepea BSOD :comp1: ... era jale... luam din 5 in 5 min... :comp1:

dar akm vad ca nu am luat nici unu de cand s-a trecut la S2.

mai asteptam :> :crazy:

[bunny]

Revin cu noi info.BSOD din nou.Aia e.

Ai luat bsod pe S2? Damn! >_<

[LiNU]

pune si tu minidump aici sa ti-l analizam :beer:

C:\Windows\MiniDump\

panduru2 se poate?

Eu inca nu am luat nici unul pana acum.

[tranced]

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Documents and Settings\Alex\Desktop\Mini120109-04.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 = 0x8055d720

Debug session time: Tue Dec 1 14:50:23.578 2009 (GMT+2)

System Uptime: 0 days 0:30:20.309

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

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

Debugging Details:

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

READ_ADDRESS: 0000000c

CURRENT_IRQL: 2

FAULTING_IP:

tcpip!ReadNextTCB+152

babd7fa9 8b400c mov eax,dword ptr [eax+0Ch]

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: start-S2.exe

LAST_CONTROL_TRANSFER: from babc8b5e to babd7fa9

STACK_TEXT:

b99d08f0 babc8b5e 0267fec0 b99d0a90 86581788 tcpip!ReadNextTCB+0x152

b99d0b24 c00150b0 00000000 0000000e 0003e712 tcpip!TdiQueryInformationEx+0x865

WARNING: Frame IP not in any known module. Following frames may be wrong.

b99d0b40 baba819a 0000000e 0000000e 804f0fbd 0xc00150b0

b99d0bec baba55b5 86581788 865817f8 865817f8 tcpip!TCPQueryInformationEx+0x1c2

b99d0c08 baba556d 86581788 865817f8 865176d8 tcpip!TCPDispatchDeviceControl+0x129

b99d0c40 804ef19f 87073910 86581788 806e6410 tcpip!TCPDispatch+0x127

b99d0c64 805807f7 87073910 86581788 865176d8 nt!MiFlushSectionInternal+0x256

b99d0d00 80579274 00000034 000004ac 00000000 nt!NtSetInformationThread+0x125

b99d0d34 8054162c 00000034 000004ac 00000000 nt!SepOpenTokenOfThread+0x87

b99d0d64 7c90e514 badb0d00 041ceab4 b8ad5d98 nt!RtlIpv4StringToAddressExW+0xad

b99d0d78 00000000 00000000 00000000 00000000 0x7c90e514

STACK_COMMAND: kb

FOLLOWUP_IP:

tcpip!ReadNextTCB+152

babd7fa9 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

---------

BSOD fresh la unul din calculatoarele lui Sadi , eu inca nu am luat dar vad ca problema asta persista si e doar e chestiune de timp pana o sa apara la mai multa lume

[dracy21]

la fel odata la 3-4 zile

[Guest My_albanezu]

pe s2 nu mai iau d/c din care pe s1 luam de 4 ori pe zi d.c

hai cu s2:)

[tranced]

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini121109-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 Dec 11 02:22:05.059 2009 (GMT+2)

System Uptime: 1 days 1:07:28.223

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

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

Debugging Details:

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

READ_ADDRESS: 0000000c

CURRENT_IRQL: 2

FAULTING_IP:

tcpip!ReadNextTCB+152

ab6ccfa9 8b400c mov eax,dword ptr [eax+0Ch]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: start-S2.exe

LAST_CONTROL_TRANSFER: from ab6bdb5e to ab6ccfa9

STACK_TEXT:

ab5158f0 ab6bdb5e 027ebdc8 ab515a90 87dc5b40 tcpip!ReadNextTCB+0x152

ab515b24 00000000 878309c0 c0300000 00235000 tcpip!TdiQueryInformationEx+0x865

STACK_COMMAND: kb

FOLLOWUP_IP:

tcpip!ReadNextTCB+152

ab6ccfa9 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

---------

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

Debugging Details:

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

READ_ADDRESS: 0000000c

CURRENT_IRQL: 2

FAULTING_IP:

tcpip!ReadNextTCB+152

ab6ccfa9 8b400c mov eax,dword ptr [eax+0Ch]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: start-S2.exe

LAST_CONTROL_TRANSFER: from ab6bdb5e to ab6ccfa9

STACK_TEXT:

ab5158f0 ab6bdb5e 027ebdc8 ab515a90 87dc5b40 tcpip!ReadNextTCB+0x152

ab515b24 00000000 878309c0 c0300000 00235000 tcpip!TdiQueryInformationEx+0x865

STACK_COMMAND: kb

FOLLOWUP_IP:

tcpip!ReadNextTCB+152

ab6ccfa9 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

---------

[Andr3y(^_^)]

si eu am inceput de azi sa i-au BSOD azi cel putin de 8 ori :| pana acum nu am avut preoblema asta

pe s1 luam dar nu asa des o data la 2 zile

[LiNU]

pune si tu minidump aici sa ti-l analizam :beer:

C:\Windows\MiniDump\

Andr3y(^ _ ^) se poate ? :beer:

[Andr3y(^_^)]

nu gasesc MiniDump.. are si alta denumire ..?

[LiNU]

Nu, il gasesti in acel director. Si mie mi s-a restartat de vre-o 3 ori PCu si nu am gasit minidump cea ce ma face sa cred ca nu a fost tcpip...

[dracy21]

Minidump.rar

am arhivat eu Minidump o sa instaz winds si eu curand sa vad poate nu mai da eu mai rar acum da iau cand e lumea mai draga

[eddy_s69]

salut....am avut o singura data BSOD....din cauza ramilor....iam schimbat dupa aia nu am mai avut probleme....eu folosesc windows service pack 3 fara modificari(original ca sa zic asa).....cu el nu am absolut nici o problema...va sfatuiesc sa`l folositi si voi....si incercati sa va puneti ventilatie la PC(in caz ca nu aveti) + curatati unitatea bucata cu bucata macar odata pe saptamana....puneti doar programele necesare de care aveti nevoie....zic asta deoarece am intalnit anumite persoane ca puneau fel si fel de programe fara rost si din cauza asta calculatorul ii mergea greu, se bloca, isi dadea restart etc....

[Biggles]

panduru2 se poate?

Eu inca nu am luat nici unul pana acum.

poftim.

http://www.easy-share.com/1908750980/Mini082309-01.zip

sper ca intelegi chineza. :comp1:

Din cate am observat... cu cat stau mai mult in joc... cu atata creste sansa sa imi iau BSOD. ex daca acuma intru in joc... nu imi iau ... daca am deja 12 ore .... deja strang din buci sa numi iau... si.... poc da.... o sa imi iau.

[tranced]

poftim.

http://www.easy-share.com/1908750980/Mini082309-01.zip

sper ca intelegi chineza. :comp1:

Din cate am observat... cu cat stau mai mult in joc... cu atata creste sansa sa imi iau BSOD. ex daca acuma intru in joc... nu imi iau ... daca am deja 12 ore .... deja strang din buci sa numi iau... si.... poc da.... o sa imi iau.

uite log-ul

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Documents and Settings\Alex\Desktop\Mini082309-01\Mini082309-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: Sun Aug 23 18:39:04.359 2009 (GMT+2)

System Uptime: 0 days 11:48:26.086

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

Probably caused by : hardware ( tcpip!InsertIntoFTrie+a )

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

Debugging Details:

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

READ_ADDRESS: 0000000c

CURRENT_IRQL: 2

FAULTING_IP:

tcpip!InsertIntoFTrie+a

f39c99de 8b400c mov eax,dword ptr [eax+0Ch]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: start.exe

MISALIGNED_IP:

tcpip!InsertIntoFTrie+a

f39c99de 8b400c mov eax,dword ptr [eax+0Ch]

LAST_CONTROL_TRANSFER: from 865531b8 to f39c99de

STACK_TEXT:

ba6158dc 865531b8 80701830 ba615b6c 000000a8 tcpip!InsertIntoFTrie+0xa

WARNING: Frame IP not in any known module. Following frames may be wrong.

ba6158f0 f39ba617 025531b8 ba615a90 86479600 0x865531b8

ba615b01 73ffffff fff39671 2bffffff fff739ff tcpip!TdiQueryInformationEx+0x32a

ba615bec f3996e9a 86479600 86479670 86479670 0x73ffffff

ba615bf0 86479600 86479670 86479670 86479600 tcpip!CancelGroupResponseTimer+0x8

ba615c08 f3996e53 86479600 86479670 86607a88 0x86479600

ba615c40 804e13d9 86bcdbe8 86479600 80701410 tcpip!FindIGMPAddr+0xe

ba615c40 86bcdbe8 86bcdbe8 86479600 80701410 nt!KiTrap0D+0x493

ba615cd4 00000000 86607a88 86f317e8 ba615d48 0x86bcdbe8

STACK_COMMAND: kb

FOLLOWUP_IP:

tcpip!InsertIntoFTrie+a

f39c99de 8b400c mov eax,dword ptr [eax+0Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: tcpip!InsertIntoFTrie+a

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

Followup: MachineOwner

---------

[AngelDust]

Pana la urma reuseste cineva sa dea un raspuns pe aici?

[Biggles]

uite log-ul

si cum rezolvam problema?

[JustAnotherPlayer]

Treaba cu BSOD-ul nu este numa' din cauza start.exe

EU am o versiune de xp sp2 pe care nu iau bsod,decat odata la 2 saptamani.

Daca bag SP2 clean,sau SP3,iau odata la 1-2 ore.

salut....am avut o singura data BSOD....din cauza ramilor....iam schimbat dupa aia nu am mai avut probleme....eu folosesc windows service pack 3 fara modificari(original ca sa zic asa).....cu el nu am absolut nici o problema...va sfatuiesc sa`l folositi si voi....si incercati sa va puneti ventilatie la PC(in caz ca nu aveti) + curatati unitatea bucata cu bucata macar odata pe saptamana....puneti doar programele necesare de care aveti nevoie....zic asta deoarece am intalnit anumite persoane ca puneau fel si fel de programe fara rost si din cauza asta calculatorul ii mergea greu, se bloca, isi dadea restart etc....

Ce net ai?

Daca ai net prin LAN,sansele sa iei BSOD sunt foarte mari

Eu daca stau cu netu prin lan iau des de tot

Cu modem clicknet pe usb,iau mai rar,1-2 pe zi

Cu net prin telefon,adica N73 cu vodafone live,nu iau bsod NICIODATA.

[Biggles]

momentan eu sunt limitat doar la vreo 12 -14 ore de link pe zi...

adica intru in joc pe la 10-11 ziua... totul merge super... dar dupa vreo 10 -12-14 ore de mu ... incepe sa imi dea BSOD. Cauza??? nu mai stiu... am incercat tot posibililul.

PS: am vreo 3 calc acasa, doar pe cel mai performant imi iau BSOD, pe celalalte nici vorba de asa ceva.

[JustAnotherPlayer]

Mie mi se pare ca Iei cel mai mult BSOD pe placile LAN integrate de la placile mai noi de 2007(Aprox)

eu n-am vazut PC mai vechi sa aibe probleme.

[tranced]

ia uita-te la log-rile de la crash dump-urile de pe ultimele 2 pagini si o sa iti seama de la ce e