Hello,
Got an unexpected sudden bsod last evening. It's an almost brand new pc with windows only installed for a week. My oh my.
This pc:
Mobo Asus P5G41T (new) with 4 Gb Patriot DDR3
E7400 cpu
video Asus GTS 450
windows 7, x64, pro, trial period
Thanks for any help!!
Easy, your logitech camera driver. Re-install with the newest version available.
Downloads
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\060311-14726-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c65000 PsLoadedModuleList = 0xfffff800`02eaa650
Debug session time: Fri Jun 3 16:39:47.667 2011 (GMT-4)
System Uptime: 0 days 15:16:21.259
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {8, 2, 1, fffff8800542883c}
Unable to load image \SystemRoot\system32\DRIVERS\LV302V64.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for LV302V64.SYS
*** ERROR: Module load completed but symbols could not be loaded for LV302V64.SYS
Probably caused by : LV302V64.SYS ( LV302V64+1683c )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8800542883c, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f14100
0000000000000008
CURRENT_IRQL: 2
FAULTING_IP:
LV302V64+1683c
fffff880`0542883c 49895008 mov qword ptr [r8+8],rdx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88002fe0320 -- (.trap 0xfffff88002fe0320)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8800568b3d0
rdx=fffffa8003bcee40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800542883c rsp=fffff88002fe04b0 rbp=beeffeed01233210
r8=0000000000000000 r9=0000000000000000 r10=fffff8800568aac0
r11=fffffa8003c07e50 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
LV302V64+0x1683c:
fffff880`0542883c 49895008 mov qword ptr [r8+8],rdx ds:519e:00000000`00000008=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ce42a9 to fffff80002ce4d00
STACK_TEXT:
fffff880`02fe01d8 fffff800`02ce42a9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02fe01e0 fffff800`02ce2f20 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`04d25058 : nt!KiBugCheckDispatch+0x69
fffff880`02fe0320 fffff880`0542883c : 00000000`00000002 fffff880`05414345 fffffa80`03c2e790 fffffa80`04d25058 : nt!KiPageFault+0x260
fffff880`02fe04b0 00000000`00000002 : fffff880`05414345 fffffa80`03c2e790 fffffa80`04d25058 fffff880`02fe0500 : LV302V64+0x1683c
fffff880`02fe04b8 fffff880`05414345 : fffffa80`03c2e790 fffffa80`04d25058 fffff880`02fe0500 beeffeed`01233210 : 0x2
fffff880`02fe04c0 fffffa80`03c2e790 : fffffa80`04d25058 fffff880`02fe0500 beeffeed`01233210 00000000`00000000 : LV302V64+0x2345
fffff880`02fe04c8 fffffa80`04d25058 : fffff880`02fe0500 beeffeed`01233210 00000000`00000000 fffff880`054340e7 : 0xfffffa80`03c2e790
fffff880`02fe04d0 fffff880`02fe0500 : beeffeed`01233210 00000000`00000000 fffff880`054340e7 fffffa80`04d25058 : 0xfffffa80`04d25058
fffff880`02fe04d8 beeffeed`01233210 : 00000000`00000000 fffff880`054340e7 fffffa80`04d25058 fffff880`05613320 : 0xfffff880`02fe0500
fffff880`02fe04e0 00000000`00000000 : fffff880`054340e7 fffffa80`04d25058 fffff880`05613320 00000000`00000000 : 0xbeeffeed`01233210
STACK_COMMAND: kb
FOLLOWUP_IP:
LV302V64+1683c
fffff880`0542883c 49895008 mov qword ptr [r8+8],rdx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: LV302V64+1683c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: LV302V64
IMAGE_NAME: LV302V64.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 49fa298e
FAILURE_BUCKET_ID: X64_0xD1_LV302V64+1683c
BUCKET_ID: X64_0xD1_LV302V64+1683c
Followup: MachineOwner
---------
0: kd> lmvm LV302V64
start end module name
fffff880`05412000 fffff880`056b1000 LV302V64 T (no symbols)
Loaded symbol image file: LV302V64.SYS
Image path: \SystemRoot\system32\DRIVERS\LV302V64.SYS
Image name: LV302V64.SYS
Timestamp: Thu Apr 30 18:43:26 2009 (49FA298E)
CheckSum: 002AFCCB
ImageSize: 0029F000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
These drivers need updating
Code:
LVUSBS64.sys 7/26/2008 11:06:36 AM fffff880`05de7000 fffff880`05df1980 0x0000a980 0x488b3d7c
ISODrv64.sys 2/10/2009 5:22:18 AM fffff880`02dba000 fffff880`02dd8000 0x0001e000 0x4991474a
lv302a64.sys 4/30/2009 6:41:07 PM fffff880`05df2000 fffff880`05df4400 0x00002400 0x49fa2903
lvrs64.sys 4/30/2009 6:43:25 PM fffff880`05c1b000 fffff880`05c69580 0x0004e580 0x49fa298d
LV302V64.SYS 4/30/2009 6:43:26 PM LV302V64.SYS+1683c fffff880`05412000 fffff880`056b1000 0x0029f000 0x49fa298e
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
Quote