Bluescreen

Prilimaj sem log od hijackthis. Kater antivirus(in ostalo zaščito) uporabljaš?

Microsoft ® Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symb...

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Dec 21 13:45:51.406 2008 (GMT+4)
System Uptime: 0 days 2:17:39.125
Loading Kernel Symbols
...............................................................
.....................................................
Loading User Symbols
Loading unloaded module list
...............
Unable to load image AFS2K.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AFS2K.SYS
*** ERROR: Module load completed but symbols could not be loaded for AFS2K.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8053a930, f7a33020, f7a32d1c}

Probably caused by : AFS2K.SYS ( AFS2K+6ef3 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8053a930, The address that the exception occurred at
Arg3: f7a33020, Exception Record Address
Arg4: f7a32d1c, Context Record Address
Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Navodilo na 0x%08lx se je sklicevalo na pomnilnik na 0x%08lx . Pomnilnika ni bilo mogo


FAULTING_IP:
nt!memmove+a0
8053a930 8807 mov byte ptr [edi],al

EXCEPTION_RECORD: f7a33020 -- (.exr 0xfffffffff7a33020)
ExceptionAddress: 8053a930 (nt!memmove+0x000000a0)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 30f774ce
Attempt to write to address 30f774ce

CONTEXT: f7a32d1c -- (.cxr 0xfffffffff7a32d1c)
eax=00000041 ebx=00000000 ecx=0000000a edx=00000002 esi=f774e2f0 edi=30f774ce
eip=8053a930 esp=f7a330e8 ebp=f7a330f0 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!memmove+0xa0:
8053a930 8807 mov byte ptr [edi],al ds:0023:30f774ce=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc0000005 - Navodilo na 0x%08lx se je sklicevalo na pomnilnik na 0x%08lx . Pomnilnika ni bilo mogo

EXCEPTION_PARAMETER1: 00000001

EXCEPTION_PARAMETER2: 30f774ce

WRITE_ADDRESS: 30f774ce

FOLLOWUP_IP:
AFS2K+6ef3
f7752ef3 ?? ???

BUGCHECK_STR: 0x7E

LOCK_ADDRESS: 8055b4e0 -- (!locks 8055b4e0)

Resource @ nt!PiEngineLock (0x8055b4e0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x8055b4e0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from f7752ef3 to 8053a930

STACK_TEXT:
f7a330f0 f7752ef3 30f774ce f774e2f0 0000000c nt!memmove+0xa0
WARNING: Stack unwind information not available. Following frames may be wrong.
f7a33108 f775212c f7757305 f774e2f0 f7757300 AFS2K+0x6ef3
f7a3311c f7751cde f774e208 86373100 00000000 AFS2K+0x612c
f7a33150 f774fe5c f774e208 f7a33100 f774e200 AFS2K+0x5cde
f7a33988 f774e3c5 864de030 00000008 f774e2f0 AFS2K+0x3e5c
f7a339b8 f774e084 00000000 00000060 6f436d49 AFS2K+0x23c5
f7a339e8 804f73bf 865caa18 86716158 e2f77470 AFS2K+0x2084
f7a33a00 80590eff f774e00c 00000003 00000001 nt!PpvUtilCallAddDevice+0x19
f7a33ac8 80592264 00000000 01000001 00000000 nt!PipCallDriverAddDevice+0x3b9
f7a33d24 805927fa 867df398 00000001 00000000 nt!PipProcessDevNodeTree+0x1a4
f7a33d54 804f698e 00000003 8055b5c0 8056485c nt!PiRestartDevice+0x80
f7a33d7c 8053876d 00000000 00000000 867c2640 nt!PipDeviceActionWorker+0x168
f7a33dac 805cff64 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f7a33ddc 805460de 8053867e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: AFS2K+6ef3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AFS2K

IMAGE_NAME: AFS2K.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 3c7ac329

STACK_COMMAND: .cxr 0xfffffffff7a32d1c ; kb

FAILURE_BUCKET_ID: 0x7E_AFS2K+6ef3

BUCKET_ID: 0x7E_AFS2K+6ef3

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