• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Kernel Power 41 error

Joined
Jan 2, 2009
Messages
9,899 (1.66/day)
Location
Essex, England
System Name My pc
Processor Ryzen 5 3600
Motherboard Asus Rog b450-f
Cooling Cooler master 120mm aio
Memory 16gb ddr4 3200mhz
Video Card(s) MSI Ventus 3x 3070
Storage 2tb intel nvme and 2tb generic ssd
Display(s) Generic dell 1080p overclocked to 75hz
Case Phanteks enthoo
Power Supply 650w of borderline fire hazard
Mouse Some wierd Chinese vertical mouse
Keyboard Generic mechanical keyboard
Software Windows ten
Hi there I built a basic server for a friend about 6 months ago but now he gets instant resets every 7 hours or so with that message.

Any clues as to what is up?

My friend has tried disabling audio drivers already.
 
Last edited:
Windows Kernel event ID 41 error is generated when the system does not shutdown properly.

More info on this, here>Windows Kernel event ID 41 error in Windows 7 or in Windows Server 2008 R2: “The system has rebooted without cleanly shutting down first”
Quote from page at MS:
An event 41 is used to report that something unexpected happened that prevents Windows from shutting down correctly. Therefore, there may not always be enough information to explicitly define what happened. To determine what may have happened and to identify a potential resolution, it is important to know what the computer was doing at the time just before the event occurred.

If event 41 is logged because power to the computer was interrupted, you may want to consider obtaining an uninterruptible power supply (UPS) such as a battery backup power supply. Maybe an underpowered or failing power supply caused this behavior. For example, if you added RAM or additional devices or hard disks when this problem began, the power supply may be a cause of the problem.

This error can be caused by various problems:
Drivers - Audio, Video, etc.
Hardware
even a windows update

There have been some fixes to address some issues:
An update rollup package for the Hyper-V role in Windows Server 2008 R2: August 24, 2010
Stop error message on a Windows Vista or Windows Server 2008-based computer that has multiple processors installed: "STOP: 0x00000101 CLOCK_WATCHDOG_TIMEOUT"
Stop error message on a Windows Server 2008 R2-based computer that has the Hyper-V role installed and that uses one or more Intel CPUs that are code-named Nehalem: "0x00000101 - CLOCK_WATCHDOG_TIMEOUT"

However, without more info, it would be just a guess at the cause or causes.
:)
 


Thanks for the info, originally the crash happened whilst running 2 Killingfloor game servers
how ever it now just does it even when the system is idle.



I'm thinking PSU myself since It's cheap 450w but I don't want the guy to buy a new psu just yet incase it's something more.

Windows has been reinstalled recently too.
 
Could be the PSU or overheating check the temps. If it's a server I would check the logs may be useful :)
 
I found something to do with sound drivers, the guy solved the error. Don't know if it helps but it might give you a clue.

http://www.techsupportforum.com/forums/f299/solved-kernel-power-41-63-error-434613.html

Said in first post he's already tried that : ] :toast:

Could be the PSU or overheating check the temps. If it's a server I would check the logs may be useful :)

I don't have access to the server at the moment as the owner is in a town over.
 
I don't have access to the server at the moment as the owner is in a town over.

Then I can't help much if you don't have access to the server, because I think this is a symptom of (in order what I consider more likely):

  • Bad PSU as stated before
  • A component is overheating.
  • Bad mains power
  • finally bad RAM, hard disk (unlikely) or motherboard.

It would be useful the specs of the server and when you or your friend would have access to it, the temps or voltages. .
 
Then I can't help much if you don't have access to the server, because I think this is a symptom of:

  • Bad mains power
  • Bad PSU as stated before
  • A component is overheating.
  • finally bad RAM or motherboard

It would be useful the specs of the server.



Just finding out full specs now. ( will a DXdiag txt file help you out?)

I'll be popping round later to see what I can see as well, he reaches 75 under load which whilst within spec is pretty high, might be causing other components to fizz out ( mosfets)

Going to replace a broken fan and give them a 120mm tower heatsink : ]
 
Just finding out full specs now. ( will a DXdiag txt file help you out?)

I'll be popping round later to see what I can see as well, he reaches 75 under load which whilst within spec is pretty high, might be causing other components to fizz out ( mosfets)

Going to replace a broken fan and give them a 120mm tower heatsink : ]

Yeah, with a Dxdiag report would be sufficient to know most of the hardware :)
 

Perfect :toast:. summarizing:

CPU: Intel Xeon X3220 2.40GHz
Motherboard: A Gigabyte GA-G41MT-D3
Video card: IGP Intel G41 Express Chipset with 128 MB.
RAM: 4 GB DDR3, 3 Available (for being a 32 bit OS maybe.
Sound card: Disabled (Realtek ALC888B).

That CPU (according to Intel) has a Tcase temp of 62.2°C, but I don't know what is Tcase :confused:


EDIT: BTW I saw you are using a Xeon CPU but in the motherboard CPU support list doesn't mention Xeon as supported. Maybe is that the root of the problem? or that Dxdiag didn't detected correctly the CPU/motherboard :confused:
 
Last edited:
x3220 is just a q6600 with some bonus features. So shares the same compatibility as that cpu.
 
x3220 is just a q6600 with some bonus features. So shares the same compatibility as that cpu.

And has more TDP 105 vs 95 W, I don't know if this has something to do. The MB list doesn't mention any 105W CPU I don't know if could cause issues.

Anyway I would check the temps, specially if the Tcase is the max core temp (62.2), and you reported 75.
 
And has more TDP 105 vs 95 W, I don't know if this has something to do. The MB list doesn't mention any 105W CPU I don't know if could cause issues.

Anyway I would check the temps, specially if the Tcase is the max core temp (62.2), and you reported 75.

Will be going round with a Coolermaster gemini and some new case fans soon : ] :toast:
 
Will be going round with a Coolermaster gemini and some new case fans soon : ] :toast:

perfect, specially if at first you get the crashes at full load and now even on idle, the fan or thermal paste may be degraded/faulty :)
 
Back
Top