locked
blue screen Microsoft-Windows-Kernel-Power EventID=41 RRS feed

  • General discussion

  • Hello.
    I just got an bluescreen now and couldnt find the reason by now:
    - <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-12-07T14:46:03.664824800Z" />
    <EventRecordID>479703</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>TOM</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    - <EventData>
    <Data Name="BugcheckCode">30</Data>
    <Data Name="BugcheckParameter1">0xffffffffc0000047</Data>
    <Data Name="BugcheckParameter2">0xfffff80003108590</Data>
    <Data Name="BugcheckParameter3">0x11b766100</Data>
    <Data Name="BugcheckParameter4">0xfffffa801b00ff02</Data>
    <Data Name="SleepInProgress">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
    </EventData>
    </Event>
    i wasnt doing any special things there but downloading or installing some windows updates while surfing. so i am not sure if he still downloaded it or allrdy started with installing. but shouldnt play a role all in all.
    drivers are up to date and it was the blue screen since months.
    sadly i was to slow to see the stop code since i was searching for pen and paper. but irc it was stop 0xe1(...).
    looking forward to get at least an hint. ty =)
    edit: minidump: https://skydrive.live.com/redir.aspx?cid=6aac249c7991c3dc&resid=6AAC249C7991C3DC!145&parid=6AAC249C7991C3DC!136&authkey=!AFkN39NHHi7kTvw
    • Changed type un]skilled Wednesday, December 7, 2011 3:25 PM
    • Edited by un]skilled Wednesday, December 7, 2011 3:46 PM no newlines
    Wednesday, December 7, 2011 3:18 PM

All replies

  • Bug Check 0x30 : http://msdn.microsoft.com/en-us/library/ff557478(v=vs.85).aspx

     

    Please Upload the DMP files From C:\Windows\minidump into SkyDrive.

     

    Regards,

     


    MCP ✦ MCTS ✦ MCITP
    Wednesday, December 7, 2011 3:29 PM
  • https://skydrive.live.com/redir.aspx?cid=6aac249c7991c3dc&resid=6AAC249C7991C3DC!145&parid=6AAC249C7991C3DC!136&authkey=!AFkN39NHHi7kTvw
    Wednesday, December 7, 2011 3:42 PM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc0000047, The exception code that was not handled
    Arg2: fffff80003108590, The address that the exception occurred at
    Arg3: 000000011b766100, Parameter 0 of the exception
    Arg4: fffffa801b00ff02, Parameter 1 of the exception
    Debugging Details:
    ------------------
    EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.
    FAULTING_IP: 
    nt!RtlRaiseStatus+18
    fffff800`03108590 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h]
    EXCEPTION_PARAMETER1:  000000011b766100
    EXCEPTION_PARAMETER2:  fffffa801b00ff02
    ERROR_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.
    BUGCHECK_STR:  0x1E_c0000047
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    LAST_CONTROL_TRANSFER:  from fffff80003126588 to fffff800030dac40
    STACK_TEXT:  
    fffff880`0351a7f8 fffff800`03126588 : 00000000`0000001e ffffffff`c0000047 fffff800`03108590 00000001`1b766100 : nt!KeBugCheckEx
    fffff880`0351a800 fffff800`03128af8 : fffff880`0351b2d0 fffff880`0351b2d0 fffff880`0351b110 fffff880`0351b370 : nt! ?? ::FNODOBFM::`string'+0x4977d
    fffff880`0351aea0 fffff800`030dc9fb : fffff880`0351b2d0 fffff880`009f0f40 fffffa80`1bbaddc0 00000000`00000002 : nt!KiRaiseException+0x1b4
    fffff880`0351afd0 fffff800`030d9ed3 : fffffa80`1b9d8c30 fffff880`01abeb80 fffffa80`1b7b9100 00000000`00000000 : nt!NtRaiseException+0x7b
    fffff880`0351b110 fffff800`03108590 : fffff880`0351b2d0 fffff880`0351b370 fffffa80`00000001 fffffa80`1b98d010 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`0351b2b0 fffff800`0309570a : fffffa80`07ff3b10 fffffa80`07ff3b10 00000000`00000000 fffff880`0351b978 : nt!RtlRaiseStatus+0x18
    fffff880`0351b850 fffff880`06a561b7 : fffffa80`1bbaddc0 fffff800`00000000 fffffa80`1badb010 fffffa80`1badb200 : nt! ?? ::FNODOBFM::`string'+0xf5a9
    fffff880`0351b8d0 fffffa80`1bbaddc0 : fffff800`00000000 fffffa80`1badb010 fffffa80`1badb200 fffffa80`00000000 : Arctosa+0x11b7
    fffff880`0351b8d8 fffff800`00000000 : fffffa80`1badb010 fffffa80`1badb200 fffffa80`00000000 fffffa80`1bbadf10 : 0xfffffa80`1bbaddc0
    fffff880`0351b8e0 fffffa80`1badb010 : fffffa80`1badb200 fffffa80`00000000 fffffa80`1bbadf10 00000000`00000000 : 0xfffff800`00000000
    fffff880`0351b8e8 fffffa80`1badb200 : fffffa80`00000000 fffffa80`1bbadf10 00000000`00000000 ffff0280`00000090 : 0xfffffa80`1badb010
    fffff880`0351b8f0 fffffa80`00000000 : fffffa80`1bbadf10 00000000`00000000 ffff0280`00000090 fffffa80`00000008 : 0xfffffa80`1badb200
    fffff880`0351b8f8 fffffa80`1bbadf10 : 00000000`00000000 ffff0280`00000090 fffffa80`00000008 fffffa80`07cbd940 : 0xfffffa80`00000000
    fffff880`0351b900 00000000`00000000 : ffff0280`00000090 fffffa80`00000008 fffffa80`07cbd940 00000000`00000000 : 0xfffffa80`1bbadf10
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    Arctosa+11b7
    fffff880`06a561b7 ??              ???
    SYMBOL_STACK_INDEX:  7
    SYMBOL_NAME:  Arctosa+11b7
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: Arctosa
    IMAGE_NAME:  Arctosa.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a8bb060
    FAILURE_BUCKET_ID:  X64_0x1E_c0000047_Arctosa+11b7
    BUCKET_ID:  X64_0x1E_c0000047_Arctosa+11b7
    Followup: MachineOwner
    ---------------------------------------------------------------------------------------------------------------------------------------------------------
    The Blue Screen Caused by Arctosa.sys 
    Arctosa.sys with description Razer Arctosa Keyboard Driver is a driver file from company Razer USA Ltd. belonging to product Razer Arctosa.
    so Update your Keyboard Driver it Solve Your Blue Screen.
    Regards,


    MCP ✦ MCTS ✦ MCITP
    Wednesday, December 7, 2011 3:55 PM
  • Thank you but this driver is allrdy up to date (v1.00). Hopefully it was the first and only error. Thank you! :)
    Wednesday, December 7, 2011 8:19 PM
  • Ok, make a Contact with Razer Support team and tell them , that you want another Driver Version for your keyboard : http://www.razersupport.com/index.php?_m=downloads&_a=view

     

     

    Regards,

     


    MCP ✦ MCTS ✦ MCITP
    Wednesday, December 7, 2011 8:32 PM