Hello Lugdunon.
I guess the Cam3820 PC camera device that you are using in not very much compatible with your system, and the
driver is of 2008.
Code:
0: kd> !irp fffffa8006cdbc10
Irp is active with 11 stacks 9 is current (= 0xfffffa8006cdbf20)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
>[ 16, 2] 0 0 fffffa8008a97050 00000000 00000000-00000000
Unable to load image \SystemRoot\System32\Drivers\cam3820.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cam3820.sys
*** ERROR: Module load completed but symbols could not be loaded for cam3820.sys
Unable to load image \SystemRoot\system32\DRIVERS\ks.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ks.sys
*** ERROR: Module load completed but symbols could not be loaded for ks.sys
\Driver\Cam3820
Args: 00016600 00000000 00000006 00000006
[ 16, 2] 0 e1 fffffa800873ee30 00000000 fffff800030d0e50-fffffa800872e5e0 Success Error Cancel pending
\Driver\ksthunk nt!PopSystemIrpCompletion
Args: 00016600 00000000 00000006 00000006
[ 0, 0] 0 0 00000000 00000000 00000000-fffffa800872e5e0
Args: 00000000 00000000 00000000 00000000
0: kd> !devobj fffffa800873ee30
Device object (fffffa800873ee30) is for:
InfoMask field not found for _OBJECT_HEADER at fffffa800873ee00
\Driver\ksthunk DriverObject fffffa800717ca70
Current Irp 00000000 RefCount 0 Type 0000002f Flags 00002050
DevExt fffffa800873ef80 DevObjExt fffffa800873ef88
ExtensionFlags (0x00000800) DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000180) FILE_AUTOGENERATED_DEVICE_NAME, FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) fffffa8008a97050 \Driver\Cam3820
Device queue is not busy.
0: kd> lmvm Cam3820
start end module name
fffff880`09106000 fffff880`0912d100 cam3820 T (no symbols)
Loaded symbol image file: cam3820.sys
Image path: \SystemRoot\System32\Drivers\cam3820.sys
Image name: cam3820.sys
Timestamp: Fri Jan 04 16:54:24 2008 (477E1768)
CheckSum: 0002CC1C
ImageSize: 00027100
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 I guess it is connected via a USB hub? If it is not attached, does it still results a BSOD? Let us know. If not, better you either try to update the driver or change the device.
Also, you dont have service pack 1 installed.
Code:
Versão 6.1.7600 Compilação 7600
Install Service pack 1.
Learn how to install Windows 7 Service Pack 1 (SP1) Service Pack Center - Microsoft Windows Daemon Tools, Alcohol 120% and Power Archiver Pro uses
SCSI Pass Through Direct (
SPTD), which is a well known BSOD causer. Uninstall
Daemon Tools at first. Then download SPTD standalone installer from
Disk-Tools.com, and execute the downloaded file as guided below :
- Double click to open it.
- Click this button only:

- If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
Free up the startup. - Click on the Start button
- Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
- Select the “Startup” tab.
- Deselect all items other than the antivirus.
- Apply > OK
- Accept the restart.
Let us know the results.