Server randomly rebooting with no error logs or dumps
Most unexpected server reboots trigger blank Kernel-Power 41 events with zero bugcheck parameters and leave management controller logs completely silent. Because these hard resets generate no minidumps or error entries, troubleshooting hits a dead end until underlying hardware issues like a failing UPS are identified.
Core Friction Pattern
Analysis of 5 peer accounts across online developer and community forums reveals that “Server randomly rebooting with no error logs or dumps” repeatedly surfaces due to edge-case mismatches between standard defaults and real-world environments. Standard troubleshooting frequently falls short, compelling practitioners to develop custom workarounds.
+10 alternative community-tested workarounds cataloged below.
What the numbers show
Counted from the threads quoted below. How we count
- People have been saying this in most months since September 2026.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
Server randomly rebooting with no error logs or dumps
- 1Updating IDRAC and BIOS to the latest versionDid this help you?
- 2Running the server booted from a USB drive or different OSDid this help you?
- 3Connecting power supply legs to separate power sources instead of relying solely on the UPSDid this help you?
- 4performing hard rebootsDid this help you?
- 5holding September patchesDid this help you?
- 6Forcing a reboot by holding the power button.Did this help you?
- 7Capturing USB ETW traces during successful connections to compare behavior.Did this help you?
- 8Opening the device software at startup to see if it prevents the crash.Did this help you?
- 9Checking event viewer logs for specific event IDsDid this help you?
- 10Inspecting hypervisor and backup job statusesDid this help you?
- 11Reviewing update history and scheduled tasksDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“Server hard-resets every 728.4 minutes ±1 min, 12 times running. No bugcheck, no iDRAC SEL entry, timer survives reboots. I'm out of ideas.”source ↗
“Every event is Kernel-Power 41 with BugcheckCode: 0 and all bugcheck parameters 0x0. No BSOD, no minidump, no MEMORY.DMP, ever.”source ↗
“iDRAC SEL — completely silent across all 15 crashes. Not one entry.”source ↗
“Starting early this morning some of our servers have been freezing up completely requiring a hard reboot.”source ↗
“Windows logs dont show anything specific right before the reboot.”source ↗
“I’m troubleshooting one business workstation that intermittently freezes completely when a DS-9100 dictation recorder is connected.”source ↗
“During a failure, mouse/keyboard input stops, Ctrl+Alt+Delete does nothing, and RDP cannot connect. Recovery requires holding the power button.”source ↗
“The System critical/error/warning entries checked around those windows contain no preceding error identifying the cause.”source ↗
“How would you capture the next natural hard hang when keyboard and remote access are unavailable?”source ↗
“Yup I've had servers randomly rebooting and it ended up being the 18 year old ups”source ↗
“if it rebooted for an unknown reason, should I fire up anything offline without finding why? Could be an IOC.”source ↗
Where this came up
People with this problem also raised
Related community dilemmas clustered by discussion consensus
Windows Server 2019 fails to boot after cumulative update
Recent cumulative updates cause Windows Server 2019 domain controllers to crash with a critical service failure and enter a boot loop during startup. Recovering the environment requires using the DISM command-line tool to revert pending actions. Subsequent patches can also break explorer.exe upon login.
Windows Server freezing at the welcome screen
Windows Server 2019 virtual machines randomly stop accepting remote desktop connections and hang indefinitely at the welcome screen or frozen desktop. Even though remote PowerShell commands may still connect, console and RDP logins lock up during the authentication or user settings loading phase. This leaves administrators unable to reach a working desktop session.
How to read system crash logs when you have no idea what you're doing
When you have to handle both end-user support and sysadmin tasks with very little time, figuring out where to start with unfamiliar crash logs feels like guessing. This lack of deep debugging experience makes it difficult to decide whether to spend precious time investigating the issue or just give up and reimage the device.
Why does DNS stop working across the domain after an update?
An update causes DNS to stop working across the entire domain and triggers an "Access Denied" error when trying to open dnsmgmt.msc. This failure prevents proper domain management and causes DNS to repeatedly stop working upon reboot, even though internet connectivity remains functional.
WorldShip crashing and Edge errors after update
Recent updates are causing WorldShip to crash repeatedly during normal tasks like printing labels, while Edge throws errors immediately upon launch. Although users can reopen the applications to work temporarily, they inevitably crash again. This creates a persistent cycle of disruption affecting dozens of PCs across organizations while IT teams search for a fix.
Thermostat showing low voltage and no power
HVAC systems often lose power due to a blown low-voltage fuse on the control board or a tripped float switch in the condensate drain pan. When this safety switch cuts power to prevent flooding, the thermostat loses its connection and displays low voltage errors, leaving the heating or cooling system completely unresponsive.