none
System BSOD Kernel-power Event ID 41 Task 63 BugCodecheck 126 or 0x7E

    Question

  • Hi Guys!

    Just had a BSOD and looking it up in the event viewer I get what's in the the title.

     

     

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
    <EventID>41</EventID>
    <Version>2</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000002</Keywords>
    <TimeCreated SystemTime="2011-07-26T19:17:59.864811200Z" />
    <EventRecordID>64766</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>Clifford-PC</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    - <EventData>
    <Data Name="BugcheckCode">126</Data>
    <Data Name="BugcheckParameter1">0xffffffffc0000005</Data>
    <Data Name="BugcheckParameter2">0xfffff88002210435</Data>
    <Data Name="BugcheckParameter3">0xfffff880065ef898</Data>
    <Data Name="BugcheckParameter4">0xfffff880065ef0f0</Data>
    <Data Name="SleepInProgress">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
    </EventData>
    </Event>

     
    I've got the minidump and I'll put it on my skydrive (if I can figure that one out :D)
    I was having other BSOD's recently and turns out I had a faulty stick of RAM so I've got the good half running on my PC now. Going to RMA soon.
    Thanks in advance!
    • Edited by Clifbel Tuesday, July 26, 2011 10:59 PM
    Tuesday, July 26, 2011 8:02 PM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        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: fffff88002210435, The address that the exception occurred at
    Arg3: fffff880065ef898, Exception Record Address
    Arg4: fffff880065ef0f0, Context Record Address
    Debugging Details:
    ------------------
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L
    FAULTING_IP: 
    lvrs64+10435
    fffff880`02210435 894620          mov     dword ptr [rsi+20h],eax
    EXCEPTION_RECORD:  fffff880065ef898 -- (.exr 0xfffff880065ef898)
    ExceptionAddress: fffff88002210435 (lvrs64+0x0000000000010435)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000001
       Parameter[1]: 00000000027346a0
    Attempt to write to address 00000000027346a0
    CONTEXT:  fffff880065ef0f0 -- (.cxr 0xfffff880065ef0f0)
    rax=0000000000000000 rbx=fffffa80098fc740 rcx=fffffa8008837840
    rdx=0000000000000001 rsi=0000000002734680 rdi=fffffa8003d58e60
    rip=fffff88002210435 rsp=fffff880065efad0 rbp=fffffa80088377e0
     r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
    r11=fffff880033d7180 r12=0000000000000002 r13=0000000000000000
    r14=0000000000000001 r15=fffff8800224a870
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    lvrs64+0x10435:
    fffff880`02210435 894620          mov     dword ptr [rsi+20h],eax ds:002b:00000000`027346a0=????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    ERROR_CODE: (NTSTATUS) 0xc0000005 - L
    EXCEPTION_PARAMETER1:  0000000000000001
    EXCEPTION_PARAMETER2:  00000000027346a0
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000370b100
     00000000027346a0 
    FOLLOWUP_IP: 
    lvrs64+10435
    fffff880`02210435 894620          mov     dword ptr [rsi+20h],eax
    BUGCHECK_STR:  0x7E
    LAST_CONTROL_TRANSFER:  from fffffa80098fc740 to fffff88002210435
    STACK_TEXT:  
    fffff880`065efad0 fffffa80`098fc740 : fffffa80`088377e0 00000000`02734680 fffffa80`06555f70 00000000`00000000 : lvrs64+0x10435
    fffff880`065efad8 fffffa80`088377e0 : 00000000`02734680 fffffa80`06555f70 00000000`00000000 fffff880`065efc18 : 0xfffffa80`098fc740
    fffff880`065efae0 00000000`02734680 : fffffa80`06555f70 00000000`00000000 fffff880`065efc18 00000000`00000000 : 0xfffffa80`088377e0
    fffff880`065efae8 fffffa80`06555f70 : 00000000`00000000 fffff880`065efc18 00000000`00000000 fffff880`065efb30 : 0x2734680
    fffff880`065efaf0 00000000`00000000 : fffff880`065efc18 00000000`00000000 fffff880`065efb30 fffff880`0224b1a0 : 0xfffffa80`06555f70
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  lvrs64+10435
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: lvrs64
    IMAGE_NAME:  lvrs64.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d955c33
    STACK_COMMAND:  .cxr 0xfffff880065ef0f0 ; kb
    FAILURE_BUCKET_ID:  X64_0x7E_lvrs64+10435
    BUCKET_ID:  X64_0x7E_lvrs64+10435
    Followup: MachineOwner
    ---------
    3: kd> lmvm lvrs64
    start             end                 module name
    fffff880`02200000 fffff880`02251d00   lvrs64   T (no symbols)           
        Loaded symbol image file: lvrs64.sys
        Image path: \SystemRoot\system32\DRIVERS\lvrs64.sys
        Image name: lvrs64.sys
        Timestamp:        Fri Apr 01 06:01:39 2011 (4D955C33)
        CheckSum:         0005FD09
        ImageSize:        00051D00
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    ----------------------------------------------------------------------------------------------------------
    The BSOD was caused by lvrs64.sys driver. It belongs to Logitech. Try updating it or contact Logitech Technical Support.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    • Marked as answer by Clifbel Wednesday, July 27, 2011 11:53 AM
    Wednesday, July 27, 2011 6:53 AM

All replies

  •  

    <Data Name="BugcheckCode">126</Data>

    I think you mean <Data Name="BugcheckCode">124</Data>.

    Bug Check Code 0x124: http://msdn.microsoft.com/en-us/library/ff557321(v=VS.85).aspx

    Bug Check Code 0x7E: http://msdn.microsoft.com/en-us/library/ff559239(v=VS.85).aspx

    Please use Microsoft Skydrive to upload dump files (c:\windows\minidumps). Once done, post a link here.

    You can also contact Microsoft CSS.

     

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

     


    Tuesday, July 26, 2011 8:55 PM
  • Here you are as promised, it's got the actual file as well as a zipped version.

    Thanks for the quick reply.

    I'm pretty sure it's 126 I've just checked again and it is, maybe I've converted into hex wrong sorry! 



    Tuesday, July 26, 2011 11:03 PM
  • *******************************************************************************
    *                                                                             *
    *                        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: fffff88002210435, The address that the exception occurred at
    Arg3: fffff880065ef898, Exception Record Address
    Arg4: fffff880065ef0f0, Context Record Address
    Debugging Details:
    ------------------
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L
    FAULTING_IP: 
    lvrs64+10435
    fffff880`02210435 894620          mov     dword ptr [rsi+20h],eax
    EXCEPTION_RECORD:  fffff880065ef898 -- (.exr 0xfffff880065ef898)
    ExceptionAddress: fffff88002210435 (lvrs64+0x0000000000010435)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000001
       Parameter[1]: 00000000027346a0
    Attempt to write to address 00000000027346a0
    CONTEXT:  fffff880065ef0f0 -- (.cxr 0xfffff880065ef0f0)
    rax=0000000000000000 rbx=fffffa80098fc740 rcx=fffffa8008837840
    rdx=0000000000000001 rsi=0000000002734680 rdi=fffffa8003d58e60
    rip=fffff88002210435 rsp=fffff880065efad0 rbp=fffffa80088377e0
     r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
    r11=fffff880033d7180 r12=0000000000000002 r13=0000000000000000
    r14=0000000000000001 r15=fffff8800224a870
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    lvrs64+0x10435:
    fffff880`02210435 894620          mov     dword ptr [rsi+20h],eax ds:002b:00000000`027346a0=????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    ERROR_CODE: (NTSTATUS) 0xc0000005 - L
    EXCEPTION_PARAMETER1:  0000000000000001
    EXCEPTION_PARAMETER2:  00000000027346a0
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000370b100
     00000000027346a0 
    FOLLOWUP_IP: 
    lvrs64+10435
    fffff880`02210435 894620          mov     dword ptr [rsi+20h],eax
    BUGCHECK_STR:  0x7E
    LAST_CONTROL_TRANSFER:  from fffffa80098fc740 to fffff88002210435
    STACK_TEXT:  
    fffff880`065efad0 fffffa80`098fc740 : fffffa80`088377e0 00000000`02734680 fffffa80`06555f70 00000000`00000000 : lvrs64+0x10435
    fffff880`065efad8 fffffa80`088377e0 : 00000000`02734680 fffffa80`06555f70 00000000`00000000 fffff880`065efc18 : 0xfffffa80`098fc740
    fffff880`065efae0 00000000`02734680 : fffffa80`06555f70 00000000`00000000 fffff880`065efc18 00000000`00000000 : 0xfffffa80`088377e0
    fffff880`065efae8 fffffa80`06555f70 : 00000000`00000000 fffff880`065efc18 00000000`00000000 fffff880`065efb30 : 0x2734680
    fffff880`065efaf0 00000000`00000000 : fffff880`065efc18 00000000`00000000 fffff880`065efb30 fffff880`0224b1a0 : 0xfffffa80`06555f70
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  lvrs64+10435
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: lvrs64
    IMAGE_NAME:  lvrs64.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d955c33
    STACK_COMMAND:  .cxr 0xfffff880065ef0f0 ; kb
    FAILURE_BUCKET_ID:  X64_0x7E_lvrs64+10435
    BUCKET_ID:  X64_0x7E_lvrs64+10435
    Followup: MachineOwner
    ---------
    3: kd> lmvm lvrs64
    start             end                 module name
    fffff880`02200000 fffff880`02251d00   lvrs64   T (no symbols)           
        Loaded symbol image file: lvrs64.sys
        Image path: \SystemRoot\system32\DRIVERS\lvrs64.sys
        Image name: lvrs64.sys
        Timestamp:        Fri Apr 01 06:01:39 2011 (4D955C33)
        CheckSum:         0005FD09
        ImageSize:        00051D00
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    ----------------------------------------------------------------------------------------------------------
    The BSOD was caused by lvrs64.sys driver. It belongs to Logitech. Try updating it or contact Logitech Technical Support.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    • Marked as answer by Clifbel Wednesday, July 27, 2011 11:53 AM
    Wednesday, July 27, 2011 6:53 AM