Find time of Windows unexpected shutdown
I'm trying to find any clues towards time when Windows session was ended unexpectedly. Not only due to BSOD, but due to other reasons, like power outage, etc.
There is event 41 in event log, which allows me to determine that Windows session was ended unexpectedly, but event is recorded when Windows starts up, and does not contain any relevant information about shutdown time (so, I cannot tell, if it was 5 minutes since crash or 10 hours).
So far, the only clue I have is Reliablity registry values, such as LastAliveStamp, but apparently it doesn't work for my target Windows version, which is Windows 10.
I've also tried to check time of last event before event 12 (which is Windows boot event), but events are not periodic, so there are occurances, when there might be hour or so between two events, and this is way too inaccurate.
So, are there any more or less accurate and persistent ways to determine time when Windows session was ended unexpectedly?
windows-10 shutdown
asked Jan 22 at 12:41
lentinantlentinant
1013
add a comment |
I'm trying to find any clues towards time when Windows session was ended unexpectedly. Not only due to BSOD, but due to other reasons, like power outage, etc.
There is event 41 in event log, which allows me to determine that Windows session was ended unexpectedly, but event is recorded when Windows starts up, and does not contain any relevant information about shutdown time (so, I cannot tell, if it was 5 minutes since crash or 10 hours).
So far, the only clue I have is Reliablity registry values, such as LastAliveStamp, but apparently it doesn't work for my target Windows version, which is Windows 10.
I've also tried to check time of last event before event 12 (which is Windows boot event), but events are not periodic, so there are occurances, when there might be hour or so between two events, and this is way too inaccurate.
So, are there any more or less accurate and persistent ways to determine time when Windows session was ended unexpectedly?
windows-10 shutdown
asked Jan 22 at 12:41
lentinantlentinant
1013
eventviewer - View Shutdown Event Tracker logs under Windows Server 2008 R2 - Server Fault
– DavidPostill♦
Jan 22 at 13:06
Ticket mentions event 1076, which seems to be not applicable for Windows 10, and event 6008, which I've already investigated - it is even less accurate than "last event before 12" approach. For system crashed on 2:51 pm, last event before 12 was on 2:36 pm, yet event 6008 reported shutdown time on 2:18 pm. As you can see, first method was 15 minutes off, second - 33 minutes off.
– lentinant
Jan 22 at 13:32
add a comment |
I'm trying to find any clues towards time when Windows session was ended unexpectedly. Not only due to BSOD, but due to other reasons, like power outage, etc.
There is event 41 in event log, which allows me to determine that Windows session was ended unexpectedly, but event is recorded when Windows starts up, and does not contain any relevant information about shutdown time (so, I cannot tell, if it was 5 minutes since crash or 10 hours).
So far, the only clue I have is Reliablity registry values, such as LastAliveStamp, but apparently it doesn't work for my target Windows version, which is Windows 10.
I've also tried to check time of last event before event 12 (which is Windows boot event), but events are not periodic, so there are occurances, when there might be hour or so between two events, and this is way too inaccurate.
So, are there any more or less accurate and persistent ways to determine time when Windows session was ended unexpectedly?
windows-10 shutdown
asked Jan 22 at 12:41
lentinantlentinant
1013
I'm trying to find any clues towards time when Windows session was ended unexpectedly. Not only due to BSOD, but due to other reasons, like power outage, etc.
There is event 41 in event log, which allows me to determine that Windows session was ended unexpectedly, but event is recorded when Windows starts up, and does not contain any relevant information about shutdown time (so, I cannot tell, if it was 5 minutes since crash or 10 hours).
So far, the only clue I have is Reliablity registry values, such as LastAliveStamp, but apparently it doesn't work for my target Windows version, which is Windows 10.
I've also tried to check time of last event before event 12 (which is Windows boot event), but events are not periodic, so there are occurances, when there might be hour or so between two events, and this is way too inaccurate.
So, are there any more or less accurate and persistent ways to determine time when Windows session was ended unexpectedly?
windows-10 shutdown
windows-10 shutdown
asked Jan 22 at 12:41
lentinantlentinant
1013
asked Jan 22 at 12:41
lentinantlentinant
1013
asked Jan 22 at 12:41
lentinantlentinant
1013
asked Jan 22 at 12:41
lentinantlentinant
1013
asked Jan 22 at 12:41
lentinantlentinant
1013
1013
eventviewer - View Shutdown Event Tracker logs under Windows Server 2008 R2 - Server Fault
– DavidPostill♦
Jan 22 at 13:06
Ticket mentions event 1076, which seems to be not applicable for Windows 10, and event 6008, which I've already investigated - it is even less accurate than "last event before 12" approach. For system crashed on 2:51 pm, last event before 12 was on 2:36 pm, yet event 6008 reported shutdown time on 2:18 pm. As you can see, first method was 15 minutes off, second - 33 minutes off.
– lentinant
Jan 22 at 13:32
add a comment |
eventviewer - View Shutdown Event Tracker logs under Windows Server 2008 R2 - Server Fault
– DavidPostill♦
Jan 22 at 13:06
Ticket mentions event 1076, which seems to be not applicable for Windows 10, and event 6008, which I've already investigated - it is even less accurate than "last event before 12" approach. For system crashed on 2:51 pm, last event before 12 was on 2:36 pm, yet event 6008 reported shutdown time on 2:18 pm. As you can see, first method was 15 minutes off, second - 33 minutes off.
– lentinant
Jan 22 at 13:32
eventviewer - View Shutdown Event Tracker logs under Windows Server 2008 R2 - Server Fault
– DavidPostill♦
Jan 22 at 13:06
eventviewer - View Shutdown Event Tracker logs under Windows Server 2008 R2 - Server Fault
– DavidPostill♦
Jan 22 at 13:06
Ticket mentions event 1076, which seems to be not applicable for Windows 10, and event 6008, which I've already investigated - it is even less accurate than "last event before 12" approach. For system crashed on 2:51 pm, last event before 12 was on 2:36 pm, yet event 6008 reported shutdown time on 2:18 pm. As you can see, first method was 15 minutes off, second - 33 minutes off.
– lentinant
Jan 22 at 13:32
Ticket mentions event 1076, which seems to be not applicable for Windows 10, and event 6008, which I've already investigated - it is even less accurate than "last event before 12" approach. For system crashed on 2:51 pm, last event before 12 was on 2:36 pm, yet event 6008 reported shutdown time on 2:18 pm. As you can see, first method was 15 minutes off, second - 33 minutes off.
– lentinant
Jan 22 at 13:32
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1397006%2ffind-time-of-windows-unexpected-shutdown%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1397006%2ffind-time-of-windows-unexpected-shutdown%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
eventviewer - View Shutdown Event Tracker logs under Windows Server 2008 R2 - Server Fault
– DavidPostill♦
Jan 22 at 13:06
Ticket mentions event 1076, which seems to be not applicable for Windows 10, and event 6008, which I've already investigated - it is even less accurate than "last event before 12" approach. For system crashed on 2:51 pm, last event before 12 was on 2:36 pm, yet event 6008 reported shutdown time on 2:18 pm. As you can see, first method was 15 minutes off, second - 33 minutes off.
– lentinant
Jan 22 at 13:32