Pantalla Azul en windows 7

Hola!
Hace una semana tenia instalado Windows Xp, esta semana me regalaron el Windows 7 Professional, no podia instalarlo porque me faltaba ram tenia 512MB, me decidi a comprar una memoria de 1Gb (DDR kingstone , con las mismas caracteristicas que la anteriror) para que asi quedara mi maquina con 1,5 GB.
por fin instale Windows 7, apartir de ahi, mi pc manda el pantallazo azul y me reinicia la computadora, eh leido sobre el tema un poco, y me tope con WinDbg, realice un "open Crash dump" a los 3 archivos que encontre en "C.\windows\minidump
y esto salio en los 2 ultimos
_______________ primero ____________________
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\121709-47406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Kernel base = 0x82619000 PsLoadedModuleList = 0x82761810
Debug session time: Thu Dec 17 23:48:48.537 2009 (GMT-6)
System Uptime: 0 days 0:08:45.615
Loading Kernel Symbols
...............................................................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {d, 0, 0, 0}
Probably caused by : ntkrpamp.exe ( nt!KiSystemFatalException+f )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR:  0x7f_d
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 82738da6 to 8265ff2b
STACK_TEXT: 
9858d9bc 82738da6 badb0d00 00020000 9858da18 nt!KiSystemFatalException+0xf
9858da7c 82859381 00000001 00000078 6d4e6f49 nt!ExAllocatePoolWithTag+0x1f6
9858db60 8283a1d7 8509fba8 85152eb0 845924c0 nt!IopParseDevice+0xc2b
9858dbdc 8286024d 00000000 9858dc30 00000040 nt!ObpLookupObjectName+0x4fa
9858dc38 828585ab 04cef48c 84152eb0 85beb201 nt!ObOpenObjectByName+0x159
9858dcb4 82863eb6 04cef4e8 00100081 04cef48c nt!IopCreateFile+0x673
9858dd00 8265c42a 04cef4e8 00100081 04cef48c nt!NtCreateFile+0x34
9858dd00 76ff64f4 04cef4e8 00100081 04cef48c nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
04cef4f0 00000000 00000000 00000000 00000000 0x76ff64f4
STACK_COMMAND:  kb
FOLLOWUP_IP:
nt!KiSystemFatalException+f
8265ff2b c3              ret
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!KiSystemFatalException+f
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007
FAILURE_BUCKET_ID:  0x7f_d_nt!KiSystemFatalException+f
BUCKET_ID:  0x7f_d_nt!KiSystemFatalException+f
Followup: MachineOwner
---------
------------------segundo --------------------------
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright...

1 Respuesta

Respuesta
1
Basicamente podria ser un problema con hardware... yo revisaria frecuencias y multiplos correctamente seteados, tambien podrias intentar arrancar solo con 1 modulo de memoria.. (el de 1 giga), o intercambiar posiciones de los modulos..
Aca tienes info sobre el tema.
http://support.microsoft.com/kb/842465

Añade tu respuesta

Haz clic para o

Más respuestas relacionadas