Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client >
> 
> 
Can you help me find the cause of event IDs: 41, 6008 and 1001

Unanswered Can you help me find the cause of event IDs: 41, 6008 and 1001

  • Wednesday, October 24, 2012 5:58 PM
     
     
    Sign In to Vote
    0

    Hi everyone and thanks for helping out!

    Today, out of the blue our machine had a BSOD. The Event Viewer lists event IDs 41, 6008 and 1001. The details are listed below. The MEMORY.DMP has been uploaded to a server, but I cannot link to it here because of the security rules of this forum.

    I would really appreciate any help in finding the cause of this issue. Please note that the machine has the newest BIOS, it has passed a 16 hour Memtest 86+  and a 56 hour Prime95 blend test.

    - <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="2012-10-24T11:33:15.247203100Z" /> 
      <EventRecordID>24901</EventRecordID> 
      <Correlation /> 
      <Execution ProcessID="4" ThreadID="8" /> 
      <Channel>System</Channel> 
      <Computer>DR3</Computer> 
      <Security UserID="S-1-5-18" /> 
      </System>
    - <EventData>
      <Data Name="BugcheckCode">59</Data> 
      <Data Name="BugcheckParameter1">0xc0000005</Data> 
      <Data Name="BugcheckParameter2">0xfffff800037762d1</Data> 
      <Data Name="BugcheckParameter3">0xfffff88009e5db30</Data> 
      <Data Name="BugcheckParameter4">0x0</Data> 
      <Data Name="SleepInProgress">false</Data> 
      <Data Name="PowerButtonTimestamp">0</Data> 
      </EventData>
      </Event>

    --

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="EventLog" /> 
      <EventID Qualifiers="32768">6008</EventID> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2012-10-24T11:33:22.000000000Z" /> 
      <EventRecordID>24897</EventRecordID> 
      <Channel>System</Channel> 
      <Computer>DR3</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>13:32:19</Data> 
      <Data>‎24-‎10-‎2012</Data> 
      <Data /> 
      <Data /> 
      <Data>86508</Data> 
      <Data /> 
      <Data /> 
      <Binary>DC070A00030018000D0020001300B201DC070A00030018000B0020001300B201600900003C000000010000006009000000000000B004000001000000F3FFFFFF</Binary> 
      </EventData>
      </Event>

    --

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" /> 
      <EventID Qualifiers="16384">1001</EventID> 
      <Version>0</Version> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Opcode>0</Opcode> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2012-10-24T11:33:23.000000000Z" /> 
      <EventRecordID>24954</EventRecordID> 
      <Correlation /> 
      <Execution ProcessID="0" ThreadID="0" /> 
      <Channel>System</Channel> 
      <Computer>DR3</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data Name="param1">0x0000003b (0x00000000c0000005, 0xfffff800037762d1, 0xfffff88009e5db30, 0x0000000000000000)</Data> 
      <Data Name="param2">C:\Windows\MEMORY.DMP</Data> 
      <Data Name="param3">102412-10327-01</Data> 
      </EventData>
      </Event>


    • Edited by NiemiOn Wednesday, October 24, 2012 5:59 PM
    •  
     

All Replies

  • Friday, October 26, 2012 2:19 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    Regarding the event ID, you may refer to the following Microsoft Knowledge Base article:

    Windows Kernel event ID 41 error in Windows 7 or in Windows Server 2008 R2: "The system has rebooted without cleanly shutting down first".

    http://support.microsoft.com/kb/2028504

    Update the drivers and boot in the safe mode to see if the BSOD will occur again.

    In order to better analyze the issue, we need the minidump files. You can upload the c:\windows\minidump file to skydrive.

    You can also check it by yourself.

    How to read the small memory dump files that Windows creates for debugging

    http://support.microsoft.com/kb/315263/en-u

    Tracy Cai

    TechNet Community Support

     
  • Sunday, October 28, 2012 7:02 PM
     
     
    Sign In to Vote
    0

    Hi Tracey, thank you for helping out,

    Does it have to be the minidump files or can the Kernel memory dump serve the same purpose?


     
  • Tuesday, October 30, 2012 8:34 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    Have you tried my suggestions?

    The minidump file is much smaller than Kernel memory dump which records the smallest set of useful information that may help identify why your computer has stopped unexpectedly. Thus, it is better to upload the minidump files rather than a full one.

    Tracy Cai

    TechNet Community Support

     
  • Thursday, November 08, 2012 3:04 PM
     
     
    Sign In to Vote
    0

    I do not have the minidump files, I only have the Kernel memory dump. I have set it to generate minidumps in the future, but for now, can you help me diggest the kernel dump?

    I have read the article, but it doesn't aid me particularly well in finding the cause.

    As I cannot get it to bluescreen again, I have not updated drivers or tested in fail-safe mode.

     
  • Sunday, November 11, 2012 4:38 PM
     
     
    Sign In to Vote
    0
    Your power supply is failing.

    I just went through the exact issue.

    Replace your PSU.
     
  • Monday, November 12, 2012 2:13 PM
     
     
    Sign In to Vote
    0

    It's a new Corsair AX750, and although there might have been some strain from the CPU, the PSU would have been far from saturated. I'm not sure this is PSU related, it seems to me that it can be caused by a number of things. The day after the computer locked and the screen got completely filled with pink artifacts.

    Now, trying to recreate any of these issues it runs completely stable. But this is a machine which we cannot risk acting like this. 

    It would be really valuable if someone could assist me in interpreting the kernel memory dump which can be found here.

    • Edited by NiemiOn Monday, November 12, 2012 3:59 PM Added link to the memory dump
    •  
     
  • Monday, November 12, 2012 7:48 PM
     
     
    Sign In to Vote
    0

    It turns out I might actually have the minidump file after all.

    http://delivery.kundelink.dk/johan/102412-10327-01.dmp

    Are you able to gather anything from it?

     
  • Wednesday, November 14, 2012 6:47 PM
     
     
    Sign In to Vote
    0

    It turns out I might actually have the minidump file after all.

    http://delivery.kundelink.dk/johan/102412-10327-01.dmp

    Are you able to gather anything from it?

    Tracy? Anyone?

     
  • Monday, November 19, 2012 2:26 PM
     
     
    Sign In to Vote
    0
    How to keep thread from dying?
     
  • Monday, November 26, 2012 8:15 AM
     
     
    Sign In to Vote
    0

    I still could use some help analyzing the dump file.

    http://delivery.kundelink.dk/johan/102412-10327-01.dmp

    Any help would be great!

     
  • Saturday, December 01, 2012 9:55 PM
     
     
    Sign In to Vote
    0
    Not yet resolved
     
  • Wednesday, December 05, 2012 4:39 PM
     
     
    Sign In to Vote
    0
    Any help?
     
  • Wednesday, December 12, 2012 4:45 PM
     
     
    Sign In to Vote
    0
    Up up
     
  • Wednesday, December 12, 2012 5:54 PM
     
     
    Sign In to Vote
    0
    Have you tried replacing the RAM?  Weird seemingly random total failures like this could be indicative of bad RAM.