|
|
|
|
|
Pantallazo azul Probably caused by : ntoskrnl.exe ( nt+71f00 ) |
|
| Windows 7 (6.1) 32b, Firefox 13.0.1 hola, recientemente he comprado un pc intel core i5 3575k , disco duros wd caviar black 500 gb, grafica saphire radeon hd 7870 gh edition placa base asus maximus, ram g.skill ripjaws 8 gb a 2133. a veces me aparece una blue screen sin previo aviso me ha pasado 3 veces, en el dump me aparece sto a ver si alguiew npuede ayudarme porfavor.instale windows 7 profesional pirata y sin codigo porque lo perdi. microsoft (r) windows debugger version 6.2.8400.4218 amd64 copyright (c) microsoft corporation. all rights reserved. loading dump file [c:\ \ windows\ \ minidump\ \ 071412-22198-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 7600 mp (4 procs) free x64 product: winnt, suite: terminalserver singleuserts built by: 7600.16385.amd64fre.win7_rtm.090713-1255 machine name: kernel base = 0xfffff800`03053000 psloadedmodulelist = 0xfffff800`03290e50 debug session time: sat jul 14 13:33:30.185 2012 (utc + 2:00) system uptime: 0 days 0:32:01.434 ********************************************************************* * 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 . *** warning: unable to verify timestamp for ntfs.sys *** error: module load completed but symbols could not be loaded for ntfs.sys ******************************************************************************* * * * bugcheck analysis * * * ******************************************************************************* use !analyze -v to get detailed debugging information. bugcheck 24, {c08a2, 0, 0, 0} ***** kernel symbols are wrong. please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. unqualified symbol *** *** resolution is turned off by default. please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** for some commands 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. unqualified symbol *** *** resolution is turned off by default. please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** for some commands 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. unqualified symbol *** *** resolution is turned off by default. please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** for some commands 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. unqualified symbol *** *** resolution is turned off by default. please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** for some commands 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. unqualified symbol *** *** resolution is turned off by default. please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** for some commands 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. unqualified symbol *** *** resolution is turned off by default. please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** for some commands 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. unqualified symbol *** *** resolution is turned off by default. please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** for some commands 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. unqualified symbol *** *** resolution is turned off by default. please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** for some commands 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 *** *** *** ************************************************************************* probably caused by : ntoskrnl.exe ( nt+71f00 ) followup: machineowner --------- |
|
#1   Xesvs (16.070 Posts) - 14/07/2012 16:10:07 | ||
| Hola, pues seguramente, la causa es porque sea un SO pirata y es algo muy normal.
No damos ningún soporte a software ilegal. Por un lado porque esta Web está totalmente en contra de la piratería y por otro por que en un software ilegal es totalmente imposible predecir su comportamiento. Puedes encontrar muchas soluciones tanto en la sección Comunidad, como en la de Tutoriales | ||
| Bajar - Subir |
Temas relacionados: |
| Reparar / Reemplazar archivo ntoskrnl.exe (Pantallazo Azul) | |
| Windows 7 Ultimate, 64bits, Intel Core 2 Quad Q9400 2.66ghz, 8GB Ram Buenas, tengo un problema con mi pc y es que ultimamente me da pantallazos azules y reinicia a cada rato, he investigado y he descartado que sea cosa del Hardware (seguro al 95%), al final gracias al BlueScreenView, supe que el problema era el archivo NTOSKRNL.EXE, mi pregunta es ¿que puedo hacer? ¿Se puede reemplazar sin más? ¿Reparar? ¿O a último remedio, si formateo el PC se corrige ese error? Muchas gracias de antemano. ... | |
| Windows 7 pantallazo azul aparece una pantalla en azul con una especie de | |
| Windows 7 (6.1) 32b, Firefox 12.0 advertencia en ingles y se bloquea le apago y rengo que encender y apagar varias veces hasta que consigo que se inicie ... | |
| Pantallazo Azul en Win 7 | |
| Windows 7 Ultimate, Core 2 Quad, 8 gb Ram, 2.66ghz Buenas, hace una semanas tenía unos problemas de pantallazos azules, y puesto que no logre arreglarlo por mi cuenta lo lleve a un técnico el cual me dijo tras una semana, que mis fallos venian de la RAM, la cual quitó dejándome con 4gb, pero los pantallazos continúan, y siempre dicen; PAGE_FAULT_IN_NONPAGED_AREA He pensado, que tal vez sea porque cambie el S.O. de mi pc, (de Vista a 7)? Es posible? También me he fijado en que me da pantallazo a veces cuando le doy a Reiniciar Equipo, o cu... | |
| El pantallazo azul | |
| WINDOWS XP me aparece muchos errores como estos: 0x0000007e,0x80f07030,0xfaf72050,0xfaf71d4c y no se que acer osea que la formateo y me aparece eso ... | |
| Pantallazo Azul | |
| Hola a todos, tengo un notebook olidata L41, con el win7 ultimate, hace un par de meses le cambie placa por que se me echo a perder y encontre una barata en mercadolibre, prendio un par de veces y como a los 2 dias lo prendo y me salio que habia ocurrido un error, entonces eleji la primera opción que era reparar,pero antes de empezar se reinicio y con la otra opción pasaba lo mismo,he probado de todo, pense que podia ser el disco, entonces lo puse en mi pc de escritorio y hay entraba bien,lo formatee con win xp y al colocarlo en el note da u... | |
| Subir |
Foros: |
|
- 