BSOD Playing any games for a while and working on programs

[koolkat77]

I've been running driver verifier all morning and managed to get one.

Hmm. Driver verifier did find something: lvuvc64.sys, Logitech USB Video Class Driver (WebCam)

[FONT="Verdana"]*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, f80, fffffa80100adb30, fffff88005e66ca3}

*** WARNING: Unable to verify timestamp for lvuvc64.sys
*** ERROR: Module load completed but symbols could not be loaded for lvuvc64.sys
Probably caused by : lvuvc64.sys ( lvuvc64+1eca3 )

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

5: 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: 0000000000000f80, Handle value being referenced.
Arg3: fffffa80100adb30, Address of the current process.
Arg4: fffff88005e66ca3, 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 fffff800035633dc to fffff800030dcfc0

STACK_TEXT:  
fffff880`08fc8b68 fffff800`035633dc : 00000000`000000c4 00000000`000000f6 00000000`00000f80 fffffa80`100adb30 : nt!KeBugCheckEx
fffff880`08fc8b70 fffff800`03578ae4 : 00000000`00000f80 fffffa80`100adb30 00000000`00000004 fffff880`08fc8bf8 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`08fc8bb0 fffff800`03330000 : fffff880`08fc0001 fffff880`08fc8e00 fffff880`08fc8f00 fffff880`08fc9188 : nt!VfCheckUserHandle+0x1b4
fffff880`08fc8c90 fffff800`033a9ba5 : 00000000`00000000 00000000`00000001 fffffa80`0cacef30 00000000`00010200 : nt! ?? ::NNGAKEGL::`string'+0x212de
fffff880`08fc8d60 fffff800`030dc253 : fffffa80`0e6f3a50 fffff880`08fc9118 fffff8a0`00000002 00000000`00000000 : nt!NtQueryValueKey+0x115
fffff880`08fc8ef0 fffff800`030d8810 : fffff800`03567c86 fffff880`05e66ca3 fffff880`08fc9188 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`08fc90f8 fffff800`03567c86 : fffff880`05e66ca3 fffff880`08fc9188 00000000`00000000 fffff800`03196e03 : nt!KiServiceLinkage
fffff880`08fc9100 fffff880`05e66ca3 : 00000000`00000000 fffff880`08fc91f0 fffff880`08fc91f8 fffff880`06165f70 : nt!VfZwQueryValueKey+0x76
fffff880`08fc9150 00000000`00000000 : fffff880`08fc91f0 fffff880`08fc91f8 fffff880`06165f70 00000000`00000000 : lvuvc64+0x1eca3


STACK_COMMAND:  kb

FOLLOWUP_IP: 
lvuvc64+1eca3
fffff880`05e66ca3 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  lvuvc64+1eca3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: lvuvc64

IMAGE_NAME:  lvuvc64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  46450350

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_lvuvc64+1eca3

BUCKET_ID:  X64_0xc4_f6_VRF_lvuvc64+1eca3

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

5: kd> lmvm lvuvc64
start             end                 module name
fffff880`05e48000 fffff880`061b8500   lvuvc64  T (no symbols)           
    Loaded symbol image file: lvuvc64.sys
    Image path: \SystemRoot\system32\DRIVERS\lvuvc64.sys
    Image name:[COLOR="red"] lvuvc64.sys[/COLOR]
    Timestamp:        [COLOR="Red"]Sat May 12 05:59:12 2007[/COLOR] (46450350)
    CheckSum:         0037D627
    ImageSize:        00370500
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4[/FONT]

Look for possible driver updates: Source

 

[DeusImp3riuM]

It appears I'm getting more and more bluescreen is had two today when playing games.

 

[koolkat77]

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
• Guide to using Memtest86+ - Geeks to Go Forums

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.