How to debug a core file without debug symbols?

Please help (Blue Screen of Death)?

• I am getting these minidumps persistently. Please help me, what likely might be the cause?? I am pasting below the debugging report: Microsoft (R) Windows Debugger Version 6.9.0003.113 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Documents and Settings\Kala Kabra\My Documents\Mini022609-02.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp_sp2_rtm.040803-2158 Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700 Debug session time: Thu Feb 26 11:00:19.406 2009 (GMT+6) System Uptime: 0 days 0:01:09.109 Loading Kernel Symbols ......................................… Loading User Symbols Loading unloaded module list .... **************************************… * * * Bugcheck Analysis * * * **************************************… Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 8050504f, b058fb98, 0} Unable to load image aswSP.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for aswSP.SYS *** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS Probably caused by : aswSP.SYS ( aswSP+66f0 ) Followup: MachineOwner --------- 1: kd> kd> !analyze -v Numeric expression missing from '> !analyze -v' 1: kd> !analyze -v **************************************… * * * Bugcheck Analysis * * * **************************************… KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 8050504f, The address that the exception occurred at Arg3: b058fb98, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: nt!MiLocateAndReserveWsle+51 8050504f 8b0c81 mov ecx,dword ptr [ecx+eax*4] TRAP_FRAME: b058fb98 -- (.trap 0xffffffffb058fb98) ErrCode = 00000000 eax=000003b5 ebx=80560ec0 ecx=0000003c edx=00000001 esi=c0e00000 edi=0fffffff eip=8050504f esp=b058fc0c ebp=b058fc18 iopl=0 nv up ei ng nz ac po cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293 nt!MiLocateAndReserveWsle+0x51: 8050504f 8b0c81 mov ecx,dword ptr [ecx+eax*4] ds:0023:00000f10=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: services.exe LAST_CONTROL_TRANSFER: from 80512c2c to 8050504f STACK_TEXT: b058fc18 80512c2c 0000003c 8a4a9a40 80560bc0 nt!MiLocateAndReserveWsle+0x51 b058fc30 8066b0fc 9387af50 c049c3d0 823ed770 nt!MiAddValidPageToWorkingSet+0x84 b058fc54 8066b98b 9387af50 c049c3d0 00000041 nt!MiMakeSpecialPoolPagable+0x56 b058fc8c 80536036 9387a000 41735370 00000041 nt!MiAllocateSpecialPool+0x2d5 b058fcac 80658103 00000041 000000b0 41735370 nt!ExAllocatePoolWithTagPriority+0x2c b058fcd8 80658730 00000041 00000000 41735370 nt!VeAllocatePoolWithTagPriority+0x13b b058fcfc aaf5a6f0 00000001 000000a6 41735370 nt!VerifierAllocatePoolWithTag+0x46 WARNING: Stack unwind information not available. Following frames may be wrong. b058fd18 aaf5c52f e11bb1e0 919bef60 00000001 aswSP+0x66f0 b058fd34 aaf5c688 00d0f884 e11bb1e0 919bef60 aswSP+0x852f b058fd50 8054060c 00d0f884 00020019 00d0f7bc aswSP+0x8688 b058fd50 7c90eb94 00d0f884 00020019 00d0f7bc n

• Answer:

  There are many types of situations addressed on different sites that list this could be related to a "Spy ware" or that your drivers are affecting your computer (XP OS) one site to check for spy ware of this type of crash and a solution is listed here http://www.techspot.com/vb/all/windows/t-27478-bat...%3C/t-60037-XP-crashes-and-reboots-Errorcode-1000008e.html For a error related to windows XP driver check this site for a solution: http://support.microsoft.com/?kbid=316424 For an incredible detailed list of how to track, find and solve almost every issue related to this kind of bug check here and read the solution: http://www.pcreview.co.uk/forums/thread-439539.php