problema blue screen en windows 7 home premium

Publicado: Domingo 14 Marzo 2010, 2:16

Hola que tal de igual manera tengo problemas con mi windows 7 home premium con respecto a blue screen. Agradecere infinitamente su ayuda para solucionar mi situacion.

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

Loading Dump File [C:\Windows\Minidump\030810-73008-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 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 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x82a4d000 PsLoadedModuleList = 0x82b95810
Debug session time: Mon Mar 8 12:15:40.463 2010 (GMT-6)
System Uptime: 0 days 0:00:53.601
*********************************************************************
* 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 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
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 8552e4dc, 0, 0}

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

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

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

0: kd> ANALYZE -V
*** WARNING: Unable to verify timestamp for kdcom.dll
*** ERROR: Module load completed but symbols could not be loaded for kdcom.dll
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*** WARNING: Unable to verify timestamp for WMILIB.SYS
*** ERROR: Module load completed but symbols could not be loaded for WMILIB.SYS
*** WARNING: Unable to verify timestamp for msisadrv.sys
*** ERROR: Module load completed but symbols could not be loaded for msisadrv.sys
*** WARNING: Unable to verify timestamp for mcupdate.dll
*** ERROR: Module load completed but symbols could not be loaded for mcupdate.dll
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*** WARNING: Unable to verify timestamp for BOOTVID.dll
*** ERROR: Module load completed but symbols could not be loaded for BOOTVID.dll
*** WARNING: Unable to verify timestamp for CLFS.SYS
*** ERROR: Module load completed but symbols could not be loaded for CLFS.SYS
*** WARNING: Unable to verify timestamp for CI.dll
*** ERROR: Module load completed but symbols could not be loaded for CI.dll
*** WARNING: Unable to verify timestamp for Wdf01000.sys
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*** WARNING: Unable to verify timestamp for WDFLDR.SYS
*** ERROR: Module load completed but symbols could not be loaded for WDFLDR.SYS
*** WARNING: Unable to verify timestamp for ACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
*** WARNING: Unable to verify timestamp for pci.sys
*** ERROR: Module load completed but symbols could not be loaded for pci.sys
*** WARNING: Unable to verify timestamp for vdrvroot.sys
*** ERROR: Module load completed but symbols could not be loaded for vdrvroot.sys
*** WARNING: Unable to verify timestamp for partmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
*** WARNING: Unable to verify timestamp for compbatt.sys
*** ERROR: Module load completed but symbols could not be loaded for compbatt.sys
*** WARNING: Unable to verify timestamp for BATTC.SYS
*** ERROR: Module load completed but symbols could not be loaded for BATTC.SYS
*** WARNING: Unable to verify timestamp for volmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for volmgr.sys
*** WARNING: Unable to verify timestamp for volmgrx.sys
*** ERROR: Module load completed but symbols could not be loaded for volmgrx.sys
*** WARNING: Unable to verify timestamp for pciide.sys
*** ERROR: Module load completed but symbols could not be loaded for pciide.sys
*** WARNING: Unable to verify timestamp for PCIIDEX.SYS
*** ERROR: Module load completed but symbols could not be loaded for PCIIDEX.SYS
*** WARNING: Unable to verify timestamp for mountmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for mountmgr.sys
*** WARNING: Unable to verify timestamp for atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
*** WARNING: Unable to verify timestamp for ataport.SYS
*** ERROR: Module load completed but symbols could not be loaded for ataport.SYS
*** WARNING: Unable to verify timestamp for amdxata.sys
*** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
*** WARNING: Unable to verify timestamp for fltmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltmgr.sys
*** WARNING: Unable to verify timestamp for fileinfo.sys
*** ERROR: Module load completed but symbols could not be loaded for fileinfo.sys
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
*** WARNING: Unable to verify timestamp for dump_atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_atapi.sys
*** WARNING: Unable to verify timestamp for dump_dumpfve.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_dumpfve.sys
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** WARNING: Unable to verify timestamp for msrpc.sys
*** ERROR: Module load completed but symbols could not be loaded for msrpc.sys
*** WARNING: Unable to verify timestamp for ksecdd.sys
*** ERROR: Module load completed but symbols could not be loaded for ksecdd.sys
*** WARNING: Unable to verify timestamp for fvevol.sys
*** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS
*** WARNING: Unable to verify timestamp for disk.sys
*** ERROR: Module load completed but symbols could not be loaded for disk.sys
*** WARNING: Unable to verify timestamp for dump_ataport.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_ataport.sys
*** WARNING: Unable to verify timestamp for cng.sys
*** ERROR: Module load completed but symbols could not be loaded for cng.sys
*** WARNING: Unable to verify timestamp for pcw.sys
*** ERROR: Module load completed but symbols could not be loaded for pcw.sys
*** WARNING: Unable to verify timestamp for Fs_Rec.sys
*** ERROR: Module load completed but symbols could not be loaded for Fs_Rec.sys
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
*** WARNING: Unable to verify timestamp for NETIO.SYS
*** ERROR: Module load completed but symbols could not be loaded for NETIO.SYS
*** WARNING: Unable to verify timestamp for ksecpkg.sys
*** ERROR: Module load completed but symbols could not be loaded for ksecpkg.sys
*** WARNING: Unable to verify timestamp for rdyboost.sys
*** ERROR: Module load completed but symbols could not be loaded for rdyboost.sys
*** WARNING: Unable to verify timestamp for mup.sys
*** ERROR: Module load completed but symbols could not be loaded for mup.sys
*** WARNING: Unable to verify timestamp for hwpolicy.sys
*** ERROR: Module load completed but symbols could not be loaded for hwpolicy.sys
*** WARNING: Unable to verify timestamp for crashdmp.sys
*** ERROR: Module load completed but symbols could not be loaded for crashdmp.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for fwpkclnt.sys
*** ERROR: Module load completed but symbols could not be loaded for fwpkclnt.sys
*** WARNING: Unable to verify timestamp for mfewfpk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfewfpk.sys
*** WARNING: Unable to verify timestamp for TDI.SYS
*** ERROR: Module load completed but symbols could not be loaded for TDI.SYS
*** WARNING: Unable to verify timestamp for volsnap.sys
*** ERROR: Module load completed but symbols could not be loaded for volsnap.sys
*** WARNING: Unable to verify timestamp for TVALZ_O.SYS
*** ERROR: Module load completed but symbols could not be loaded for TVALZ_O.SYS
*** WARNING: Unable to verify timestamp for spldr.sys
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
Couldn't resolve error at 'NALYZE -V'
0: kd> !ANALIZE - V
No export ANALIZE found
0: kd> !ANALIZE-V
No export ANALIZE-V found
0: kd> ! analize -v
No export analize found
0: kd> ! analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, MCA_ASSERT
Arg2: 8552e4dc, Address of WHEA_ERROR_RECORD structure
Arg3: 00000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had
the error
Arg4: 00000000, Low 32 bits of MCi_STATUS MSR for the MCA bank that had
the error

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

FAULTING_MODULE: 82a4d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

WHEA_ERROR_RECORD: !errrec ffffffff8552e4dc

BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
88f27cc4 82b1c0c5 8552e4c0 82bb4c28 82bb4c20 nt+0x322493
88f27ce4 82b1ceef 82bb4c20 8552e4c0 82bb4c50 nt+0xcf0c5
88f27d00 82abb02b 82bb4c20 00000000 844df4c0 nt+0xcfeef
88f27d50 82c5b66d 00000001 9d97111f 00000000 nt+0x6e02b
88f27d90 82b0d1d9 82abaf1e 00000001 00000000 nt+0x20e66d
00000000 00000000 00000000 00000000 00000000 nt+0xc01d9

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

BUCKET_ID: WRONG_SYMBOLS

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

Publicado: Domingo 14 Marzo 2010, 2:32

Testea tu disco duro con hddregenerator y la memoria ram con memtest

Salu2

Gohuca

Publicado: Lunes 15 Marzo 2010, 0:24

gohuca escribió:

Testea tu disco duro con hddregenerator y la memoria ram con memtest

Salu2

Gohuca

Muchas gracias por tus recomendaciones y te comento lo siguiente, ya aplique los dos test y ninguno de los programas me arrojo un solo error.
Que mas puedo hacer?

Gracias

Administrador Registrado: Oct 21, 2008 Mensajes: 10438

¿Tu disco duro es SATA? Si es así, ¿lo tienes en modo IDE o en modo AHCI en la BIOS?

Saludos.

Publicado: Martes 16 Marzo 2010, 3:18

Sabes al parecer mi problema es generado por que los drivers de video no estan actualizados pero a la hora de intentar actualizar ATI RADEON no me permite hacerlo.

Saludos

Administrador Registrado: Oct 21, 2008 Mensajes: 10438

¿Tu ordenador es de marca? Si es así, deberás descargar los drivers de tu gráfica desde la web del fabricante de tu ordenador.

Saludos.