velman Posted October 29, 2008 Report Share Posted October 29, 2008 Hi,I have the same problem as several others here. Utorrent gives me BSOD. I have version 1.8.1, Vista x64 SP1.Crashdump:======================================================Microsoft ® Windows Debugger Version 6.9.0003.113 AMD64Copyright © Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\Mini102108-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol 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 Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSKernel base = 0xfffff800`0221b000 PsLoadedModuleList = 0xfffff800`023e0db0Debug session time: Tue Oct 21 19:41:31.055 2008 (GMT+1)System Uptime: 0 days 1:43:21.258********************************************************************** 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 A, {9800000007e, 2, 1, fffff8000227b153}***** 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 ****** ************************************************************************************************************************************************** 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 : ntoskrnl.exe ( nt+60153 )Followup: MachineOwner--------- Link to comment Share on other sites More sharing options...
DreadWingKnight Posted October 29, 2008 Report Share Posted October 29, 2008 Kapersky 2009? Link to comment Share on other sites More sharing options...
velman Posted October 29, 2008 Author Report Share Posted October 29, 2008 No, avast (x64) Link to comment Share on other sites More sharing options...
DreadWingKnight Posted October 29, 2008 Report Share Posted October 29, 2008 upload the minidump to a file hosting site and link it Link to comment Share on other sites More sharing options...
velman Posted October 29, 2008 Author Report Share Posted October 29, 2008 http://www.whitephoto.com/minidump/ Link to comment Share on other sites More sharing options...
Ultima Posted October 30, 2008 Report Share Posted October 30, 2008 Did you see the exact error given in the BSOD? Any file specified? Link to comment Share on other sites More sharing options...
GTHK Posted October 30, 2008 Report Share Posted October 30, 2008 The 2nd newest dump specifies a driver, I found this (someone with a similar crash): http://www.dslreports.com/forum/r20428607-Vista-BSOD-vistaLooks like it might be driver issues, update your wireless and everything else you can. Link to comment Share on other sites More sharing options...
velman Posted October 30, 2008 Author Report Share Posted October 30, 2008 "Did you see the exact error given in the BSOD? Any file specified?"No,My computer is (was) set to reboot when I get a BSOD so I have not been able to write it down. But I do remember some thing like "IRQL NOT LESS OR EQUAL".When I'm on wireless i use Intel 4965AGN. I have the latest firmware from Intel.com Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.