Windows 7 PC crashes / stops upon reboot
I have an Hewlett Packard (fairly basic) Windows 7 PC, that crashed (no blue screen, the screen simply went black with no response from any peripherals) and then once the machine is powered off and back on again it crashes or stops upon a reboot (black screen again).
The crash is simply just a freeze on a black screen, no errors, nothing obvious, it simply just sits there doing nothing whilst powered on.
If we button off the machine it will load Hewlett Packard's version of the recovery prompt, allowing us to run "System Restore" or "System Recovery". So far I have run "System Restore" about 3 times from different dates (progressively getting earlier), which will recover the system to any of the set dates successfully.
Once back into the system I have full use as normal of the machine in Windows 7, but upon scouring the Windows Event Log the only error we can see around the time of the crash is:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log Name: System
Source: Kernel-Power
Event ID: 41
Level: Critical
User: System
OpCode: Info
Logged: 11/04/2013 08:45:21
Task Category: (63)
Keywords: (2)
Computer: Home-PC
It seems that this error is hard to trouble shoot due to the vague nature of what could have caused the computer to fail in such a way. The is no BugcheckCode (it is "0").
What I'm concerned about is that I've run System Restore a few times, the computer has got back into a functioning state, but invariable it will crash again, requiring another System Restore. If I decide to run a full factory recovery on the machine, I'm wondering what the major differences are with this over a System Restore option. I realise the disk will be formatted and recovered from image, however if the machine still ends up crashing after a System Restore, is there any point in going through this process?
Could a failing hard disk be the cause? Or if it was, would we see some more specific errors in the Event Log? Can anyone recommend any software that might be able to scan the machines hardware to check if this issue might be hardware related? Note: The Event Log shows NO other errors prior to the Critical Event ID 41 - i.e. nothing obvious to say "Hey, I'm struggling a bit here with something and might give up any second now..."
Appreciate any advice.
windows-7 crash system-restore event-log
asked Apr 11 '13 at 8:38
HarryHarry
10112
add a comment |
I have an Hewlett Packard (fairly basic) Windows 7 PC, that crashed (no blue screen, the screen simply went black with no response from any peripherals) and then once the machine is powered off and back on again it crashes or stops upon a reboot (black screen again).
The crash is simply just a freeze on a black screen, no errors, nothing obvious, it simply just sits there doing nothing whilst powered on.
If we button off the machine it will load Hewlett Packard's version of the recovery prompt, allowing us to run "System Restore" or "System Recovery". So far I have run "System Restore" about 3 times from different dates (progressively getting earlier), which will recover the system to any of the set dates successfully.
Once back into the system I have full use as normal of the machine in Windows 7, but upon scouring the Windows Event Log the only error we can see around the time of the crash is:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log Name: System
Source: Kernel-Power
Event ID: 41
Level: Critical
User: System
OpCode: Info
Logged: 11/04/2013 08:45:21
Task Category: (63)
Keywords: (2)
Computer: Home-PC
It seems that this error is hard to trouble shoot due to the vague nature of what could have caused the computer to fail in such a way. The is no BugcheckCode (it is "0").
What I'm concerned about is that I've run System Restore a few times, the computer has got back into a functioning state, but invariable it will crash again, requiring another System Restore. If I decide to run a full factory recovery on the machine, I'm wondering what the major differences are with this over a System Restore option. I realise the disk will be formatted and recovered from image, however if the machine still ends up crashing after a System Restore, is there any point in going through this process?
Could a failing hard disk be the cause? Or if it was, would we see some more specific errors in the Event Log? Can anyone recommend any software that might be able to scan the machines hardware to check if this issue might be hardware related? Note: The Event Log shows NO other errors prior to the Critical Event ID 41 - i.e. nothing obvious to say "Hey, I'm struggling a bit here with something and might give up any second now..."
Appreciate any advice.
windows-7 crash system-restore event-log
asked Apr 11 '13 at 8:38
HarryHarry
10112
This sounds like a hard hardware failure. I would check the S.M.A.R.T data on the hdd. I would also check to validate your memory is failing.
– Ramhound
Apr 11 '13 at 11:33
Thanks Ramhound, I've had a look and found HD Tune as a util to scan the disk, and when I get physically in front of the machine I'll run a memory diagnostic from the BIOS as well. Thanks again!
– Harry
Apr 11 '13 at 11:59
add a comment |
I have an Hewlett Packard (fairly basic) Windows 7 PC, that crashed (no blue screen, the screen simply went black with no response from any peripherals) and then once the machine is powered off and back on again it crashes or stops upon a reboot (black screen again).
The crash is simply just a freeze on a black screen, no errors, nothing obvious, it simply just sits there doing nothing whilst powered on.
If we button off the machine it will load Hewlett Packard's version of the recovery prompt, allowing us to run "System Restore" or "System Recovery". So far I have run "System Restore" about 3 times from different dates (progressively getting earlier), which will recover the system to any of the set dates successfully.
Once back into the system I have full use as normal of the machine in Windows 7, but upon scouring the Windows Event Log the only error we can see around the time of the crash is:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log Name: System
Source: Kernel-Power
Event ID: 41
Level: Critical
User: System
OpCode: Info
Logged: 11/04/2013 08:45:21
Task Category: (63)
Keywords: (2)
Computer: Home-PC
It seems that this error is hard to trouble shoot due to the vague nature of what could have caused the computer to fail in such a way. The is no BugcheckCode (it is "0").
What I'm concerned about is that I've run System Restore a few times, the computer has got back into a functioning state, but invariable it will crash again, requiring another System Restore. If I decide to run a full factory recovery on the machine, I'm wondering what the major differences are with this over a System Restore option. I realise the disk will be formatted and recovered from image, however if the machine still ends up crashing after a System Restore, is there any point in going through this process?
Could a failing hard disk be the cause? Or if it was, would we see some more specific errors in the Event Log? Can anyone recommend any software that might be able to scan the machines hardware to check if this issue might be hardware related? Note: The Event Log shows NO other errors prior to the Critical Event ID 41 - i.e. nothing obvious to say "Hey, I'm struggling a bit here with something and might give up any second now..."
Appreciate any advice.
windows-7 crash system-restore event-log
asked Apr 11 '13 at 8:38
HarryHarry
10112
I have an Hewlett Packard (fairly basic) Windows 7 PC, that crashed (no blue screen, the screen simply went black with no response from any peripherals) and then once the machine is powered off and back on again it crashes or stops upon a reboot (black screen again).
The crash is simply just a freeze on a black screen, no errors, nothing obvious, it simply just sits there doing nothing whilst powered on.
If we button off the machine it will load Hewlett Packard's version of the recovery prompt, allowing us to run "System Restore" or "System Recovery". So far I have run "System Restore" about 3 times from different dates (progressively getting earlier), which will recover the system to any of the set dates successfully.
Once back into the system I have full use as normal of the machine in Windows 7, but upon scouring the Windows Event Log the only error we can see around the time of the crash is:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log Name: System
Source: Kernel-Power
Event ID: 41
Level: Critical
User: System
OpCode: Info
Logged: 11/04/2013 08:45:21
Task Category: (63)
Keywords: (2)
Computer: Home-PC
It seems that this error is hard to trouble shoot due to the vague nature of what could have caused the computer to fail in such a way. The is no BugcheckCode (it is "0").
What I'm concerned about is that I've run System Restore a few times, the computer has got back into a functioning state, but invariable it will crash again, requiring another System Restore. If I decide to run a full factory recovery on the machine, I'm wondering what the major differences are with this over a System Restore option. I realise the disk will be formatted and recovered from image, however if the machine still ends up crashing after a System Restore, is there any point in going through this process?
Could a failing hard disk be the cause? Or if it was, would we see some more specific errors in the Event Log? Can anyone recommend any software that might be able to scan the machines hardware to check if this issue might be hardware related? Note: The Event Log shows NO other errors prior to the Critical Event ID 41 - i.e. nothing obvious to say "Hey, I'm struggling a bit here with something and might give up any second now..."
Appreciate any advice.
windows-7 crash system-restore event-log
windows-7 crash system-restore event-log
asked Apr 11 '13 at 8:38
HarryHarry
10112
asked Apr 11 '13 at 8:38
HarryHarry
10112
asked Apr 11 '13 at 8:38
HarryHarry
10112
asked Apr 11 '13 at 8:38
HarryHarry
10112
asked Apr 11 '13 at 8:38
HarryHarry
10112
10112
This sounds like a hard hardware failure. I would check the S.M.A.R.T data on the hdd. I would also check to validate your memory is failing.
– Ramhound
Apr 11 '13 at 11:33
Thanks Ramhound, I've had a look and found HD Tune as a util to scan the disk, and when I get physically in front of the machine I'll run a memory diagnostic from the BIOS as well. Thanks again!
– Harry
Apr 11 '13 at 11:59
add a comment |
This sounds like a hard hardware failure. I would check the S.M.A.R.T data on the hdd. I would also check to validate your memory is failing.
– Ramhound
Apr 11 '13 at 11:33
Thanks Ramhound, I've had a look and found HD Tune as a util to scan the disk, and when I get physically in front of the machine I'll run a memory diagnostic from the BIOS as well. Thanks again!
– Harry
Apr 11 '13 at 11:59
This sounds like a hard hardware failure. I would check the S.M.A.R.T data on the hdd. I would also check to validate your memory is failing.
– Ramhound
Apr 11 '13 at 11:33
This sounds like a hard hardware failure. I would check the S.M.A.R.T data on the hdd. I would also check to validate your memory is failing.
– Ramhound
Apr 11 '13 at 11:33
Thanks Ramhound, I've had a look and found HD Tune as a util to scan the disk, and when I get physically in front of the machine I'll run a memory diagnostic from the BIOS as well. Thanks again!
– Harry
Apr 11 '13 at 11:59
Thanks Ramhound, I've had a look and found HD Tune as a util to scan the disk, and when I get physically in front of the machine I'll run a memory diagnostic from the BIOS as well. Thanks again!
– Harry
Apr 11 '13 at 11:59
add a comment |
1 Answer
1
active
oldest
votes
Check the 5 steps posted here under scenario 3:
Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first"
http://support.microsoft.com/kb/2028504
answered Apr 11 '13 at 17:48
magicandre1981magicandre1981
82.3k20126204
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%2f581288%2fwindows-7-pc-crashes-stops-upon-reboot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Check the 5 steps posted here under scenario 3:
Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first"
http://support.microsoft.com/kb/2028504
answered Apr 11 '13 at 17:48
magicandre1981magicandre1981
82.3k20126204
add a comment |
Check the 5 steps posted here under scenario 3:
Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first"
http://support.microsoft.com/kb/2028504
answered Apr 11 '13 at 17:48
magicandre1981magicandre1981
82.3k20126204
add a comment |
Check the 5 steps posted here under scenario 3:
Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first"
http://support.microsoft.com/kb/2028504
answered Apr 11 '13 at 17:48
magicandre1981magicandre1981
82.3k20126204
Check the 5 steps posted here under scenario 3:
Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first"
http://support.microsoft.com/kb/2028504
answered Apr 11 '13 at 17:48
magicandre1981magicandre1981
82.3k20126204
answered Apr 11 '13 at 17:48
magicandre1981magicandre1981
82.3k20126204
answered Apr 11 '13 at 17:48
magicandre1981magicandre1981
82.3k20126204
answered Apr 11 '13 at 17:48
magicandre1981magicandre1981
82.3k20126204
82.3k20126204
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%2f581288%2fwindows-7-pc-crashes-stops-upon-reboot%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
This sounds like a hard hardware failure. I would check the S.M.A.R.T data on the hdd. I would also check to validate your memory is failing.
– Ramhound
Apr 11 '13 at 11:33
Thanks Ramhound, I've had a look and found HD Tune as a util to scan the disk, and when I get physically in front of the machine I'll run a memory diagnostic from the BIOS as well. Thanks again!
– Harry
Apr 11 '13 at 11:59