Página 1 de 1
javigarci69
javigarci69
ZoNeR@
ZoNeR@
 
Mensajes: 4
Registrado: Vie 17 Feb, 01:00

» Mar 22 Oct, 23:21

Hola, cada vez que intento actualizar mi avast! Internet Security a la versión 14, cuando me pide que reinicie el PC y lo hago me aparece una pantalla azul que dice:
Se ha encontrado un problema y Windows ha sido apagado para evitar dañar al equipo.
El problema parece estar originado por el siguiente archivo: fssfltr_tdi.sys.
Se descargo el controlador sin cancelar las operaciones pendientes.

Esto me ha pasado varias veces y restaurando el sistema parece que se arregla, pero ahora me aparece el antivirus como que ha caducado, he pedido a avast una nueva licencia, y cuando la ejecuto me dice que no se puede introducir el archivo de licencia y que el sistema no puede hallar el archivo especificado, no se que ha pasado pero la licencia me caduca en junio del 2014 y ahora me he quedado sin antivirus,

Ademas cada vez que enciendo el ordenador me aparece un mensaje que dice que no se puede obtener el sistema de archivo de la unidad y me salen muchos numeros y letras x entre parentesis, no pasa nada por que el sistema operativo se inicia sin ningun problema, pero es muy molesto.

Tengo Windows XP SP3 de 32 bits.

¿alguna solución? Gracias.

Aquí dejo el resultado del archivo equivalente a la pantalla azul.

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


Loading Dump File [C:\WINDOWS\Minidump\Mini102213-01.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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Oct 22 14:14:39.171 2013 (UTC + 2:00)
System Uptime: 0 days 0:00:30.937
*********************************************************************
* 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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D4, {b53d6fc0, ff, 1, 80546b09}

*** 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 ***
*** ***
*************************************************************************
Probably caused by : ntkrnlpa.exe ( nt+6fb09 )

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

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

SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD (d4)
A driver unloaded without cancelling lookaside lists, DPCs, worker threads, etc.
The broken driver's name is displayed on the screen.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
An attempt was made to access the driver at raised IRQL after it unloaded.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: b53d6fc0, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 80546b09, address which referenced memory

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

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 51d4d90f

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
b53d6fc0

CURRENT_IRQL: ff

FAULTING_IP:
nt+6fb09
80546b09 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD4

LAST_CONTROL_TRANSFER: from 00000000 to 8054480c

STACK_TEXT:
b84ebb6c 00000000 b53d6fc0 000000ff 00000001 nt+0x6d80c


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt+6fb09
80546b09 ?? ???

SYMBOL_NAME: nt+6fb09

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------
Avatar de Usuario
rayoni
Supermoderador
Supermoderador
 
Mensajes: 11936
Registrado: Dom 07 Dic, 01:00

» Mié 23 Oct, 07:41

Actualiza los controladores del sistema, en este caso por el log que subes el pantallazo es distinto a lo que comentas del archivo fssfltr_tdi.sys... A no ser que te haya creado otro log con lo que dices.

Para lo que comentas de la ventana con el mensaje y si sigue tirando pantallazos después de actualizar controladores realiza una reparación del sistema.

:arrow: Reparar XP. Como realizar una reparación en Windows XP






Saludos...
Imagen
javigarci69
javigarci69
ZoNeR@
ZoNeR@
 
Mensajes: 4
Registrado: Vie 17 Feb, 01:00

» Mié 23 Oct, 19:39

Problema solucionado, resulta que el archivo "fssfltr_tdi.sys" estaba vinculado al programa "Safety Family" de "Windows Essentials".
Al desinstalar el control parental se soluciono.
Página 1 de 1

Volver a Software