BSOD’d Again! Windows 7, 64-bit

Today’s BSOD on my Windows 7 x64 laptop:

A clock interrupt was not received on the secondary processor within the allocated time interval.

*** STOP: 0x00000101 (0x31, 0x0, 0xFFFFF880009EE180, 0x1)

Actually, it’s been quite a while since I’ve had an actual Blue Screen Of Death (BSOD).  Since I’ve been having random resets, this BSOD may actually be helpful for diagnosis.  My primary development VM (VirtualBox) was installing the beta of Visual Studio 2010 SP1 at the time.  I sure hope the environment is intact enough to do some work!

UPDATE, 1/13/2011:

The clock interrupt BSOD occurred again overnight (~3:15 am).  I left a VBox VM running with software installing, but that completed long  before the BSOD.  I took a quick snapshot with my cell before restarting the M6500.

BSOD – Clock Interrupt screenshot
BSOD – Clock Interrupt

Security Essentials Causes Hard Reset? (WRONG)

I’ve been having intermittent hard resets (no BSOD) over the past few months.  At first I thought it a problem with VirtualBox because it always happens when VBox is running.  I do most of my work in VMs, however, so I began to suspect that it was just coincidental.

Then I thought it may be due to my laptop’s network driver.  Correlation? Sometimes resets would occur during significant network activity – downloading a multi-gig ISO, for example.  Unfortunately, resets also occurred when network activity was all but idle.

Recently I noticed some a nasty serious of events in Event Log which indicate that Microsoft Security Essentials (MSSE) is the culprit.  My laptop reset tonight and, sure enough, the same MSSE event was in the log.

MSSE OOBE - Critical Event

A little research online provides some credibility to MSSE being the culprit.  In particular, skr68’s comments in this post on 5/11/2010 ascribes BSODs with the same Event Log data.

So, after tonight’s reset I confirmed that the “Microsoft Security Essentials OOBE” error was in the Event Log, and then I uninstalled MSSE.  Yup, I’m flying unprotected – forgoing virus protection for now.  The best case scenario is that no more resets occur over the next few weeks.  If that happens, I’ll gladly spend some bucks on non-reseting virus protection