Problem sa utorrentom

Ako bi mi netko mogao, molim vas, pomoći oko jednog problema.

Dakle, kada pokrenem uTorrent iduće što vidim je BSOD!

Dosada nisam imao takve probleme, do prije 2-3 dana!

Napiši konfiguraciju.Pokušaj reinstalirati drivere za mrežnu karticu.Napiši stop code iz bsod-a-

STOP code su oni brojevi i x.Primjer: 0x0000008E (0x00000005, 0xBF804C75, OxF797D4FC, 0x00000000).

Pise na samome BSOD-u kada se pojavi. U slucaju da ti se racunalo automatski restarta nakon BSOD-a, tada trebas iskljuciti automatski restart.

1. Desni klik na My Computer

2. Advanced

3. U Startup and Recovery odaberi settings

4. Makni kvacicu sa Automatically restart

(postupak kod XP-a)

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Teh info:

STOP: 0x000000D1 (0X00000000,0X00000002,0X00000000, 0X887E88EA)

______________________________________________________________

Radio sam analizu dump file-a i evo ovo je rezultat pa ako netko može pohvatat što to sve znači!

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


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

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Wed May 20 20:05:35.578 2009 (GMT+2)
System Uptime: 0 days 0:16:05.144
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {0, 2, 0, 887e88ea}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for psched.sys
*** ERROR: Module load completed but symbols could not be loaded for psched.sys
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
*** WARNING: Unable to verify timestamp for Epfwndis.sys
*** ERROR: Module load completed but symbols could not be loaded for Epfwndis.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Probably caused by : Epfwndis.sys ( Epfwndis+114d )

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

gadan neki dump file...moram priznat da nemam pojma što se tu dogodilo...  :O

Skinuo sam: Windows XP with Service Pack 2 x86 retail symbols, all languages

Pokrenuo WinDbg i evo rezultati:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini052009-13.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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Wed May 20 20:05:35.578 2009 (GMT+2)
System Uptime: 0 days 0:16:05.144
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
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {0, 2, 0, 887e88ea}

*** WARNING: Unable to verify timestamp for psched.sys
*** WARNING: Unable to verify timestamp for NDIS.sys
*** WARNING: Unable to verify timestamp for Epfwndis.sys
*** ERROR: Module load completed but symbols could not be loaded for Epfwndis.sys
Probably caused by : Epfwndis.sys ( Epfwndis+114d )

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

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: 00000000, value 0 = read operation, 1 = write operation
Arg4: 887e88ea, address which referenced memory

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


READ_ADDRESS:  00000000

CURRENT_IRQL:  2

FAULTING_IP:
+114d
887e88ea f3a5            rep movs dword ptr es:[edi],dword ptr [esi]

CUSTOMER_CRASH_COUNT:  13

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  vsmon.exe

LAST_CONTROL_TRANSFER:  from 887bf1e4 to 887e88ea

SYMBOL_ON_RAW_STACK:  1

STACK_ADDR_RAW_STACK_SYMBOL: ffffffffb69627e0

STACK_COMMAND:  dds B69627E0-0x20 ; kb

STACK_TEXT: 
b69627c0  01acf4e0
b69627c4  887c7983
b69627c8  89d642cc
b69627cc  b6962a08
b69627d0  b6962a08
b69627d4  b6962894
b69627d8  b69629fc
b69627dc  b60e814d Epfwndis+0x114d
b69627e0  00000001
b69627e4  88acf4e0
b69627e8  00000000
b69627ec  b6962834
b69627f0  887e3e48
b69627f4  00000024
b69627f8  b6962a08
b69627fc  b6962894
b6962800  89ce1cb8
b6962804  b6962840
b6962808  b69629fc
b696280c  00000000
b6962810  88960008
b6962814  887f03b1
b6962818  00002711
b696281c  b6962840
b6962820  89ce1cb8
b6962824  89ce1cb0
b6962828  b69629fc
b696282c  00000041
b6962830  00000000
b6962834  b6962854
b6962838  9c994da2 epfw+0x7da2
b696283c  00002711


FOLLOWUP_IP:
Epfwndis+114d
b60e814d ??              ???

SYMBOL_NAME:  Epfwndis+114d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Epfwndis

IMAGE_NAME:  Epfwndis.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48a956b3

FAILURE_BUCKET_ID:  0xD1_Epfwndis+114d

BUCKET_ID:  0xD1_Epfwndis+114d

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

Anblivbl... aj mi molim te reci iz kojih detalja si to pričitao, izvukao te informacije?

i da, ima dva FW-a (imao)

Tnx!!!

Ahm...

godine čine svoje... (i kaciga) uostalom nije teško kad znaš gdje treba gledat...

Kak je već ihush rekao - Epfwndis.sys (ESET Personal...) + vsmon.exe (ZoneAlarm)

Ovako ja imam jedan problem sa uTorrentom. Kad skinem neki torrent i pokrenem ga i počinje skidanje, ali jako sporo ali nema veze, i onda dolazi do problema u kojem mi uspori internet i kad hocu surfat internetom to nije moguće jer se stranice učitavaju i učitavaju i nikako da se učitaju, neznam u čemu je problem, kada izgasim uTorrent moram pričekat 10-ak minuta da mi se brzina vrati i da mogu opet normalno surfat, neznam u čemu je problem???