ASUS DVD-RW restarts when DVD is inserted randomly

[Messerschmitt]

Greetings.

I am in vacation at my aunt, and her computer restarts randomly when a DVD is inserted. Sometimes it restarts, sometimes it doesn't. A few times it starts a cycle, where it restarts the first time, then restarts again when windows is finished loading (taskbar applications starts up like the network and sound icons).

The DVD is a Asus drw-2014S1. She also says she had this problem with another DVDRW Pioneer.

Windows is XP SP2.

Attached is 2 minidumps from the last restart.

Minidump.rar

Edited April 8, 2009 by Messerschmitt

[cluberti]

Not seeing the attachments...

[Messerschmitt]

Sorry. up now

[cluberti]

// It's a STOP 0x8E, meaning a kernel mode unhandled exception happened in a driver, thus the crash:
0: kd> .bugcheck
Bugcheck code 1000008E
Arguments c0000005 806ff94f b64cdb18 00000000

// The trapframe shows that it's failing during an Acquire of a FastMutex lock:
0: kd> .trap 0xffffffffb64cdb18
ErrCode = 00000002
eax=00000000 ebx=b64cdc50 ecx=00000001 edx=8a75b1e0 esi=8a7d83a0 edi=8a7ac6e0
eip=806ff94f esp=b64cdb8c ebp=b64cdb9c iopl=0		 nv up ei pl nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000			 efl=00010213
hal!ExAcquireFastMutex+0xf:
806ff94f f0ff09		  lock dec dword ptr [ecx]	 ds:0023:00000001=????????

// The thread, showing us talking to a filter driver on the system:
0: kd> !thread
GetPointerFromAddress: unable to read from 80566eb4
THREAD 8a965960  Cid 0734.0168  Teb: 7ffa9000 Win32Thread: 00000000 RUNNING on processor 0
IRP List:
	Unable to read nt!_IRP @ 8a772db8
Not impersonating
GetUlongFromAddress: unable to read from 80566ec4
Owning Process			0	   Image:		 <Unknown>
Attached Process		  8a825490	   Image:		 explorer.exe
ffdf0000: Unable to get shared data
Wait Start TickCount	  2360		 
Context Switch Count	  5			 
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime				  00:00:00.000
KernelTime				00:00:00.000
Win32 Start Address 0x77f7422b
Start Address 0x7c810856
Stack Init b64ce000 Current b64cd7fc Base b64ce000 Limit b64cb000 Call 0
Priority 10 BasePriority 8 PriorityDecrement 2 DecrementCount 16
ChildEBP RetAddr  Args to Child			  
b64cdb88 804f3548 8a7ac6e0 00000000 b64cdc50 hal!ExAcquireFastMutex+0xf (FPO: [0,0,0])
b64cdb9c f744fc06 8a7d83a0 8a75b1e0 00000000 nt!FsRtlLookupPerStreamContextInternal+0x14 (FPO: [Non-Fpo]) (CONV: stdcall)
b64cdc00 f74601a7 8a75b1e0 8a7ac6e0 00000000 fltMgr!FltpGetStreamListCtrl+0x5a (FPO: [Non-Fpo]) (CONV: stdcall)
b64cdc1c f744cac9 8a75b1e0 8a7ac6e0 8a75b1e0 fltMgr!FltpCleanupStreamListCtrlForFileObjectClose+0x17 (FPO: [Non-Fpo]) (CONV: stdcall)
b64cdc38 f744cffb b64cdc50 8a772dc8 8abf4ae8 fltMgr!FltpPassThrough+0x93 (FPO: [Non-Fpo]) (CONV: stdcall)
b64cdc68 804e13d9 8a79e020 8a772db8 8a772db8 fltMgr!FltpDispatch+0xf3 (FPO: [Non-Fpo]) (CONV: stdcall)
b64cdc78 8057c403 8a7ac6c8 00000000 00000000 nt!IopfCallDriver+0x31 (FPO: [0,0,0]) (CONV: fastcall)
b64cdcb0 8056c78f 007ac6e0 00000000 8a7ac6c8 nt!IopDeleteFile+0x132 (FPO: [Non-Fpo]) (CONV: stdcall)
b64cdccc 804e1957 8a7ac6e0 00000000 000003d8 nt!ObpRemoveObjectRoutine+0xdf (FPO: [Non-Fpo]) (CONV: stdcall)
b64cdce4 8056e9f4 8a825490 e264a6f0 8a965960 nt!ObfDereferenceObject+0x4c (FPO: [0,0,0]) (CONV: fastcall)
b64cdcfc 8056e912 e264a6f0 8a7ac6e0 000003d8 nt!ObpCloseHandleTableEntry+0x155 (FPO: [Non-Fpo]) (CONV: stdcall)
b64cdd44 8056e95c 000003d8 00000001 00000000 nt!ObpCloseHandle+0x87 (FPO: [Non-Fpo]) (CONV: stdcall)
b64cdd58 804dd99f 000003d8 011bfaec 7c90eb94 nt!NtClose+0x1d (FPO: [Non-Fpo]) (CONV: stdcall)
b64cdd58 7c90eb94 000003d8 011bfaec 7c90eb94 nt!KiFastCallEntry+0xfc (FPO: [0,0] TrapFrame @ b64cdd64)
WARNING: Frame IP not in any known module. Following frames may be wrong.
011bfaec 00000000 00000000 00000000 00000000 0x7c90eb94

// Looking at the filter list by tracking down it's pool tag:
0: kd> .frame 2
02 b64cdc00 f74601a7 fltMgr!FltpGetStreamListCtrl+0x5a

0: kd> dt FileObject FsContext
Local var @ 0xb64cdc0c Type _FILE_OBJECT*
0x8a7ac6e0 
   +0x00c FsContext : 0x8a7d83a0

// It's a device driver object:
0: kd> !pool 0x8a7d83a0 2
Pool page 8a7d83a0 region is Unknown
*8a7d82b0 size:  4b8 previous size:   28  (Allocated) *Devi (Protected)
		Pooltag Devi : Device objects

// Digging apart the device driver object to find the driver behind it:
0: kd>  dt nt!_device_object 8a7d82b0+20
   +0x000 Type			 : 3
   +0x002 Size			 : 0x468
   +0x004 ReferenceCount   : 1
   +0x008 DriverObject	 : 0x8aaa1788 _DRIVER_OBJECT
   +0x00c NextDevice	   : 0x8a7e8768 _DEVICE_OBJECT
   +0x010 AttachedDevice   : 0x8a79e020 _DEVICE_OBJECT
   +0x014 CurrentIrp	   : (null) 
   +0x018 Timer			: (null) 
   +0x01c Flags			: 0
   +0x020 Characteristics  : 0
   +0x024 Vpb			  : (null) 
   +0x028 DeviceExtension  : 0x8a7d8388 
   +0x02c DeviceType	   : 3
   +0x030 StackSize		: 12 ''
   +0x034 Queue			: __unnamed
   +0x05c AlignmentRequirement : 1
   +0x060 DeviceQueue	  : _KDEVICE_QUEUE
   +0x074 Dpc			  : _KDPC
   +0x094 ActiveThreadCount : 0
   +0x098 SecurityDescriptor : (null) 
   +0x09c DeviceLock	   : _KEVENT
   +0x0ac SectorSize	   : 0x800
   +0x0ae Spare1		   : 1
   +0x0b0 DeviceObjectExtension : 0x8a7d8738 _DEVOBJ_EXTENSION
   +0x0b4 Reserved		 : (null) 

// The DeviceExtension is completely invalid:
0: kd> dt fltmgr!FSRTL_ADVANCED_FCB_HEADER 0x8a7d8388
   +0x000 NodeTypeCode	 : 0
   +0x002 NodeByteSize	 : 0
   +0x004 Flags			: 0 ''
   +0x005 IsFastIoPossible : 0 ''
   +0x006 Flags2		   : 0 ''
   +0x007 Reserved		 : 0 ''
   +0x008 Resource		 : 0x8a7d8390 _ERESOURCE
   +0x00c PagingIoResource : 0x8a7d8390 _ERESOURCE
   +0x010 AllocationSize   : _LARGE_INTEGER 0x0
   +0x018 FileSize		 : _LARGE_INTEGER 0x8a9aac38`03980302
   +0x020 ValidDataLength  : _LARGE_INTEGER 0x8a97e9b0
   +0x028 FastMutex		: 0x8a9aa218 _FAST_MUTEX
   +0x02c FilterContexts   : _LIST_ENTRY [ 0x0 - 0xb832c468 ]

// Looking at the memory for this, it's vobiw.SYS:
0: kd> dds 0x8a7d8388
8a7d8388  00000000
8a7d838c  00000000
8a7d8390  8a7d8390
8a7d8394  8a7d8390
8a7d8398  00000000
8a7d839c  00000000
8a7d83a0  03980302
8a7d83a4  8a9aac38
8a7d83a8  8a97e9b0
8a7d83ac  00000000
8a7d83b0  8a9aa218
8a7d83b4  00000000
8a7d83b8  b832c468Unable to load image vobiw.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vobiw.SYS
*** ERROR: Module load completed but symbols could not be loaded for vobiw.SYS
 vobiw+0x1f468
8a7d83bc  b832c468 vobiw+0x1f468
8a7d83c0  00000000
8a7d83c4  00000000
8a7d83c8  00000001
8a7d83cc  00000000
8a7d83d0  00000000
8a7d83d4  00000000
8a7d83d8  00000000
8a7d83dc  00000000
8a7d83e0  00000001
8a7d83e4  e1c31338
8a7d83e8  8aa16e38
8a7d83ec  8a9ea440
8a7d83f0  0000000a
8a7d83f4  8a7e3e78
8a7d83f8  8a7d83f8
8a7d83fc  8a7d83f8
8a7d8400  01000013
8a7d8404  00000000

It seems that at some recent time, a filter driver installed on this machine was updated with a mini filter driver. Installing mini filter drivers causes filter manager to do additional checks on loaded drivers and their contents, and it appears that the Pinnacle Systems' filter driver (vobiw.SYS) has a bug. This driver is from 2004, so I'm suggesting contacting them for a newer version that has this bug fixed.

[Messerschmitt]

Thanks for the diagnostic.

So how exactly do you update the vobiw.SYS? The computer had Pinnacle 9, 10 and 12 installed on it. I un-installed 12 and 10 but the problem is still there, getting resets.

[cluberti]

I'd uninstall them all, and see if vobiw.sys gets removed from the system. If it doesn't, you'll probably have to ask Pinnacle that (technically it's their driver, so making sure all the versions are completely removed *should* remove their drivers). If uninstallation does remove it, I'd see if installing the latest version gives you a newer version of the driver.

If not, you'll have to talk to Pinnacle about the issue, as it's their driver that's buggy. If they don't know about the issue, however, I don't know that they would have fixed it, so if that's the case it may explain new versions shipping with an older driver.

I wish I had something better for you, but if you're using the product you'll have to harass them to get it fixed if they haven't already.

[Messerschmitt]

I'm asking this because my aunt told me only since the recent format she had this problem. She used pinnacle before before, version 9 and this didn't happened.

Another wired thing is, that she took a DVDR from another computer to check if it's the DVDR unit fault. It had the same problems with reset. Now when that DVDR got returned to the original computer, that computer too now keeps resting.