BSOD over and over again

[jemping]

Hi,

Recently I kept getting BSODs whenever I booted up my PC.
When I checked with WhoCrashed, it shows ntoskernel.exe and lvuvc64.sys as the drivers that crash my PC.
I notice that lvuvc64.sys is Logitech driver. Do you think it is possible that the logitech driver is the main cause of me keep getting BSODs?

I attached the minidump for BSODs in the last two days.

Thanks a lot.

 

[usasma]

If it's pointing at Logitech drivers, then that's the first thing that's suspect. It's also possible that the Logitech device is broken - or that there are problems with Windows. But that's less likely than the driver issue.

Uninstall the current Logitech device from Control Panel...Programs...Uninstall a program.
Then download a fresh copy from the Logitech website and install it.
Monitor for further BSOD's.

----------------------------------------------------------------------------------------
Here's the information from the minidumps:

5 memory dumps with 5 different error messages - with blame being placed on 4 different causes.
Most often this is a symptom of a hardware problem (or a compatibility issue).

But, in this case, I'd suspect your Logitech stuff first. Remove the software and remove the Logitech device to see if the errors stop. If not, then start by running these diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

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 manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:

ATITool64.sys Wed Aug 08 12:42:26 [COLOR=Red]2007[/COLOR] - Overclocking utility for ATI/nVidia cards - will only work on Windows 2000/XP/2003 - http://www.carrona.org/dvrref.html#ATITool64.sys
jraid.sys    Mon Nov 03 21:20:09 2008 - JMicron RAID Driver - http://www.carrona.org/dvrref.html#jraid.sys
pcouffin.sys Tue Dec 05 09:39:30 [COLOR=Red]2006[/COLOR] - low level access layer for CD devices (A  part of many different CD/DVD burning   programs) - http://www.carrona.org/dvrref.html#pcouffin.sys

Summary of the BSOD's:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May  4 19:12:03.528 2010 (GMT-4)
System Uptime: 0 days 0:00:32.870
BugCheck 3B, {c0000005, fffff8000389f414, fffff8800bf1ecd0, 0}
Probably caused by : ntkrnlmp.exe ( nt!FsRtlLookupPerStreamContextInternal+7c )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  LVPrcSrv.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May  4 19:10:47.328 2010 (GMT-4)
System Uptime: 0 days 0:00:30.671
BugCheck D4, {fffff8800980fb48, 2, 0, fffff8000389b499}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+d9 )
BUGCHECK_STR:  0xD4
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May  4 19:09:07.820 2010 (GMT-4)
System Uptime: 0 days 0:00:26.162
BugCheck 1E, {ffffffffc0000005, fffff800038ee00b, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiCheckVirtualAddress+cb )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  AODAssist.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May  3 09:43:45.374 2010 (GMT-4)
System Uptime: 0 days 0:01:33.091
BugCheck 1A, {1236, fffffa8007ae8c50, fffffa8007ae8c80, 0}
Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e )
BUGCHECK_STR:  0x1a_1236
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May  3 03:01:16.372 2010 (GMT-4)
System Uptime: 0 days 0:00:22.089
BugCheck A, {fffffa8547bb6230, 2, 0, fffff80003ddf3da}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmSetup+6b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System