Multiple different BSODs over a span of roughly a year and a half.

Xileize · 08 Aug 2014

Hello all,

I've been receiving intermittent BSODs for a long time now and I'm running out of ideas on what to try to get it fixed. I've reinstalled windows, I've replaced RAM, I've replaced my GPU and tried using other forums to get to the bottom of the issue to no avail. If you want to see previous recent progress on what I have tried, you can find it here:

Keep BSODing, want to get to the bottom of it. - bit-tech.net Forums

I have attached a copy of the zip from the DM Log Collector.

Any help would be greatly appreciated!

Xileize · 09 Aug 2014

For further information, they don't seem to happen when anything specific is going on. I've had them when browsing, when gaming, when on skype etc. I don't think I've received one yet while my computer is idle, it has always been during use. My temperatures are around 58c when my CPU is at full load and 70c when my GPU is at full load. I have run Driver Verifier and it was BSODing when trying to uninstall the Xonar DG drivers, so I turned it off and removed them but I am still getting BSODs.

I'm not really sure what else to try but if there's any other information you need, I am more than happy to provide it.

Arc · 09 Aug 2014

Hi Xileize.

Update the driver to HD Pro Webcam C920. Support + Downloads: HD Pro Webcam C920 - Logitech

Let us know the result.

BTW, did you have a sound card installed at any time, like ASUS Xoner? Let us know. Because this answer will be highly important.
_______________________________

Code:

*** WARNING: Unable to verify timestamp for lvrs64.sys
*** ERROR: Module load completed but symbols could not be loaded for lvrs64.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88007b2ef86, fffff88006b6d898, fffff88006b6d0f0}

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

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff88007b2ef86, The address that the exception occurred at
Arg3: fffff88006b6d898, Exception Record Address
Arg4: fffff88006b6d0f0, 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+2f86
fffff880`07b2ef86 45396924        cmp     dword ptr [r9+24h],r13d

EXCEPTION_RECORD:  fffff88006b6d898 -- (.exr 0xfffff88006b6d898)
ExceptionAddress: fffff88007b2ef86 (lvrs64+0x0000000000002f86)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000001c4bff4
Attempt to read from address 0000000001c4bff4

CONTEXT:  fffff88006b6d0f0 -- (.cxr 0xfffff88006b6d0f0;r)
rax=0000000000000000 rbx=fffffa80079c6210 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007b2ef86 rsp=fffff88006b6dad0 rbp=0000000001c4bfd0
 r8=0000000000000000  r9=0000000001c4bfd0 r10=0000000000000002
r11=0000000001c4bfd0 r12=fffffa800973d3a0 r13=0000000000000000
r14=0000000001c4bfd0 r15=0000000001c4bfd0
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+0x2f86:
fffff880`07b2ef86 45396924        cmp     dword ptr [r9+24h],r13d ds:002b:00000000`01c4bff4=????????
Last set context:
rax=0000000000000000 rbx=fffffa80079c6210 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007b2ef86 rsp=fffff88006b6dad0 rbp=0000000001c4bfd0
 r8=0000000000000000  r9=0000000001c4bfd0 r10=0000000000000002
r11=0000000001c4bfd0 r12=fffffa800973d3a0 r13=0000000000000000
r14=0000000001c4bfd0 r15=0000000001c4bfd0
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+0x2f86:
fffff880`07b2ef86 45396924        cmp     dword ptr [r9+24h],r13d ds:002b:00000000`01c4bff4=????????
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:  0000000001c4bff4

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bf100
GetUlongFromAddress: unable to read from fffff800034bf1c0
 0000000001c4bff4 Nonpaged pool

FOLLOWUP_IP: 
lvrs64+2f86
fffff880`07b2ef86 45396924        cmp     dword ptr [r9+24h],r13d

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000001 to fffff88007b2ef86

STACK_TEXT:  
fffff880`06b6dad0 00000000`00000001 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`0a82c1d0 : lvrs64+0x2f86
fffff880`06b6dad8 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0a82c1d0 00000000`00000000 : 0x1
fffff880`06b6dae0 00000000`00000000 : 00000000`00000000 fffffa80`0a82c1d0 00000000`00000000 00000000`00000000 : 0xfffffa80`00000000


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  lvrs64+2f86

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: lvrs64

IMAGE_NAME:  lvrs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ee981fa

STACK_COMMAND:  .cxr 0xfffff88006b6d0f0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_lvrs64+2f86

BUCKET_ID:  X64_0x7E_lvrs64+2f86

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_lvrs64+2f86

FAILURE_ID_HASH:  {4d8561a1-00b2-4c1f-de87-0ae3c17279cd}

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

0: kd> lmvm lvrs64
start             end                 module name
fffff880`07b2c000 fffff880`07b7fb80   lvrs64   T (no symbols)           
    Loaded symbol image file: lvrs64.sys
    Image path: lvrs64.sys
    Image name: lvrs64.sys
    Timestamp:        Thu Dec 15 10:43:30 2011 (4EE981FA)
    CheckSum:         00065895
    ImageSize:        00053B80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm lvuvc64
start             end                 module name
fffff880`0766f000 fffff880`07b10080   lvuvc64    (deferred)             
    Image path: lvuvc64.sys
    Image name: lvuvc64.sys
    Timestamp:        Thu Dec 15 10:44:00 2011 (4EE98218)
    CheckSum:         004A7E46
    ImageSize:        004A1080
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {62, fffffa800781fd48, fffffa800798d510, 1b}

*** WARNING: Unable to verify timestamp for cmudaxp.sys
*** ERROR: Module load completed but symbols could not be loaded for cmudaxp.sys
Probably caused by : cmudaxp.sys

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

1: 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: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: fffffa800781fd48, name of the driver having the issue.
Arg3: fffffa800798d510, verifier internal structure with driver information.
Arg4: 000000000000001b, total # of (paged+nonpaged) allocations that weren't freed.
    Type !verifier 3 drivername.sys for info on the allocations
    that were leaked that caused the bugcheck.

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


BUGCHECK_STR:  0xc4_62

IMAGE_NAME:  cmudaxp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d78814f

MODULE_NAME: cmudaxp

FAULTING_MODULE: fffff88004cc4000 cmudaxp

VERIFIER_DRIVER_ENTRY: dt nt!_MI_VERIFIER_DRIVER_ENTRY fffffa800798d510
Symbol nt!_MI_VERIFIER_DRIVER_ENTRY not found.

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8000370b4ec to fffff8000327ebc0

STACK_TEXT:  
fffff880`031af6c8 fffff800`0370b4ec : 00000000`000000c4 00000000`00000062 fffffa80`0781fd48 fffffa80`0798d510 : nt!KeBugCheckEx
fffff880`031af6d0 fffff800`0371a65a : 00000000`00000001 00000000`00000000 fffff880`04cc4000 00000000`00000001 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`031af710 fffff800`03371270 : 00000000`00000000 00000000`00000000 fffff880`009e6180 00000000`00000000 : nt!VfPoolCheckForLeaks+0x4a
fffff880`031af750 fffff800`0363450e : fffffa80`0781fc30 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfTargetDriversRemove+0x160
fffff880`031af7f0 fffff800`03658f63 : 00000000`00000000 00000000`000e0082 00000000`00000000 00000000`00000001 : nt!VfDriverUnloadImage+0x2e
fffff880`031af820 fffff800`036593dd : 00000000`00000000 fffffa80`0781fc30 00000000`00000000 00000000`00010200 : nt!MiUnloadSystemImage+0x283
fffff880`031af890 fffff800`036fa981 : 00000000`00000000 00000000`00000015 fffffa80`053c4750 00000000`00000018 : nt!MmUnloadSystemImage+0x4d
fffff880`031af8d0 fffff800`03287e54 : 00000000`00000000 00000000`00000015 fffffa80`053c4750 00000000`00000004 : nt!IopDeleteDriver+0x41
fffff880`031af900 fffff800`034e9d39 : 00000000`00000015 fffffa80`06bc5930 fffffa80`053c48a0 fffff8a0`0753a120 : nt!ObfDereferenceObject+0xd4
fffff880`031af960 fffff800`03287e54 : fffffa80`06ba6c90 fffff800`0366ae8e fffff8a0`056f8978 fffffa80`06ba6c90 : nt!IopDeleteDevice+0x49
fffff880`031af990 fffff800`033810fb : 00000000`00000015 fffff8a0`056f8970 00000000`10af4780 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`031af9f0 fffff800`0366aef4 : fffffa80`069ee010 00000000`00000000 00000000`00000002 00000000`00000018 : nt!PnpRemoveLockedDeviceNode+0x23b
fffff880`031afa40 fffff800`0366b000 : 00000000`00000000 fffff8a0`168c3001 fffff8a0`16679430 ffffca9c`51b31713 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`031afa70 fffff800`036fbee4 : 00000000`00000002 00000000`00000000 fffffa80`069ee010 fffff8a0`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`031afae0 fffff800`036fc53c : fffff880`00000000 00000000`00010200 fffff880`031afc00 00000000`00000000 : nt!PnpProcessQueryRemoveAndEject+0xc34
fffff880`031afc20 fffff800`035e573e : 00000000`00000000 fffffa80`09aff990 fffff8a0`168c3010 fffff800`03424200 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`031afc50 fffff800`03288261 : fffff800`034e93d8 fffff8a0`168c3010 fffff800`034242d8 fffffa80`053c0040 : nt! ?? ::NNGAKEGL::`string'+0x54d9b
fffff880`031afcb0 fffff800`0351a73a : 00000000`00000000 fffffa80`053c0040 00000000`00000080 fffffa80`053a2040 : nt!ExpWorkerThread+0x111
fffff880`031afd40 fffff800`0326f8e6 : fffff880`02f64180 fffffa80`053c0040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031afd80 00000000`00000000 : fffff880`031b0000 fffff880`031aa000 fffff880`031af1d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xc4_62_LEAKED_POOL_IMAGE_cmudaxp.sys

BUCKET_ID:  X64_0xc4_62_LEAKED_POOL_IMAGE_cmudaxp.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xc4_62_leaked_pool_image_cmudaxp.sys

FAILURE_ID_HASH:  {03f0f943-0482-3ba6-d637-ea4e76f493c5}

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

1: kd> lmvm cmudaxp
start             end                 module name
fffff880`04cc4000 fffff880`04fef000   cmudaxp  T (no symbols)           
    Loaded symbol image file: cmudaxp.sys
    Image path: cmudaxp.sys
    Image name: cmudaxp.sys
    Timestamp:        Thu Mar 10 13:14:15 2011 (4D78814F)
    CheckSum:         002A05E0
    ImageSize:        0032B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Xileize · 09 Aug 2014

Hello,

I have downloaded and installed the drivers for my C920 Webcam.

To answer your other question, I do have an Asus Xonar DG PCI card installed in my PC that I don't use. I ran driver verifier a while ago to try and get to the bottom of my issue and forgot that I had turned it on. On Wednesday, I decided to uninstall the Xonar DG software because I don't use the card and Driver Verifier threw a BSOD every time I tried. Since then I have turned off Driver Verifier and uninstalled the software, but the card is still in my system as I haven't turned my PC off and taken it out yet. Will this have left corrupt drivers lying about on my system?

Arc · 09 Aug 2014

Xileize said:

Hello,

I have downloaded and installed the drivers for my C920 Webcam.

Good job. Let us know how it runs.

Xileize said:

To answer your other question, I do have an Asus Xonar DG PCI card installed in my PC that I don't use. I ran driver verifier a while ago to try and get to the bottom of my issue and forgot that I had turned it on. On Wednesday, I decided to uninstall the Xonar DG software because I don't use the card and Driver Verifier threw a BSOD every time I tried. Since then I have turned off Driver Verifier and uninstalled the software, but the card is still in my system as I haven't turned my PC off and taken it out yet. Will this have left corrupt drivers lying about on my system?

Apparently.

06/08/2014 09:08
Windows Error Reporting
Fault bucket X64_0xc4_62_LEAKED_POOL_IMAGE_cmudaxp.sys, type 0
Event Name: BlueScreen
&#x000a

Though it was caused by the driver verifier (0xC4). And as you are aware of it and already have taken precautions, I think we can consider it as less significant ATM.

Xileize · 09 Aug 2014

Arc said:

Xileize said:

Hello,

I have downloaded and installed the drivers for my C920 Webcam.

Good job. Let us know how it runs.

Xileize said:

To answer your other question, I do have an Asus Xonar DG PCI card installed in my PC that I don't use. I ran driver verifier a while ago to try and get to the bottom of my issue and forgot that I had turned it on. On Wednesday, I decided to uninstall the Xonar DG software because I don't use the card and Driver Verifier threw a BSOD every time I tried. Since then I have turned off Driver Verifier and uninstalled the software, but the card is still in my system as I haven't turned my PC off and taken it out yet. Will this have left corrupt drivers lying about on my system?

Apparently.

06/08/2014 09:08
Windows Error Reporting
Fault bucket X64_0xc4_62_LEAKED_POOL_IMAGE_cmudaxp.sys, type 0
Event Name: BlueScreen
&#x000a

Though it was caused by the driver verifier (0xC4). And as you are aware of it and already have taken precautions, I think we can consider it as less significant ATM.

Unfortunately, through all the BSODs I've had, I haven't noticed a pattern. My GPU was very old and overheating (8800GTX), which I replaced with a 560Ti. This occurred right before the month or so I didn't get BSODs, and I thought that it fixed the problem. Once I started getting them again I decided to memtest all my RAM and one of them came back with an error, so I replaced those and it's still BSODing. I will say that I have not run memtest on the new RAM that I bought, however. I may need to do this as I did purchase used DDR2 RAM.

I have also run prime95 on my PC at least twice in the last month overnight and there were no problems at all.

Arc · 09 Aug 2014

Its a bad history, mate. Let us see how far we can do.

First let us wait and observe how the computer runs after updating the webcam driver?

Xileize · 09 Aug 2014

Arc said:

Its a bad history, mate. Let us see how far we can do.

First let us wait and observe how the computer runs after updating the webcam driver?

Sure thing. I'll post back here in either a week or so, or after it BSODs again, whichever comes first!

Thank you very much for your help so far.

Xileize · 16 Aug 2014

Just a quick update to let you know that I haven't had a BSOD since the 8th of August when I updated the Webcam drivers and uninstalling/removing my Xonar DG card.

Knock on wood that I won't have any more problems, but if I do I'll let you know.

Thanks for your help!

Arc · 16 Aug 2014

That is a reasonably long time. So we are considering the issue as solved.

If the issue bounces back, just unmark and continue. I will be subscribed. :)