none
Windows 7 Event ID: 41 Microsoft-Windows-Kernel-Power

    Question

  • I am having critical failures on my Toshiba laptop. Error details below. Can anybody assist?

    I have checked for updated drivers, done virus scan and searched for solutions. But to no avail

    Windows Operating System; Version: 6.1.7600.16385; Event ID: 41; Event Source: Microsoft-Windows-Kernel-Power;

    Log Name:      System

    Source:        Microsoft-Windows-Kernel-Power

    Date:          10/05/2010 3:29:03 PM

    Event ID:      41

    Task Category: (63)

    Level:         Critical

    Keywords:      (2)

    User:          SYSTEM

    Computer:      Toshiba

    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>2</Version>

        <Level>1</Level>

        <Task>63</Task>

        <Opcode>0</Opcode>

        <Keywords>0x8000000000000002</Keywords>

        <TimeCreated SystemTime="2010-05-10T05:29:03.378013800Z" />

        <EventRecordID>44011</EventRecordID>

        <Correlation />

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

        <Channel>System</Channel>

        <Computer>Toshiba</Computer>

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

      </System>

      <EventData>

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

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

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

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

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

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

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

      </EventData>

    </Event>

    Monday, May 10, 2010 6:07 AM

Answers

  • Hi,

     

    If any blue screen of death (BSoD) is encountered, would you please upload the minidump files to the public folder of SkyDrive and provide us the link for further research?

     

    Collect Minidump Files

    =================

    1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”.

    2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery".

    3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected.

    4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”.

     

    If the Blue Screen appears again, please refer to the following steps to collect memory dump files:

     

    1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”.

    2. Go to your Desktop, right-click on it and create a new folder named "Dump".

    3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder.

    4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder".

    5. Please send the ZIP file to us.

     

    You may also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link:

     

    http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx

     

    WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging.

     

    If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Regards,

     

     


    Arthur Li - MSFT
    Tuesday, May 11, 2010 5:51 AM
    Moderator

All replies

  • You got bugcheck 0x19 - BAD_POOL_HEADER - because "The pool freelist is corrupt." This indicates memory corruption is occurring, and could be caused by a bad/incompatible driver, or faulty hardware such as RAM.  

    Are the bugcheck codes always the same? For memory corruption such as this, turn on verifier as described below and upload a dump when you have a bugcheck, after enabling verifier.

    General guidance for dealing with bluescreens follows:

    Consider running chkdsk on all partitions.  Let chkdsk complete on each partition and see if that helps.

    Also consider running SFC /SCANNOW.

    It can be helpful to use Driver Verifier.  To enable Driver Verifier... start->verifier.exe->OK->Create standard settings->Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out of the dialog.

    Then, reboot and use the system as you normally would, and wait for a problem.  In the event that the system does not boot completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes.

    Wait for a bugcheck to occur after enabling verifier as described, and then upload it to you SkyDrive and provide a link.

    If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot?

    Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily good memory - it just hasn't failed a test.  Consider systematically eliminating RAM from the system - run with a couple of modules for a while, and see how things go. Then try the other modules.

    Other common suggestions include ensuring drivers are up to date (including video drivers), as well as ensuring that you're using the latest BIOS.

    • Proposed as answer by No.Compromise Friday, May 14, 2010 10:42 AM
    Monday, May 10, 2010 11:00 AM
  • Hi,

     

    If any blue screen of death (BSoD) is encountered, would you please upload the minidump files to the public folder of SkyDrive and provide us the link for further research?

     

    Collect Minidump Files

    =================

    1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”.

    2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery".

    3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected.

    4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”.

     

    If the Blue Screen appears again, please refer to the following steps to collect memory dump files:

     

    1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”.

    2. Go to your Desktop, right-click on it and create a new folder named "Dump".

    3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder.

    4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder".

    5. Please send the ZIP file to us.

     

    You may also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link:

     

    http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx

     

    WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging.

     

    If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call.

     

    To obtain the phone numbers for specific technology request please take a look at the web site listed below:

     

    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607

     

    Regards,

     

     


    Arthur Li - MSFT
    Tuesday, May 11, 2010 5:51 AM
    Moderator
  • I need some assistance also with this problem.

     

    http://cid-8e5e59da6c6716bd.skydrive.live.com/self.aspx/Se7en%20Dump%20Folder/Dump.zip

    Sunday, May 23, 2010 3:06 PM
  • @wsucoug95 - your problem is different and warrants a new thread.

    Uninstall ZoneAlarm (not just disable - uninstall), and run for several days.  See if that helps.


    In addition, or alternatively, consider disabling NetBIOS over TCP/IP (NBT).

    (You got a double-fault kernel trap, and you have vsdatant.sys on your system. This is a component of ZoneAlarm (and some other) software that has been involved in similar situations (1), (2).)
    Sunday, May 23, 2010 3:30 PM
  • I have had Error ID 41 for sometime. Running ZoneAlarm Extreme on a W7 X64 system. Returned to manufacturer  returned No Fault Found.
    Contacted CentrePoint S/W who suggested stopping NetBIOS on IvP4 to no effect. Seconf suggestion was two hotfixes KB976759 and KB979278.
    The first stated it was not applicable but the second installed successfully.

    I have not suffered the symptom since. Previously it occurred between 10 mins and 10 hours continuous use.

    The symptom is running normally then randomly BSOD followed immediately by the boot option screen (which boot mode, normal, safe, etc).

    Ex computer H/W maintenance & S/W development
    Wednesday, January 05, 2011 6:03 PM