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