I have a Netframe 620 PC with Windows XP Professional and an external USB MO Drive. I am able to load and access MO disks, but whenever I try to eject an MO disk, it causes my computer to reboot.

I have the output from a mini dump. Actually, I have about 25 mini dumps and they all say basically the same thing. It looks like disk.sys is causing the problem, though I'm sure it's possible that something else is causing disk.sys to crash the system.

Here is the minidump. I would greatly appreciate if anyone could let me know what they think. I'd like to know if you agree or disagree that disk.sys is causing this, and if anyone else knows of a problem with disk.sys or even if there is any way to get an updated version.

Thank you.

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\All Users\Desktop\Penn Hosp\Mini102506-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\localsymbols*http://msd1.microsoft.com/download/s...wnload/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Wed Oct 25 14:58:44.136 2006 (GMT-5)
System Uptime: 1 days 8:25:57.815
Loading Kernel Symbols
.................................................. .................................................. ..............................................
Loading User Symbols
Loading unloaded module list
...
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 35, {89b17bf8, 0, 0, 0}

*** WARNING: Unable to verify timestamp for disk.sys
*** ERROR: Module load completed but symbols could not be loaded for disk.sys
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS
*** WARNING: Unable to verify timestamp for MacOpen.sys
*** ERROR: Module load completed but symbols could not be loaded for MacOpen.sys
Probably caused by : disk.sys ( disk+45a5 )

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

1: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

NO_MORE_IRP_STACK_LOCATIONS (35)
A higher level driver has attempted to call a lower level driver through
the IoCallDriver() interface, but there are no more stack locations in the
packet, hence, the lower level driver would not be able to access its
parameters, as there are no parameters for it. This is a disasterous
situation, since the higher level driver "thinks" it has filled in the
parameters for the lower level driver (something it MUST do before it calls
it), but since there is no stack location for the latter driver, the former
has written off of the end of the packet. This means that some other memory
has probably been trashed at this point.
Arguments:
Arg1: 89b17bf8, Address of the IRP
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x35

PROCESS_NAME: rsntmain.exe

LAST_CONTROL_TRANSFER: from 80520983 to 80537832

STACK_TEXT:
b5f6eb8c 80520983 00000035 89b17bf8 00000000 nt!KeBugCheckEx+0x1b
b5f6eba4 f76ab5a5 89b4d450 89b17bf8 89b4d508 nt!IopfCallDriver+0x17
WARNING: Stack unwind information not available. Following frames may be wrong.
b5f6ebc0 f76b83a2 89b54020 89b17bf8 89b17c8c disk+0x45a5
b5f6ebdc 804e19ee 89b4d450 89b17bf8 89b17bf8 CLASSPNP+0x13a2
b5f6eca0 804e19ee 8948b670 89b17bf8 89930550 nt!IopfCallDriver+0x31
b5f6ecb8 804e19ee 8930ce08 89b17bf8 80703410 nt!IopfCallDriver+0x31
b5f6ecc8 8057184c 894c8770 89b17bf8 00000000 nt!IopfCallDriver+0x31
b5f6ec5c f795e958 89ae4b68 89b17bf8 88f91870 nt!IopSynchronousServiceTail+0x60
b5f6eca0 804e19ee 8948b670 89b17bf8 89930550 MacOpen+0x5958
b5f6ecb8 804e19ee 8930ce08 89b17bf8 80703410 nt!IopfCallDriver+0x31
b5f6ecc8 8057184c 894c8770 89b17bf8 00000000 nt!IopfCallDriver+0x31
b5f6ecb8 804e19ee 8930ce08 89b17bf8 80703410 nt!IopSynchronousServiceTail+0x60
b5f6ecdc 80591b31 8930ce08 89b17bf8 894c8770 nt!IopfCallDriver+0x31
b5f6ecdc 80591b31 8930ce08 89b17bf8 894c8770 nt!NtFlushBuffersFile+0x1b9
b5f6ed54 804ddf0f 00000ddc 0012df04 0012df0c nt!NtFlushBuffersFile+0x1b9
b5f6ed54 7c90eb94 00000ddc 0012df04 0012df0c nt!KiFastCallEntry+0xfc
0012df0c 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
disk+45a5
f76ab5a5 ?? ???

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: disk

IMAGE_NAME: disk.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b59

SYMBOL_NAME: disk+45a5

FAILURE_BUCKET_ID: 0x35_disk+45a5

BUCKET_ID: 0x35_disk+45a5

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

1: kd> lmvm disk
start end module name
f76a7000 f76afe00 disk T (no symbols)
Loaded symbol image file: disk.sys
Image path: disk.sys
Image name: disk.sys
Timestamp: Wed Aug 04 01:59:53 2004 (41107B59)
CheckSum: 0000CE3F
ImageSize: 00008E00
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0



<<<Wino>>>

Is this a new problem? Were things working OK previously? Any new hardware or software?


You have three processes being pointed out:

disk.sys

CLASSPNP.SYS

MacOpen.sys


Do you have any other USB devices installed? IPod etc.?


Cache writing might be an issue.


Do you have SP2 and all the latest updates?


Also what is the exact model of the external USB MO Drive?