I have a Dell Optiplex GX280 that's restarting randomly. I've checked everything I can think to check, and still can't find the cause. The user describes the restart (which, unfortunately, I have yet to be present for) as: "A quick, high whine, and then it turns off." I've tested the mobo, proc, memory, HDD, and power supply. I've checked the fans. I've checked for blown caps. I've reseated all connections. I've even replaced the CMOS battery and PSU with known good/working ones.

I don't think it's going to be anything related to software, since the user has indicated it doesn't seem to shut down on her while she's doing any particular thing. The high-pitched whine she describes should also be a good indicator that I'm looking at a hardware problem, I should think.

My first thought was PSU or possibly fan failure/overheating, but neither appear to be the case. Any ideas?

Any advice at this point will be greatly appreciated.

- Devin

Dani AI

Generated

This thread illustrates a common blind spot: intermittent restarts with a short audible warning often trace back to the power chain (UPS, surge strip, building wiring) rather than an internal component. The checklist below focuses on fast, low-cost checks and on gathering the right data so future troubleshooting isn’t a series of parts swaps.

  • Plug the PC directly into a known-good wall outlet on a different circuit (no strips) and run until the fault either repeats or stays quiet.
  • Bypass or swap the UPS/surge devices; if the system only fails when on a particular UPS outlet, that’s a major clue.
  • Reduce to a minimal configuration (one stick of RAM, onboard video, no external devices) so you’re not chasing marginal peripherals or power spikes.
  • Record the event: use a phone to capture sound and time, and if available use a watt-meter/Kill‑A‑Watt or UPS data logging to catch sags/transfer events.
  • If the problem is intermittent, try a different circuit or known-good UPS to differentiate building wiring vs equipment.

Log and OS pointers: on Windows, look for Kernel‑Power events (Event ID 41) and enable full crash dumps; powercfg -lastwake can show recent wake/stop sources. On Linux, check dmesg and journalctl for ACPI/power messages. UPS vendor software or SNMP logs are often decisive because they show transfer-to-battery and battery-fail events with timestamps you can correlate to OS logs.

Prevention and best practices: exercise UPS batteries regularly, replace them according to the vendor schedule (typical life ~3–5 years), size the UPS for the actual load (VA vs W), and prefer true sine‑wave units for modern active‑PFC PSUs. When asking for help, include UPS model, battery age, exact audible description, and timestamps. Good troubleshooting instincts from and the BIOS suggestion from are useful early steps; ’s methodical exclusion of components is the right approach. Safety note: don’t open or probe mains equipment unless qualified—call an electrician for suspected building wiring faults.

Recommended Answers

All 6 Replies

Have you checked and/or reset the bios? Just a gander, it may be LAN.

Have you checked and/or reset the bios? Just a gander, it may be LAN.

The BIOS was reset when I removed/replaced the CMOS battery, and I made sure to check all settings while resetting the clock. Everything's in good shape, as far as the BIOS is concerned.

Thanks for the reply, and if you have any other ideas, please let me know. I'm still completely stumped.

- Devin

first got to control panel - administration tools - event logs does it give any error codes that could point to a problem.
also if you right click on my computer, select properties - advanced -startup and recovery. if you untick automatically restart the next time it fails you will get a blue screen with error codes these can be checked on the microsoft website for further pointers. once you have got these restsrt your system and set it back to automatic restart.
you may find its as simple as a dodgy driver. if unsure post the err codes and i'll see what i can find out

Thanks for the advice. I'll give both of those a try and see what I come up with. I'll post the results as soon as I have them.

- Devin

Okay. So I checked the error log (there are plenty, but nothing to cause this that I saw), and then went into system properties to uncheck "Automatically Restart" if it needed it. It didn't. As I was sitting pondering how this could be the case when I was not seeing any BSODs after a crash, I was fortunate enough to actually witness the "crash" for myself.

The high-pitched whine the user described to me was actually a single beep. A single beep produced by the UPS as it temporarily lost all power and then came back up. I replaced the UPS, and we've had no more problems.

Thanks for the help and suggestions. In spite of the outcome, I still really appreciate the assistance.

- Devin

The high-pitched whine the user described to me was actually a single beep.

Don't you just love end-users?
Good to hear you tracked it down.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.