| austa |  |
|
2011-07-13 02:02 - Respuestas: 3 - Tema nº: 2806351
Mi maquina es : Mother Asus p5VDC-X Ram: DDR2 533mhz (2 de 512 c/u) Procesador: dualcore intel pentium D 940 , 3200 mhz (socket 775) Video : geforce 7300 Gs Disco: maxtor de 300gb
mi problema es: uso mi maquina tranquilamente capas por dias no pasa nada y de repente se freezea o dsp de prenderla al toque, utilize programas para ver si era la temperatura pero la temperatura esta perfecto, la verdad nose que podia ser hasta q encontre
microsoft debugging tools dsp del blue screen(en realidad queda conjelada la pantalla)
bueno aca hice el reporte, a ver si alguien sabe interpretarlo y que me diga que puede ser, la ram (ya utilize programas de todo tipo hasta de d.o.s para testiarlas y nada) disco duro no creo q sea, prosesador no levanta temperatura y la placa de video tampoco. espero su ayuda, es urgente
installe varios os y lo mismo (2000, xp , win7)
reporte:
microsoft (r) windows debugger version 6.9.0003.113 x86
copyright (c) microsoft corporation. all rights reserved.
loading dump file [c:\windows\minidump\071211-28921-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 tosymbol 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
unable to load image \systemroot\system32\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 7601 (service pack 1) mp (2 procs) free x86 compatible
product: winnt, suite: terminalserver singleuserts
built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
kernel base = 0x8284c000 psloadedmodulelist = 0x8298c230
debug session time: tue jul 12 17:23:53.739 2011 (gmt-3)
system uptime: 0 days 0:55:49.708
************************************************** *******************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
unable to load image \systemroot\system32\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
loading unloaded module list
....
1: kd> !analyze -v
************************************************** *****************************
* *
* bugcheck analysis *
* *
************************************************** *****************************
bad_pool_header (19)
the pool is already corrupt at the time of the current request.
this may or may not be due to the caller.
the internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
arguments:
arg1: 00000003, the pool freelist is corrupt.
arg2: 84230740, the pool entry being checked.
arg3: 84230740, the read back flink freelist value (should be the same as 2).
arg4: 00000000, the read back blink freelist value (should be the same as 2).
debugging details:
*** warning: unable to verify timestamp for luafv.sys
*** error: module load completed but symbols could not be loaded for luafv.sys
*** warning: unable to verify timestamp for mpfilter.sys
*** error: module load completed but symbols could not be loaded for mpfilter.sys
***** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
module_name: luafv
faulting_module: 8284c000 nt
debug_flr_image_timestamp: 4a5bc020
bugcheck_str: 0x19_3
customer_crash_count: 1
default_bucket_id: wrong_symbols
last_control_transfer: from 877cdd0a to 8296466e
stack_text:
warning: stack unwind information not available. following frames may be wrong.
a1865720 877cdd0a 00000001 000000fc 6e664d46 nt+0x11866e
a1865740 877ce771 8616cb00 00000000 8616cb00 fltmgr+0x1dd0a
a1865758 877b8b21 8616cb00 00000000 00000000 fltmgr+0x1e771
a1865788 877b8fa3 862748b4 8556ea20 8439b388 fltmgr+0x8b21
a18657b0 91d42952 00b8d068 00000102 a18657e0 fltmgr+0x8fa3
a18657cc 877cdf27 86379498 84a7d510 84b8d068 luafv+0x9952
a18657fc 877ce75d 8439b388 00000000 8439b388 fltmgr+0x1df27
a1865814 877b8b21 8439b388 00000000 00000000 fltmgr+0x1e75d
a1865844 877b8fa3 862748b4 a18658b8 00000000 fltmgr+0x8b21
a186586c 87ee76a7 00b8d068 00000102 a1865904 fltmgr+0x8fa3
a186593c 87ee8020 84b8d068 a186598c 00000040 mpfilter+0xb6a7
a1865968 877b2324 84b8d068 a186598c 00000040 mpfilter+0xc020
a18659d0 877b5512 00b8d008 84b8d008 1000000c fltmgr+0x2324
a18659e4 877b5b46 84b8d008 84c14c80 a1865a24 fltmgr+0x5512
a18659f4 877b629c 85991ad8 84c14c80 84b8d008 fltmgr+0x5b46
a1865a24 877c98c9 a1865a44 00000000 00000000 fltmgr+0x629c
a1865a70 8287b067 85991ad8 850af008 84a7d56c fltmgr+0x198c9
a1865a88 82a4ee7b 88edc8c4 a1865c30 00000000 nt+0x2f067
a1865b60 82a52056 85037240 852c8a00 84a88d20 nt+0x202e7b
a1865bdc 82a90a7b 00000000 a1865c30 00000040 nt+0x206056
a1865c38 82a4c41c 002dedbc 842c8a00 80d41001 nt+0x244a7b
a1865cb4 82a9749b 002dee18 80100080 002dedbc nt+0x20041c
a1865d00 828818ba 002dee18 80100080 002dedbc nt+0x24b49b
a1865d34 77c370b4 badb0d00 002ded84 00000000 nt+0x358ba
a1865d38 badb0d00 002ded84 00000000 00000000 0x77c370b4
a1865d3c 002ded84 00000000 00000000 00000000 0xbadb0d00
a1865d40 00000000 00000000 00000000 00000000 0x2ded84
stack_command: kb
followup_ip:
luafv+9952
91d42952 ?? ???
symbol_stack_index: 5
symbol_name: luafv+9952
followup_name: machineowner
image_name: luafv.sys
bucket_id: wrong_symbols
followup: machineowner
| |
|
|
| enrique1970 |  |
|
Re: Blue screen! ayuda! (solucionado) - 2011-07-13 02:52 - Respuesta 2
Tiene pinta de ser el disco duro. Haz un testeo con HDD Regenerator de prueba, si te detecta sectores defectuosos te reparará el primero, si hay mas deberás adquirir el programa para reparar el resto, pero ya con la versión demo sabemos si se trata del disco duro, en tal caso también puedes usar MHDD que es gratuito ya hce practicamente lo mismo que el HDD R, solo que es más complicado de usar
Cuéntanos.saludos!
Recuerda notificar si solucionaste tu problema y si tienes conocimientos en algún area puedes ayudar a otros cómo tu has sido ayudado!
No se permiten consultas por mensajes privados
| |
|
|
| austa | |
|
Re: Blue screen! ayuda! (solucionado) - 2011-07-14 20:41 - Respuesta 3
Gracias, anda perdecto (por ahora) cualquier cosa posteo si se vuelve a tildar :) | |
|
|
| enrique1970 | |
|
Re: Blue screen! ayuda! (solucionado) - 2011-07-16 18:03 - Respuesta 4
Nos alegra. Doy el post cómno solucionado, si se vuelve a presentar el problema (esperemos que no) envias un mensaje privado a un moderador para que lo abra .
Saludos!
Recuerda notificar si solucionaste tu problema y si tienes conocimientos en algún area puedes ayudar a otros cómo tu has sido ayudado!
No se permiten consultas por mensajes privados
| |
|
|
|
