|
|
|
|
|
Interpretacion de analisis de Windbg |
|
| WINDOWS 7 HOME BASIC ; Intel(R) Core(TM)2 Quad CPU Q6600 @ 2,40 GHz 2,40 GHz ; RAM 2,00 GB ; Sistema operativo de 32 bits tras varios pantallazos azules y después de leer varias soluciones , opte por ir al minidump , analizarlo con el programa debugging tools for windows y me dio un resultado que no se interpretar , os mando el resultado del analisis y haber si alguien me manda una solución para evitar los pantallazos. 2: kd> !analyze -v ******************************************************************************* * * * bugcheck analysis * * * ******************************************************************************* irql_not_less_or_equal (a) an attempt was made to access a pageable (or completely invalid) address at an interrupt request level (irql) that is too high. this is usually caused by drivers using improper addresses. if a kernel debugger is available get the stack backtrace. arguments: arg1: 00000064, memory referenced arg2: 00000002, irql arg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) arg4: 83081f9e, address which referenced memory debugging details: ------------------ ***** 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 *** *** *** ************************************************************************* 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: win32k faulting_module: 83019000 nt debug_flr_image_timestamp: 4a5bc2a2 write_address: unable to get nt!mmspecialpoolstart unable to get nt!mmspecialpoolend unable to get nt!mmpoolcodestart unable to get nt!mmpoolcodeend 00000064 current_irql: 0 faulting_ip: nt+68f9e 83081f9e 894804 mov dword ptr [eax+4],ecx customer_crash_count: 1 default_bucket_id: vista_driver_fault bugcheck_str: 0xa last_control_transfer: from 83081f9e to 8305f7eb stack_text: warning: stack unwind information not available. following frames may be wrong. 952d0ac4 83081f9e badb0d00 00000000 83209fbf nt+0x467eb 952d0b48 83080753 8af00120 858c7de0 952d0c34 nt+0x68f9e 952d0b74 8298aa8e 858c7de0 00000002 00000000 nt+0x67753 952d0b90 8293f3d8 fe54c358 00000040 17806a20 win32k+0xbaa8e 952d0c00 829947e8 fea20ca0 00000000 00000000 win32k+0x6f3d8 952d0c50 829420d8 fea20ca0 00000000 00000000 win32k+0xc47e8 952d0cbc 8293df4e fea20ca0 00000000 00000000 win32k+0x720d8 952d0cd8 82981864 fea20ca0 00000000 00000000 win32k+0x6df4e 952d0d10 8305c42a 0002026a 00000000 00000000 win32k+0xb1864 952d0d34 779064f4 badb0d00 03e6f5c0 00000000 nt+0x4342a 952d0d38 badb0d00 03e6f5c0 00000000 00000000 0x779064f4 952d0d3c 03e6f5c0 00000000 00000000 00000000 0xbadb0d00 952d0d40 00000000 00000000 00000000 00000000 0x3e6f5c0 stack_command: kb followup_ip: win32k+baa8e 8298aa8e ? ? symbol_stack_index: 3 symbol_name: win32k+baa8e followup_name: machineowner image_name: win32k.sys bucket_id: wrong_symbols followup: machineowner |
Temas relacionados: |
| ¿ Que análisis es este ? | |
| No funciona con Nexus 7 (2012), android 4.4.2 No funciona con Galaxy S4, android 4.3 En ninguno de ambos existe \"pantalla inalámbrica, que dice en las instrucciones. En el Nexus 7 existe una opción \"Pantalla de Cast\" pero le falta una casilla para habilitar \"pantalla inalámbrica\". En el S4, con la función Screen Mirroring intenta conectar, pero parece que está capado. ¿qué análisis de esta maravilla de las maravillas se ha hecho ? Woxter Miracast 110. ... | |
| Analisis de datos | |
| Windows vista Necesito saber que posibles herramienta de analisis de datos en la actualidad se esta utilizando y que ayuden a la toma de decisiones en las empresas. ... | |
| Análisis de HijackThis | |
| Gracias a este foro, espero encontrar solución ya que mi pc está muy lenta, el cpu sube al 100% incluso cuando tengo solamente una página abierta (sea de iexplorer, mozilla o chrome), se pone en espera por varios minutos, pongo a continuación el hijackthis para su análisis (creo que así se llama, según veo) ya ando más de un mes buscando ayuda, con sus esperiencia en el foro espero solucionar el caso. gracias por el tiempo en darme una respuesta. logfile of random\'s system information tool 1.09 (written by random/random) run by lm at 2013... | |
| Herramientas de analisis web | |
| Windows 7 (6.1) 32b, Chrome 18.0 Queremos lanzar un curso online gratuito y nos gustaría saber qué herramienta de análisis web utilizar y qué posibilidades tiene. ¿Habéis lanzado algun curso online y qué herramienta de análisis habéis utilizado? Un saludo ... | |
| Clempad error de analisis | |
| Al intentar descargar algo en la tablet clempad sale error de analisis al analizar el paquete y no puedo descargar nada Clempad. ... | |
| Foros: Análisis |
| Subir |
Foros: |
|
-