|
|
|
|
|
Pantallazo aul al intentar cerrar o reiniciar |
|
| Windows 7 (6.1) 32b, Chrome 23.0 holas, a ver si podeis ayudarme, tengo portatil toshiba, todo va bien menos cuando intento cerrar o reiniciar, me sale el pantallazo azul y no se apaga ni reinicia desde inicio,tengo que apagarlo desde el boton, hos voy a poner esto por si sirve de ayuda, porque no no entiendo nada microsoft (r) windows debugger version 6.11.0001.404 x86 copyright (c) microsoft corporation. all rights reserved. loading dump file [c:\ \ windows\ \ minidump\ \ 111912-25552-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 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 x64 product: winnt, suite: terminalserver singleuserts personal built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333 machine name: kernel base = 0xfffff800`02a63000 psloadedmodulelist = 0xfffff800`02ca7670 debug session time: mon nov 19 11:33:23.535 2012 (gmt+1) system uptime: 0 days 2:50:15.375 ********************************************************************* * 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 . ******************************************************************************* * * * bugcheck analysis * * * ******************************************************************************* use !analyze -v to get detailed debugging information. bugcheck f4, {3, fffffa8004921060, fffffa8004921340, fffff80002de1460} ***** kernel symbols are wrong. please fix symbols to do analysis. unable to get nt!kicurrentetwbufferoffset unable to get nt!kicurrentetwbufferbase ************************************************************************* *** *** *** *** *** 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+ * ********************************************************************* probably caused by : win32.exe followup: machineowner --------- 1: kd> !analyze -v ******************************************************************************* * * * bugcheck analysis * * * ******************************************************************************* critical_object_termination (f4) a process or thread crucial to system operation has unexpectedly exited or been terminated. several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. arguments: arg1: 0000000000000003, process arg2: fffffa8004921060, terminating object arg3: fffffa8004921340, process image file name arg4: fffff80002de1460, explanatory message (ascii) debugging details: ------------------ ***** kernel symbols are wrong. please fix symbols to do analysis. unable to get nt!kicurrentetwbufferoffset unable to get nt!kicurrentetwbufferbase ************************************************************************* *** *** *** *** *** 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+ * ********************************************************************* additional_debug_text: use '!findthebuild' command to search for the target build information. if the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. module_name: win32 faulting_module: 0000000000000000 debug_flr_image_timestamp: 0 process_object: fffffa8004921060 image_name: win32.exe customer_crash_count: 1 default_bucket_id: vista_driver_fault bugcheck_str: 0xf4 current_irql: 0 stack_text: fffff880`02189b08 fffff800`02e69822 : 00000000`000000f4 00000000`00000003 fffffa80`04921060 fffffa80`04921340 : nt+0x7efc0 fffff880`02189b10 00000000`000000f4 : 00000000`00000003 fffffa80`04921060 fffffa80`04921340 fffff800`02de1460 : nt+0x406822 fffff880`02189b18 00000000`00000003 : fffffa80`04921060 fffffa80`04921340 fffff800`02de1460 00000000`00000004 : 0xf4 fffff880`02189b20 fffffa80`04921060 : fffffa80`04921340 fffff800`02de1460 00000000`00000004 fffffa80`04921060 : 0x3 fffff880`02189b28 fffffa80`04921340 : fffff800`02de1460 00000000`00000004 fffffa80`04921060 fffff800`02e15e0b : 0xfffffa80`04921060 fffff880`02189b30 fffff800`02de1460 : 00000000`00000004 fffffa80`04921060 fffff800`02e15e0b ffffffff`ffffffff : 0xfffffa80`04921340 fffff880`02189b38 00000000`00000004 : fffffa80`04921060 fffff800`02e15e0b ffffffff`ffffffff fffffa80`03eceb50 : nt+0x37e460 fffff880`02189b40 fffffa80`04921060 : fffff800`02e15e0b ffffffff`ffffffff fffffa80`03eceb50 fffffa80`04921060 : 0x4 fffff880`02189b48 fffff800`02e15e0b : ffffffff`ffffffff fffffa80`03eceb50 fffffa80`04921060 fffffa80`0387e060 : 0xfffffa80`04921060 fffff880`02189b50 ffffffff`ffffffff : fffffa80`03eceb50 fffffa80`04921060 fffffa80`0387e060 00000000`00000324 : nt+0x3b2e0b fffff880`02189b58 fffffa80`03eceb50 : fffffa80`04921060 fffffa80`0387e060 00000000`00000324 00000000`00000008 : 0xffffffff`ffffffff fffff880`02189b60 fffffa80`04921060 : fffffa80`0387e060 00000000`00000324 00000000`00000008 fffffa80`0387e060 : 0xfffffa80`03eceb50 fffff880`02189b68 fffffa80`0387e060 : 00000000`00000324 00000000`00000008 fffffa80`0387e060 00000000`40010004 : 0xfffffa80`04921060 fffff880`02189b70 00000000`00000324 : 00000000`00000008 fffffa80`0387e060 00000000`40010004 fffffa80`03eceb50 : 0xfffffa80`0387e060 fffff880`02189b78 00000000`00000008 : fffffa80`0387e060 00000000`40010004 fffffa80`03eceb50 fffff800`02d94f04 : 0x324 fffff880`02189b80 fffffa80`0387e060 : 00000000`40010004 fffffa80`03eceb50 fffff800`02d94f04 ffffffff`ffffffff : 0x8 fffff880`02189b88 00000000`40010004 : fffffa80`03eceb50 fffff800`02d94f04 ffffffff`ffffffff 00000000`00000001 : 0xfffffa80`0387e060 fffff880`02189b90 fffffa80`03eceb50 : fffff800`02d94f04 ffffffff`ffffffff 00000000`00000001 fffffa80`04921060 : 0x40010004 fffff880`02189b98 fffff800`02d94f04 : ffffffff`ffffffff 00000000`00000001 fffffa80`04921060 fffff800`00000008 : 0xfffffa80`03eceb50 fffff880`02189ba0 ffffffff`ffffffff : 00000000`00000001 fffffa80`04921060 fffff800`00000008 00000000`746c6644 : nt+0x331f04 fffff880`02189ba8 00000000`00000001 : fffffa80`04921060 fffff800`00000008 00000000`746c6644 fffff880`02189c20 : 0xffffffff`ffffffff fffff880`02189bb0 fffffa80`04921060 : fffff800`00000008 00000000`746c6644 fffff880`02189c20 00000000`00000000 : 0x1 fffff880`02189bb8 fffff800`00000008 : 00000000`746c6644 fffff880`02189c20 00000000`00000000 00000000`00436810 : 0xfffffa80`04921060 fffff880`02189bc0 00000000`746c6644 : fffff880`02189c20 00000000`00000000 00000000`00436810 00000000`00010203 : 0xfffff800`00000008 fffff880`02189bc8 fffff880`02189c20 : 00000000`00000000 00000000`00436810 00000000`00010203 00000000`00000000 : 0x746c6644 fffff880`02189bd0 00000000`00000000 : 00000000`00436810 00000000`00010203 00000000`00000000 00000000`0043ce90 : 0xfffff880`02189c20 stack_command: kb followup_name: machineowner bucket_id: wrong_symbols followup: machineowner --------- |
#1   bacter (20.410 Posts) - 24/11/2012 13:33:59 | ||
| Podría tratarse de un error de instalación, tanto poeque se haya instalado sobre un vista en lugar de instalación limpia, o de un cd con imágen defectuosa.
No indicas ni de que versión de W7 se trata, ni si te ha funcionado alguna vez bien, ni si has instalado desde un cd de W7 original. Es más fácil ayudarte cuando nos proporcionas la información relevante, historial de los pasos que has efectuado previamente al problema etc. Como ya has realizado varias preguntas en este foro, entre ellas una sobre un toshiba (probablemente este mismo), te recordamos que agradecemos cuando recibas respuestas, que nos comuniques que has podido solucionar el problema y como, en el caso que se resolvió. Un saludo. | ||
| Bajar - Subir | ||
#2  maika40 (35 Posts) - 24/11/2012 17:16:34 | ||
| Holas y gracias por contestar, ye windows 7 home premiun, 64, lo instale y active hace meses y va de maravilla, digo va porque el esta funcionando bien, pero en algo meti mis manazas que la lie, va todo bien hasta que le doy reiniciar o apagar desde inicio, que ye cuando me sale el pantallazo azul y ni reinicia ni apaga | ||
| Bajar - Subir | ||
#3  jrfii (2.005 Posts) - 24/11/2012 20:58:54 | ||
| Hola que tal. En tu caso lo mejor es que, copies tu archivos importanes en otros soportes y hagas una instalación limpia del sistema operativo.
Suerte. saludos. | ||
| Bajar - Subir |
Temas relacionados: |
| Intentar reiniciar | |
| Se me apagó sin mas ahora la reinicio y se queda en el logotipo y no me sale el escritorio,solo tiene dos botones el de encendido y esc.quisieran que me audarana saber como darle vida a mi table Linux Ubuntu Linu 64 b, Firefox 32.0. ... | |
| Pantallazo azul al intentar instalar el driver para red wiffi | |
| Cuando intento instalar el driver para el adaptador de red wiffi, en windows 7 profesional me sale un pantallazo azul y se reinicia Acer Aspire One D257. ... | |
| No puedo cerrar reiniciar ni apagar mi notebook | |
| WINDOW ULTIMATE, NOTEBOOK TOSHIBA SATELLITE C645 abri una carpeta de la biblioteca para ver unos videos y ahora no la puedo cerrar, anda todo bien pero me quedo esa carpeta abierte y quiero cerrar,reiniciar o apagar la notebook del modo correcto y no me deja. la apago con el boton de encendido y apagado pero cuando se enciende esta la carpeta que habia abierto antes. no la puedo cerrar!!!! ... | |
| Cuales son las aplicaciones que debo cerrar para reiniciar la cámara curve 9320? | |
| No se ha podido iniciar la cámara. cierre las otras apicaciones antes de reiniciar la cámara BlackBerry Curve 9320. ... | |
| Problemas al intentar ver gol tv | |
| He cambiado de pc y no consigo ver gol tv estoy dado de alta pero cada vez que lo intento me da error loading player me falta algún tipo de archivo. El so es w7 gracias Windows 7 (6.1) 32b, Mozilla 5.0. ... | |
| Subir |
Foros: |
|