So, I was trying out my HDMI cable with my tv monitor. It works really good, I can play any game on it and watch movies etc. Then for some reason I went in to Live Central to use the integrated webcam, the HDMI is still connected. Live Central runns like it should but when I hit the Settings tab I get the BSOD and after like four seconds it rebooted my laptop.
Was this only caused because I still had my HDMI connected? Since I have been using the webcam before without any problems.
Thanks
-
Does it do this everytime? Could just be a random BSOD, happens once in a great while.
-
-
I got a BSOD when trying to exit Live Central. Doesn't happen every time.
I have a dump of the bugcheck and have been meaning to debug it.
Maybe I'll do that today and see what is causing it. -
ok, so when mine had the blue screen, I did not have any HDMI plugged in. I don't think yours crashed due to the cable for any reason.
it seems that the webcam drivers are buggy.
I debugged my crash dump, and found that the webcam software was definately the cause.
The type of bugcheck indicates a 'bit-flip' occurred.
this usually happens when an event object is de-referenced more than it is referenced. The handle count of the object may be 1 while a pointer count is zero when it should not be.
it is definately something in the driver for the webcam, because an application fault would not blue screen the machine. So the webcam software must have interacted with the driver during exit on mine, and the bit flip caused the bugcheck.
I tried to make it happen again, but it didn't.
Code:[size='1']REFERENCE_BY_POINTER (18) Arguments: Arg1: fffffa80078a1080, Object type of the object whose reference count is being lowered Arg2: fffffa8007afa7b0, Object whose reference count is being lowered Arg3: 0000000000000001, Reserved Arg4: 0000000000000001, Reserved The reference count of an object is illegal for the current state of the object. Each time a driver uses a pointer to an object the driver calls a kernel routine to increment the reference count of the object. When the driver is done with the pointer the driver calls another kernel routine to decrement the reference count. Drivers must match calls to the increment and decrement routines. This bugcheck can occur because an object's reference count goes to zero while there are still open handles to the object, in which case the fourth parameter indicates the number of opened handles. It may also occur when the objects reference count drops below zero whether or not there are open handles to the object, and in that case the fourth parameter contains the actual value of the pointer references count. Debugging Details: ------------------ Debugger CompCtrlDb Connection::Open failed 80004005 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x18 PROCESS_NAME: WebcamInt.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002c6df85 to fffff80002cd6740 STACK_TEXT: fffff880`09a72428 fffff800`02c6df85 : 00000000`00000018 fffffa80`078a1080 fffffa80`07afa7b0 00000000`00000001 : nt!KeBugCheckEx fffff880`09a72430 fffff800`02fd2329 : fffff880`09a72ca0 fffff880`09a72730 00000000`00000002 fffff800`00000006 : nt! ?? ::FNODOBFM::`string'+0x463ba fffff880`09a72490 fffff800`02ff8e41 : fffffa80`084baa01 fffffa80`084bafb0 fffffa80`00000001 fffffa80`0addf400 : nt!ObpWaitForMultipleObjects+0x2d3 fffff880`09a72960 fffff800`02cd5993 : 00000000`74422450 00000000`0227f170 00000000`0227fd20 fffff880`09a72c20 : nt!NtWaitForMultipleObjects32+0xec fffff880`09a72bb0 00000000`74422dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0227f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74422dd9 [/SIZE]
if it happens again, I'll call dell and complain, and provide the debug info and see if it will help get things fixed.Last edited by a moderator: May 8, 2015
What the... BSOD?!
Discussion in 'Alienware M11x' started by FreddeN, Mar 2, 2011.