Hello.
I have just installed in my PC a Watchport/V camera and I have experienced some BSODs during the PC reset process. I am using windows xp pro and the “vicamusb.sys” version I installed is 6.7.0.029. Here I copy you the BSOD’s minidump:
Probably caused by : vicamusb.sys ( vicamusb+2621 )
Followup: MachineOwner
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: f7996621, The address that the exception occurred at
Arg3: f4257b60, 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:
vicamusb+2621
f7996621 ?? ???
TRAP_FRAME: f4257b60 – (.trap 0xfffffffff4257b60)
Unable to read trap frame at f4257b60
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 00000000 to f7996621
STACK_TEXT:
f4257bd0 00000000 82d5d290 0377f358 0001e400 vicamusb+0x2621
STACK_COMMAND: kb
FOLLOWUP_IP:
vicamusb+2621
f7996621 ?? ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: vicamusb+2621
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vicamusb
IMAGE_NAME: vicamusb.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 38038aa9
FAILURE_BUCKET_ID: 0x8E_vicamusb+2621
BUCKET_ID: 0x8E_vicamusb+2621
Followup: MachineOwner
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: f7996621, The address that the exception occurred at
Arg3: f4257b60, 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:
vicamusb+2621
f7996621 ?? ???
TRAP_FRAME: f4257b60 – (.trap 0xfffffffff4257b60)
Unable to read trap frame at f4257b60
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 00000000 to f7996621
STACK_TEXT:
f4257bd0 00000000 82d5d290 0377f358 0001e400 vicamusb+0x2621
STACK_COMMAND: kb
FOLLOWUP_IP:
vicamusb+2621
f7996621 ?? ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: vicamusb+2621
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vicamusb
IMAGE_NAME: vicamusb.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 38038aa9
FAILURE_BUCKET_ID: 0x8E_vicamusb+2621
BUCKET_ID: 0x8E_vicamusb+2621
Followup: MachineOwner
Loading Dump File [C:\Documents and Settings\AW515733\Desktop\Mini051309-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRVc:\websymbolshttp://msdl.microsoft.com/download/symbols
Executable search path is: c:\i386
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Wed May 13 17:07:44.654 2009 (GMT+0)
System Uptime: 0 days 0:02:08.254
Loading Kernel Symbols
…
Loading User Symbols
Loading unloaded module list
…
*** WARNING: Unable to verify timestamp for vicamusb.sys
*** ERROR: Module load completed but symbols could not be loaded for vicamusb.sys
-
* -
Bugcheck Analysis * -
*
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, f7996621, f4257b60, 0}
Probably caused by : vicamusb.sys ( vicamusb+2621 )
Followup: MachineOwner
I hope it helps.
Many thanks in advance for your help.
Best Regards
Manuel