mahakohl
21/07/08, 21:33:19
Hola... bueno regresando al foro >.< y saludandolos a todos uds...
Bueno tengo un problema con mi pc, mmm tendra unos cuantos meses que la compre por internet y ya saben paqueteria y blabla... compre la mobo, ram y procesador, todo en un paquete, mas abajo les doy las especificaciones de cada uno.
En fin tengo un problema recurrente que he estado intentando arreglar, la pc es una core duo 2gb procesador y 2gb de ram... y el problema es que a veces varias veces en el dia se traba, aveces 1 o aveces 3 o 4 veces en 1 dia, tambien despues de estar toda una noche sin trabajar en la mañana al encenderla inicia bien todo y despues de encenderla se traba, por lo que hay que reiniciarla de nuevo y funciona bien...
otras veces de igual forma me aparece la pantalla azul con las letras blancas la cual no he podido ver pq tenia activada la opcion de que despues de que apareciera esta pantalla se reiniciara automaticamente (ya la desactive)
mmm con el everest he checado la temperatura del procesador, velocidad de ventilador y todo eso... aparentemente todo esta bien... mmm he analizado el stress de la memoria ram y todo bien... entonces a ver que puede ser..
analize el minidump con el WINDBG que encontre en este otro topico (http://www.forospyware.com/archive/t-83891.html) pero bueno... analize el minidump de uno de ellos q precisamente sucedio ayer, y esto es lo que me aparece.
================================================== =======
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: bf801213, The address that the exception occurred at
Arg3: b721ea48, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
MODULE_NAME: win32k
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48025f2a
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:
win32k+1213
bf801213 8b4624 mov eax,dword ptr [esi+24h]
TRAP_FRAME: b721ea48 -- (.trap ffffffffb721ea48)
ErrCode = 00000000
eax=00706d74 ebx=00000015 ecx=0000612b edx=00008145 esi=6e5c706d edi=00000000
eip=bf801213 esp=b721eabc ebp=b721ead4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
win32k+0x1213:
bf801213 8b4624 mov eax,dword ptr [esi+24h] ds:0023:6e5c7091=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from bf89fcf9 to bf801213
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b721ead4 bf89fcf9 00000022 0073fff4 bf8010e7 win32k+0x1213
b721ed30 bf884705 b9c17490 00000002 b721ed54 win32k+0x9fcf9
b721ed40 bf80110a b9c17490 b721ed64 0073fff4 win32k+0x84705
b721ed54 804dd98f 00000000 00000022 00000000 win32k+0x110a
b721ed64 7c91e4f4 badb0d00 0073ffec ffffffff nt+0x698f
00000000 00000000 00000000 00000000 00000000 0x7c91e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k+1213
bf801213 8b4624 mov eax,dword ptr [esi+24h]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: win32k.sys
SYMBOL_NAME: win32k+1213
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
================================================== =====
por lo que dice el topico según el problema del "win32k.sys" puede ser provocado por el sp2, tengo WIN XP PRO SP3, y "originalmente" el windows viene incluido con el SP2 y nunca me habia dado problemas... con instalaciones previas, el SP3 se lo instale recientemente pero desde antes ya me causaba problemas. Pero en fin en realidad no se a que se refiere todo esto del debug, asi que si hay algun interprete por ahi muchas gracias.
Asi que bueno se me agotan las ideas de que checarle, espero que no sea algun problema fisico de hardware!!! >.<!!! la maquina funciona bien pero pues solo esta ese pequeño gran detallito molesto...
Alguna sugerencia?...
ESPECIFICACIONES DE LA MAQUINA:
MOBO: Elitegrup GF7100PVT-M3 (http://www.ecsusa.com/ECSWebSite/Products/ProductsDetail.aspx?detailid=853&CategoryID=1&DetailName=Specification&MenuID=44&LanID=7)
RAM: Kingston 1gb 2x. Bus 800.
Procesador Intel CORE DUO 2.0 Ghz
----------
Disco duro 80gb mmm no recuerdo la marca si seagate o maxtor. que por cierto no esta conectado en su ranura SATA, sino en la ATA, no he podido comprar un buen disco duro para la maquina ... asi que bueno solo funciona con una lectora de dvd o un quemador de cds.
Tambien tengo un mmm multilector interno de tarjetas SD, Produo y blablabla
Fuente de poder 600w, 20+4 pines.
En fin cualquier idea es bienvenida. Muchas gracias.
Bueno tengo un problema con mi pc, mmm tendra unos cuantos meses que la compre por internet y ya saben paqueteria y blabla... compre la mobo, ram y procesador, todo en un paquete, mas abajo les doy las especificaciones de cada uno.
En fin tengo un problema recurrente que he estado intentando arreglar, la pc es una core duo 2gb procesador y 2gb de ram... y el problema es que a veces varias veces en el dia se traba, aveces 1 o aveces 3 o 4 veces en 1 dia, tambien despues de estar toda una noche sin trabajar en la mañana al encenderla inicia bien todo y despues de encenderla se traba, por lo que hay que reiniciarla de nuevo y funciona bien...
otras veces de igual forma me aparece la pantalla azul con las letras blancas la cual no he podido ver pq tenia activada la opcion de que despues de que apareciera esta pantalla se reiniciara automaticamente (ya la desactive)
mmm con el everest he checado la temperatura del procesador, velocidad de ventilador y todo eso... aparentemente todo esta bien... mmm he analizado el stress de la memoria ram y todo bien... entonces a ver que puede ser..
analize el minidump con el WINDBG que encontre en este otro topico (http://www.forospyware.com/archive/t-83891.html) pero bueno... analize el minidump de uno de ellos q precisamente sucedio ayer, y esto es lo que me aparece.
================================================== =======
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: bf801213, The address that the exception occurred at
Arg3: b721ea48, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
MODULE_NAME: win32k
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48025f2a
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:
win32k+1213
bf801213 8b4624 mov eax,dword ptr [esi+24h]
TRAP_FRAME: b721ea48 -- (.trap ffffffffb721ea48)
ErrCode = 00000000
eax=00706d74 ebx=00000015 ecx=0000612b edx=00008145 esi=6e5c706d edi=00000000
eip=bf801213 esp=b721eabc ebp=b721ead4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
win32k+0x1213:
bf801213 8b4624 mov eax,dword ptr [esi+24h] ds:0023:6e5c7091=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from bf89fcf9 to bf801213
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b721ead4 bf89fcf9 00000022 0073fff4 bf8010e7 win32k+0x1213
b721ed30 bf884705 b9c17490 00000002 b721ed54 win32k+0x9fcf9
b721ed40 bf80110a b9c17490 b721ed64 0073fff4 win32k+0x84705
b721ed54 804dd98f 00000000 00000022 00000000 win32k+0x110a
b721ed64 7c91e4f4 badb0d00 0073ffec ffffffff nt+0x698f
00000000 00000000 00000000 00000000 00000000 0x7c91e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k+1213
bf801213 8b4624 mov eax,dword ptr [esi+24h]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: win32k.sys
SYMBOL_NAME: win32k+1213
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
================================================== =====
por lo que dice el topico según el problema del "win32k.sys" puede ser provocado por el sp2, tengo WIN XP PRO SP3, y "originalmente" el windows viene incluido con el SP2 y nunca me habia dado problemas... con instalaciones previas, el SP3 se lo instale recientemente pero desde antes ya me causaba problemas. Pero en fin en realidad no se a que se refiere todo esto del debug, asi que si hay algun interprete por ahi muchas gracias.
Asi que bueno se me agotan las ideas de que checarle, espero que no sea algun problema fisico de hardware!!! >.<!!! la maquina funciona bien pero pues solo esta ese pequeño gran detallito molesto...
Alguna sugerencia?...
ESPECIFICACIONES DE LA MAQUINA:
MOBO: Elitegrup GF7100PVT-M3 (http://www.ecsusa.com/ECSWebSite/Products/ProductsDetail.aspx?detailid=853&CategoryID=1&DetailName=Specification&MenuID=44&LanID=7)
RAM: Kingston 1gb 2x. Bus 800.
Procesador Intel CORE DUO 2.0 Ghz
----------
Disco duro 80gb mmm no recuerdo la marca si seagate o maxtor. que por cierto no esta conectado en su ranura SATA, sino en la ATA, no he podido comprar un buen disco duro para la maquina ... asi que bueno solo funciona con una lectora de dvd o un quemador de cds.
Tambien tengo un mmm multilector interno de tarjetas SD, Produo y blablabla
Fuente de poder 600w, 20+4 pines.
En fin cualquier idea es bienvenida. Muchas gracias.