Hi everyone! I've tried to set up windbg to analyze the kernel minidump on my pc without success. Essentially the pc is connected to a DeviceMaster (Ethernet to Serial) hub. Applications on the pc heavily poll serial devices through the devicemaster. Once the DeviceMaster's power supply is disconnected, the pc crashes shortly thereafter. I wanted to determine whether the problem is with the application software or the devicemaster driver. The pc is running win2k sp3. I've download w2k sp3 symbol files and set up the symbol file path, to no avail. This is the output I get in WinDbg: =================================================================== Microsoft ® Windows Debugger Version 6.2.0013.1 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [D:\CBSHARE\blowers\Mini061303-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: C:\WINNT\Symbols;D:\w2kSp3\Symbols Executable search path is: Unable to load image ntoskrnl.exe, Win32 error 2 Windows 2000 Kernel Version 2195 (Service Pack 3) UP Free x86 compatible Kernel base = 0x80400000 PsLoadedModuleList = 0x8046d9f0 Debug session time: Fri Jun 13 15:52:34 2003 System Uptime: not available Unable to load image ntoskrnl.exe, Win32 error 2 Loading Kernel Symbols ............................................................................................... Loading unloaded module list .................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C2, {40, 0, 80000000, 0} Unable to load image smwdm.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for smwdm.sys *** ERROR: Module load completed but symbols could not be loaded for smwdm.sys *** WARNING: symbols timestamp is wrong 0x3c9d0fba 0x3e9cd7ea for portcls.sys *** WARNING: symbols timestamp is wrong 0x39f16f09 0x3e9cd5c3 for KS.SYS Probably caused by : smwdm.sys ( smwdm+4b5b ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_CALLER (c2) The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc. Arguments: Arg1: 00000040, Attempt to free usermode address to kernel pool Arg2: 00000000, Starting address Arg3: 80000000, Start of system address space Arg4: 00000000, 0 Debugging Details: ------------------ DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xC2 LAST_CONTROL_TRANSFER: from 000000c2 to 8046be9a STACK_TEXT: ed42f41c 000000c2 00000040 00000000 80000000 nt!MiFreePoolPages+0x87 FOLLOWUP_IP: smwdm+4b5b bfdfdb5b ?? ??? FOLLOWUP_NAME: MachineOwner SYMBOL_NAME: smwdm+4b5b MODULE_NAME: smwdm IMAGE_NAME: smwdm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 3d10f1f3 STACK_COMMAND: kb BUCKET_ID: 0xC2_smwdm+4b5b Followup: MachineOwner --------- ============================================================ I will greatly appreciate any help. I've also attached the Minidump file. Mini061303_01.zip
