Blue screen while using Skype

Got a blue screen while using Skype yesterday. I was on a video chat and the monitor froze with a horrible buzzing sound and then the blue screen. I've attached the error and can provide mini-dump.

 

Hi, Vic.

That dump is likely to be huge, zip it and upload it to a publicly accessible folder - Outlook/Skydrive would be good, link it back here.

Yours looks like it might be a 'bad' driver interfering/loading where it shouldn't.

If you carefully read and follow the BSOD Sticky here and attach the needed zipped folder to a reply (don't include that dump again), it'll give us a lot of background info as well.

 

It's really not that big.

 

One known bad driver:
AODDriver2.sys Tue Mar 6 09:55:00 2012 (4F55DEF4) AMD Overdrive; also in EasyTune6 for Gigabyte motherboard Known BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys


Either the above caused a problem for your webcam (drivers in memory) or the webcam driver is bad/corrupted, is my guess, uninstall the above and update your webcam driver: http://www.logitech.com/en-us/support/webcams

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88006792fc6, fffff88005bc6898, fffff88005bc60f0}

Probably caused by : lvrs64.sys ( lvrs64+2fc6 )

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

1: kd> !analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88006792fc6, The address that the exception occurred at
Arg3: fffff88005bc6898, Exception Record Address
Arg4: fffff88005bc60f0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
lvrs64+2fc6
fffff880`06792fc6 45396924        cmp     dword ptr [r9+24h],r13d

EXCEPTION_RECORD:  fffff88005bc6898 -- (.exr 0xfffff88005bc6898)
.exr 0xfffff88005bc6898
ExceptionAddress: fffff88006792fc6 (lvrs64+0x0000000000002fc6)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000001fd5804
Attempt to read from address 0000000001fd5804

CONTEXT:  fffff88005bc60f0 -- (.cxr 0xfffff88005bc60f0)
.cxr 0xfffff88005bc60f0
rax=0000000000000000 rbx=fffffa8006af89c0 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88006792fc6 rsp=fffff88005bc6ad0 rbp=0000000001fd57e0
 r8=0000000000000000  r9=0000000001fd57e0 r10=0000000000000002
r11=0000000001fd57e0 r12=fffffa8006b45850 r13=0000000000000000
r14=0000000001fd57e0 r15=0000000001fd57e0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
lvrs64+0x2fc6:
fffff880`06792fc6 45396924        cmp     dword ptr [r9+24h],r13d ds:002b:00000000`01fd5804=????????
.cxr
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000001fd5804

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b2100
GetUlongFromAddress: unable to read from fffff800030b21c0
 0000000001fd5804 Nonpaged pool

FOLLOWUP_IP: 
lvrs64+2fc6
fffff880`06792fc6 45396924        cmp     dword ptr [r9+24h],r13d

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 0000000000000001 to fffff88006792fc6

STACK_TEXT:  
fffff880`05bc6ad0 00000000`00000001 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`053e0ae0 : lvrs64+0x2fc6
fffff880`05bc6ad8 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffffa80`053e0ae0 00000000`00000000 : 0x1
fffff880`05bc6ae0 00000000`00000000 : 00000000`00000000 fffffa80`053e0ae0 00000000`00000000 00000000`00000000 : 0xfffffa80`00000000


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  lvrs64+2fc6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: lvrs64

IMAGE_NAME:  lvrs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  505cb9b9

STACK_COMMAND:  .cxr 0xfffff88005bc60f0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_lvrs64+2fc6

BUCKET_ID:  X64_0x7E_lvrs64+2fc6

 

Thanks! Where do I find AODDriver2.sys to uninstall it?

 

It's part of AMD Overdrive; also in EasyTune6.

 

OK, thank you for being patient with me.

I do not find AMD Overdrive or EasyTune6. I do have an AMD VISION Engine Control Center folder in the Startup menu. In System Configuration, there is
AMD External Events Utility and AMD FUEL service. And in CCleaner uninstall section, AMD Catalyst Install Manager.

I appreciate your help.

 

At a guess, it's been incorporated into FUEL, uninstall it. I'd block the other two from auto-starting as well, just to keep things 'clean'.

 

OK, uninstalled AMD and updated Logitech webcam.
I will be on Skype this weekend and I will report back here with any results, good or bad.
Thank you so very much satrow for all your time and help.

 

Ok, have fun and keep us updated