Kernel Power - Event ID 41 - Task Category 63 (spontaneous improper sh


  1. Posts : 1
    Win7
       #1

    Kernel Power - Event ID 41 - Task Category 63 (spontaneous improper sh


    BSOD happen only recently...
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi packman888,

    Your crash dumps are not showing any finite probable cause.

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
    ________________________________________________________________
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff96000352b67, fffff880088f5fe0, 0}
    
    Probably caused by : win32k.sys ( win32k!SFMLOGICALSURFACE::SetShape+157 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff96000352b67, Address of the instruction which caused the bugcheck
    Arg3: fffff880088f5fe0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    win32k!SFMLOGICALSURFACE::SetShape+157
    fffff960`00352b67 488b5508        mov     rdx,qword ptr [rbp+8]
    
    CONTEXT:  fffff880088f5fe0 -- (.cxr 0xfffff880088f5fe0)
    rax=fffff880088f6a08 rbx=0000000000000000 rcx=fffff900c076bbd0
    rdx=fffff900c00d2280 rsi=0000000000000000 rdi=fffff900c076bbd0
    rip=fffff96000352b67 rsp=fffff880088f69c0 rbp=0000000000000018
     r8=000000000712ff11  r9=000000000000ff12 r10=000000000002fd36
    r11=fffff880088f69f0 r12=0000000000000001 r13=fffff900c00d2280
    r14=fffff900c00d2280 r15=8000000000001000
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    win32k!SFMLOGICALSURFACE::SetShape+0x157:
    fffff960`00352b67 488b5508        mov     rdx,qword ptr [rbp+8] ss:0018:00000000`00000020=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  dwm.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff96000352b67
    
    STACK_TEXT:  
    fffff880`088f69c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SFMLOGICALSURFACE::SetShape+0x157
    
    
    FOLLOWUP_IP: 
    win32k!SFMLOGICALSURFACE::SetShape+157
    fffff960`00352b67 488b5508        mov     rdx,qword ptr [rbp+8]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  win32k!SFMLOGICALSURFACE::SetShape+157
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51aeb1a7
    
    STACK_COMMAND:  .cxr 0xfffff880088f5fe0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_win32k!SFMLOGICALSURFACE::SetShape+157
    
    BUCKET_ID:  X64_0x3B_win32k!SFMLOGICALSURFACE::SetShape+157
    
    Followup: MachineOwner
    ---------
      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 13:06.
Find Us