locked
My PC crashes, goes black with a looping sound? RRS feed

  • Question

  • My pc just crashes, goes black with a looping sound.
    Then i have to restart it by the restart button.
    CAPS LOCK doesn't work when this crash occurs.
    It appears with this error in even viewer:


    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          05-07-2011 09:14:16
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      Layton-PC
    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="2011-07-05T08:14:16.449621000Z" />
        <EventRecordID>67123</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>Layton-PC</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">false</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
    </Event>
    Tuesday, July 5, 2011 10:10 AM

All replies

  • Hello,

    refer to this KB: http://support.microsoft.com/kb/2028504

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    Tuesday, July 5, 2011 10:22 AM
  • I don't see how that helps... as this never happend before....pc running for 1 year....cleaned it out every month....maybe a windows update gone wrong?
    Tuesday, July 5, 2011 11:13 AM
    1. Overclocking: Disable overclocking and see whether the issue happens when the system is run at the correct speed. (How do i disable any overclocking? I have never altered any settings of such kind.)
    2. Check the memory: Verify the memory by using a memory checker. Verify that each memory chip is the same speed and that it is configured correctly in the system. (CHECKED and found no problems.)
    3. Power Supply: Make sure that the power supply has enough wattage to appropriately handle the installed devices. If you added memory, installed a newer processor, installed additional drives, or added external devices, such devices may require more energy than the current power supply can provide consistently. (It's been running for one year...)
    4. Overheating: Check whether the system is overheating by examining the internal temperature of the hardware.(Not sure about this one....when playing a game reches max 55 ºC..Idle is 40ºC
    5. Defaults: Use system defaults, and run the system.(Where do i do this?)

    Tuesday, July 5, 2011 11:23 AM
  • Hi,

     

    If you didn’t set any overclocking setting, it shouldn’t be turned on.

     

    Before moving on troubleshooting, I want to know did you install any new device recently?

     

    I suggest that you may try to run Windows 7 in safe mode and check whether this problem occurs again.

     

    Please understand that unstable power supply may cause this problem. “It's been running for one year”. You cannot guarantee it works fine now, right?  So, if the issue persists, I suggest that you may contact manufacture to check the it.

     

    Also you may collect and compress all files in the path of C:\Windows\MiniDump, upload them via SkyDrive and post link here.

     

    http://explore.live.com/windows-live-skydrive?wa=wsignin1.0

     

     

    Hope that helps


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Monday, July 11, 2011 8:13 AM
    1. Overclocking: Disable overclocking and see whether the issue happens when the system is run at the correct speed. (How do i disable any overclocking? I have never altered any settings of such kind.)
    2. Check the memory: Verify the memory by using a memory checker. Verify that each memory chip is the same speed and that it is configured correctly in the system. (CHECKED and found no problems.)
    3. Power Supply: Make sure that the power supply has enough wattage to appropriately handle the installed devices. If you added memory, installed a newer processor, installed additional drives, or added external devices, such devices may require more energy than the current power supply can provide consistently. (It's been running for one year...)
    4. Overheating: Check whether the system is overheating by examining the internal temperature of the hardware.(Not sure about this one....when playing a game reches max 55 ºC..Idle is 40ºC
    5. Defaults: Use system defaults, and run the system.(Where do i do this?)


    I suggest you to check the temp for the processor, to ensure the temps is within it's appropriate range. By going into cmos setup in bios and verify it under health status or hardware monitor (depending which bios you're using). If it falls within 70-80, then is too high and is a cause for concern.

    Btw how frequent you get the auto shut down after you power up your comp?



    Monday, July 11, 2011 8:33 AM
    Answerer