A Windows XP help forum. PCbanter

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.

Go Back   Home » PCbanter forum » Microsoft Windows 7 » Windows 7 Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Win 7 / 64 /Pro....Won't reboot after system changes



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old March 13th 17, 05:33 AM posted to alt.windows7.general
OREALLY
external usenet poster
 
Posts: 96
Default 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

Ads
  #2  
Old March 13th 17, 06:45 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default 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  
Old March 13th 17, 07:04 AM posted to alt.windows7.general
Char Jackson
external usenet poster
 
Posts: 10,449
Default 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
  #4  
Old March 13th 17, 08:36 AM posted to alt.windows7.general
Mike Tomlinson
external usenet poster
 
Posts: 654
Default 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
(")_(")
  #5  
Old March 14th 17, 03:13 AM posted to alt.windows7.general
Mike S[_4_]
external usenet poster
 
Posts: 496
Default Win 7 / 64 /Pro....Won't reboot after system changes

On 3/13/2017 5:50 AM, Wolf K wrote:
On 2017-03-13 02:04, Char Jackson wrote:
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.


Another possibility is a firmware update. Example: I have to block a
firmware update on my Surface Pro (W8.1) every time, else the Bluetooth
shuts down.

HTH


I had a friend whose computer acted like that, his DVD drive was dying
and somehow locked up the system badly, but not consistently.

  #6  
Old March 14th 17, 03:18 AM posted to alt.windows7.general
Mike S[_4_]
external usenet poster
 
Posts: 496
Default Win 7 / 64 /Pro....Won't reboot after system changes

On 3/13/2017 1:30 PM, OREALLY wrote:
Looks like the scandisk operation has worked. It only took 5 hours, but
the computer boots up after several installs and uninstalls. Just
wondering where I can view the results of the scan to see what was
causing what?


You might try here

Start - Run - type "eventvwr.msc" (no quotes) - ENTER. Click on
Application and select the most recent winlogon entry.

https://superuser.com/questions/1738...utility-logged

This might be useful if scandisk ran during a boot

https://askleo.com/how_do_i_see_the_...ran_on_b oot/




"Wolf K" wrote in message ...

On 2017-03-13 02:04, Char Jackson wrote:
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.


Another possibility is a firmware update. Example: I have to block a
firmware update on my Surface Pro (W8.1) every time, else the Bluetooth
shuts down.

HTH


  #7  
Old March 14th 17, 11:34 AM posted to alt.windows7.general
J. P. Gilliver (John)[_4_]
external usenet poster
 
Posts: 2,679
Default Win 7 / 64 /Pro....Won't reboot after system changes

In message , Mike S
writes:
[]
I had a friend whose computer acted like that, his DVD drive was dying
and somehow locked up the system badly, but not consistently.

My blind friend's system had an external (USB) HDD which caused erratic
behaviour (not just of the USB, which included the wifi, as you might
expect, but the whole OS - see the thread "sulk mode"). It took us
months to realise that was the cause. (The drive itself was fine, it was
the electronics in the housing that were causing problems. Not
surprising considering how cheap a replacement
housing-including-electronics [I couldn't find just the electronics]
was.)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

.... "Peter and out." ... "Kevin and out." (Link episode)
  #8  
Old March 14th 17, 05:15 PM posted to alt.windows7.general
OREALLY
external usenet poster
 
Posts: 96
Default Win 7 / 64 /Pro....Won't reboot after system changes

I had a similar problem several years ago when XP wouldn't boot because of a
dead external backup hard drive! Figured it out just by trial and error!

"J. P. Gilliver (John)" wrote in message
...

In message , Mike S
writes:
[]
I had a friend whose computer acted like that, his DVD drive was dying and
somehow locked up the system badly, but not consistently.

My blind friend's system had an external (USB) HDD which caused erratic
behaviour (not just of the USB, which included the wifi, as you might
expect, but the whole OS - see the thread "sulk mode"). It took us
months to realise that was the cause. (The drive itself was fine, it was
the electronics in the housing that were causing problems. Not
surprising considering how cheap a replacement
housing-including-electronics [I couldn't find just the electronics]
was.)
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

.... "Peter and out." ... "Kevin and out." (Link episode)

 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 12:29 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.