I am getting the BSOD with SYMDS.SYS as the problem. I have N360 4.0 running on Win XP SP3. It started happening two weeks ago (have been running 360 for a few years). Here is the minidump:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini102710-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Oct 27 12:00:11.578 2010 (GMT-4)
System Uptime: 0 days 18:14:52.293
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image SYMDS.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMDS.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMDS.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, b7e2cf87, 9a1d9810, 0}
*** WARNING: Unable to verify timestamp for Ironx86.SYS
*** ERROR: Module load completed but symbols could not be loaded for Ironx86.SYS
Probably caused by : SYMDS.SYS ( SYMDS+4f87 )
Followup: MachineOwner
---------
0: 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: b7e2cf87, The address that the exception occurred at
Arg3: 9a1d9810, 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:
SYMDS+4f87
b7e2cf87 f77118 div eax,dword ptr [ecx+18h]
TRAP_FRAME: 9a1d9810 -- (.trap 0xffffffff9a1d9810)
ErrCode = 00000000
eax=00000000 ebx=ea007008 ecx=00000000 edx=00000000 esi=ea007008 edi=e4a7ab08
eip=b7e2cf87 esp=9a1d9884 ebp=9a1d9898 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
SYMDS+0x4f87:
b7e2cf87 f77118 div eax,dword ptr [ecx+18h] ds:0023:00000018=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: ccsvchst.exe
LAST_CONTROL_TRANSFER: from b7e2ca5d to b7e2cf87
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9a1d9898 b7e2ca5d e4a7ab08 00000926 00000002 SYMDS+0x4f87
9a1d98b4 b7e2f7cf 00000926 00000002 9a1d98d8 SYMDS+0x4a5d
9a1d98e4 b7e311da e4c52330 00000926 9a1d990c SYMDS+0x77cf
9a1d98fc b7e312b3 00000926 9a1d993c 00000000 SYMDS+0x91da
9a1d991c b7e32d40 00000926 e236dc00 00000000 SYMDS+0x92b3
9a1d9934 b7e32eb0 00000000 00000057 e916df20 SYMDS+0xad40
9a1d9960 b7e333c9 e916df20 9a1d9a00 e99fee30 SYMDS+0xaeb0
9a1d9980 b7e3e2d2 e916df20 9a1d9a00 e3f4e9f0 SYMDS+0xb3c9
9a1d9ab0 b7e3a0b7 e92fa4f0 e3f4e9f0 00000015 SYMDS+0x162d2
9a1d9ac8 b7e3a130 b7e6ac50 b7e6c020 e2048280 SYMDS+0x120b7
9a1d9ae4 b7e70577 e92fa4f0 00000001 9a1d9b60 SYMDS+0x12130
9a1d9b04 a0bbb122 e92fa4f0 00000001 00000000 SYMDS+0x48577
9a1d9bf8 a0bb4bf5 31535753 9a1d9c14 894ae298 Ironx86+0x10122
9a1d9c1c a0bb6e7f 0000015a 8a5e5f38 9a1d9c40 Ironx86+0x9bf5
9a1d9c2c a0bb6f9d 894ae298 8a89bbb0 8a5e5f38 Ironx86+0xbe7f
9a1d9c40 804ef19f 8a622448 894ae298 806e6410 Ironx86+0xbf9d
9a1d9c64 805807f7 8a622448 894ae298 8a89bbb0 nt!MiFlushSectionInternal+0x256
9a1d9d00 80579274 00003ae8 00000000 00000000 nt!NtSetInformationThread+0x125
9a1d9d34 8054164c 00003ae8 00000000 00000000 nt!SepOpenTokenOfThread+0x87
9a1d9d64 7c90e514 badb0d00 03a9f7fc 00000000 nt!RtlIpv4StringToAddressExW+0xcd
9a1d9d78 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
SYMDS+4f87
b7e2cf87 f77118 div eax,dword ptr [ecx+18h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: SYMDS+4f87
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SYMDS
IMAGE_NAME: SYMDS.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a89e90f
FAILURE_BUCKET_ID: 0x8E_SYMDS+4f87
BUCKET_ID: 0x8E_SYMDS+4f87
Followup: MachineOwner
---------
0: kd> lmvm SYMDS
start end module name
b7e28000 b7e7e000 SYMDS T (no symbols)
Loaded symbol image file: SYMDS.SYS
Image path: SYMDS.SYS
Image name: SYMDS.SYS
Timestamp: Mon Aug 17 19:34:39 2009 (4A89E90F)
CheckSum: 00056AC9
ImageSize: 00056000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4