Member Avatar for mefredbob

Hello all, I've been trying to figure this one out for a while to no avail.

I have disabled the "Auto-restart."

I've also tried to recreate the problem, to see if it was a specific program or driver, but that also has lead to nothing.

It happens are various times, under various activities (even an idle PC). It restarts, and never gives me a blue screen. When it loads up, it gives the typical "Windows has recovered from a serious error", and I send in the report. Microsoft has given me two suggestions as to the cause of the problem, one was a video card issue and the other was to update my BIOS.

I did all that, and nothing.

I thought, perchance, it was a heating issue, but I stuck in Knoppix, and the system is running fine with no errors at all. That also takes away from a HDD issue, and a power issue.

So, I'm at wit's end. Any suggestions?

  • 2 Contributors
  • 2 Replies
  • 131 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by mefredbob

Dani AI

Generated

A few focused diagnostics that weren’t spelled out in the thread will help anyone who hits the same silent, random-restart symptom that experienced.

Start by capturing Windows-level evidence before changing things. Check Event Viewer (System and Application) for entries around the restart time and look for Event IDs, service or driver names. Make sure Windows is writing crash dumps (small memory dumps in C:\Windows\Minidump) so crashes can be analyzed. If you have dumps, analyze them with WinDbg or a simpler viewer (they’ll often point at a driver or module).

If no clear driver jumps out, isolate hardware and firmware at a higher level. Run a long RAM test (MemTest86+ ideally overnight), and a CPU/GPU stress run (Prime95/OCCT) to expose power/thermal faults that Linux might not trigger the same way. Swap or bench-test the power supply if possible — many unexplained restarts are PSU-related. Do a visual check for bulging/leaking caps on the motherboard and GPU.

Driver and OS integrity checks are next. Use sfc /scannow to verify system files, consider Driver Verifier to stress test suspect drivers (back up first; Verifier can force BSODs so have a recovery plan), and update chipset/storage drivers from the motherboard vendor rather than automatic driver packs. Collect systeminfo and driverquery /v output to show exact versions if asking for help.

What to post when asking for more help: timestamps of recent restarts, corresponding Event Viewer entries, any minidump files, full systeminfo and driverquery outputs, and hardware details (PSU/motherboard/GPU models). Small, reproducible data points make root-cause hunting practical. Finally, avoid quick “registry cleaner” fixes as a first resort and back up before any low-level changes.

Member Avatar for koulvivek

try to scan your boot sector with ur antivirus.

Member Avatar for mefredbob

Ok, I fixed it myself, thanks for the help. :-p </sarcasm>

For anyone else experiencing this problem, here's what I did:

I booted into safe mode because the computer didn't randomly restart whilst in safe mode. From there, I defragged and cleaned my registry. Then I defragged my computer. After that, I scanned my drive for errors. It reported a few and automatically fixed them.

Since then, the compter's yet to reset... Knock on wood, of course.

So, yes. After hours of waiting, and what not, tada.

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.