lyseth Posted March 18, 2014 Report Share Posted March 18, 2014 Hola chicos , necesito ayuda con el resultado que me dio Debugging tools. Hace unos días mi pc (windows 7) empezó a mostrarme el famoso pantallazo azul, mi pc tiene antivirus el cual ocupo siempre (no soy la única que ocupa el pc,pero solo yo trato de mantenerlo bien >< ) Empece a buscar soluciones y llegue a dar con este programa , el cual me arrojo lo siguiente al analizar un archivo mas reciente de la carpeta minidump: Microsoft ® Windows Debugger Version 6.11.0001.404 X86Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\031814-23540-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 <symbol_path> 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.exeWindows 7 Kernel Version 7600 MP (2 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 7600.17273.amd64fre.win7_gdr.130318-1532Machine Name:Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`03248e70Debug session time: Tue Mar 18 13:13:47.345 2014 (GMT-4)System Uptime: 0 days 0:54:09.969********************************************************************** 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 <symbol_path> 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.exeLoading Kernel Symbols.....................................................................................................................................................Loading User SymbolsLoading unloaded module list.......******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck D1, {1da70150, 2, 0, fffff88005b311ea} ***** 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 ****** ****************************************************************************Unable to load image \??\C:\Program Files (x86)\ShopperPro\JSDriver\1.0.0.30\jsdrv.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for jsdrv.sys*** ERROR: Module load completed but symbols could not be loaded for jsdrv.sys**************************************************************************** ****** ****** 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 <symbol_path> 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 <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Probably caused by : jsdrv.sys ( jsdrv+51ea ) Followup: MachineOwner--------- Yo no me manejo en estos temas, espero puedan ayudarme. Saludos :) Link to comment Share on other sites More sharing options...
ExtreemD4t4 Posted March 18, 2014 Report Share Posted March 18, 2014 dice que el archivo que genera el error es el jsdrv.sys, detectado como adware xD proviene del programa ShopperPro o tambien puede estar alojado en la carpeta drivers de system32 xD te conviene aplicar avira + malwarebits antimalware Link to comment Share on other sites More sharing options...
Varit Posted March 19, 2014 Report Share Posted March 19, 2014 En modo seguro man, en modo seguro no falla Link to comment Share on other sites More sharing options...
lyseth Posted March 20, 2014 Author Report Share Posted March 20, 2014 Gracias por la ayuda chicos, claramente era Shopper pro.Lo elimine y nada de BSOD hasta ahora.... espero siga igual mi pc. Se agradece ;) Link to comment Share on other sites More sharing options...
Varit Posted March 20, 2014 Report Share Posted March 20, 2014 Okaps man, cerramos entonces, cualquier duda o consulta vuelves Link to comment Share on other sites More sharing options...
Recommended Posts