Pantallazo azul ocasional

Invitado

Bueno primero q nada, saludos. Bueno mi post es por el siguiente problema, mi pc da este pantallazo azul solo en raras ocaciones, o mayormente cuando pasa mucho tiempo prendida. Bueno copie el log del volcado de memoria a ver si alguien sabe como solucionar este problema.

Por lo que yo veo es problemas del realtek HD , quisiera saber si alguien tuvo este mismo inconveniente, para saber como solucionarlo. Sera q es por actualizar el controlador u otra cosa?

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

Loading Dump File [C:\WINDOWS\Minidump\Mini031710-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
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Mar 17 03:08:01.781 2010 (GMT-4)
System Uptime: 0 days 14:16:54.401
*********************************************************************
* 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
...............
*** WARNING: Unable to verify timestamp for RtkHDAud.sys
*** ERROR: Module load completed but symbols could not be loaded for RtkHDAud.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, b77dbb5b, b68db71c, 0}

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

*** WARNING: Unable to verify timestamp for portcls.sys
*** ERROR: Module load completed but symbols could not be loaded for portcls.sys
*** WARNING: Unable to verify timestamp for ks.sys
*** ERROR: Module load completed but symbols could not be loaded for ks.sys
*** WARNING: Unable to verify timestamp for sysaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for sysaudio.sys
*************************************************************************
*** ***
*** ***
*** 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 : RtkHDAud.sys ( RtkHDAud+6bb5b )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: b77dbb5b, The address that the exception occurred at
Arg3: b68db71c, Trap Frame
Arg4: 00000000

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 ***
*** ***
*************************************************************************
*********************************************************************
* 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: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48070b50

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en "0x%08lx" hace referencia a la memoria en "0x%08lx". La memoria no se puede "%s".

FAULTING_IP:
RtkHDAud+6bb5b
b77dbb5b ?? ???

TRAP_FRAME: b68db71c -- (.trap 0xffffffffb68db71c)
Unable to read trap frame at b68db71c

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from b77dc14d to b77dbb5b

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b68db78c b77dc14d b68db9e0 b77990de 00000000 RtkHDAud+0x6bb5b
b68db794 b77990de 00000000 88a16128 88ddcc28 RtkHDAud+0x6c14d
b68db9e0 b775e97d b775e872 00000000 b775e97d RtkHDAud+0x290de
b68dba04 b775e9cf 889c52d0 88a16128 e1addf4c portcls+0x1297d
b68dba2c b9e4ef5c 00000004 89963a20 89963a18 portcls+0x129cf
b68dba90 b9e4eed9 889c52d0 0000000c e1addf4c ks+0x8f5c
b68dbab4 b775c6a9 889c52d0 0000000c e1addec0 ks+0x8ed9
b68dbac8 b776970f 889c52d0 0000000c e1addec0 portcls+0x106a9
b68dbb00 b775c74d 88a160a8 89614030 889c52d0 portcls+0x1d70f
b68dbb1c b9e4ef1f 89614030 889c52d0 b68dbb44 portcls+0x1074d
b68dbb2c b775c8c0 89614030 889c52d0 896140e8 ks+0x8f1f
b68dbb44 b775c881 89614030 889c52d0 b68dbb78 portcls+0x108c0
b68dbb54 b7b6608e 89614030 889c52d0 00000000 portcls+0x10881
b68dbb78 804ef18f 89614030 00000004 889c52d0 RtkHDAud+0x3f608e
b68dbbd8 b70642a2 889c52d0 89963a20 e11dc4a0 nt+0x1818f
b68dbc30 b9e4ef95 8967f030 889c52d0 b68dbc64 sysaudio+0x32a2
b68dbc40 804ef18f 8967f030 889c52d0 806e7410 ks+0x8f95
b68dbc64 805807f7 8967f030 889c52d0 89937ee8 nt+0x1818f
b68dbd00 80579274 00004864 00004288 00000000 nt+0xa97f7
b68dbd34 8054161c 00004864 00004288 00000000 nt+0xa2274
b68dbd64 7c91e4f4 badb0d00 0012f3dc b5699d98 nt+0x6a61c
b68dbd68 badb0d00 0012f3dc b5699d98 b5699dcc 0x7c91e4f4
b68dbd6c 0012f3dc b5699d98 b5699dcc 00000000 0xbadb0d00
b68dbd70 b5699d98 b5699dcc 00000000 00000000 0x12f3dc
b68dbd74 b5699dcc 00000000 00000000 00000000 0xb5699d98
b68dbd78 00000000 00000000 00000000 00000000 0xb5699dcc

STACK_COMMAND: kb

FOLLOWUP_IP:
RtkHDAud+6bb5b
b77dbb5b ?? ???

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: RtkHDAud+6bb5b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: RtkHDAud

IMAGE_NAME: RtkHDAud.sys

BUCKET_ID: WRONG_SYMBOLS

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

Administrador Registrado: Oct 21, 2008 Mensajes: 10438

Parece que el error es provocado como bien dices por los drivers de Realtek. Haz lo siguiente:

1) antes de nada, crea un punto de restauración del sistema.

2) Hecho ésto, ve a la página web del fabricante de tu placa base y descarga los drivers más recientes de tu tarjeta de sonido para tu modelo concreto de placa base.

3) Una vez los tengas, desinstala por completo usando Driver Cleaner o Driver Sweeper los drivers actuales de tu tarjeta de sonido.

4) Instala los drivers más recienes que te has descargado.

Saludos.

Invitado

Ok pero, yo no se mucho de los driver de realtek el driver q tiene creo q es R2.91 si mal no recuerdo te dejo los datos de mi pc para ver si me puedes ayudar.

------------------
System Information
------------------
Time of this report: 3/17/2010, 21:42:21
Machine name: User
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp.080413-2111)
Language: Spanish (Regional Setting: Spanish)
System Manufacturer: OEM
System Model: OEM
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz (2 CPUs)
Memory: 2046MB RAM
Page File: 714MB used, 3224MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 32bit Unicode

Tarjeta madre Foxconn modelo: G31MV/G31MV-K
Chipset intel P35/G33/G31

Te sirve eso?

Administrador Registrado: Oct 21, 2008 Mensajes: 10438

Tú sigue los pasos detallados que te he especificado. Si te atascas en alguno de ellos, coméntanos.

Saludos.

Invitado

Lo que quiero q me expliques es como descargar el driver apropiado para la pc yo en realidad no se de los driver de realtek, si quiero actualizar al mas nuevo como hago?

Publicado: Viernes 19 Marzo 2010, 0:47

Descarga el controlador de audio para tu sistema operativo desde aquí (onboard audio) el primero es para windows 7 y el segundo para XP

Salu2

Gohuca