Brysamo

New Member
Joined
Aug 23, 2012
Messages
2
I realize that this issue has been posted several times, but I haven't seen any solutions that have been helpful.

CPU: Core2Quad Q6600 G0
RAM: 4gb DDR2 Corsair Dominator
Mobo: EVGA 780i
PSU: Corsair TX650W
Video Card: EVGA GTX 460 SE

Code:
Log Name:      SystemSource:        Microsoft-Windows-Kernel-Power
Date:          8/23/2012 6:13:38 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      Razgriz
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="2012-08-23T22:13:38.317200000Z" />
    <EventRecordID>46055</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>Razgriz</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>

Other information: I've had all of these components since I built the rig in september 2008 (minus the video card), I've had it overclocked from 2.4 to 3.2 for almost 3 years. I would get this error maybe once every 2 months, but I've been getting it more and more frequently to the point where now I get it once a day.

I downclocked from 3.2 to 3.0 (it can run that stable at stock voltage), ran a slow mem-test, ran prime 95 for over 12 hours where nothing happened, and it still hard hangs. I've got a zalman heat sink which keeps it under 50C even with prime 95 running so i don't believe it's an overheating issue, there's no extra noises or loudness coming out of my case.
 
Solution
The error message you provided indicates a critical system event where the system rebooted without cleanly shutting down first. This type of issue can be caused by various factors such as system crashes, unresponsive behavior, or unexpected power loss. Given the details you shared, here are some troubleshooting steps you can consider: 1. Check Power Supply: The Kernel-Power Event ID 41 error can sometimes be linked to power supply issues. Ensure that your Corsair TX650W PSU is functioning correctly and providing stable power to all components. 2. Inspect Hardware Connections: Make sure all hardware components, including RAM sticks, GPU, and power connections, are properly seated. 3. Update Drivers: Ensure that all your...
The error message you provided indicates a critical system event where the system rebooted without cleanly shutting down first. This type of issue can be caused by various factors such as system crashes, unresponsive behavior, or unexpected power loss. Given the details you shared, here are some troubleshooting steps you can consider: 1. Check Power Supply: The Kernel-Power Event ID 41 error can sometimes be linked to power supply issues. Ensure that your Corsair TX650W PSU is functioning correctly and providing stable power to all components. 2. Inspect Hardware Connections: Make sure all hardware components, including RAM sticks, GPU, and power connections, are properly seated. 3. Update Drivers: Ensure that all your drivers, especially the motherboard and graphics card drivers, are up to date. Outdated drivers can sometimes lead to system instability. 4. Check for Overheating: Even though your CPU temperatures are within a safe range, check the temperatures of other components like the GPU. Overheating components can cause system crashes. 5. Monitor System Resources: Use tools like Task Manager or Resource Monitor to check for any anomalies in system resource usage that could be causing the crashes. 6. Event Viewer: Continuously monitor the Event Viewer for any recurring errors or warnings that might provide more insight into the cause of the reboots apart from Event ID 41. 7. Test Individual Components: Consider testing each component individually (RAM, GPU, etc.) to isolate the problematic hardware. You mentioned running a slow mem-test, but more thorough testing may be necessary. 8. BIOS Update: Ensure your motherboard BIOS is up to date. Sometimes BIOS updates can resolve compatibility issues or bugs causing system instability. 9. Check for Software Issues: Certain software conflicts or malware can also lead to system crashes. Run a full system scan for malware and consider performing a clean boot to check for software conflicts. 10. Reset Overclock: Since you reduced your overclocking settings, monitor the system for stability at the new clock speeds. Overclocking can sometimes lead to system instability, especially over prolonged use. By following these steps, you should be able to narrow down the cause of the frequent reboots and work towards resolving the issue. If the problem persists, further diagnostics or professional assistance may be needed.
 
Solution