Witam,
pierwszy raz tutaj, ale sprobuję: windows debugger podał problem w hardware (częste ostatnio zwisy - czasem BSOD, czasem samoczynny reset)
czy zapis pomoże jakoś zawęzić krąg poszukiwań?:
system ma już ze dwa lata intensywnej pracy, będę na dniach instalował nowy, ale jeśli są problemy ze sprzętem to nowy system zapewne niewiele pomoże...
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\WINDOWS\Minidump\Mini021609-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 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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTSMachine Name:Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720Debug session time: Fri Feb 13 22:13:59.250 2009 (GMT+1)System Uptime: 0 days 0:07:20.960********************************************************************** 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 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..........................Unable to load image sptd.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for sptd.sys*** ERROR: Module load completed but symbols could not be loaded for sptd.sys******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 100000D1, {ba814800, 2, 0, ba6c177d}***** Kernel symbols are WRONG. Please fix symbols to do analysis.*** WARNING: Unable to verify timestamp for rdbss.sys*** ERROR: Module load completed but symbols could not be loaded for rdbss.sys*** WARNING: Unable to verify timestamp for tcpip.sys*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys*** WARNING: Unable to verify timestamp for psched.sys*** ERROR: Module load completed but symbols could not be loaded for psched.sys*** WARNING: Unable to verify timestamp for NDIS.sys*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys*** WARNING: Unable to verify timestamp for Epfwndis.sys*** ERROR: Module load completed but symbols could not be loaded for Epfwndis.sys*** WARNING: Unable to verify timestamp for bridge.sys*** ERROR: Module load completed but symbols could not be loaded for bridge.sys*** WARNING: Unable to verify timestamp for NVENETFD.sys*** ERROR: Module load completed but symbols could not be loaded for NVENETFD.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 : hardware ( sptd+1777d )Followup: MachineOwner---------1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high. This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: ba814800, memory referencedArg2: 00000002, IRQLArg3: 00000000, value 0 = read operation, 1 = write operationArg4: ba6c177d, address which referenced memoryDebugging 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 ****** ************************************************************************************************************************************************** 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+ **********************************************************************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.FAULTING_MODULE: 804d7000 ntDEBUG_FLR_IMAGE_TIMESTAMP: 0READ_ADDRESS: unable to get nt!MmSpecialPoolStartunable to get nt!MmSpecialPoolEndunable to get nt!MmPoolCodeStartunable to get nt!MmPoolCodeEnd ba814800CURRENT_IRQL: 2FAULTING_IP:sptd+1777dba6c177d 0000 add byte ptr [eax],alCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTBUGCHECK_STR: 0xD1MISALIGNED_IP:sptd+1777dba6c177d 0000 add byte ptr [eax],alLAST_CONTROL_TRANSFER: from ba6c195a to ba6c177dSTACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong.bacdba6c ba6c195a 0000eb02 ba814800 87d0b7e0 sptd+0x1777dbacdbaac ba6c1f08 0000eb02 8800636b bacdbaf8 sptd+0x1795abacdbaf0 ba6c309b 00000000 bacdbb20 87e04008 sptd+0x17f08bacdbb3c b6c22363 88006360 87d0b7e0 0000103b sptd+0x1909bbacdbb5c 804f16c0 00000000 87e04008 886b8510 rdbss+0x2363bacdbb8c b6dad942 88522220 8813ae68 8813ae6c nt+0x1a6c0bacdbba4 b6db1455 87e04008 00000000 0000103b tcpip+0x4942bacdbbe0 b6db1508 00000000 00000002 00000040 tcpip+0x8455bacdbc04 b6da9a0e 00000002 00000002 bacdbc30 tcpip+0x8508bacdbc38 b6da9955 00000002 b6da9901 b6da93d6 tcpip+0xa0ebacdbca4 b96f645c c000009a bacdbcc8 00000001 tcpip+0x955bacdbcd0 ba4c4ef2 0125c788 8807f710 8807f75c psched+0x845cbacdbd38 baa3af49 c000009a bacdbd68 00000001 NDIS+0x22ef2bacdbd60 baa3bc35 8807f710 00000000 8a255008 Epfwndis+0x2f49bacdbd80 baa3bc6a 8a266738 8a255008 00000002 Epfwndis+0x3c35bacdbd94 baa3a0e3 8a266738 8a255008 8a266738 Epfwndis+0x3c6abacdbdb4 baa3a3bf 8a26685c 8a255008 00000000 Epfwndis+0x20e3bacdbde8 ba4c4ef2 8807f058 89f96a80 89f020ca Epfwndis+0x23bfbacdbe50 b9718d4b 00000000 bacdbe7c 00000001 NDIS+0x22ef2bacdbe74 b9719282 89f96a80 8a237130 89f96a80 bridge+0x2d4bbacdbe94 b971977d 89f96a80 8a21b730 8a237130 bridge+0x3282bacdbed8 ba4c4b9f 8a21b730 0100050d 00000000 bridge+0x377dbacdbf2c ba95e14a 00f148c8 89fb15d0 00000001 NDIS+0x22b9f00000000 00000000 00000000 00000000 00000000 NVENETFD+0x614aSTACK_COMMAND: kbFOLLOWUP_IP:sptd+1777dba6c177d 0000 add byte ptr [eax],alSYMBOL_STACK_INDEX: 0SYMBOL_NAME: sptd+1777dFOLLOWUP_NAME: MachineOwnerIMAGE_NAME: hardwareMODULE_NAME: hardwareFAILURE_BUCKET_ID: IP_MISALIGNED_sptd.sysBUCKET_ID: IP_MISALIGNED_sptd.sysFollowup: MachineOwner---------
pozdrawiam
