locked
BSOD with BugCheck Error 1001 Memory Dump Help RRS feed

  • Question

  • Hello, I need a bit of help.  My computer just crashed with a blue screen of death suddenly while I was doing some audio editing (I do this frequently, never had an issue before).  I have no idea what to do with this memory dump I got, so I was hoping someone could help me.

    https://onedrive.live.com/redir?resid=3BE2487D830FFF04!107&authkey=!ANb7Ny6ZZXtBfL8&ithint=file%2c.dmp

    That's the link to the memory dump file.  Let me know if you need any other data from me.  Thanks!

    Thursday, February 27, 2014 5:55 AM

Answers

  • Thompa2

    This was Related to lvrs64.sys Kernel Audio Improvement Filter Driver from Logitech Inc.  I would install the newest driver available.  Yours is ~ 2years old.

    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0xfffff800`03407000 PsLoadedModuleList = 0xfffff800`0364a6d0
    Debug session time: Thu Feb 27 00:37:31.119 2014 (UTC - 5:00)
    System Uptime: 0 days 15:35:44.212
    
    
    
    BugCheck 1000007E, {ffffffffc0000005, fffff88002ec1fc6, fffff88007de3758, fffff88007de2fb0}
    
    Probably caused by : lvrs64.sys ( lvrs64+2fc6 )
    
    
    
    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: fffff88002ec1fc6, The address that the exception occurred at
    Arg3: fffff88007de3758, Exception Record Address
    Arg4: fffff88007de2fb0, 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`02ec1fc6 45396924        cmp     dword ptr [r9+24h],r13d
    
    EXCEPTION_RECORD:  fffff88007de3758 -- (.exr 0xfffff88007de3758)
    ExceptionAddress: fffff88002ec1fc6 (lvrs64+0x0000000000002fc6)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 00000000003cd464
    Attempt to read from address 00000000003cd464
    
    CONTEXT:  fffff88007de2fb0 -- (.cxr 0xfffff88007de2fb0;r)
    rax=0000000000000000 rbx=fffffa800eb37970 rcx=0000000000000001
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88002ec1fc6 rsp=fffff88007de3990 rbp=00000000003cd440
     r8=0000000000000000  r9=00000000003cd440 r10=0000000000000002
    r11=00000000003cd440 r12=fffffa800eb33df0 r13=0000000000000000
    r14=00000000003cd440 r15=00000000003cd440
    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`02ec1fc6 45396924        cmp     dword ptr [r9+24h],r13d ds:002b:00000000`003cd464=????????
    Last set context:
    rax=0000000000000000 rbx=fffffa800eb37970 rcx=0000000000000001
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88002ec1fc6 rsp=fffff88007de3990 rbp=00000000003cd440
     r8=0000000000000000  r9=00000000003cd440 r10=0000000000000002
    r11=00000000003cd440 r12=fffffa800eb33df0 r13=0000000000000000
    r14=00000000003cd440 r15=00000000003cd440
    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`02ec1fc6 45396924        cmp     dword ptr [r9+24h],r13d ds:002b:00000000`003cd464=????????
    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:  00000000003cd464
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b4100
    GetUlongFromAddress: unable to read from fffff800036b41c0
     00000000003cd464 Nonpaged pool
    
    FOLLOWUP_IP: 
    lvrs64+2fc6
    fffff880`02ec1fc6 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 fffff88002ec1fc6
    
    STACK_TEXT:  
    fffff880`07de3990 00000000`00000001 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`12f495f0 : lvrs64+0x2fc6
    fffff880`07de3998 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffffa80`12f495f0 00000000`00000000 : 0x1
    fffff880`07de39a0 00000000`00000000 : 00000000`00000000 fffffa80`12f495f0 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 0xfffff88007de2fb0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_lvrs64+2fc6
    
    BUCKET_ID:  X64_0x7E_lvrs64+2fc6
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x7e_lvrs64+2fc6
    
    FAILURE_ID_HASH:  {4d85bbe7-3359-5d02-03c0-19e8d54c8fdc}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by thompa2 Thursday, February 27, 2014 6:30 AM
    Thursday, February 27, 2014 6:02 AM

All replies

  • Thompa2

    This was Related to lvrs64.sys Kernel Audio Improvement Filter Driver from Logitech Inc.  I would install the newest driver available.  Yours is ~ 2years old.

    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0xfffff800`03407000 PsLoadedModuleList = 0xfffff800`0364a6d0
    Debug session time: Thu Feb 27 00:37:31.119 2014 (UTC - 5:00)
    System Uptime: 0 days 15:35:44.212
    
    
    
    BugCheck 1000007E, {ffffffffc0000005, fffff88002ec1fc6, fffff88007de3758, fffff88007de2fb0}
    
    Probably caused by : lvrs64.sys ( lvrs64+2fc6 )
    
    
    
    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: fffff88002ec1fc6, The address that the exception occurred at
    Arg3: fffff88007de3758, Exception Record Address
    Arg4: fffff88007de2fb0, 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`02ec1fc6 45396924        cmp     dword ptr [r9+24h],r13d
    
    EXCEPTION_RECORD:  fffff88007de3758 -- (.exr 0xfffff88007de3758)
    ExceptionAddress: fffff88002ec1fc6 (lvrs64+0x0000000000002fc6)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 00000000003cd464
    Attempt to read from address 00000000003cd464
    
    CONTEXT:  fffff88007de2fb0 -- (.cxr 0xfffff88007de2fb0;r)
    rax=0000000000000000 rbx=fffffa800eb37970 rcx=0000000000000001
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88002ec1fc6 rsp=fffff88007de3990 rbp=00000000003cd440
     r8=0000000000000000  r9=00000000003cd440 r10=0000000000000002
    r11=00000000003cd440 r12=fffffa800eb33df0 r13=0000000000000000
    r14=00000000003cd440 r15=00000000003cd440
    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`02ec1fc6 45396924        cmp     dword ptr [r9+24h],r13d ds:002b:00000000`003cd464=????????
    Last set context:
    rax=0000000000000000 rbx=fffffa800eb37970 rcx=0000000000000001
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88002ec1fc6 rsp=fffff88007de3990 rbp=00000000003cd440
     r8=0000000000000000  r9=00000000003cd440 r10=0000000000000002
    r11=00000000003cd440 r12=fffffa800eb33df0 r13=0000000000000000
    r14=00000000003cd440 r15=00000000003cd440
    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`02ec1fc6 45396924        cmp     dword ptr [r9+24h],r13d ds:002b:00000000`003cd464=????????
    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:  00000000003cd464
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b4100
    GetUlongFromAddress: unable to read from fffff800036b41c0
     00000000003cd464 Nonpaged pool
    
    FOLLOWUP_IP: 
    lvrs64+2fc6
    fffff880`02ec1fc6 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 fffff88002ec1fc6
    
    STACK_TEXT:  
    fffff880`07de3990 00000000`00000001 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`12f495f0 : lvrs64+0x2fc6
    fffff880`07de3998 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffffa80`12f495f0 00000000`00000000 : 0x1
    fffff880`07de39a0 00000000`00000000 : 00000000`00000000 fffffa80`12f495f0 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 0xfffff88007de2fb0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_lvrs64+2fc6
    
    BUCKET_ID:  X64_0x7E_lvrs64+2fc6
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x7e_lvrs64+2fc6
    
    FAILURE_ID_HASH:  {4d85bbe7-3359-5d02-03c0-19e8d54c8fdc}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by thompa2 Thursday, February 27, 2014 6:30 AM
    Thursday, February 27, 2014 6:02 AM
  • SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

    Bug Check code: 0x1000007e

    Caused By Driver : lvrs64.sys

    -----------------------

    lvrs64.sys is related with Logitech Web Cam. Try to update or reinstall driver


    Roman Levchenko, MCITP, MCTS http://www.rlevchenko.com

    • Proposed as answer by R.LevchenkoMVP Thursday, February 27, 2014 6:36 AM
    Thursday, February 27, 2014 6:02 AM
  • Thank you!  That logitech web cam has given me nothing but problems since I bought it...
    Thursday, February 27, 2014 6:31 AM
  • Thompa2

    Let us know if we can help further.  YOu might want to try installing the drivers in compatibility dome

    To Run in compatibility mode do the following:

    Right click the installer>properties>compatibility>choose OS

    http://windows.microsoft.com/en-US/windows-vista/Make-older-programs-run-in-this-version-of-Windows?SignedIn=1


    Wanikiya and Dyami--Team Zigzag

    Thursday, February 27, 2014 6:40 AM