pantallazo azul

Estado
Cerrado para nuevas respuestas

dhueso

Nuevo Miembro
Miembro
Hola, llevo unos días que me sale un pantallazo azul, de esos famoso, que te ponen cardiaco, he leido el volcado con windbg y me sele este mensaje, haber si alguien me podría decir que lo origina y como podría solucionarlo, se lo agradecería muchisimo.

Me esta cansando ya de verlo es continuo.

Gracias.

Microsoft ® Windows Debugger Version 6.7.0005.0

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\MEMORY.DMP]

Kernel Complete Dump File: Full address space is 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+ *

*********************************************************************

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -

Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 2600.xpsp_sp2_rtm.040803-2158

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700

Debug session time: Wed Jun 13 23:48:58.000 2007 (GMT+2)

System Uptime: 0 days 6:47:44.685

*********************************************************************

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

*********************************************************************

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -

Loading Kernel Symbols

............................................................................................................................................................................

Loading User Symbols

Loading unloaded module list

..................................................

*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1902fe, a7b253e0, a7b250dc, ba5f5997}

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

*** ERROR: Module load completed but symbols could not be loaded for ShldDrv.SYS

*** ERROR: Module load completed but symbols could not be loaded for pavdrv51.sys

*** ERROR: Module load completed but symbols could not be loaded for NETFLTDI.SYS

Probably caused by : Ntfs.sys ( Ntfs+2997 )

Followup: MachineOwner
 
Estado
Cerrado para nuevas respuestas
Arriba Pie