BSODs (Probably because of driver)

Lagoudisio · 26 Sep 2010

Hello everyone. Since i'm posting here and as the title says, i have BSOD problems.

The BSODs started while playing a game. No hardware changes. From then, in every game i played, after some time i got BSOD(not immediately, let's say after 1-2 hours or so). Also sometimes after the crash, i got more BSODs before login in to windows. From the error codes(which where different most of the times), i found that it may be a faulty driver.

I used the Driver Verifier(read in a thread here what to do) and when i rebooted my system i got BSOD before logging in to windows that said about a driver that is verified causing trouble and needs debugging or delete and use a working version. I used safe mode to disable the verifier so i can log in to windows.

Here is the information about the problem:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1032

Additional information about the problem:
BCCode: c9
BCP1: 0000000000000006
BCP2: 0000000000000103
BCP3: FFFFF98008E80990
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\092610-24171-01.dmp
C:\Users\MaD BunNy\AppData\Local\Temp\WER-37609-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I attached the dump file from the last bsod(that happened because of verifier).
So can you tell me if it is a faulty driver and how can i find him and delete him?
Thank you so much.

zigzag3143 · 26 Sep 2010

Lagoudisio said:

Hello everyone. Since i'm posting here and as the title says, i have BSOD problems.

The BSODs started while playing a game. No hardware changes. From then, in every game i played, after some time i got BSOD(not immediately, let's say after 1-2 hours or so). Also sometimes after the crash, i got more BSODs before login in to windows. From the error codes(which where different most of the times), i found that it may be a faulty driver.

I used the Driver Verifier(read in a thread here what to do) and when i rebooted my system i got BSOD before logging in to windows that said about a driver that is verified causing trouble and needs debugging or delete and use a working version. I used safe mode to disable the verifier so i can log in to windows.

Here is the information about the problem:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1032

Additional information about the problem:
BCCode: c9
BCP1: 0000000000000006
BCP2: 0000000000000103
BCP3: FFFFF98008E80990
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\092610-24171-01.dmp
C:\Users\MaD BunNy\AppData\Local\Temp\WER-37609-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I attached the dump file from the last bsod(that happened because of verifier).
So can you tell me if it is a faulty driver and how can i find him and delete him?
Thank you so much.

This crash was caused by your logitech webcam driver lv302a64.sys. I would download the latest driver from Logitech and re-install it.

I would also run a system, file check to verify and repair you system file check

SFC /SCANNOW Command - System File Checker

Also dont forget to turn driver verifier off

Ken J

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\092610-24171-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03a1c000 PsLoadedModuleList = 0xfffff800`03c59e50
Debug session time: Sun Sep 26 16:26:56.062 2010 (GMT-4)
System Uptime: 0 days 0:00:22.093
Loading Kernel Symbols
...............................................................
...............................................................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {6, 103, fffff98008e80990, 0}

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

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000006, IRP passed to IoCompleteRequest contains invalid status
Arg2: 0000000000000103, the status
Arg3: fffff98008e80990, the IRP
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc9_6

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  6

IRP_ADDRESS:  fffff98008e80990

DEVICE_OBJECT: fffffa8006bc7bd0

DRIVER_OBJECT: fffffa8006bbfe70

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003f2c0c2 to fffff80003a8c740

STACK_TEXT:  
fffff880`033c3f18 fffff800`03f2c0c2 : 00000000`000000c9 00000000`00000006 00000000`00000103 fffff980`08e80990 : nt!KeBugCheckEx
fffff880`033c3f20 fffff880`068f35e1 : fffff880`033c4020 fffff980`00000000 00000000`00000103 00000000`00000000 : nt!IovCompleteRequest+0xc2
fffff880`033c3ff0 fffff880`033c4020 : fffff980`00000000 00000000`00000103 00000000`00000000 00000000`00000000 : lv302a64+0x15e1
fffff880`033c3ff8 fffff980`00000000 : 00000000`00000103 00000000`00000000 00000000`00000000 fffff800`03f1f2a7 : 0xfffff880`033c4020
fffff880`033c4000 00000000`00000103 : 00000000`00000000 00000000`00000000 fffff800`03f1f2a7 00000001`06060000 : 0xfffff980`00000000
fffff880`033c4008 00000000`00000000 : 00000000`00000000 fffff800`03f1f2a7 00000001`06060000 fffff880`033c4028 : 0x103


STACK_COMMAND:  kb

FOLLOWUP_IP: 
lv302a64+15e1
fffff880`068f35e1 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  lv302a64+15e1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: lv302a64

IMAGE_NAME:  lv302a64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49fa2903

FAILURE_BUCKET_ID:  X64_0xc9_6_VRF_lv302a64+15e1

BUCKET_ID:  X64_0xc9_6_VRF_lv302a64+15e1

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

cybercore · 26 Sep 2010

Update the logitech camera:

\SystemRoot\system32\DRIVERS\lv302a64.sys
Image name: lv302a64.sys
Timestamp: Fri May 01 01:41:07 2009

Lagoudisio · 26 Sep 2010

Thank you for your replies! What should i do now? Delete that file? Can i uninstall it instead?

Also can you explain me what the cam driver has to do with the bsods i get while playing games? I can't see a connection.

Thank you again!

cybercore · 26 Sep 2010

You should uninstall the Logitech cam and its driver first, reboot, and then download and install the latest 7 compatible version from Logitech support.

Lagoudisio · 26 Sep 2010

Here is what happened:

I uninstalled the driver and rebooted. Then windows tried to install the cam again. Then i went to drivers folder to see if the file will appear again. When the file appeared i got a BSOD. The thing now is that the file still exists and there is no option to uninstall the driver in the Programs and Features. I unplugged and replugged the cam and it tried to install it through the web. Just before the installation finished it said that this product is not compatible with my system. I uninstalled it through the Device Manager, but the driver file still exists. What should i do?

Lagoudisio · 26 Sep 2010

I managed to uninstall the cam driver and i run the system file check. Now i'll play a game and see if i get a bsod(i hope not). If i get one i will post here.
Thank you again for your time and your help!

Lagoudisio · 26 Sep 2010

I got BSOD again.

Here is the info:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1032

Additional information about the problem:
BCCode: 109
BCP1: A3A039D89A026A03
BCP2: B3B7465EEC803959
BCP3: FFFFF80003C174F0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\092710-19781-01.dmp
C:\Users\MaD BunNy\AppData\Local\Temp\WER-31546-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Dump attached.

CarlTR6 · 26 Sep 2010

Error code 109, CRITICAL_STRUCTURE_CORRUPTION - usual causes are Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular).

Code:

Kernel base = 0xfffff800`03a60000 PsLoadedModuleList = 0xfffff800`03c9de50
Debug session time: Sun Sep 26 20:36:12.939 2010 (GMT-4)
System Uptime: 0 days 1:28:00.001
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89a026a03, b3b7465eec803959, fffff80003c174f0, 0}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See Patching Policy for x64-Based Systems: Information for Driver Developers
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89a026a03, Reserved
Arg2: b3b7465eec803959, Reserved
Arg3: fffff80003c174f0, Failure type dependent information
Arg4: 0000000000000000, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003ad0740

STACK_TEXT:  
fffff880`033cb5d8 00000000`00000000 : 00000000`00000109 a3a039d8`9a026a03 b3b7465e`ec803959 fffff800`03c174f0 : nt!KeBugCheckEx


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x109_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_0x109_ANALYSIS_INCONCLUSIVE

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

First, please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads. Be sure you select Uninstall; do not select Reinstall. SPTD is almost guaranteed to cause a BSOD with Win 7.

Next, I find two out of date drivers on your system; one is critically out of date. Out of date drivers can and do cause conflicts, memory corruption, and BSODs. Update the following drivers. Start with the 2007 driver.

nvmfdx64.sys Sat Nov 17 18:47:57 2007 - nVidia Ethernet Networking Driver (nForce chipset driver) Drivers - Download NVIDIA Drivers

nvstor.sys Wed May 20 02:45:37 2009 - nVidia Storage Drivers Drivers - Download NVIDIA Drivers

After you uninstall your CD virtualization program and update the above drivers, reboot and let's see how your system runs.

Lagoudisio · 26 Sep 2010

CarlTR6 said:

First, please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads. Be sure you select Uninstall; do not select Reinstall. SPTD is almost guaranteed to cause a BSOD with Win 7.

Next, I find two out of date drivers on your system; one is critically out of date. Out of date drivers can and do cause conflicts, memory corruption, and BSODs. Update the following drivers. Start with the 2007 driver.

nvmfdx64.sys Sat Nov 17 18:47:57 2007 - nVidia Ethernet Networking Driver (nForce chipset driver) Drivers - Download NVIDIA Drivers

nvstor.sys Wed May 20 02:45:37 2009 - nVidia Storage Drivers Drivers - Download NVIDIA Drivers

After you uninstall your CD virtualization program and update the above drivers, reboot and let's see how your system runs.

I uninstalled the virtual image software and the SPTD. (Can you suggest me another virtual image software to use?)

About the drivers, i don't know if they are updated. For the first one, i downloaded this driver: NVIDIA DRIVERS 15.51 WHQL
For the second one i couldn't find a driver. Actually i don't know how to find it. Also there is a nvstor64.sys driver. Can you tell me how to check if they are updated?

Thank you so much. I will play a game tomorrow and see if i get a BSOD. So, i will post here tomorrow.

EDIT:
I searched the drivers in Device Manager and i found that the NVIDIA nForce 10/100/1000 Mbps Ethernet uses the nvmf6264.sys and not the nvmfdx64.sys. Also the Serial ATA Controller uses the nvstor64.sys and not the nvstor.sys. Is this a bad thing? Which software uses the drivers you said?