well.. i underclocked cpu at stock, and i removed secondd hdd and dvd-rom and crash happened again.. 2 times. At second time i had no blank screen, sound crashed too..
According to Event viewer i have this info:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 3/9/2014 5:28:27 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: Home
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="">
<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-03-09T15:28:27.938140000Z" />
<EventRecordID>5892</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Home</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>
I googled and after reading microsoft support site about this event I suppose it is more likely to be a power supply problem..
I am on this scenario:
" Scenario 3: The system randomly restarts and no Stop error BugcheckCode is listed, or the computer is completely unresponsive (hard hang)
Click here to show/hide scenario
The Stop error code and the PowerButtonTimestamp are listed as zero. For example, consider the following scenarios:
The Stop error BugcheckCode value is listed as zero. Circumstances can prevent writing the Stop error BugcheckCode information before the computer restarts or shuts down. In this case, a BugcheckCode value of zero is logged. Also, perhaps no Stop error occurred, and the shutdown resulted from a power loss. For example, on a portable computer, this could mean that the battery is removed or completely drained. Or, on a desktop computer, this could mean that the computer was unplugged, or a power outage occurred.
The PowerButtonTimestamp is listed as zero. Circumstances can prevent writing the PowerButtonTimestamp information before the computer restarts or shuts down. In this case, a value of zero is logged. This can occur if the power button is pressed and held for at least four seconds when Windows has an operation running that prevents writing the event to disk. You might also see this scenario if the computer is “hard-locked” and therefore unresponsive to any input, and the computer has to be powered off. To determine whether the computer is unresponsive, try pressing the CAPS LOCK key to toggle the CAPS light on the keyboard.
To check whether this scenario is occurring, press the CAPS LOCK key on the keyboard. When you do this, if the CAPS LOCK light on the keyboard does not change when you press the CAPS LOCK key, the computer may be completely unresponsive (hard hang).
This scenario usually indicates a problem with the hardware. To help isolate the problem, check the following items:
Overclocking: Disable overclocking to see whether the issue occurs when the system is run at the correct speed.
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.
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 can require more energy than the current power supply can provide consistently.
Overheating: Check whether the system is overheating by examining the internal temperature of the hardware.
Defaults: Reset the system back to the system defaults to see whether the issues occur when the system is running in its default configuration. "
Any info/opinion would be useful , Thanx in advance