If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
Win 7 / 64 /Pro....Won't reboot after system changes
My Win 7/64/Pro although 6 years old works great...as long as it is booted up and running. Howvwer, when there is a system change meaning an update, an install of a new program or an uninstall the computer just stalls at the "Starting Windows" emblem. I've gone through the hoops using the repair the computer option, startup repair etc. But the only way to get it to boot up in normal mode is to do a system restore through Safe Mode. Of course, this means no updates, programs or uninstalls. What could be causing this? Does this mean the system is fried? And would running the Win 7 ISO file over the existing Windows 7 (SP1) bwe worth the time? Thanks for any help |
#2
|
|||
|
|||
Win 7 / 64 /Pro....Won't reboot after system changes
OREALLY wrote:
My Win 7/64/Pro although 6 years old works great...as long as it is booted up and running. Howvwer, when there is a system change meaning an update, an install of a new program or an uninstall the computer just stalls at the "Starting Windows" emblem. I've gone through the hoops using the repair the computer option, startup repair etc. But the only way to get it to boot up in normal mode is to do a system restore through Safe Mode. Of course, this means no updates, programs or uninstalls. What could be causing this? Does this mean the system is fried? And would running the Win 7 ISO file over the existing Windows 7 (SP1) bwe worth the time? Thanks for any help Well, No GUI Boot doesn't seem to help. It replaces the "balls" animation with a black screen. There is no text hiding underneath. This article shows how to add some additional text, with no guarantee it'll show everything. https://www.howtogeek.com/howto/3247...rtup-problems/ And while you can enable "Boot Logging" to a text file, you still need a way to read it. You might need to boot to Safe Mode (if that would work), or use another OS to read the boot log. And generally, it's the code module *after* the last line in the file that is stuck. It is not the last line in the file, as that one was "successful". So for the most part, the boot log only helps if you can compare the last working bootup boot log, against the failing boot log. Being able to view Event Viewer from another OS would be nice, but I don't know of a way to do that. The Sysinternals Process Monitor has an option to trace bootup, and it collects ETW trace events for later. But if you have to kill the current OS boot process, there is no guarantee the file it collects, would be usable. There are many dead ends for this stuff, unfortunately... It's Rocket Scientist material. You'd have to be very lucky to trace it down by Safe Booting, and noting some difference. So all I can suggest, is turn on that extra decorative text and see if you get more hints. Paul |
#3
|
|||
|
|||
Win 7 / 64 /Pro....Won't reboot after system changes
En el artículo , Paul
escribió: So all I can suggest, is turn on that extra decorative text and see if you get more hints. An sfc /scannow might be worth doing. -- (\_/) (='.'=) systemd: the Linux version of Windows 10 (")_(") |
#4
|
|||
|
|||
Win 7 / 64 /Pro....Won't reboot after system changes
On Sun, 12 Mar 2017 21:33:12 -0700, "OREALLY" wrote:
My Win 7/64/Pro although 6 years old works great...as long as it is booted up and running. Then it's not fried. Howvwer, when there is a system change meaning an update, an install of a new program or an uninstall the computer just stalls at the "Starting Windows" emblem. I had a system like that last year, but it depends on *exactly* where it's stalling. In my case, I had a bad RAM module that I just happened to find by accident. After I removed the bad stick, the system worked normally. I'm absolutely not saying your PC has a memory issue, but it's one of the things you could check, using Memtest86+. You could also boot from a Linux live CD, just to see how it goes. I don't expect you to actually do anything after Linux boots. I'm just saying see if it boots. The idea is to try to isolate the issue to hardware versus software. I'd also suggest checking the Event Viewer, but that can be daunting if you aren't already familiar with it. -- Char Jackson |
Thread Tools | |
Display Modes | Rate This Thread |
|
|