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

This time thing is interesting to me.

I'm looking at the event log in my work computer, and the time resets are never more than unnoticeable fractions of a second - versus the occasional hours that I see in my home computer event log.

My work computer does not "sleep," and I have my home computer set to sleep after 2 1/2 hours of inactivity. Still, many of the sleep wakeups don't have the massive time adjustments.

Should I try the advice in Can anyone please shed any light on this? relative to stopping and resetting/resyncing the time service?

I have, in the past week, run sfc /scannow and everything was found to be normal.

450125 said:

This time thing is interesting to me.

I'm looking at the event log in my work computer, and the time resets are never more than unnoticeable fractions of a second - versus the occasional hours that I see in my home computer event log.

My work computer does not "sleep," and I have my home computer set to sleep after 2 1/2 hours of inactivity. Still, many of the sleep wakeups don't have the massive time adjustments.

Should I try the advice in Can anyone please shed any light on this? relative to stopping and resetting/resyncing the time service?

I have, in the past week, run sfc /scannow and everything was found to be normal.

450125, I will be watching this from the sideline, as I am not a BSOD expert, in fact I am here to learn at this time. I would not want to complicate things for you and Axe0. He can ask for my opinion, but that is up to him.

Regarding the observations about the system time changing, I took a look at my event log, filtered down to EventID 1, and it appears that every radical system time reset immediately follows a wake-from-sleep condition, and the time differential is the amount of sleep time.

It was just a quick look that I took, but in all likelihood whatever is (or hopefully just happened to be) wrong with the computer, the hours-long readjustments of time aren't a cause or an effect of that.

I took another look at my event log and maybe the following information will be helpful.

The two most-recent BSOD incidents were on 11/24 and 11/29.

Because I restart my computer every night, there are usually consecutive events with IDs 13 (Windows stopping) and 12 (Windows starting), about 20-30 seconds apart.

On 11/24, the 13 (Windows stopping) event happened, but there was no starting event, until the next day when I forced a start from the BSOD. Whatever the cause of the BSOD it was not logged, and obviously would have occurred after the Windows stopping (by my hand). My antivirus scan, which runs after midnight, did not run on the morning of the 25th, more proof that the BSOD happened during the restart.

My computer generally goes to sleep after 2 1/2 hours of inactivity - that's how I have it set. There are some times when this does not happen, and I've never figured out the pattern. Maybe out of 60 "sleep opportunities" in a month, 55 will happen and five won't, to make a guess.

In the past week, the only night the computer did not sleep was overnight 11/28 into the 29th, and that night the BSOD event, with stop code 0x00000101, happened just after 3:00 in the morning, which is the time that Windows updates are pushed to my computer, I believe.

So I'm wondering if this Windows update push somehow triggered the most recent BSOD.

I've been reluctant to try the disk tests axe0 suggested. No good reasons, just laziness and inertia on my part, and the fact that I have three HDDs and the tests are lengthy. I image my C drive each month after Patch Tuesday (once a quarter to an external HDD, and the other two months simply to my internal D drive, which mirrors to the F drive, and the two of them appear synchronized). I have no logged disk errors, and the C imaging has always happened without error or incident.

Hello 450125
I would like to experiment without running diagnostic and cleaner apps for the moment. Axe0 don't kill me!
I don't do many forced shut downs and I don't use Hibernate. I only use sleep mode. I have not had a BSOD since the day I fired up this custom build in September of 2013.
If you are willing, for test purposes only, start putting it to sleep at the times you would usually shut down and don't let it hibernate under any conditions. I have a friend whose machine hated to come out of hibernate. Leave everything else as it is. Sleep shuts down the HDD's but remembers exactly everything that was open and active. I have mine set to wake on USB or Keyboard, but Wake on LAN is disabled to prevent phone home activity from waking it and any other reason the LAN from waking it out of a nap.
That is just a step in a process of elimination for what might events are/might be triggering BSOD's.
Let me know what you think (axe0 that means you too, please).

cyclops said:

Hello 450125
I would like to experiment without running diagnostic and cleaner apps for the moment. Axe0 don't kill me!
I don't do many forced shut downs and I don't use Hibernate. I only use sleep mode. I have not had a BSOD since the day I fired up this custom build in September of 2013.
If you are willing, for test purposes only, start putting it to sleep at the times you would usually shut down and don't let it hibernate under any conditions. I have a friend whose machine hated to come out of hibernate. Leave everything else as it is. Sleep shuts down the HDD's but remembers exactly everything that was open and active. I have mine set to wake on USB or Keyboard, but Wake on LAN is disabled to prevent phone home activity from waking it and any other reason the LAN from waking it out of a nap.
That is just a step in a process of elimination for what might events are/might be triggering BSOD's.
Let me know what you think (axe0 that means you too, please).

Just to make clear, my regular regimen is to restart (using Restart from the Start circle) at the end of each day. The computer then sleeps (?*) after 2 1/2 hours. I wake it in the morning, and while I'm at work it again sleeps (?*) after 2 1/2 hours. Most of the time on weekends, I'm on the computer often enough during the day that it stays awake until I do the evening restart.

I essentially never shut the computer down. Certainly if moving it or opening it up. Sometimes if I'm going to be gone for a long period of time. 99% of the time, it's a nightly restart.

When I say "sleeps (?*)" above I am referring to I am afraid I have never grasped the differences between sleep, hibernation, hybrid sleep. When I'm home I can check (tell me where please) on what I use. When it goes to "sleep (?*)" the power light shuts off on the case, and then no one can (for example) print to the USB printer attached to the computer. To wake it, I click twice on the mouse, or press the power button, and it takes about 10 seconds for the display to return and the computer be functional again.

Hi again.
I am gathering some info for you. Be back shortly. I'd like to make sure I give you the most accurate descriptions of what is what.

Just to make clear, my regular regimen is to restart (using Restart from the Start circle) at the end of each day. The computer then sleeps (?*) after 2 1/2 hours. I wake it in the morning, and while I'm at work it again sleeps (?*) after 2 1/2 hours. Most of the time on weekends, I'm on the computer often enough during the day that it stays awake until I do the evening restart.

I essentially never shut the computer down. Certainly if moving it or opening it up. Sometimes if I'm going to be gone for a long period of time. 99% of the time, it's a nightly restart.

When I say "sleeps (?*)" above I am referring to I am afraid I have never grasped the differences between sleep, hibernation, hybrid sleep. When I'm home I can check (tell me where please) on what I use. When it goes to "sleep (?*)" the power light shuts off on the case, and then no one can (for example) print to the USB printer attached to the computer. To wake it, I click twice on the mouse, or press the power button, and it takes about 10 seconds for the display to return and the computer be functional again.[/QUOTE]


OK Let's see if I put this together in a way that will be easy to follow. Please see the images below, you can right click the image/select view image to enlarge it in a new window and then use the back arrow in your browser to return. Let me know how it goes.

Attachment 377149

Attachment 377150