errores pantalla azul luego de instalar vista ultimate x64

Foro referente al sistema operativo Windows Vista (Longhorn)
pablo_delu
Usuario linuxero
Usuario linuxero
Mensajes: 4
Registrado: 18 Sep 2008, 22:03
Contactar:

errores pantalla azul luego de instalar vista ultimate x64

Mensajepor pablo_delu » 18 Sep 2008, 22:11

hola como andan??
soy nuevo, me acabo de registrar y les quiero comentar que tengo un problema
ayer a la noche me instale windows vista ultimate x64 en ingles en mi otro ordenador y el problema es que a cada rato me saltan errores de pantalla azul
aveces dicen paged fault in nonpaged area, aveces irql_not_less_or_equal y otras veces solo 0x00000... etc
el error me puede saltar unos 5 minutos despues de prender la pc o unas 2 o 3 horas luego, lo que quiero decir con esto es que me sale en cualquier momento no cuando hago una funcion especifica
mi maquina es:
mother: msi k9n neo
memorias:2x1gb ocz platinium rev2 en dualchannel
procesador: amd athlon 64 x2 5600+ de 2.8
placa de video: visontek ati radeon x1950 pro 256mb
disco rigido: western digital de 160gb
espero que me puedan tirar una mano porque necesito arreglarla rapido ya que la uso mucho para trabajar
bueno muchas gracias

saludos!!!

Avatar de Usuario
robert_dll
Usuario Bill Gates
Usuario Bill Gates
Mensajes: 1615
Registrado: 08 Feb 2008, 04:59
Agradecido : 1 vez
Agradecimiento recibido: 2 veces
Contactar:

Re: errores pantalla azul luego de instalar vista ultimate x64

Mensajepor robert_dll » 18 Sep 2008, 22:21

Has instalado todos los drivers después de instalar Windows? Si no lo has hecho empieza por el driver del chipset.

Saludos
No respondo dudas por MP, por favor publicalas en el foro para compartir la posible solución con toda la comunidad ;)

pablo_delu
Usuario linuxero
Usuario linuxero
Mensajes: 4
Registrado: 18 Sep 2008, 22:03
Contactar:

Re: errores pantalla azul luego de instalar vista ultimate x64

Mensajepor pablo_delu » 18 Sep 2008, 22:32

hola,gracias por responder, ya actualize todos los drivers de TODO y tampoco obtube solucion asi que eso ya lo descarte
si tenes alguna otra idea no dudes en decirme, gracias!

Avatar de Usuario
robert_dll
Usuario Bill Gates
Usuario Bill Gates
Mensajes: 1615
Registrado: 08 Feb 2008, 04:59
Agradecido : 1 vez
Agradecimiento recibido: 2 veces
Contactar:

Re: errores pantalla azul luego de instalar vista ultimate x64

Mensajepor robert_dll » 18 Sep 2008, 22:52

Sin al menos un código de error completo no puedo seguir ayudandote, en el próximo pantallazo toma nota de todos los datos, principalmente código de error y el nombre del archivo relacionado en caso de que exista.
No respondo dudas por MP, por favor publicalas en el foro para compartir la posible solución con toda la comunidad ;)

pablo_delu
Usuario linuxero
Usuario linuxero
Mensajes: 4
Registrado: 18 Sep 2008, 22:03
Contactar:

Re: errores pantalla azul luego de instalar vista ultimate x64

Mensajepor pablo_delu » 21 Sep 2008, 04:31

hola gracias por las respuestas
aca analize el archivo memory.dmp con el windbg
estos son los resultados:

____________________________________________________


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


Loading Dump File [C:\Users\Pablo\Desktop\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18000.amd64fre.longhorn_rtm.080118-1840
Kernel base = 0xfffff800`01a1a000 PsLoadedModuleList = 0xfffff800`01bdfdb0
Debug session time: Sun Sep 21 00:04:01.433 2008 (GMT-3)
System Uptime: 0 days 1:20:10.292
Loading Kernel Symbols
..................................................................................................................................
Loading User Symbols
.......................................
Loading unloaded module list
........Unable to enumerate user-mode unloaded modules, NTSTATUS 0xC0000147
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {7fefe7256ca, 0, ffff, fffffa6004f69ca0}

*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+209 )

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

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

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them. A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 000007fefe7256ca, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 000000000000ffff, Thread->KernelApcDisable
Arg4: fffffa6004f69ca0, Previous KernelApcDisable

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

*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************

FAULTING_IP:
GDI32!NtGdiGetAppClipBox+a
000007fe`fe7256ca c3 ret

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001a6f12e to fffff80001a6f390

STACK_TEXT:
fffffa60`04f69ad8 fffff800`01a6f12e : 00000000`00000001 000007fe`fe7256ca 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffffa60`04f69ae0 fffff800`01a6f044 : fffffa80`02dd4bb0 00000000`00000000 00000000`00000000 fffffa80`046e57a0 : nt!KiBugCheckDispatch+0x6e
fffffa60`04f69c20 000007fe`fe7256ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x209
00000000`05ffe298 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : GDI32!NtGdiGetAppClipBox+0xa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiSystemServiceExit+209
fffff800`01a6f044 4883ec50 sub rsp,50h

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiSystemServiceExit+209

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 479192b7

FAILURE_BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+209

BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+209

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

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

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them. A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 000007fefe7256ca, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 000000000000ffff, Thread->KernelApcDisable
Arg4: fffffa6004f69ca0, Previous KernelApcDisable

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

*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************

FAULTING_IP:
GDI32!NtGdiGetAppClipBox+a
000007fe`fe7256ca c3 ret

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001a6f12e to fffff80001a6f390

STACK_TEXT:
fffffa60`04f69ad8 fffff800`01a6f12e : 00000000`00000001 000007fe`fe7256ca 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffffa60`04f69ae0 fffff800`01a6f044 : fffffa80`02dd4bb0 00000000`00000000 00000000`00000000 fffffa80`046e57a0 : nt!KiBugCheckDispatch+0x6e
fffffa60`04f69c20 000007fe`fe7256ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x209
00000000`05ffe298 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : GDI32!NtGdiGetAppClipBox+0xa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiSystemServiceExit+209
fffff800`01a6f044 4883ec50 sub rsp,50h

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiSystemServiceExit+209

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 479192b7

FAILURE_BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+209

BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+209

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

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

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them. A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 000007fefe7256ca, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 000000000000ffff, Thread->KernelApcDisable
Arg4: fffffa6004f69ca0, Previous KernelApcDisable

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

*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************

FAULTING_IP:
GDI32!NtGdiGetAppClipBox+a
000007fe`fe7256ca c3 ret

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001a6f12e to fffff80001a6f390

STACK_TEXT:
fffffa60`04f69ad8 fffff800`01a6f12e : 00000000`00000001 000007fe`fe7256ca 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffffa60`04f69ae0 fffff800`01a6f044 : fffffa80`02dd4bb0 00000000`00000000 00000000`00000000 fffffa80`046e57a0 : nt!KiBugCheckDispatch+0x6e
fffffa60`04f69c20 000007fe`fe7256ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x209
00000000`05ffe298 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : GDI32!NtGdiGetAppClipBox+0xa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiSystemServiceExit+209
fffff800`01a6f044 4883ec50 sub rsp,50h

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiSystemServiceExit+209

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 479192b7

FAILURE_BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+209

BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+209

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

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

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them. A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 000007fefe7256ca, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 000000000000ffff, Thread->KernelApcDisable
Arg4: fffffa6004f69ca0, Previous KernelApcDisable

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

*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************

FAULTING_IP:
GDI32!NtGdiGetAppClipBox+a
000007fe`fe7256ca c3 ret

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001a6f12e to fffff80001a6f390

STACK_TEXT:
fffffa60`04f69ad8 fffff800`01a6f12e : 00000000`00000001 000007fe`fe7256ca 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffffa60`04f69ae0 fffff800`01a6f044 : fffffa80`02dd4bb0 00000000`00000000 00000000`00000000 fffffa80`046e57a0 : nt!KiBugCheckDispatch+0x6e
fffffa60`04f69c20 000007fe`fe7256ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x209
00000000`05ffe298 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : GDI32!NtGdiGetAppClipBox+0xa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiSystemServiceExit+209
fffff800`01a6f044 4883ec50 sub rsp,50h

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiSystemServiceExit+209

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 479192b7

FAILURE_BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+209

BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+209

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

0: kd> analyze -v
*** ERROR: Symbol file could not be found. Defaulted to export symbols for atiumd6a.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for atiumd64.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for slc.dll -
*** 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 fdc.sys
*** ERROR: Module load completed but symbols could not be loaded for fdc.sys
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
*** WARNING: Unable to verify timestamp for flpydisk.sys
*** ERROR: Module load completed but symbols could not be loaded for flpydisk.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for Rtlh64.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.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 Null.SYS
*** ERROR: Module load completed but symbols could not be loaded for Null.SYS
*** WARNING: Unable to verify timestamp for Msfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Msfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for cdfs.sys
*** ERROR: Module load completed but symbols could not be loaded for spsys.sys
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
Couldn't resolve error at 'nalyze -v'

____________________________________________________

bueno espero que te sirvan para poder ayudarme,

desde ya gracuias
saludos!


Volver a “Windows Vista”

¿Quién está conectado?

Usuarios navegando por este Foro: Yahoo [Bot] y 2 invitados