Post by D***@MadCow.net Post by Paul Post by dadiOH Post by philo Post by D***@MadCow.net
After replacing the HD one week ago, it worked fine every day, until
Everything appears normal up to the Login screen. I enter my password
and "Welcome" appears but nothing more happens.
Sometimes it will finish startup, but take much longer.
No error messages appear except on a restart after a lockup, the
basic Windows startup menu appears because of a failed proper
I'm really upset. After all I did, it appears I'm back to square one.
I have no idea what to try now.
Could be a RAM problem or possibly a bad mobo.
Or power supply
The OP has already tested the RAM, which passed.
And if it is a power supply issue, why does it have
the earmarks of a "failed profile at startup" ? A power
supply failure will cause random failures at different
times of the day. Or perhaps consistently, when the
system has "power peaks". I've seen power peaks at
BIOS level (because the power management isn't very good
there), and if the PSU is pooping out, it could die
just as easily at BIOS level, before the desktop appears.
If, during shutdown, the system is actually doing "unclean"
shutdowns, that could be damaging some registry related
stuff. If you had "Automatically Reboot" set, your system
probably wouldn't shut down for you. It would reboot.
If the Automatically Reboot on a failure wasn't set, the
system could crash during shutdown, not write the registry
properly, and just... stop. Sometimes you get log entries
for things like that (Event Viewer), but not if it was a BSOD.
It might crash before having time to make a log entry.
Now, that's a lot of supposition on my part, but it's the
most likely thing to be messing up the profile (without
it being a disk issue, and the disk has been replaced).
When it comes to "BSOD Spectrum", if you look at a large
number of BSODS on your system, you'll notice a fingerprint.
For example, say the NVidia driver is really crap, then
there will be a ton of BSODS with "nvxx" in the name for
you to look at. If, on the other hand, the power supply
is bad, you'll be getting obscure errors nobody has
ever heard of. Ones you might have trouble finding in
the Aumha STOP list. At the moment, the OPs symptoms
seem to be pretty focused, but we don't have an overview
of Event Viewer to see anything else that might be
interesting. Or a view of any minidumps.
(Pictures for dramatic effect...)
You made me think about a corrupted User Profile.
Followed the steps and created a new user as administrator, like my
original user account.
I thought if a new account wasn't corrupted, it would start properly.
Today I ran some tests and was disappointed.
Didn't matter which user I tried logging on as. The symptoms of not
getting beyond the "Welcome" screen and the disk activity light being
mostly steady for a few minutes occurred.
Sometimes it would finish starting and seem to work ok. But even
then, a normal automated Log off, Shutdown and Restart, might or might
not go smoothly.
Tomorrow I'll read the pages you linked to see if I can
understand/learn anything else to try.
Still having the problem and it's still a crap shoot every time to see
if it will complete successfully or if I have to shut off power and
The only suspicious Event that happens at every startup (if successful
or not) is this one for ATC.SYS not loading. It's a file installed by
BitDefender AV Free.
Here's the full content of the Event Viewer Details:
Log Name: System
Source: Service Control Manager
Date: 4/2/2018 1:57:13 PM
Event ID: 7026
Task Category: None
The following boot-start or system-start driver(s) failed to load:
<Provider Name="Service Control Manager"
Control Manager" />
<TimeCreated SystemTime="2018-04-02T18:57:13.063476500Z" />
<Execution ProcessID="876" ThreadID="880" />
I found this:
where someone was having a similar problem and Kate Li (MSFT CSG)
suggested removing the file to see if that solved it.
I was able to copy it to another drive for safe keeping, but I can't
remove or rename it. I receive a msg saying I need permission from
the administrators to do so. I am an administrator but that's not
At first the atc.sys properties said TrustedInstaller was in control
and I couldn't find a way to edit/change that. But now after several
attempts the TrustedInstaller entry is gone and it says SYSTEM is in
control, but it still won't let me mess with it.
I also tried to rename or delete it via Command Prompt (run as
Administrator) and as another user I created earlier (also an
administrator), but no go.
Next to try will be to learn how to use process monitor to capture the
statup process, but that will take a while.
Note that when startup does complete successfully and the desktop
appears, etc., everything seems to work fine for as long as I want to
use it. But then a restart, with normal appearing logoff, shutdown
and restart may or may not be a successful startup.