Foro de InfoSpyware - Foro de Hijackthis - Foro de Virus

Un saludo a todos, se me ha planteado un problema que es el siguiente:

Al reproducir video, se me cuelga el ordenador, da igual con qué reproductor.

He seguido los pasos que indica Claw en el siguiente link:

http://www.forospyware.com/archive/t-87861.html

Me he instalado el depurador, y el mensaje que me da, a ver si alguien me puede decir que pasa, es:


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


Loading Dump File [C:\WINDOWS\Minidump\Mini080408-08.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 2
*** 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) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Aug 4 03:00:51.875 2008 (GMT+2)
System Uptime: 0 days 0:20:10.579
************************************************** *******************
* 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 2
*** 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
...........
Unable to load image atkosdmini.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for atkosdmini.dll
*** ERROR: Module load completed but symbols could not be loaded for atkosdmini.dll
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {80000015, 1c, 0, 804fa246}

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

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

*** WARNING: Unable to verify timestamp for atkdisp.dll
*** ERROR: Module load completed but symbols could not be loaded for atkdisp.dll
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*** WARNING: Unable to verify timestamp for dxg.sys
*** ERROR: Module load completed but symbols could not be loaded for dxg.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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
Probably caused by : atkosdmini.dll ( atkosdmini+1370 )

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


Muchas gracias

Buenas, yo tengo un error similar, pero a mi me ha dado mientras jugaba a Sacred 2.

Siguiendo las instrucciones de debug a mi me salio lo siguiente:

MODULE_NAME: atkdisp

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 488ee091

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en "0x%08lx" hace referencia a la memoria en "0x%08lx". La memoria no se puede "%s".

FAULTING_IP:
atkdisp+1500
bf013500 8b4008 mov eax,dword ptr [eax+8]

TRAP_FRAME: a5c7ac04 -- (.trap ffffffffa5c7ac04)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=e16023e0 edi=a5c7ad00
eip=bf013500 esp=a5c7ac78 ebp=a5c7ad00 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
atkdisp+0x1500:
bf013500 8b4008 mov eax,dword ptr [eax+8] ds:0023:00000008=????????
Resetting default scope

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 804fe5eb to 804f9d1b

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a5c7a7cc 804fe5eb 0000008e c0000005 bf013500 nt!KeBugCheckEx+0x1b
a5c7ab94 80541175 a5c7abb0 00000000 a5c7ac04 nt!KeRaiseUserException+0xc29
a5c7ac28 8054070c ffffffff 00000000 00000023 nt!Kei386EoiHelper+0x1d9
a5c7ad10 bf000e2a 05607b15 00000000 00000000 nt!KeReleaseInStackQueuedSpinLockFromDpcLevel+0xb7 4
a5c7ad58 8054070c 0167eb30 0167eb18 7c91eb94 dxg+0xe2a
a5c7addc 805451ce f710fb85 89170990 00000000 nt!KeReleaseInStackQueuedSpinLockFromDpcLevel+0xb7 4
a5c7ade0 f710fb85 89170990 00000000 4020027f nt!KiDispatchInterrupt+0x72e
a5c7ade4 89170990 00000000 4020027f 01590000 NDIS!NdisFreeToBlockPool+0x15e1
a5c7ade8 00000000 4020027f 01590000 01d18778 0x89170990


STACK_COMMAND: kb

FOLLOWUP_IP:
atkdisp+1500
bf013500 8b4008 mov eax,dword ptr [eax+8]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: atkdisp.dll

SYMBOL_NAME: atkdisp+1500

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

Alguien me puede ayudar?