Windows Server 2008 R2 restarts every hour
Since a few days our server is starting every hour.
Shows critical error 41
Here ist the log:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Ke
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2011-03-29T13:
<EventRecordID>109313</Eve
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>ICRSRV2.icrnet.l
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">0</Dat
<Data Name="BugcheckParameter1">
<Data Name="BugcheckParameter2">
<Data Name="BugcheckParameter3">
<Data Name="BugcheckParameter4">
<Data Name="SleepInProgress">fal
<Data Name="PowerButtonTimestamp
</EventData>
</Event>
Shows critical error 41
Here ist the log:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Ke
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2011-03-29T13:
<EventRecordID>109313</Eve
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>ICRSRV2.icrnet.l
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">0</Dat
<Data Name="BugcheckParameter1">
<Data Name="BugcheckParameter2">
<Data Name="BugcheckParameter3">
<Data Name="BugcheckParameter4">
<Data Name="SleepInProgress">fal
<Data Name="PowerButtonTimestamp
</EventData>
</Event>
uescomp
Is the server bluescreening? Check to see if there are any dump files and you can read them using whocrashed, by chance do you have sql on the server. I know sql chews up free resources and if you have a bad ram module once sql start grabbing resources and gets to a certain level it could be crashing when sql goes through a bad block in the ram.
ASKER
No, it's just restarting.
No SQL Server on the machine, only Exchange 2010.
RAM Modules we have changed, already.
No SQL Server on the machine, only Exchange 2010.
RAM Modules we have changed, already.
Hi oidualc61,
This scenario usually indicates a problem with the hardware. Another possibility is that a driver may cause this problem. To help isolate the problem, check the following items:
1. Overclocking: Disable overclocking and see whether the issue happens when the system is run at the correct speed.
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.
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.
4. Overheating: Check whether the system is overheating by examining the internal temperature of the hardware.
5. Defaults: Use system defaults, and run the system.
If none of the above helps, usually it is a bad CPU or other hardware, I would suggest you contact your computer vendor to diagnose the CPU and motherboard. You may also consider replacing the computer, if this is a recent purchase.
Todar
This scenario usually indicates a problem with the hardware. Another possibility is that a driver may cause this problem. To help isolate the problem, check the following items:
1. Overclocking: Disable overclocking and see whether the issue happens when the system is run at the correct speed.
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.
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.
4. Overheating: Check whether the system is overheating by examining the internal temperature of the hardware.
5. Defaults: Use system defaults, and run the system.
If none of the above helps, usually it is a bad CPU or other hardware, I would suggest you contact your computer vendor to diagnose the CPU and motherboard. You may also consider replacing the computer, if this is a recent purchase.
Todar
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Todar,
Thank you for your comment:
Overlocking is not the case, memory is checked and OK.
We isolated the machine on a separate power supply this afternoon at 4 PM since then, it looks ok.
We will see in the next ours what is happening.
Thank you for your comment:
Overlocking is not the case, memory is checked and OK.
We isolated the machine on a separate power supply this afternoon at 4 PM since then, it looks ok.
We will see in the next ours what is happening.
