|
|
|
|
|
Errores graves en Windows 8 |
|
| Buenos días a todos,
antes de nada agradecer la ayuda desinteresada que mostráis en este foro. os voy a plantear mi problema. antes de tener windows 8 en mi ordenador, tenía instalado windows 7. tras tener bastantes pantallazos azules, me decidí a formatear el ordenador y aproveché para instalar windows 8 pensando que así podía solucionar el problemas. pues bien, ahora no me salen pantallazos azules, pero cada vez que reinicio o enciendo el ordenador me salen pantallas de recuperación del sistema de errores graves. me temo que pueda ser algo de memoria ram o placa base, aunque por lo que veo al final del análisis (probably caused by : nvlddmkm.sys) que me remite a un problema con la gráfica. a ver si me pueden echar una mano: microsoft (r) windows debugger version 6.2.9200.20512 amd64 copyright (c) microsoft corporation. all rights reserved. loading dump file [c:windowsmemory.dmp] kernel bitmap dump file: only kernel address space is 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+ * ********************************************************************* *** error: symbol file could not be found. defaulted to export symbols for ntkrnlmp.exe - windows 8 kernel version 9200 mp (4 procs) free x64 product: winnt, suite: terminalserver singleuserts built by: 9200.16628.amd64fre.win8_gdr.130531-1504 machine name: kernel base = 0xfffff802`25288000 psloadedmodulelist = 0xfffff802`25554a20 debug session time: fri sep 13 13:51:24.993 2013 (utc + 2:00) system uptime: 0 days 0:00:11.664 ********************************************************************* * 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+ * ********************************************************************* *** error: symbol file could not be found. defaulted to export symbols for ntkrnlmp.exe - loading kernel symbols . . . loading user symbols peb is paged out (peb.ldr = 000007f6`c2776018). type ".hh dbgerr001" for details loading unloaded module list . ******************************************************************************* * * * bugcheck analysis * * * ******************************************************************************* use !analyze -v to get detailed debugging information. bugcheck 3b, {c0000005, fffff880049b8095, fffff880078b7b00, 0} *** error: symbol file could not be found. defaulted to export symbols for nvlddmkm.sys - *** error: symbol file could not be found. defaulted to export symbols for dxgkrnl.sys - page 107346 not present in the dump file. type ".hh dbgerr004" for details page 107468 not present in the dump file. type ".hh dbgerr004" for details page 107346 not present in the dump file. type ".hh dbgerr004" for details *** error: module load completed but symbols could not be loaded for win32k.sys ***** 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 : nvlddmkm.sys ( nvlddmkm!nvdumpconfig+2676cd ) followup: machineowner he probado el memtest86 y no ha salido ningún error. he intentado resetear la bios y me ha sido imposible. he hecho tanto la opción del jumper como la de quitar la pila (durante toda la noche), y no ha habido forma. tengo que deciros que cuando me compré el pc por piezas (de sobremesa) leí que la placa asus p5qc tiene comportamientos "extraños" con ciertas memorias ram. adquirí en su momento dos módulos de 2gb mushkin ddr3 a 1333mhz y lo que me suele pasar es que tengo que quitar un módulo para que arranque el pc porque si no, no arranca. para intentar solucionar este problema, asus lanzó una actualización de la bios y la actualicé pensando que dejaría de tener este problema, pero sigue pasando. no sé si tendrá que ver que realicé esta actualización para que no pueda volver a la anterior. así mismo, hay veces que con los dos módulos funciona y otras veces no funciona. eso sí, he tenido que modificar en la bios y poner las memorias a 1066 y 333mhz. no sé si ésta será la raíz de mi problema o no, y como solucionarlo, porque asus ya no volvió a actualizar la bios. no sé si actualizando al bios con alguna otra placa similar de asus será una solución, pero claro, no tengo la menor idea. tampoco sé si otra solución sería comprar otros módulos, pero, ¿y si no vale? ¿qué hago con las memorias? en fin. agradezco cualquier sugerencia y/o ayuda. una cosa más, he encontrado una actualización "casera" de un usuario de un foro que asegura solucionar el problema de las compatibilidades de memoria ram pero no me atrevo a utilizarla Windows 7 (6.1) 32b, Chrome 29.0. |
#1  bruzan (2.062 Posts) - 16/09/2013 13:51:56 | ||
| Hola
prueba con ubuntu de la web de ubuntu descargas la verion 12.04 o 13.04 inicias con el disco de ubuntu ( no instalar ) comenta como funciona Comenta si solucionaste el problema | ||
| Bajar - Subir | ||
| #2 Nitter (2 Posts) - 16/09/2013 14:09:00 | ||
| Hola bruzan, ¿qué se supone que tengo que hacer con ubuntu? Jamás lo he utilizado.
| ||
| Bajar - Subir | ||
| #3 bruzan (2.062 Posts) - 16/09/2013 15:48:54 | ||
| Hola
windows estas instalando actualizacion o de 0 lo descargas, grabas en un disco dvd, cambias el boot a cd/dvd e inicias el disco es un live cd. que inicia ubuntu en el ordenador ( no instalar ) si funciona con normalidad el problema es del s.o. Comenta si solucionaste el problema | ||
| Bajar - Subir |
Temas relacionados: |
| ¿Te falla Windows 10?, cuéntanos que problemas o errores te da el nuevo Windows | |
| ¿Has instalado Windows 10 y te da algún problema o error?, ¿problemas con los controladores o drivers?, ¿problemas de inestabilidad, compatibilidad con programas o servicios?, comentanos que error te da Windows 10 e intentaremos ayudarte. Recuerda, que antes de instalar Windows 10 debes asegurarte de que tu PC tiene que tener Windows 7 Sp1 o Windows 8.1, de lo contrario tu sistema podría volverse inestable. Si necesitas preguntar alguna duda, pulsa en responder y deja tu mensaje o crea un tema nuevo explicando que problema o error te da W... | |
| Incovenientes Graves | |
| Primero que todo el equipo presenta como si tuviera activado un modo de ahorro de enegía y ahora se le va el sonido de un omento a otro y toca riniciar el computador para que coa el sonido de nuevo y siempre que abre uno caso le pieden reinstalar el S.O puede que con esto solucione el error de sonido en teoría pero el de video no Lenovo ThinkPad Twist S230u. ... | |
| Graves rotos ue megaboom | |
| Distorsionan los graves muchisimo. ¿que se puede hacer? Logitech UE Boom. ... | |
| Errores en el dll de windows | |
| Windows 7 cuando quiero poner un reproductor como predeterminado me aparese una ventana que dise que no se encuentra el archivo dll del shell ... | |
| Errores en windows 8 | |
| Ayuda, hace poco he tenido estos problemas con Windows 8, en mi laptop Toshiba,(relativamente nueva) Se dieron en el orden que los pongo y según el programa BlueScereenView son causados por esos controladores CRITICAL_PROCESS_DIED causado por el controlador ntoskrnl.exe INVALID_PROCESS_ATTACH_ATTEMPT causado por el controlador tdx.sys UNEXPECTED_KERNEL_MODE_TRAP causado por el controlador pacer.sys Pongo una imagen con algunos detalles. Gracias de antemano, **************** Los errrores paece que se dan principalmente l ver videos e... | |
| Foros: Errores |
| Subir |
Foros: |
|