3 BSODs in the last six weeks, most recent was 0x00000101

I have had three BSODs in the past six weeks.

First was on October 12, and definitely happened in the process of the normal restart of Windows I do each evening before bed, as I was watching and saw it happen. I don't know the details of the error, as it was somehow not logged.

Second one was sometime between November 24 bedtime and November 25 getting up. Unhandled exception in Managed Code Snap-In (?????) references it. In that post I said that it happened during Windows restart, but I didn't actually see it, so now I'm not sure. And again, somehow it was not logged either.

The most recent one was logged, and I have documented it here (zip file attached). Event 1001, bugcheck 0x00000101.

I'll invite any questions, but for now the noteworthy things I'll mention are that the event viewer said it happened at 3am - five hours after I restarted, 2 1/2 hours after the nightly Avast! AV scan happened. And it would have happened when no user was logged into Windows. That is, from the login screen that appears when the computer is started. Finally, I can't think of any material hardware or software changes or installations I've done in that time.

Thoughts/suggestions?

axe0 said:

Hi 450125,

Please test your hard drive

I appreciate the suggestion, but was it made after analyzing the BSOD information I uploaded?

None of my three hard drives (system C drive less than a year old; mirrored D/F data drives) has ever exhibited any troubling signs, and I have never event-logged a HDD issue or failure, and I'd not want to do a time-consuming test when there's no data suggesting that it's a HDD matter.

In a separate note, the BSOD I am documenting occurred roughly 22 seconds after 3am, which is, I believe, the time that Windows update automatically triggers. Could this have had anything to do with what happened?

Last night the computer went to sleep as it normally does, and there were no problems. I manually downloaded/installed an update during the day, which required a restart of the computer, and none of those things triggered an error.

Greetings axe0. I'm Brian and just shooting in the dark after scanning through the event log, but there were instances of unexpected shut downs indicated in a startup sequence which looks like it coincides with what was logged as BSOD. The time noted in the comment for the startup indicates an unexpected shut down at a time for which there were no events logged. I hope that makes some sense. I observed these things in the log for 2015-11-29 very early in the morning. Similar events prior to that also, but too much to sit here and bang out. Never worked on a BSOD problem before, so feel free to shoot me down if it is just. I am attaching a .doc with suspect problem in RED. Some of the time stamps make no sense at all. I also noted one incident of the clock synch was screwy when communicating with the NIST time server. Just a shot in the dark. If you don't care for me to attempt any of this sort of communication to you just say so, I won't be offended.
Good luck all.

axe0 said:

Hi Brian,

Those event logs are usual, the system always writes those kind of logs when the computer unexpectedly restarts from a crash.
Except for the bugcheck, and in some rare cases the up-time, it is kinda useless.

Axe0, Below is the event where the system time was way out of sync. Just something which has piqued my curiosity. I am going to start watch the threads here, maybe I'll learn something from you. I'll keep my mouth shut while I learn.

Event[25065]:
Log Name: System
Source: Microsoft-Windows-Kernel-General
Date: 2015-08-26T03:36:45.500
Event ID: 1
Task: N/A
Level: Information
Opcode: Info
Keyword: Time
User: N/A
User Name: N/A
Computer: DAVEWIN7
Description:
The system time has changed to ?2015?-?08?-?26T07:36:45.500000000Z from ?2015?-?08?-?26T04:44:26.059331000Z.

axe0 said:

How so is it way out of synch?

Year, month, day, minute, second, millisecond.
A few minutes difference, completely normal with a hard drive :)

3 hours off