Windows 10 Force Shut Down (Power Off/On), Data Corruption Possible?
Earlier today someone in my house reset the power by flipping the power switches for the entire house on and off really fast. This resulted in my computer forcibly being shutdown. Since then I have restarted/rebooted my computer and everything seems to be just fine. I ran the chkdsk
and sfc /verifyonly
commands on my windows machine after restarting it and both commands indicated that there was nothing wrong with the filesystem, etc...
My computer uses a HDD (not SSD), my worry is that when the power forcibly got cut off some of my data could have been corrupted. Is it possibly that this could have caused some of my files to have been corrupted even if the files weren't opened/being edited at the time of the forcible shut down?
At the time of the shut down I only had Google Chrome open and a few Projects were open in Visual Studios, all projects in Visual Studio were saved before the shut down occurred so I'm hoping no data corruption/data loss occurred there.
Just browsing around my computer I can't seem to notice any missing files/corrupted files, so does that mean it's safe for me to assume that nothing bad happening and/or none of my files were effected by the shut down?
If I look in Event Viewer I can notice an event logged when the shut down occurred:
Event 41, Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
With the following event data
BugcheckCode 0
BugcheckParameter1 0x0
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 0
CsEntryScenarioInstanceId 0
BugcheckInfoFromEFI false
CheckpointStatus 0
windows-10 hard-drive shutdown
add a comment |
Earlier today someone in my house reset the power by flipping the power switches for the entire house on and off really fast. This resulted in my computer forcibly being shutdown. Since then I have restarted/rebooted my computer and everything seems to be just fine. I ran the chkdsk
and sfc /verifyonly
commands on my windows machine after restarting it and both commands indicated that there was nothing wrong with the filesystem, etc...
My computer uses a HDD (not SSD), my worry is that when the power forcibly got cut off some of my data could have been corrupted. Is it possibly that this could have caused some of my files to have been corrupted even if the files weren't opened/being edited at the time of the forcible shut down?
At the time of the shut down I only had Google Chrome open and a few Projects were open in Visual Studios, all projects in Visual Studio were saved before the shut down occurred so I'm hoping no data corruption/data loss occurred there.
Just browsing around my computer I can't seem to notice any missing files/corrupted files, so does that mean it's safe for me to assume that nothing bad happening and/or none of my files were effected by the shut down?
If I look in Event Viewer I can notice an event logged when the shut down occurred:
Event 41, Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
With the following event data
BugcheckCode 0
BugcheckParameter1 0x0
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 0
CsEntryScenarioInstanceId 0
BugcheckInfoFromEFI false
CheckpointStatus 0
windows-10 hard-drive shutdown
If you had any documents open and were editing them, then yes, possible data loss, otherwise no.
– Moab
Feb 20 at 1:50
add a comment |
Earlier today someone in my house reset the power by flipping the power switches for the entire house on and off really fast. This resulted in my computer forcibly being shutdown. Since then I have restarted/rebooted my computer and everything seems to be just fine. I ran the chkdsk
and sfc /verifyonly
commands on my windows machine after restarting it and both commands indicated that there was nothing wrong with the filesystem, etc...
My computer uses a HDD (not SSD), my worry is that when the power forcibly got cut off some of my data could have been corrupted. Is it possibly that this could have caused some of my files to have been corrupted even if the files weren't opened/being edited at the time of the forcible shut down?
At the time of the shut down I only had Google Chrome open and a few Projects were open in Visual Studios, all projects in Visual Studio were saved before the shut down occurred so I'm hoping no data corruption/data loss occurred there.
Just browsing around my computer I can't seem to notice any missing files/corrupted files, so does that mean it's safe for me to assume that nothing bad happening and/or none of my files were effected by the shut down?
If I look in Event Viewer I can notice an event logged when the shut down occurred:
Event 41, Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
With the following event data
BugcheckCode 0
BugcheckParameter1 0x0
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 0
CsEntryScenarioInstanceId 0
BugcheckInfoFromEFI false
CheckpointStatus 0
windows-10 hard-drive shutdown
Earlier today someone in my house reset the power by flipping the power switches for the entire house on and off really fast. This resulted in my computer forcibly being shutdown. Since then I have restarted/rebooted my computer and everything seems to be just fine. I ran the chkdsk
and sfc /verifyonly
commands on my windows machine after restarting it and both commands indicated that there was nothing wrong with the filesystem, etc...
My computer uses a HDD (not SSD), my worry is that when the power forcibly got cut off some of my data could have been corrupted. Is it possibly that this could have caused some of my files to have been corrupted even if the files weren't opened/being edited at the time of the forcible shut down?
At the time of the shut down I only had Google Chrome open and a few Projects were open in Visual Studios, all projects in Visual Studio were saved before the shut down occurred so I'm hoping no data corruption/data loss occurred there.
Just browsing around my computer I can't seem to notice any missing files/corrupted files, so does that mean it's safe for me to assume that nothing bad happening and/or none of my files were effected by the shut down?
If I look in Event Viewer I can notice an event logged when the shut down occurred:
Event 41, Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
With the following event data
BugcheckCode 0
BugcheckParameter1 0x0
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 0
CsEntryScenarioInstanceId 0
BugcheckInfoFromEFI false
CheckpointStatus 0
windows-10 hard-drive shutdown
windows-10 hard-drive shutdown
asked Feb 20 at 1:32
thehaxdevthehaxdev
61
61
If you had any documents open and were editing them, then yes, possible data loss, otherwise no.
– Moab
Feb 20 at 1:50
add a comment |
If you had any documents open and were editing them, then yes, possible data loss, otherwise no.
– Moab
Feb 20 at 1:50
If you had any documents open and were editing them, then yes, possible data loss, otherwise no.
– Moab
Feb 20 at 1:50
If you had any documents open and were editing them, then yes, possible data loss, otherwise no.
– Moab
Feb 20 at 1:50
add a comment |
3 Answers
3
active
oldest
votes
You are very likely fine.
Hard drives are designed so they will NOT randomly write to the media upon a sudden power removal. (They include a tiny bit of energy storage onboard, enough to complete any currently-in-progress write operation, and enough to ensure a "clean" shutdown of the drive electronics.)
Your biggest concern would be the drive's write cache, but as long as you did NOT check the "Turn off Windows write-cache buffer flushing" option in the drive properties, Windows automatically flushed that cache within a few seconds after the last time anything tried to write to it.
By the way, the "event data" of all 0's means there's nothing to see. If the system had rebooted after a bugcheck (BSOD) then the BugcheckCode would NOT be 0, nor would many of the other fields, and you might have a minidump to look at. But that's not the case here.
add a comment |
There is no need to worry, as their is no program in any OS to write anything on sudden power cut, their are only chance that your works are not saved but data corruption is not possible, any if by any chance it occurs you can recover that OS with last checkpoint.
add a comment |
No need to worry, when Operating system would start a task, it will set a flag for it, when it finishes the flag will reset, if in the middle of any operation a failure(including power cut) happens, the operating system will find out in next start up and erase all unwanted writes. the only risk in this situation is that the hdd head shake for high voltage power current to hard disk from the power supply and damage the sector under it, it will probably cause a phenomena called bad-sector that means the only 512kb of that sector will not be accessible anymore, if that sector was in the middle of OS file, it may cause the windows crash with blue screen, and if it was in the middle of a file, that file may be corrupted (either reparable or not), by the way it will appear itself on the start up, just check your important files, its a very rare posiblity.
add a comment |
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%2f1407664%2fwindows-10-force-shut-down-power-off-on-data-corruption-possible%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
You are very likely fine.
Hard drives are designed so they will NOT randomly write to the media upon a sudden power removal. (They include a tiny bit of energy storage onboard, enough to complete any currently-in-progress write operation, and enough to ensure a "clean" shutdown of the drive electronics.)
Your biggest concern would be the drive's write cache, but as long as you did NOT check the "Turn off Windows write-cache buffer flushing" option in the drive properties, Windows automatically flushed that cache within a few seconds after the last time anything tried to write to it.
By the way, the "event data" of all 0's means there's nothing to see. If the system had rebooted after a bugcheck (BSOD) then the BugcheckCode would NOT be 0, nor would many of the other fields, and you might have a minidump to look at. But that's not the case here.
add a comment |
You are very likely fine.
Hard drives are designed so they will NOT randomly write to the media upon a sudden power removal. (They include a tiny bit of energy storage onboard, enough to complete any currently-in-progress write operation, and enough to ensure a "clean" shutdown of the drive electronics.)
Your biggest concern would be the drive's write cache, but as long as you did NOT check the "Turn off Windows write-cache buffer flushing" option in the drive properties, Windows automatically flushed that cache within a few seconds after the last time anything tried to write to it.
By the way, the "event data" of all 0's means there's nothing to see. If the system had rebooted after a bugcheck (BSOD) then the BugcheckCode would NOT be 0, nor would many of the other fields, and you might have a minidump to look at. But that's not the case here.
add a comment |
You are very likely fine.
Hard drives are designed so they will NOT randomly write to the media upon a sudden power removal. (They include a tiny bit of energy storage onboard, enough to complete any currently-in-progress write operation, and enough to ensure a "clean" shutdown of the drive electronics.)
Your biggest concern would be the drive's write cache, but as long as you did NOT check the "Turn off Windows write-cache buffer flushing" option in the drive properties, Windows automatically flushed that cache within a few seconds after the last time anything tried to write to it.
By the way, the "event data" of all 0's means there's nothing to see. If the system had rebooted after a bugcheck (BSOD) then the BugcheckCode would NOT be 0, nor would many of the other fields, and you might have a minidump to look at. But that's not the case here.
You are very likely fine.
Hard drives are designed so they will NOT randomly write to the media upon a sudden power removal. (They include a tiny bit of energy storage onboard, enough to complete any currently-in-progress write operation, and enough to ensure a "clean" shutdown of the drive electronics.)
Your biggest concern would be the drive's write cache, but as long as you did NOT check the "Turn off Windows write-cache buffer flushing" option in the drive properties, Windows automatically flushed that cache within a few seconds after the last time anything tried to write to it.
By the way, the "event data" of all 0's means there's nothing to see. If the system had rebooted after a bugcheck (BSOD) then the BugcheckCode would NOT be 0, nor would many of the other fields, and you might have a minidump to look at. But that's not the case here.
edited Feb 20 at 3:23
answered Feb 20 at 1:48
Jamie HanrahanJamie Hanrahan
18.9k34280
18.9k34280
add a comment |
add a comment |
There is no need to worry, as their is no program in any OS to write anything on sudden power cut, their are only chance that your works are not saved but data corruption is not possible, any if by any chance it occurs you can recover that OS with last checkpoint.
add a comment |
There is no need to worry, as their is no program in any OS to write anything on sudden power cut, their are only chance that your works are not saved but data corruption is not possible, any if by any chance it occurs you can recover that OS with last checkpoint.
add a comment |
There is no need to worry, as their is no program in any OS to write anything on sudden power cut, their are only chance that your works are not saved but data corruption is not possible, any if by any chance it occurs you can recover that OS with last checkpoint.
There is no need to worry, as their is no program in any OS to write anything on sudden power cut, their are only chance that your works are not saved but data corruption is not possible, any if by any chance it occurs you can recover that OS with last checkpoint.
answered Feb 20 at 5:31
Ally SonAlly Son
63
63
add a comment |
add a comment |
No need to worry, when Operating system would start a task, it will set a flag for it, when it finishes the flag will reset, if in the middle of any operation a failure(including power cut) happens, the operating system will find out in next start up and erase all unwanted writes. the only risk in this situation is that the hdd head shake for high voltage power current to hard disk from the power supply and damage the sector under it, it will probably cause a phenomena called bad-sector that means the only 512kb of that sector will not be accessible anymore, if that sector was in the middle of OS file, it may cause the windows crash with blue screen, and if it was in the middle of a file, that file may be corrupted (either reparable or not), by the way it will appear itself on the start up, just check your important files, its a very rare posiblity.
add a comment |
No need to worry, when Operating system would start a task, it will set a flag for it, when it finishes the flag will reset, if in the middle of any operation a failure(including power cut) happens, the operating system will find out in next start up and erase all unwanted writes. the only risk in this situation is that the hdd head shake for high voltage power current to hard disk from the power supply and damage the sector under it, it will probably cause a phenomena called bad-sector that means the only 512kb of that sector will not be accessible anymore, if that sector was in the middle of OS file, it may cause the windows crash with blue screen, and if it was in the middle of a file, that file may be corrupted (either reparable or not), by the way it will appear itself on the start up, just check your important files, its a very rare posiblity.
add a comment |
No need to worry, when Operating system would start a task, it will set a flag for it, when it finishes the flag will reset, if in the middle of any operation a failure(including power cut) happens, the operating system will find out in next start up and erase all unwanted writes. the only risk in this situation is that the hdd head shake for high voltage power current to hard disk from the power supply and damage the sector under it, it will probably cause a phenomena called bad-sector that means the only 512kb of that sector will not be accessible anymore, if that sector was in the middle of OS file, it may cause the windows crash with blue screen, and if it was in the middle of a file, that file may be corrupted (either reparable or not), by the way it will appear itself on the start up, just check your important files, its a very rare posiblity.
No need to worry, when Operating system would start a task, it will set a flag for it, when it finishes the flag will reset, if in the middle of any operation a failure(including power cut) happens, the operating system will find out in next start up and erase all unwanted writes. the only risk in this situation is that the hdd head shake for high voltage power current to hard disk from the power supply and damage the sector under it, it will probably cause a phenomena called bad-sector that means the only 512kb of that sector will not be accessible anymore, if that sector was in the middle of OS file, it may cause the windows crash with blue screen, and if it was in the middle of a file, that file may be corrupted (either reparable or not), by the way it will appear itself on the start up, just check your important files, its a very rare posiblity.
answered Feb 21 at 20:11
AliSafari186AliSafari186
3614
3614
add a comment |
add a comment |
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%2f1407664%2fwindows-10-force-shut-down-power-off-on-data-corruption-possible%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
If you had any documents open and were editing them, then yes, possible data loss, otherwise no.
– Moab
Feb 20 at 1:50