PC Crashea pantalla azul kbdclass.sys

[punkeR]

Hola, mi computadora se colgo y aparecio la pantalla azul de windows XP (de vez en cuando se freezea i tengo ke apagar i entra en modo seguro), usando el debugging tools me salio el error:

Probably caused by : kbdclass.sys ( kbdclass+1cf7 )

Alguien me puede decir que hago para que eso ya no crashee mi pc? como lo soluciono?

[Locutus]

Ese sys es del driver del Teclado Logitech, el cual te esta provocando el crash. Si lo instalastes, desinstalalo, haz una limpieza con algun programa tuneador (ccleaner, tuneup) e instala la ultima versión de ese driver.

[-Fnx-EduE]

http://www.file.net/process/kbdclass.sys.html

Es un controlador de teclado Logitech, si no tienes un teclado de ese tipo puedes probar desactivando el servicio correspondiente o simplemente cerrandolo desde el administrador de tareas.

[punkeR]

Tengo un teclado PCtronix...la cosa es que me aparecio de nuevo pantalla azul y esta vez en el debugger aparecio:
Probably caused by : win32k.sys ( win32k+91f1 )
:S y hoy dia se me colgo la pc en modo seguro lo cual no me habia pasado antes por eso no pensaba que fuera error de hardware porque solo se me colgaba en win xp pero cuando entraba en modo seguro con funciones de red nunca se colgaba solo hoy se colgo 1 vez..

[-Fnx-EduE]

Podrías poner todos los specs de tu PC? Como que es caminar a oscuras no saber con qué hardware cuentas.

[punkeR]

Placa base: Tipo de procesador Intel Celeron D, 3066 MHz
Chipset de la Placa Base nVIDIA nForce 7050-610i
Memoria del Sistema 2048 MB
Tipo de BIOS AMI (04/15/08)
Tarjeta gráfica nVIDIA GeForce 8400 GS
Acelerador 3D nVIDIA GeForce 8400 GS
Multimedia: Tarjeta de sonido nVIDIA MCP73 - High Definition Audio Controller
Windows XP 32 BIT

El ultimo pantallazo azul me dio como resultado Win32k.sys
SYMBOL_NAME: win32k+91f1

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: win32k.sys

BUCKET_ID: WRONG_SYMBOLS

Actualize el driver de la tarjeta grafica despues de que se cuelgue pero sigue ocurriendo

EDIT: hace unos minutos otro pantallazo y ahora el error es:
ntoskrnl.exe ( nt+5c736 )
:S

[punkeR]

Aqui el diagnostico del debugging tools
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini042710-02.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 \WINDOWS\system32\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
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a820
Debug session time: Tue Apr 27 19:07:45.218 2010 (GMT-5)
System Uptime: 0 days 0:39:43.722
************************************************** *******************
* 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 \WINDOWS\system32\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
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {bffd5fa4, 10a05021, b7754ad0, c}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** ***********************
*** ***
*** ***
*** 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 : ntoskrnl.exe ( nt+5c736 )

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

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: bffd5fa4, Virtual address for the attempted write.
Arg2: 10a05021, PTE contents.
Arg3: b7754ad0, (reserved)
Arg4: 0000000c, (reserved)

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

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

************************************************** ***********************
*** ***
*** ***
*** 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+ *
************************************************** *******************

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45e55172

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xBE

LAST_CONTROL_TRANSFER: from 00000000 to 80533736

STACK_TEXT:
b7754a50 00000000 bffd5fa4 10a05021 b7754ad0 nt+0x5c736


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+5c736
80533736 ?? ???

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+5c736

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

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

[Wiily]

a mi parecer problema de memoria , de antemano prueba con otra memoria. y dime si tu so boto el mismo problems . sino ageragme aver hablamos . mas espif. de tu problems . [email protected]