Windows 8 and 8.1 Forums


Kernel Error 0x8000000000000002 BSOD Event ID 41, task 63?

  1. #1


    Posts : 44
    Windows 8.1 64 Bit

    Kernel Error 0x8000000000000002 BSOD Event ID 41, task 63?


    Hi, Yeah i just recently got a new Windows 8 desktop and almost every I literally get a BSOD relating to Kernel error. 0x8000000000000002. My most recent time I just got a BSOD It said KERNEL_SECURITY_FAILURE. This is truly frustrating - <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>3</Version>

    <Level>1</Level>

    <Task>63</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000002</Keywords>

    <TimeCreated SystemTime="2014-04-02T04:44:41.100324300Z" />

    <EventRecordID>2569</EventRecordID>

    <Correlation />

    <Execution ProcessID="4" ThreadID="8" />

    <Channel>System</Channel>

    <Computer>Eric</Computer>

    <Security UserID="S-1-5-18" />

    </System>


    - <EventData>
    <Data Name="BugcheckCode">313</Data>

    <Data Name="BugcheckParameter1">0x3</Data>

    <Data Name="BugcheckParameter2">0xffffd0002115cc20</Data>

    <Data Name="BugcheckParameter3">0xffffd0002115cb78</Data>

    <Data Name="BugcheckParameter4">0x0</Data>

    <Data Name="SleepInProgress">0</Data>

    <Data Name="PowerButtonTimestamp">0</Data>

    <Data Name="BootAppStatus">0</Data>

    </EventData>


    </Event>

    Can it be because my
    Hi, Yeah i just recently got a new Windows 8 desktop and almost every I literally get a BSOD relating to Kernel error. 0x8000000000000002. My most recent time I just got a BSOD It said KERNEL_SECURITY_FAILURE. This is truly frustrating - <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>3</Version>

    <Level>1</Level>

    <Task>63</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000002</Keywords>

    <TimeCreated SystemTime="2014-04-02T04:44:41.100324300Z" />

    <EventRecordID>2569</EventRecordID>

    <Correlation />

    <Execution ProcessID="4" ThreadID="8" />

    <Channel>System</Channel>

    <Computer>Eric</Computer>

    <Security UserID="S-1-5-18" />

    </System>


    - <EventData>
    <Data Name="BugcheckCode">313</Data>

    <Data Name="BugcheckParameter1">0x3</Data>

    <Data Name="BugcheckParameter2">0xffffd0002115cc20</Data>

    <Data Name="BugcheckParameter3">0xffffd0002115cb78</Data>

    <Data Name="BugcheckParameter4">0x0</Data>

    <Data Name="SleepInProgress">0</Data>

    <Data Name="PowerButtonTimestamp">0</Data>

    <Data Name="BootAppStatus">0</Data>

    </EventData>


    </Event>

    Can it be that my Qualcomm Atheros Osprey Wireless Network Adapter isn't compatible with Windows 8.1 on a NetGear Router? If so, should I replace my Wirless card? Idk.
    Please Help I just got this PC a few weeks ago!


    UPDATE! When I tried to unsleep my pc. It was just a black screen. Frozen.


    Log Name: SystemSource: Microsoft-Windows-Kernel-Power
    Date: 4/2/2014 5:11:57 PM
    Event ID: 41
    Task Category: (63)
    Level: Critical
    Keywords: (2)
    User: SYSTEM
    Computer: Eric
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Event Xml:
    <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>3</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000002</Keywords>
    <TimeCreated SystemTime="2014-04-03T00:11:57.084043800Z" />
    <EventRecordID>2755</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>Eric</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <EventData>
    <Data Name="BugcheckCode">0</Data>
    <Data Name="BugcheckParameter1">0x0</Data>
    <Data Name="BugcheckParameter2">0x0</Data>
    <Data Name="BugcheckParameter3">0x0</Data>
    <Data Name="BugcheckParameter4">0x0</Data>
    <Data Name="SleepInProgress">0</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
    <Data Name="BootAppStatus">0</Data>
    </EventData>
    </Event>
    Last edited by Cire3; 02 Apr 2014 at 16:15.

      My System SpecsSystem Spec

  2. #2


    Posts : 660
    windows 8.1


    What antivirus are you running at the moment, because in your system Specs you mention Windows Defender and Malwarebytes.
    But in your driverlist there are many references to Eset. These drivers are from 2013. If you still use Eset please update Eset to the latest windows 8 compatible version. Else please remove Eset, look on the Esetwebsite for the removal tool.

    Please update your Qualcomm Atheros Osprey Wireless Network Adapter to the latest windows 8.1 driver Drivers for Atheros Osprey and Windows 8

    Please update all the drivers for your mainboard M5A99FX PRO R2.0 to the latest windows 8.1. drivers here ASUSTeK Computer Inc. -Support- Drivers and Download M5A99FX PRO R2.0 . Select OS windows 8.1

    Your BIOS version is 2005, the latest version is 2301 with explanation Improve system stability from 3/27/2014

    One of your dumpfiles blames memory corruption so run MemTest, Prime95, video tests, and CPU stress tests at a minimum Initial Hardware Diagnostics

    Also the atikmdag.sys is blamed in a BSOD this is the driver for your AMD Graphic card. Although your drivers is from 6 dec 2013 look for the latest version and update.




    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffff800021a3970, ffffd00027b61fe0, 0}
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : atikmdag.sys ( atikmdag+13b970 )
    Followup: MachineOwner
    ---------
    5: 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: fffff800021a3970, Address of the instruction which caused the bugcheck
    Arg3: ffffd00027b61fe0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck A0000001, {5, 0, 0, 0}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    Followup: MachineOwner
    ---------
    7: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Unknown bugcheck code (a0000001)
    Unknown bugcheck description
    Arguments:
    Arg1: 0000000000000005
    Arg2: 0000000000000000
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 109, {a3a01f58953a2743, b3b72bdee7b8c1e2, fffff8000010c19b, 1}
    Probably caused by : memory_corruption
    Followup: memory_corruption
    ---------
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    CRITICAL_STRUCTURE_CORRUPTION (109)
    This bugcheck is generated when the kernel detects that critical kernel code or
    data have been corrupted. There are generally three causes for a corruption:
    1) A driver has inadvertently or deliberately modified critical kernel code
     or data. See Kernel patch protection for x64-based operating systems
    2) A developer attempted to set a normal kernel breakpoint using a kernel
     debugger that was not attached when the system was booted. Normal breakpoints,
     "bp", can only be set if the debugger is attached at boot time. Hardware
     breakpoints, "ba", can be set at any time.
    3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arguments:
    Arg1: a3a01f58953a2743, Reserved
    Arg2: b3b72bdee7b8c1e2, Reserved
    Arg3: fffff8000010c19b, Failure type dependent information
    Arg4: 0000000000000001, Type of corrupted region, can be
     0 : A generic data region
     1 : Modification of a function or .pdata
     2 : A processor IDT
     3 : A processor GDT
     4 : Type 1 process list corruption
     5 : Type 2 process list corruption
     6 : Debug routine modification
     7 : Critical MSR modification
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 50, {fffff80316e7c000, 0, ffffe000004450c9, 0}
    
    Could not read faulting driver name
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+177cc )
    Followup: MachineOwner
    ---------
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff80316e7c000, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: ffffe000004450c9, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 0000000000000000, (reserved)
    ...........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 1E, {ffffffffc000001d, fffff80000aeb012, ffffd0002116e2a8, ffffd0002116dab0}
    *** WARNING: Unable to verify timestamp for EpfwLWF.sys
    *** ERROR: Module load completed but symbols could not be loaded for EpfwLWF.sys
    Probably caused by : EpfwLWF.sys ( EpfwLWF+226a )
    Followup: MachineOwner
    ---------
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: ffffffffc000001d, The exception code that was not handled
    Arg2: fffff80000aeb012, The address that the exception occurred at
    Arg3: ffffd0002116e2a8, Parameter 0 of the exception
    Arg4: ffffd0002116dab0, Parameter 1 of the exception


    Analyse of your BSOD Dumpfiles is based on a Canned Speech by John Carrona .
    Out of 6 memory dumps there were 5 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
    - borked (broken) hardware (several different procedures used to isolate the problem device)
    - BIOS issues (check for updates at the motherboard manufacturer's website)
    - overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
    - compatibility issues (3rd party hardware/drivers)
    - low-level driver problems
    - or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).
      My System SpecsSystem Spec

  3. #3


    Posts : 44
    Windows 8.1 64 Bit


    I haven't over clocked. And you said download ALL of the 50 Drivers for my M5A99FX PRO R2.0?
      My System SpecsSystem Spec

  4. #4


    Posts : 660
    windows 8.1


    Quote Originally Posted by Cire3 View Post
    I haven't over clocked. And you said download ALL of the 50 Drivers for my M5A99FX PRO R2.0?
    No, look if you already have the latest drivers on that site and if not update these drivers. (Audio,LAn,USb,SATA).
      My System SpecsSystem Spec

  5. #5


    Posts : 44
    Windows 8.1 64 Bit


    I'll check. Where do I install these? I go to Device Manager and chose what? ACPI x64 Based PC? Or where? How about the BIOS? I'm new to BIOS. I really appreciate the help so far
      My System SpecsSystem Spec

  6. #6


    Posts : 5,139
    Win8.1Pro - Finally!!!


    I have posted suggestions in this topic that appears to be another one of yours (duplicate):
    Kernel Error 0x8000000000000002 BSOD Event ID 41, task 63

    I'd strongly suggest restricting yourself to one topic so as to not get confusing replies from different helpers.

    Good luck!
      My System SpecsSystem Spec

Kernel Error 0x8000000000000002 BSOD Event ID 41, task 63?
Related Threads
- System
Critical error: event id 41 Kernel-power in BSOD Crashes and Debugging
Hi there, I am concerned about a new build that I received on the 12th of September. I only discovered event logs yesterday and I am alarmed to discover I have had 45 critical errors since the 12th: event id 41 , task category 63, source kernel-power. saying 'The system has...
Hi I bought my laptop about 3 months ago i got BSOD relating event 41 task 63 kernel power many times and got twice BSOD today it really made me frustrated please help
Hi, Yeah i just recently got a new Windows 8 desktop and almost every I literally get a BSOD relating to Kernel error. 0x8000000000000002. My most recent time I just got a BSOD It said KERNEL_SECURITY_FAILURE. This is truly frustrating :mad: - <Event...
"The maximum file size for session "Circular Kernel Context Logger" has been reached. As a result, events might be lost (not logged) to file "C:\Windows\system32\WDI\LogFiles\BootCKCL.etl". The maximum files size is currently set to 104857600 bytes." "Session "Circular Kernel Context Logger"...
I have had three of these shutdowns randomly occur over the last 2 days. I have no warning on when they will occur. The computer is only 5 weeks old, so i wouldn't except an overheat issue personally. I can think of no new software i have installed since this has started. So far, it has always...
I just recently built a computer in December and from the start the PSU made some clicking noises, but I didnt see it as a problem since at first there were no problems with my computer. It would restart after the first 5-10 minutes of playing league of legends. 20-30 minutes are playing Team...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook