1

Background: My computer is running Windows 7 Ultimate 64-bit. The CPU is AMD Phenom II X4 955. The motherboard is ASUS M5A88-M. About a month ago, there was a power outage at my place, and power flickered on and off a few times before coming on for good.

The problem: Since then, my computer has displayed strange intermittent freezing behavior. When I started up after the power outage, there were no freezes for 3 days. It then froze repeatedly over the course of the next week, then didn't freeze for about two weeks, then froze again, then didn't freeze for another few days, and then froze again.

I've noticed these common elements:

  • The freezes almost always occur either soon after booting up, or after leaving the computer idle for a long time (8+ hours). If it boots up and doesn't freeze within the first few minutes, it will work all day with no problems or even sluggishness, and sometimes (as I mentioned above) it will continue to work for days or weeks before freezing again.

  • When a freeze occurs, CPU usage seems to drop to zero. This was surprising to me and makes me think it is not a problem with some software grabbing too many resources.

  • The freeze appears to affect apps one by one when I try to do something. Often the taskbar will freeze, but I can still use alt-tab to switch between apps. Some apps will be unresponsive and can't be switched to, but others will work. Usually if I try to "do something" in a given app (e.g., click a menu, select an item in a list), it will freeze. Eventually all apps freeze this way. I then will often still be able to move windows, but eventually they will leave "trails" as the screen fails to repaint properly.

  • Sometimes if I wait awhile (anywhere from 5 to 30 minutes), the computer will "wake up" and function semi-normally for a few minutes before lapsing back into unresponsiveness.

What I've tried:

I tried these things:

  • I ran SMART diagnostics on the hard drive using SpeedFan and SeaTools. I also ran a "long generic" test using SeaTools. No errors were found and all SMART stats come up OK.

  • I ran the Windows Memory Diagnostic tool and it found no errors. I ran Memtest86 overnight; it made three passes and found no errors.

  • I ran scans with Microsoft Security Essentials as well as MalwareBytes and they found no major threats (just a couple registry tracker entries).

  • I ran SFC /SCANNOW. It reported no system file problems.

  • I booted a Linux live CD and hung around for awhile and experienced no problems, but I'm not sure this means much because the problem is intermittent even on Windows, so it could just be that I lucked out.

  • I noticed an "unknown device" in device manager which I figured out was an ACPI device. I installed drivers for it. I thought maybe some power settings had gotten messed up, so I tried disabling stuff in BIOS and in Windows power management settings (e.g., disabling AMD Cool 'n' Quiet, disabling CPU throttling in Windows, etc.). At times I thought I had fixed it but it would still freeze the next day. (I also blew a bunch of dust off the CPU in case it was overheating.)

I've also poked around in the Windows Event Viewer. During the middle of the night on the nights when it froze (i.e., before I noticed the freeze in the morning), there are sporadic timeout errors for certain Windows services (usually the Windows Error Reporting service). This suggests it is actually freezing sometimes in the night and Windows services are timing out.

These timeout errors are sporadic. It looks like most clumps of such errors are preceded by this event (which is not an error, just an "Information" message):

Microsoft Antimalware Real-time Protection has restarted a feature. It is recommended that you run a full system scan to detect any items that may have been missed while this agent was down.

Feature: On Access

Reason: The filter driver has restarted scanning items and is out of pass through mode.

I'm not sure if this means the problem really lies with something Microsoft Security Essentials is doing, or if it's just the canary in the mine that's the first thing to indicate the freeze is beginning. But if the computer boots up without freezing, I can run MSE scans manually with no problems (and it finds no threats).

I've also been using SpeedFan to log stuff like the CPU temps and voltages, because I wondered if there were any patterns there. I haven't found anything unusual in the readings themselves, but there are sporadic gaps in the logs. I set SpeedFan to log every 3 seconds, but, during the night on those same nights where a freeze occurred, there are many places where log entries have gaps of about 5 minutes. These gaps ONLY appear to occur at these problematic times (i.e., in the middle of the night when it is freezing or going to freeze in the morning). It again suggests it's freezing up in the middle of the night to such an extent that SpeedFan can't continue its logging.

The question:

What is going on? The fact that these problems seemed to begin after a power failure makes me suspect hardware problems, but I don't know what hardware could be causing it. On the other hand, the fact that the crashes always appear to happen at certain times (after long idle or on boot) make me suspicious that it's connected to some software thing like MSE updating itself.

The event viewer timeouts and SpeedFan log gaps all point to a freeze that starts happening after I go to bed and continues intermittently until morning (when I reboot). But I can't find any information about what is actually happening that could be causing the freezes. The only errors I can find in event viewer are just "Timeout error I am frozen" things that don't indicate any actual error condition; they just seem to mean the freeze has already taken place.

The hard disk and memory diagnostics seem to rule out those components. My current hardware guesses are the motherboard, the CPU, or the power supply. Do the problems I described above sound like something that could be caused by those components? Alternatively, are there other software solutions I should try?

4
  • 2
    Possible hard disk failure. Check your hard drives for SMART errors How can I read my hard drive's SMART status in Windows 7?, and What is the easiest method of checking SMART status for your hard drive?. Report back with the results.
    – DavidPostill
    Dec 1, 2016 at 20:54
  • I would go with David and first suspect a hard disk problem. You could also look in Event Viewer and observer the errors and warnings to see if you get anything helpful.
    – DrZoo
    Dec 1, 2016 at 20:58
  • @DavidPostill: I have run Speccy which says SMART is "OK" and shows nothing bad in the SMART readout.
    – BrenBarn
    Dec 1, 2016 at 21:03
  • @DrZoo: As I mentioned in the post, I looked at event viewer but saw nothing unusual. There are a few errors about service timeouts. There are also some "SideBySide" errors but those extend back many months so don't seem to be connected to this problem.
    – BrenBarn
    Dec 2, 2016 at 2:41

2 Answers 2

0

You are using the right attitude. Trying to find a defect long before trying to fix anything. But your best diagnostic tool is Task Manager (press Cntrl-Alt-Del simultaneously). In Processes, displayed are processes consuming CPU time. Other potential bottlenecks are memory usage, page faults, and I/O reads and writes. These can be viewed by clicking on View>Select Columns .

Look for processes that consume resources excessively. Also determine what 'frees' the system by right clicking on the process to terminate it.

Another bottleneck can be dumpreports consuming too much resources because so other process has crashed. Terminating that process to free the system is simply another useful fact - not a solution.

'Task Manager on Steroids' is provided by Microsoft - called Process Explorer. Another option.

1
  • Thanks. I just made some edits to the question with some more info. The problem doesn't appear to be caused by any particular process hogging resources. In fact, when the freezes occur, CPU usage drops to zero. Nothing is grabbing a lot of memory either. This is why I suspect a hardware issue.
    – BrenBarn
    Dec 3, 2016 at 21:35
0

I'm tentatively considering the problem fixed, and wanted to post what seemed to fix it, in case anyone else ever has a similar issue.

Contrary to my initial guesses, it seems the problem was Microsoft Security Essentials. Based on the Event Viewer messages I mentioned, I began to wonder if MSE was causing the lockups. I also got an important clue when I happened to unzip a large file and got a freeze. This made me suspect that it was again MSE freezing as it tried to scan the newly unzipped files ("On Access").

I looked around and found people saying MSE wasn't the greatest antivirus these days anyway, so I removed it (and replaced it with BitDefender). It's now been four weeks with no freezes.

I have my fingers crossed that this really fixed it, but I have some lingering doubt. I'm unable to explain why such a peculiar MSE failure was precipitated by a power outage. It's also puzzling that the error only appeared when MSE did an automated scan; I could run scans manually and encounter no problems. (I even did a full scan of the whole drive without any freezes, so it couldn't have been that it was locking up on one particular corrupted file.). And, of course, the failure mode was very strange for a software problem: it's kind of disturbing if MSE is able to throttle my CPU to zero without appearing to use any significant resources itself.

Anyway, hopefully removing MSE has resolved the issue.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .