karta sieciowa WiFi Modecom, bluescreen tvtpktfilter.sys

Post03 paź 2011, 21:49

Witajcie. Jestem tu pierwszy raz, ale na pewno nie ostatni.
Mam problem z instalacją karty sieciowej Modecom MC-UN22 do mojego laptopa Lenovo 3000 N100.
Po zainstalowaniu i połączeniu się z siecią Wi-Fi wyskakuje bluescreen, którego zrzut załączam.
Karta jest na pewno dobra, bo na innym kompie działa bez zarzutu. Pomóżcie!!!

Oto zrzut bluescreenu:

Dostępne tylko dla zarejestrowanych użytkowników

:think:

Strona WWW · Post03 paź 2011, 22:54

Zainstaluj ten sterownik od tej karty:
ftp://drivers:drivers@ftp.modecom.pl/EN ... DRIVER.zip

Post04 paź 2011, 14:16

Dziękuję za szybką odpowiedź

Pobrałem i zainstalowałem te sterowniki, ale efekt był taki:

Dostępne tylko dla zarejestrowanych użytkowników

Oczywiście przed zainstalowaniem sterowników i podłączeniu nowej karty, wyłączam Wi-Fi w laptopie - chyba dobrze robię? Kartą Modecom chcę zastąpić Wi-Fi laptopa (które jest w standardzie 802.11 b/g), a router mam w "N-ce".
Zależy mi więc bardzo, żeby ta nowa karta Wi-Fi chodziła. Pomóżcie więc!!! Co to jest za komunikat: "Probably caused by : tvtpktfilter.sys ( tvtpktfilter+a78 )"? A może tu jest przyczyna: "PROCESS_NAME: AvastSvc.exe"?? Rzeczywiście używam Avasta. :sciana:

Post04 paź 2011, 14:17

solofh pisze:Rzeczywiście używam Avasta

To spróbuj go wyłączyć, tudzież usunąć na czas próby.

Post04 paź 2011, 15:10

Więcej :
tvtpktfilter.sys, Win32 error 0n2
qbikhkXP.sys, Win32 error 0n2
sptd.sys, Win32 error 0n2
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
AvastSvc.exe

Dużo - często tj. problem z pamięcią ale nie zawsze

Masz firewalla - jakiego ?

1. Zresetuj BIOS :
http://www.hotfix.pl/resetowanie-bios-u ... ra-a21.htm
Pierwszy lub trzeci sposób Load Optimized Defaults.
2. Sprawdź pamięć :
http://www.hotfix.pl/instrukcja-obslugi ... m-a204.htm
Czym dłużej tym lepiej...
Po sprawdzeniu możesz jeszcze sprawdzić oddzielnie "kości".
3. Analiza SMART (S.M.A.R.T) dysku twardego.
4. Wrzuć logi zgodnie z tym regulaminem :
bezpieczenstwo/nowy-regulamin-dzialu-bezpiecze-stwo-t1887.html

Post20 paź 2011, 20:55

To znowu ja.
Niestety próby pracy z ta kartą nadal się nie udają! Wkurza mnie to, ba na stacjonarnym chodzi i nawet miałem
kiedyś 300 Mbit/s.
Na moim Lenovo 3000 N100 ciągle po 1, 2 minutach pracy pojawia się w końcu bluescreen. Ostatnie dwa załączam.
Może ktoś się zlituje i pomoże mi rozwiązać ten problem.

Screen1:

Kod: Zaznacz cały

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


Loading Dump File [C:\Program Files\Debugging Tools for Windows (x86)\Mini101211-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbole*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Oct 12 12:00:55.203 2011 (GMT+2)
System Uptime: 0 days 0:31:03.906
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {0, 2, 8, 0}

Unable to load image tvtpktfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tvtpktfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for tvtpktfilter.sys
Unable to load image qbikhkXP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for qbikhkXP.sys
*** ERROR: Module load completed but symbols could not be loaded for qbikhkXP.sys
Unable to load image RTL8192su.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTL8192su.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8192su.sys
Unable to load image sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : tvtpktfilter.sys ( tvtpktfilter+a78 )

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

0: 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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory

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


READ_ADDRESS:  00000000 

CURRENT_IRQL:  2

FAULTING_IP: 
+2b
00000000 ??              ???

PROCESS_NAME:  chrome.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

LAST_CONTROL_TRANSFER:  from f715b0ef to 00000000

FAILED_INSTRUCTION_ADDRESS: 
+2b
00000000 ??              ???

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7969148 f715b0ef 85ffab48 f79692ec 85cac000 0x0
f7969174 f715c9d9 868abca0 00000000 00000014 NDIS!ndisMTransferData+0x109
f7969194 f78b6a78 f79691c8 868abca0 00000000 NDIS!NdisTransferData+0x1b
f79691b8 f715b0ef 85ffab48 f79692ec 847cb620 tvtpktfilter+0xa78
f79691e4 f55aa0a6 84fc0e10 00000000 00000014 NDIS!ndisMTransferData+0x109
f7969204 f715b0ef 85ffab48 f79692ec 86601b28 psched!MpTransferData+0x3c
f7969230 aa6b2239 86b98ca8 00000000 00000014 NDIS!ndisMTransferData+0x109
f7969250 aa6926c6 83f60608 00000000 00000000 tcpip!ARPXferData+0x26
f79692fc aa684928 869862c0 86cb2c18 00000020 tcpip!IPRcvPacket+0x32b
f796933c aa6896ef 00000000 00000000 86cb2bf6 tcpip!ARPRcvIndicationNew+0x149
f796936c f70add5c 83f60608 00000000 86cb2bf6 tcpip!ARPRcv+0x42
f79693b0 f70ad1f8 849ab008 86cb2bf6 f79693f0 qbikhkXP+0x32d5c
f79693ec f7166e45 85f6a008 83f60608 845adf30 qbikhkXP+0x321f8
f7969444 f55aa01d 00fce308 8691f530 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x307
f7969458 f55aa1b4 869b0130 8691f530 00000001 psched!PsFlushReceiveQueue+0x15
f796947c f55aa5f9 86601b30 00000000 869b0130 psched!PsEnqueueReceivePacket+0xda
f7969494 f7166c40 86601b28 84f229b0 00000000 psched!ClReceiveComplete+0x13
f79694e4 f78b792f 00fce308 f7969500 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4
f79695a0 f78b7c6d 00000001 00000000 f7969600 tvtpktfilter+0x192f
f79695b0 f7166c40 847cb620 869ddf30 00000001 tvtpktfilter+0x1c6d
f7969600 a802c25b 00fce308 f7969620 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4
f7969a2c a805b897 85cac000 f7969a4c 969c7801 RTL8192su+0x925b
f7969c58 a805bac3 85cac000 85d3db30 00000000 RTL8192su+0x38897
f7969c78 a8043545 85d3db30 0000002f 85cac000 RTL8192su+0x38ac3
f7969da0 a806c87a 00cac000 01d93428 869531d8 RTL8192su+0x20545
f7969dc8 a806d434 85cac000 01e02ccc 00000002 RTL8192su+0x4987a
f7969ddc a802d337 85cac000 84e02ccc 00000002 RTL8192su+0x4a434
f7969e08 804f16c0 00000000 00000000 00000000 RTL8192su+0xa337
f7969e38 f577e0d5 85de0520 85983608 86af1028 nt!IopfCompleteRequest+0xa2
f7969ea0 f577ed47 84ec0ea8 00000000 86af17d8 USBPORT!USBPORT_CompleteTransfer+0x373
f7969ed0 f577f944 026e6f44 86af10e0 86af10e0 USBPORT!USBPORT_DoneTransfer+0x137
f7969f08 f578113a 86af1028 80546b3c 86af1230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
f7969f34 f578f24b 86af1028 80546b3c 86af1028 USBPORT!USBPORT_DpcWorker+0x224
f7969f70 f578f3c2 86af1028 00000001 86af164c USBPORT!USBPORT_IsrDpcWorker+0x38f
f7969f8c f733fe31 86af164c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
f7969fcc 80545eef 86af164c 86af1028 00000000 sptd+0x18e31
f7969ff4 80545a5b a82e6ac8 00000000 00000000 nt!KiRetireDpcList+0x61
f7969ff8 a82e6ac8 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
80545a5b 00000000 00000009 0081850f bb830000 0xa82e6ac8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tvtpktfilter+a78
f78b6a78 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tvtpktfilter+a78

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tvtpktfilter

IMAGE_NAME:  tvtpktfilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  43cb0a1f

FAILURE_BUCKET_ID:  0xD1_CODE_AV_NULL_IP_tvtpktfilter+a78

BUCKET_ID:  0xD1_CODE_AV_NULL_IP_tvtpktfilter+a78

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

Screen2:

Kod: Zaznacz cały

Loading Dump File [C:\Program Files\Debugging Tools for Windows (x86)\Mini100411-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbole*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Oct  4 13:26:28.750 2011 (GMT+2)
System Uptime: 0 days 0:09:04.426
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {0, 2, 8, 0}

Unable to load image tvtpktfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tvtpktfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for tvtpktfilter.sys
Unable to load image qbikhkXP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for qbikhkXP.sys
*** ERROR: Module load completed but symbols could not be loaded for qbikhkXP.sys
Unable to load image RTL8192su.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTL8192su.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8192su.sys
Unable to load image sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : tvtpktfilter.sys ( tvtpktfilter+a78 )

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

0: 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: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory

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


READ_ADDRESS:  00000000 

CURRENT_IRQL:  2

FAULTING_IP: 
+2b
00000000 ??              ???

PROCESS_NAME:  AvastSvc.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

LAST_CONTROL_TRANSFER:  from f719b0ef to 00000000

FAILED_INSTRUCTION_ADDRESS: 
+2b
00000000 ??              ???

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
f79a9794 f719b0ef 85956b48 f79a9938 84c98000 0x0
f79a97c0 f719c9d9 86bab958 00000000 00000014 NDIS!ndisMTransferData+0x109
f79a97e0 f78c6a78 f79a9814 86bab958 00000000 NDIS!NdisTransferData+0x1b
f79a9804 f719b0ef 85956b48 f79a9938 86bc6008 tvtpktfilter+0xa78
f79a9830 f55670a6 84de3618 00000000 00000014 NDIS!ndisMTransferData+0x109
f79a9850 f719b0ef 85956b48 f79a9938 83c0fa88 psched!MpTransferData+0x3c
f79a987c aa6b2239 84df91d0 00000000 00000014 NDIS!ndisMTransferData+0x109
f79a989c aa6926c6 837fe8e0 00000000 00000000 tcpip!ARPXferData+0x26
f79a9948 aa684928 8461b618 86c51328 00000020 tcpip!IPRcvPacket+0x32b
f79a9988 aa6896ef 00000000 00000000 86c51306 tcpip!ARPRcvIndicationNew+0x149
f79a99b8 f70edd5c 837fe8e0 00000000 86c51306 tcpip!ARPRcv+0x42
f79a99fc f70ed1f8 84452008 86c51306 00000000 qbikhkXP+0x32d5c
f79a9a38 f71a6e45 85a174f8 837fe8e0 84dbdf30 qbikhkXP+0x321f8
f79a9a90 f556701d 006952c0 85a20798 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x307
f79a9aa4 f55671b4 84e49300 85a20798 00000001 psched!PsFlushReceiveQueue+0x15
f79a9ac8 f55675f9 83c0fa90 00000000 84e49300 psched!PsEnqueueReceivePacket+0xda
f79a9ae0 f71a6c40 83c0fa88 84470130 00000000 psched!ClReceiveComplete+0x13
f79a9b30 f78c792f 006952c0 f79a9b4c 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4
f79a9bec f78c7c6d 00000001 00000000 f79a9c4c tvtpktfilter+0x192f
f79a9bfc f71a6c40 86bc6008 84c98000 00000000 tvtpktfilter+0x1c6d
f79a9c4c a7e1166d 006952c0 f79a9c80 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4
f79a9c78 a7e28567 84e06f30 84d764c4 84c98000 RTL8192su+0x966d
f79a9da0 a7e5187a 00c98000 00d764c4 84e2bdb8 RTL8192su+0x20567
f79a9dc8 a7e52434 84c98000 01bf924c 00000002 RTL8192su+0x4987a
f79a9ddc a7e12337 84c98000 83bf924c 00000002 RTL8192su+0x4a434
f79a9e08 804f16c0 00000000 00000000 00000000 RTL8192su+0xa337
f79a9e38 f575d0d5 84dfb008 8568a470 86abb028 nt!IopfCompleteRequest+0xa2
f79a9ea0 f575dd47 84e235d0 00000000 86abb7d8 USBPORT!USBPORT_CompleteTransfer+0x373
f79a9ed0 f575e944 026e6f44 86abb0e0 86abb0e0 USBPORT!USBPORT_DoneTransfer+0x137
f79a9f08 f576013a 86abb028 80546b3c 86abb230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
f79a9f34 f576e24b 86abb028 80546b3c 86abb028 USBPORT!USBPORT_DpcWorker+0x224
f79a9f70 f576e3c2 86abb028 00000001 86abb64c USBPORT!USBPORT_IsrDpcWorker+0x38f
f79a9f8c f737fe31 86abb64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
f79a9fcc 80545eef 86abb64c 86abb028 00000000 sptd+0x18e31
f79a9ff4 80545a5b a8766d44 00000000 00000000 nt!KiRetireDpcList+0x61
f79a9ff8 a8766d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
80545a5b 00000000 00000009 0081850f bb830000 0xa8766d44


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tvtpktfilter+a78
f78c6a78 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tvtpktfilter+a78

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tvtpktfilter

IMAGE_NAME:  tvtpktfilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  43cb0a1f

FAILURE_BUCKET_ID:  0xD1_CODE_AV_NULL_IP_tvtpktfilter+a78

BUCKET_ID:  0xD1_CODE_AV_NULL_IP_tvtpktfilter+a78

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

Post21 paź 2011, 08:26

tvtpktfilter.sys

PROCESS_NAME: AvastSvc.exe

Ciągle sterownik, ale to nie musi być on. Po pierwsze uaktualnij sterowniki chipsetu. Usuń Avasta, jeśli go używasz, a tak powinno być i tymczasowo zainstaluj Avirę (jest za darmo). Zmień też firewall, jeśli jakiegoś posiadasz.

Post22 paź 2011, 23:01

OK. Spróbuję tak jak sugerujesz tylko mam 2 pytania:
1. O jaki chipset chodzi -płyty głównej czy inny?
2. Używam windowsowego firewalla. Może zaproponuj może inny - lepszy(?).

Dziękuję i pozdrawiam

-- 22 paź 2011, 23:01 --

Wygląda na to, że to Avast był powodem moich kłopotów, bo po jego deinstalacji karta Wi-Fi chodzi.
Dzięki wszystkim za pomoc.