Solved BSOD / Random Freezes - possible webcam driver issues?

[NickFrancis]

Hi
I've been having issues for ages with my computer completely freezing. Normally it just freezes, no BSOD just a frozen screen sometimes with looping sound.

I tried nearly everything - repair install, new install, new hdd, new psu and yet it still keeps crashing.

Recently I finally got a BSOD which was related to my webcame (Logitech Quickcam Pro 4000). Is it possible that this driver has been causing all these issues, even though the freezes happen completely randomly and when the webcam is not being used?

My wife is on the verge of throwing me & the computer out the window, so any advice would be gratefully received!

Thanks

Nick

 

[writhziden]

Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to provide us with the full reports and information about your system. This will help us determine whether the webcam is the root of your freezes.

 

[NickFrancis]

Hi
Please find attached my BSOD files as requested. Sorry it's taken a while, had a week of sick family to look after so been distracted.
I think it is the webcam but I don't understand why.

• According to Windows the webcam is Win 7 64bit compatible (Logitech QuickCam Pro 4000)
• It has worked with Skype in the past, but in the last two weeks to try and get to the bottom of the crashes I replaced my hdd and did a clean install. It's now crashing all the time. No other hardware has changed.

Answers to the questions as per the BSOD instructions:
Is Windows 7 . . .
- x86 (32-bit) or x64 ? x65
- the original installed OS on the system? Yes - clean install on new HDD
- an OEM or full retail version? Full retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer
- What is the age of system (hardware)? 2-3 years old max
- What is the age of OS installation (have you re-installed the OS?) 2 weeks old

Thanks

Nick

 

[writhziden]

drivermax.exe	c:\program files (x86)\innovative solutions\drivermax\drivermax.exe	2888	8	200	1380	26/02/2012 20:49	6.16.0.259	8.17 MB (8,565,672 bytes)	20/02/2012 14:21
drivermax.exe	c:\program files (x86)\innovative solutions\drivermax\drivermax.exe	2900	8	200	1380	26/02/2012 20:49	6.16.0.259	8.17 MB (8,565,672 bytes)	20/02/2012 14:21

Are you using DriverMax to update all drivers? If so, this could very well be the reason for your crashes. These programs find "up to date" drivers often for different devices than what you actually have on your system. We see this scenario causing crashes a lot on these forums. It is much safer to find drivers through the manufacturers. If you have trouble finding a driver, you can start a new thread in Drivers - Windows 7 Forums and the experts in that forum will help you.

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


Loading Dump File [D:\Kingston\BSODDmpFiles\NickFrancis\Windows_NT6_BSOD_jcgriff2\022612-33711-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e45670
Debug session time: Sun Feb 26 13:48:20.081 2012 (UTC - 7:00)
System Uptime: 0 days 0:20:47.844
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, fc4, fffffa8007965650, fffff8800831fa55}

Unable to load image \SystemRoot\system32\DRIVERS\CamDrL64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for CamDrL64.sys
*** ERROR: Module load completed but symbols could not be loaded for CamDrL64.sys
Probably caused by : CamDrL64.sys ( CamDrL64+11a55 )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 0000000000000fc4, Handle value being referenced.
Arg3: fffffa8007965650, Address of the current process.
Arg4: fffff8800831fa55, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  Skype.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800031063dc to fffff80002c7cc40

STACK_TEXT:  
fffff880`088c2768 fffff800`031063dc : 00000000`000000c4 00000000`000000f6 00000000`00000fc4 fffffa80`07965650 : nt!KeBugCheckEx
fffff880`088c2770 fffff800`0311bae4 : 00000000`00000fc4 fffffa80`07965650 00000000`00000004 fffff800`02c9a7ef : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`088c27b0 fffff800`02ed4210 : 00000000`00000008 fffff880`088c2a00 fffff880`088c2b00 fffff880`088c2d50 : nt!VfCheckUserHandle+0x1b4
fffff880`088c2890 fffff800`02f4e075 : fffff6fb`7dbf1400 fffff880`00000001 fffffa80`0463af30 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x212ce
fffff880`088c2960 fffff800`02c7bed3 : fffffa80`058e7060 fffff880`088c2d18 00000000`00000001 fffff8a0`0aef6c00 : nt!NtQueryValueKey+0x115
fffff880`088c2af0 fffff800`02c78470 : fffff800`02f36b0a 00000000`00000fc4 00000000`00000000 fffff880`088c2ed0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`088c2cf8 fffff800`02f36b0a : 00000000`00000fc4 00000000`00000000 fffff880`088c2ed0 00000000`00000000 : nt!KiServiceLinkage
fffff880`088c2d00 fffff880`0831fa55 : 00000000`00000000 00000000`00000000 fffffa80`06b1e490 00000000`00000000 : nt!RtlQueryRegistryValues+0x136
fffff880`088c2dd0 00000000`00000000 : 00000000`00000000 fffffa80`06b1e490 00000000`00000000 00000000`00000000 : CamDrL64+0x11a55


STACK_COMMAND:  kb

FOLLOWUP_IP: 
CamDrL64+11a55
fffff880`0831fa55 4883c438        add     rsp,38h

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  CamDrL64+11a55

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CamDrL64

IMAGE_NAME:  CamDrL64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45c4d1b7

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_CamDrL64+11a55

BUCKET_ID:  X64_0xc4_f6_VRF_CamDrL64+11a55

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

Nearly all of your crashes were caused by Driver Verifier. Driver Verifier is to be run to determine what is causing crashes. You have only one crash prior to running it (or it just wasn't Verified and was still due to Verifier being on). I would recommend disabling Verifier and see if the system is now stable since that one crash could be related to lack of updates. To disable Verifier, Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> type the following command and then type enter

Verifier /reset​

-> Restart your computer.

 

[NickFrancis]

Thanks for the reply.

Reset verifier and the webcam worked with now with no crashing - thank you!

I did use DriverMax - yes - should I roll back the drivers on the devices that were updated? They don't seem to be causing any problems that I've identified yet.

Thanks for all the help

Nick

 

[writhziden]

If you are not having problems, leave the system as is. Just be very judicious what you update with DriverMax and check your device manager afterward. I used it myself for a while to see what it does because I was helping someone on here who was using it. Found that I ended up with devices in device manager that were not working properly after "updating" (they ended up with an exclamation mark next to them).

To reach device manager:

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left

Alternatively:

1. Login as an adminstrative user.
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)