BSOD Kernel-power 41


  1. Posts : 1
    Windows 7 Home Premium 64bit
       #1

    BSOD Kernel-power 41


    Had BSOD with Kernel-power 41 in the Event log. Info on the .rar file.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Please follow this post: Another BSOD ntoskrnl.exe
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {80, 2, 0, fffff88002aad13e}
    
    *** WARNING: Unable to verify timestamp for cm11264.sys
    *** ERROR: Module load completed but symbols could not be loaded for cm11264.sys
    Probably caused by : cm11264.sys ( cm11264+8613e )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000080, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88002aad13e, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310b100
    GetUlongFromAddress: unable to read from fffff8000310b1c0
     0000000000000080 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    cm11264+8613e
    fffff880`02aad13e 49ffcb          dec     r11
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  bf4.exe
    
    TAG_NOT_DEFINED_c000000f:  FFFFF800048F7FB0
    
    TRAP_FRAME:  fffff800048f72a0 -- (.trap 0xfffff800048f72a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000080 rbx=0000000000000000 rcx=fffffa800d779494
    rdx=fffffa800d80dd20 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88002aad13e rsp=fffff800048f7430 rbp=fffffa800d77b0b0
     r8=0000000000000080  r9=0000000000000080 r10=fffffa800d80dd4c
    r11=000000000000001f r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    cm11264+0x8613e:
    fffff880`02aad13e 49ffcb          dec     r11
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ed3129 to fffff80002ed3b80
    
    STACK_TEXT:  
    fffff800`048f7158 fffff800`02ed3129 : 00000000`0000000a 00000000`00000080 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff800`048f7160 fffff800`02ed1da0 : fffffa80`0d80d720 fffffa80`0d80dd20 fffffa80`0d80f020 00000000`000948b0 : nt!KiBugCheckDispatch+0x69
    fffff800`048f72a0 fffff880`02aad13e : 00000000`00000000 00000000`00000000 fffff800`048f74e0 fffffa80`0d77b0b0 : nt!KiPageFault+0x260
    fffff800`048f7430 00000000`00000000 : 00000000`00000000 fffff800`048f74e0 fffffa80`0d77b0b0 fffffa80`0d7ed810 : cm11264+0x8613e
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    cm11264+8613e
    fffff880`02aad13e 49ffcb          dec     r11
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  cm11264+8613e
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: cm11264
    
    IMAGE_NAME:  cm11264.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e535a4d
    
    FAILURE_BUCKET_ID:  X64_0xD1_cm11264+8613e
    
    BUCKET_ID:  X64_0xD1_cm11264+8613e
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm cm11264
    start             end                 module name
    fffff880`02a27000 fffff880`02bb2000   cm11264  T (no symbols)           
        Loaded symbol image file: cm11264.sys
        Image path: \SystemRoot\system32\drivers\cm11264.sys
        Image name: cm11264.sys
        Timestamp:        Tue Aug 23 13:44:13 2011 (4E535A4D)
        CheckSum:         0013F60A
        ImageSize:        0018B000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Please run these tests and report back the results
    ------------------------
    1. SFC /scannow to check windows for corruption - SFC /SCANNOW - System File Checker
    2. Disk check for errors on the hard drive - Run Disk Check in Windows 7
    3. Troubleshoot apps by a clean boot - Performing a Clean Startup
    4. Memtest86+ paying attention to part 3 - RAM - Test with Memtest86+
    5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 17:57.
Find Us