Windows 2003 Server Restarting constantly: BugCheck 1000008E

Hey guys am experiencing my IBM server restarting and I am experiencing trouble analyzing the minidump file....here it is below.

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\i386
Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: Server, suite: TerminalServer
Built by: 3790.srv03_sp1_rtm.050324-1447
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af988
Debug session time: Mon Apr 18 11:05:00.832 2005 (GMT+10)
System Uptime: 0 days 0:31:58.513
Loading Kernel Symbols
...........................................................................................................
Loading unloaded module list
........
Loading User Symbols
Unable to load image WDICA.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for WDICA.SYS
*** ERROR: Module load completed but symbols could not be loaded for WDICA.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f508bd75, f58e8660, 0}

Unable to load image vdtw30.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for vdtw30.dll
*** ERROR: Module load completed but symbols could not be loaded for vdtw30.dll
Probably caused by : WDICA.SYS ( WDICA+1dd75 )

Followup: MachineOwner
---------

3: 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: f508bd75, The address that the exception occurred at
Arg3: f58e8660, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


OVERLAPPED_MODULE: rdbss

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

FAULTING_IP:
WDICA+1dd75
f508bd75 8b4604 mov eax,[esi+0x4]

TRAP_FRAME: f58e8660 -- (.trap fffffffff58e8660)
ErrCode = 00000000
eax=f58e877c ebx=8aa97000 ecx=8a37bde8 edx=00000000 esi=00000001 edi=00000000
eip=f508bd75 esp=f58e86d4 ebp=f58e86e4 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
WDICA+0x1dd75:
f508bd75 8b4604 mov eax,[esi+0x4] ds:0023:00000005=????????
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0x8E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from f5088995 to f508bd75

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f58e86e4 f5088995 8aa97000 f58e877c 89d0e3e0 WDICA+0x1dd75
f58e8704 f759c155 8aa97000 f58e877c 89fd8010 WDICA+0x1a995
f58e8720 f759c531 89d0e3e0 00000005 f58e877c termdd!_IcaCallSd+0x35
f58e8740 f759cc93 89fd8008 00000005 f58e877c termdd!_IcaCallStack+0x55
f58e8764 f759d611 89bbfcd8 00000005 f58e877c termdd!IcaCallDriver+0x71
f58e8794 f7599f7d 89bbfcd8 89e82cb8 89e82d28 termdd!IcaDeviceControlVideo+0x47
f58e87b8 f759ab7a 89bbfcd8 89e82cb8 89e82d28 termdd!IcaDeviceControlChannel+0x267
f58e87e8 f759acce 89e82cb8 89e82d28 0000000c termdd!IcaDeviceControl+0x4e
f58e8800 8083f9d0 8a9cfa78 89e82cb8 00000000 termdd!IcaDispatch+0x12a
f58e8814 bf8358e4 00000000 00000000 bfa74e02 nt!IofCallDriver+0x45
f58e8844 bf82b9e9 8a9cfa78 00381048 f58e8890 win32k!GreDeviceIoControl+0x93
f58e8868 bfa69bc0 8a9cfa78 00381048 f58e8890 win32k!EngDeviceIoControl+0x1f
f58e88a0 bfa6a167 bc01a018 bfa74e10 bfa74e10 vdtw30+0x2dbc0
00000000 00000000 00000000 00000000 00000000 vdtw30+0x2e167


FOLLOWUP_IP:
WDICA+1dd75
f508bd75 8b4604 mov eax,[esi+0x4]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: WDICA+1dd75

MODULE_NAME: WDICA

IMAGE_NAME: WDICA.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 41f71601

STACK_COMMAND: .trap fffffffff58e8660 ; kb

FAILURE_BUCKET_ID: 0x8E_WDICA+1dd75

BUCKET_ID: 0x8E_WDICA+1dd75
---------
Followup: MachineOwner

 

I can't help you with the specific problem except to make this recommendation.

There is a poster whose username is JoeHobart. He has posted many responses to BSOD issues. Search this forum for his name. I think in his signature he has some links to things you will need to do. There are suggested steps and tools to use, which will help him...help you. Mini-dumps are not comprehensive enough.

As for the constant restarting...I think there is a check box under system properties \ startup and recovery \ automatically reboot. Unchecking this will stop the reboot on system errors. Basically your system will hang at a BSOD, waiting for someone to come along manually restart the system.

btw...I feel you pain. Ben down this road a feww times.
Regards,

- Don

 

Hi,

i've got an similar the same problem.

For the IBM x345 series is an BIOS update required for SP1 required

Hope it' helps

 

A quick search for vdtw30.dll and WDICA.SYS yielded:
http://www.freedomscientific.com/fs_support/BulletinView.cfm?QC=874

and

http://www.freedomscientific.com/fs_support/BulletinView.cfm?QC=873

As well as other forum articles that hint at patches to citrix. Do any of those links help?

Do you actually have JAWS installed on the server? Maybe try uninstalling it and see what happens?

-Mike

 

this is crashing in a citrix module. You have to call them to figure out whats going on.