Free tools Windows power users keep installed
One-click scans. No signup required.
A server that keeps restarting is showing a symptom, not revealing its cause. First identify whether the failure happens before the operating system loads, during Windows startup or an update, while a repair is running, or after the server becomes operational. Record the exact error and protect data before attempting disk repairs. The guidance below focuses on Windows Server; the right recovery steps depend on the server’s Windows version, hardware, storage configuration, and failure evidence.
What to record before trying another repair
Capture the failure as it happens, before changing settings or rerunning a repair. A useful incident record lets you distinguish an operating-system problem from a failed update, driver, power issue, or storage fault.
- Failure stage: firmware or POST, Windows startup, an update or repair operation, or after sign-in and normal operation begin.
- Exact message: copy the stop code, error text, inaccessible boot device message, or repair failure details. Note the last visible screen if there is no message.
- Timing: record timestamps, how often the server restarts, and whether each restart occurs at the same point. Note whether the restart appears automatic or is initiated by a user or process.
- Recent changes: list hardware, driver, BIOS or firmware, Windows update, application, and service changes made before the first failure.
- System context: record Windows Server edition and version, server make and model, storage controller and firmware, RAID or other storage configuration, and backup status.
- Evidence to preserve: keep the System and Application event logs and any available memory dump. If storage is involved, retain relevant storage, file-system, and hardware diagnostic logs.
Ask for these details before choosing an invasive fix. A procedure suitable for one Windows release, server model, or storage subsystem may be unsuitable for another.
How to tell what kind of restart loop it is
Use the boot stage and event timeline together. Event IDs are clues, not standalone diagnoses; check the event source and surrounding entries because an ID is not unique across all providers.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors#1 Best Overall
- 【Powerful Load-bearing】12U Network Rack Open Frame is constructed from durable cold rolled steel; Rack shelf supports enhance stability, wall-mounted capacity of 130lbs, the ground-mounted up to 260lbs
- 【Considerate Designs】Open-frame layout, including a top panel adding space, anti-slip shelf stops fixing devices and compatible racks for stack and expansion to meet requirements of home server rack
- 【Complete Accessories】A 12U open frame server rack, two ventilated shelves, four shelf stops, four velcro straps and a set of equipment mounting screws
- 【Versatile Application】Ideal for space-efficient multi-device setups in warehouses, retail, classrooms, offices and more; Excellent choices as AV Rack/IT Rack
- 【Effortless Setup】 Network Rack includes hardware, a comprehensive manual, mounting hole drilling template and an online assembly video to simplify setup
| Evidence | What it can indicate | What to investigate next |
|---|---|---|
| Failure before Windows starts | Firmware, hardware, boot configuration, or power may be involved. | Record the screen or firmware error and review recent hardware, firmware, and power changes. Use diagnostics and support guidance for the server model. |
| Stop error during Windows startup | Microsoft lists incompatible hardware or drivers, outdated BIOS or firmware, software conflicts, memory problems, and corrupted system files among common Windows Server stop-error causes. | Record the exact stop code and preserve any dump. Correlate the failure with recent drivers, updates, services, hardware changes, and system events. |
| Restart follows an update or repair attempt | The timing may point to a pending or failed update, but does not by itself prove that the update is the cause. | Record which update or repair ran and when. For Windows update-related boot failures, use the applicable Windows Recovery Environment (WinRE) guidance for the affected release. |
| Storage or file-system events accompany the restart | Timeouts, device or controller faults, storage-network problems, or file-system corruption may be involved. | Inspect storage events and hardware status. Confirm backups before repair operations that write to a volume or may take it offline. |
| Restart occurs after Windows becomes operational | A process-initiated restart, unexpected shutdown, power loss, crash, or hang are among the possibilities. | Correlate restart and shutdown history with application, driver, hardware, and power changes; do not infer a cause from a single event. |
Correlating Windows restart events
For a Windows Server timeline, Microsoft’s unexpected-restart guidance identifies Kernel-General and EventLog history entries, as well as these commonly relevant IDs:
- 12 and 13: useful when reconstructing system startup and shutdown history.
- 6005 and 6009: EventLog startup-related history entries.
- 1074: can indicate a shutdown or restart initiated by a process or user. Check the event details to identify the reported initiator.
- 41 and 6008: associated with an unexpected shutdown. Event 41 can follow a hang, crash, or loss of power; by itself, it does not establish which occurred.
Compare timestamps with the last successful boot, the first failure, and any update, driver, service, or hardware change. Microsoft’s event-ID guidance is for Windows Server troubleshooting; it is not a cross-platform diagnosis.
Rank #2
- ADJUSTABLE DEPTH: 4-Post 42U open frame server rack with 4 vertical rails and adjustable mounting depth 22" to 40" (56,0cm to 101,7cm); Compatible with various servers / switches / data / AV and other IT equipment; EIA/ECA-310-E Compliant
- EASY ASSEMBLY: Mobile network rack with easy-to-follow assembly instructions and online video; Compact flat-pack shipping to avoid damage and facilitate installation; Total product height of 80.3in (204 cm) with casters, 78in (198cm) without casters
- COLD ROLLED STEEL: Durable 4 Post 19in open frame rack designed for ventilation with 42U mounting height and 1320lb (600kg) weight capacity (stationary); 3 install options included: casters, levelling feet, or base-plate to secure rack to the floor
- HARDWARE INCLUDED: Rolling computer/data rack includes cage nuts and screws to mount equipment, easy to read Units (U) and depth adjustment markings, cable management hooks for organization, and required assembly tools
- THE IT PRO'S CHOICE: Designed and built for IT Professionals, this 42U rack is backed for 2-years, including free lifetime 24/5 multi-lingual technical assistance
What to check before choosing a recovery path
Recent changes and basic system conditions
Review changes made immediately before the first failure: new hardware, drivers, BIOS or firmware, Windows updates, applications, and services. If the failure began after a specific driver or service change, investigate that component and its vendor’s instructions rather than applying a generic repair sequence.
Microsoft’s Windows Server stop-error checklist recommends keeping 10–15% of disk space free in its troubleshooting context and notes that the actual space requirement varies. Treat this as Microsoft’s recommendation for that context, not a universal capacity target for every server workload. The same guidance recommends checking for current Windows updates and firmware, testing relevant memory or hardware, and investigating software installed shortly before the failure.
Rank #3
- Adjustable Depth: 23-40'' adjustable depth is used for servers and network equipment, ensuring enough space for AV equipment, components, and cabling, while allowing you to access ports and equipment from multiple sides.
- Strong Load Capacity: Ground-Mounted Load Capacity: 500 lbs, Wall-Mounted Load Capacity: 150 lbs. The av rack is made of carbon steel for better weldability performance and can help save space while meeting your need to place multiple devices.
- User-friendly Design: Ergonomic design makes the open frame av rack easier to use. The additional top panel is able to place other items with more available space. Roller design moves anywhere and anytime, is convenient, and is more energy-saving.
- Complete Accessories: We provide the accessories you need, including 2 x Pallets, 145 x M5*10 Cross Head Screws, 4 x Casters, 4 x M10*50 Expansion Screws,10 x M6*12 Cage Nuts, 1 x Grounding Wire, 1 x User Manual.
- Wide Application: The server rack wall mount maximizes the use of available space, suitable for retail venues, classrooms, offices, and other places where space is limited.
Update-related startup failures
If the server began failing during startup after an update, use Microsoft’s WinRE guidance for the relevant Windows release to inspect and address pending packages or roll back an update when the documented conditions apply. These are symptom- and version-dependent recovery steps, not a reason to edit the registry by following a generic restart-loop recipe. Record the update and recovery actions taken so the next administrator does not repeat an unsuccessful change.
Driver, firmware, power, or hardware clues
When the timeline points to a driver, firmware, power, or hardware problem, consult the server maker’s diagnostic and support documentation for the exact model. Check recent hardware and firmware changes and site power conditions. Intel’s restart guidance is narrower: it was last reviewed on 2021-12-13 and specifies Intel server products running Windows Server 2016 or Windows Server 2012 R2. Do not assume its steps apply to other vendors, models, or Windows versions.
Rank #4
- Universal 19” Rack Mount Compatibility – Perfect for pro audio, video, IT, and network gear. Compatible with mixers, routers, patch panels, servers, power amps, and more.
- Heavy-Duty Load Capacity – Built to support up to 550 lbs. Ideal for studio gear, DJ setups, server equipment, and AV components that demand serious stability.
- Robust Steel Frame & Design – Made with 1.5mm thick steel and weighs 36 lbs for maximum durability, reduced vibration, and long-term reliability in any setting.
- Mobile & Secure – Preinstalled with 3” industrial-grade caster wheels (lockable), making it easy to move and position your rack exactly where you need it.
- All-In-One Setup Kit Included – Comes with 34 rack screws (5mm & 6mm), a 1U blank spacer, and an assembly tool—ready for fast installation out of the box.
How to investigate storage without risking more data
Storage-related restart or repair failures need a cautious path. Before running a repair that writes to disk or requires exclusive access, verify that a usable backup exists and plan for possible downtime. Some checks or repairs can take a volume offline.
Read storage events before changing settings
Microsoft’s Windows Server disk-corruption guidance identifies Event ID 129 as a Storport timeout and Event ID 153 as a miniport request timeout. Possible causes include an unresponsive LUN, storage overload, controller capacity or configuration limits, unstable storage networking, and hardware faults. Events 55 and 98 can indicate file-system corruption.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Best Value
- Adjustable Depth: Depth adjustable from 23" to 40", this open frame server rack accommodates servers and network equipment while providing ample space for A/V gears and cable management. Enjoy easy access to ports and devices from multiple angles.
- High Weight Capacity: Supports up to 300 lbs on the floor (200 lbs when adjusted to maximum depth) and 200 lbs when wall-mounted (depth cannot be adjusted in wall-mounted mode). Made from carbon steel for superior welding performance and durability, this open frame rack is designed to save space while accommodating multiple devices.
- User-Friendly Design: Designed with your convenience in mind, this open frame server rack features an top shelf for extra storage and improved space utilization. The rolling casters let you move it effortlessly wherever you need it, making setup and movement a breeze.
- Widely Applicable: Maximize your space with this adaptable open frame server rack, designed to make the most of every inch. Ideal for retail spots, classrooms, offices, and any area where space is at a premium, it delivers practical solutions for your storage needs.
- Everything You Need: Our open-frame rack comes with fully equipped accessory kit for easy setup and secure installation: 2 x Trays, 4 x Casters, 1 x set of Screws, 16 x M6*12 Cage Nuts, 1 x Grounding Wire, 1 x Internal & External Hex Wrenches, and 1 x User Manual.
Review the event text and timestamps alongside controller status, storage-driver and firmware versions, storage performance, and recent changes. Start with scan-mode checks when appropriate to the affected Windows subsystem. Do not change disk-timeout registry values without direction from the storage vendor; a timeout adjustment does not establish or repair the underlying fault.
ReFS repair or mount failures
If a ReFS volume repeatedly fails to mount or repair, Microsoft’s ReFS guidance recommends verifying backups first and collecting System, Application, storage, and ReFS logs together with hardware or SMART data. Review salvage logs when available. Microsoft describes refsutil salvage as an attempt to recover data to a destination on a second disk; it is not a guarantee of recovery.
If salvage fails, preserve the logs, check the storage hardware, use available backups, and escalate to the storage or Microsoft support channel appropriate to the system. Avoid treating repeated repair attempts as harmless when the data is not protected.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose the next step by evidence, risk, and reversibility
| Failure path | Useful evidence | Safer next step | Main caution |
|---|---|---|---|
| Firmware or POST | Last screen, hardware or firmware changes, server-model diagnostics, site power conditions | Use the server maker’s model-specific diagnostic and support procedure. | Windows recovery steps cannot resolve a confirmed pre-boot hardware or power fault. |
| Windows stop error during boot | Stop code, dump file, event timeline, recent driver or service changes | Investigate the implicated component and the Windows release’s applicable recovery guidance. | A stop error has multiple possible causes; do not assume every loop is corrupted system files. |
| Update-related boot failure | Update identity and timing, boot stage, WinRE findings | Follow the applicable Microsoft update-recovery procedure for that symptom and release. | Do not generalize a targeted rollback procedure into registry edits for unrelated failures. |
| Storage or file-system fault | Events 129, 153, 55, or 98; controller and firmware details; backup and hardware status | Begin with appropriate scan-mode checks and involve the storage vendor when controller, network, or hardware faults are plausible. | Confirm backup and plan a maintenance window before offline or write-repair work. |
| Unexpected restart after boot | Correlated event timestamps, Event 1074 details, power and crash evidence | Determine whether a process initiated the restart or whether the shutdown was unexpected, then investigate the matching path. | Event 41 alone cannot distinguish a hang, crash, or power loss. |
What to send to support
Escalate with a concise evidence package rather than a list of guesses. For Microsoft, hardware, or storage support, include:
- Windows Server edition and version, volume version where relevant, and server make and model.
- Storage controller, driver, and firmware versions; RAID or other storage configuration; and recent hardware or firmware changes.
- The exact stop code, error text, relevant event details and timestamps, and the stage at which the restart occurs.
- Recent changes to updates, drivers, applications, services, hardware, or power conditions.
- Relevant System, Application, storage, and file-system logs; available dump files; performance or storage status; SMART data; and hardware diagnostic results.
- Backup status and the recovery or repair actions already attempted, including whether a step wrote to disk or took a volume offline.
Follow the current procedure for the affected Windows subsystem and server model. The cited Microsoft pages are Windows Server-focused; individual boot steps can vary by release, and the Intel article applies only to the older versions and Intel products it names. The available guidance does not establish a Linux-wide restart-loop procedure, so Linux recovery commands should be selected from documentation for the actual distribution, version, hardware, and storage stack.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
