start up repair on windows 7

I have see this happen 2 times no on the same un-maned machine. So the pc is compact form factor and runs some home automation. This unit is installed in a box on the wall with ventilation fans to control the temperature and with a small batter pack \ ups. The ups is not a smart unit, meaning that it has no software connectivity. We have used this same device before without any problem, and never seen it wait for manual intervention to go to the next step.

So I guess my first question would be how do I avoid this screen from requiring manual intervention?

Second what do you think would have caused it to end up on this screen? Besides for windows event viewer logs is there others i should be looking at?
snap-095218.png
We_Support_ITAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy LidbetterCommented:
Hi We_Support_IT,

This looks like your machine has gone down and then failed to restart correctly.
Look at the event logs to see if there is an unexpected shutdown, or if it was restarted.
Is this connected to the internet? and does it automatically update?

If there is a driver or memory problem causing a blue screen, I  would look at the minidump file located here C:\Windows\Minidump\Minidump.dmp.

Regards

Guy
JohnBusiness Consultant (Owner)Commented:
If you follow the message and the repair completes normally and the machine then starts and runs normally, it may have been a glitch of some sort (happens). If you get a good restart, run Updates again.
nobusCommented:
i would start testing the disk (that's the usual cause)
i use the UBCD for this :
Hardware diagnostic CD    UBCD

go to the download page, scroll down to the mirror section, and  click on a mirror to start the download
Download the UBCD and make the cd   <<==on a WORKING PC, and boot the problem PC from it
Here 2 links, one to the general site, and a direct link to the download

since the downloaded file is an ISO file, eg ubcd527.iso - so you need to use an ISO burning tool
if you don't have that software, install cdburnerXP : http://cdburnerxp.se/

If you want also the Ram tested - run memtest86+ at least 1 full pass,  - you should have NO errors!
 
For disk Diagnostics run the disk diag for your disk brand (eg seagate diag for seagate drive)  from the HDD section -  long or advanced diag !  (runs at least for30 minutes)

http://www.ultimatebootcd.com/                        ultimate boot cd
http://www.ultimatebootcd.com/download.html             download page

**  you can make a bootable cd - or bootable usb stick

for completeness -here's how i handle disk problems : http://www.experts-exchange.com/Storage/Hard_Drives/A_3000-The-bad-hard-disk-problem.html
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

We_Support_ITAuthor Commented:
-no Minidump dunp file was created
-System log shows kernel power, event id 41, basically an unclean shutdown

The machine did start normally and did not repair anything.

Any why to disable or ignore shutdown issues like this, so that it don't wait for a person to click the button?
JohnBusiness Consultant (Owner)Commented:
People can cause unclean shutdowns in several ways: power goes off, forced shutdown, ignore black screen shutdown warnings.

If all is well, just move on.
We_Support_ITAuthor Commented:
all is up and running but due to the nature of this running a home automation system, it sitting on this screen causes notifying to work and i have to dispatch a tech.  I would i would prefer to have windows just try and load normally.  So that is why i asked how to disable this option requiring this manual intervention. I have only seen this on 2 of the 100+ units we have installed in this environment.
JohnBusiness Consultant (Owner)Commented:
Try running System File Checker. Open cmd.exe with Run as Administrator and run SFC /SCANNOW. Allow to complete, shut down, start up and test.

While you are at it, run Disk Cleanup (Admin Tools) and select most (all) options for cleanup and then run Disk Defrag (Admin Tools) assuming hard drive and not SSD.
We_Support_ITAuthor Commented:
will rin sfc, the drive is an SSD
nobusCommented:
for an SSD - check if you have the latest firmware
We_Support_ITAuthor Commented:
we are on the latest firmware, the scan was still running when i left yesterday.
Guy LidbetterCommented:
I there,

To disable the automatic startup repair run the following command in an Admin CMD window

bcdedit /set {default} bootstatuspolicy ignoreallfailures

Open in new window


This means that if ANY failure occurs, the system will always start back up with a normal windows boot.
Please keep in mind that if you have a driver or memory problem, you will get NO blue screen or any sign that the machine went down or up.

If the Home Automation PC is internet connected, I would suggest that you run a scheduled task that monitors the event logs for failure codes and emails you with any events. This way you get notified of a failing PC  and it will continue to self recover until you can resolve the issue.

Regards

Guy
nobusCommented:
sfc does not take 20 minutes on my SSD system
if it takes longer - look into it
look also in event viewer for errors
We_Support_ITAuthor Commented:
found event id 41 in system log, this just looks like a generic message for not shutting down properly.
nobusCommented:
since it is a SFF model - check if the temperatures do not get too high
install speedfan - to monitor them : http://www.almico.com/speedfan.php

i take it there are no dmp files?
Guy LidbetterCommented:
Hi There,

As its a 41 and there is no minidump, it must have been a power loss issue.

So follow my instructions above (the bcdedit code) to prevent a repair and it will boot back up with no intervention.
I would still suggest monitoring the event logs in some way and have a reporting mechanism to keep you in the loop...

Regards

Guy
Guy LidbetterCommented:
Hi There,

As its a 41 and there is no minidump, it must have been a power loss issue.
This could be supply or safety shutdown by the motherboard in the case of overheating. But I imagine it is more likely a power loss if the fans in the case are historically sufficient to maintain temp.

So follow my instructions above (the bcdedit code) to prevent a repair and it will boot back up with no intervention.
I would still suggest monitoring the event logs in some way and have a reporting mechanism to keep you in the loop...

Regards

Guy
We_Support_ITAuthor Commented:
I am already ignore all failures was already changed as it is part of my standard setup in this environment, I have not seen anything else in the log since. Temp is fine.
Guy LidbetterCommented:
If that's the case it should never have gone to repair....
JohnBusiness Consultant (Owner)Commented:
I am not clear yet from the posts. I know there was a problem. But now is startup normal? or is still looking for manual intervention to start. Sorry if I missed this as I read.
nobusCommented:
it never hurts to run a diagnostic on the drive - so that's what i would do
otherwise, it can be caused by a lot of things (eg updates)
Guy LidbetterCommented:
I'm sorry, just to be clear We_Support_IT, this post is a request on help avoiding the repair screen and possible causes?

So going back and clearing this up:
1. Drive failure: You should get event log errors prior to the failure. But a Scan wont hurt.
2. Dodgy memory: BSOD, so there should be a minidump - no minidump so unlikely.
3. Overheating: Possible as safety is a powercut - no logs and no minidump expected other than event 41.
4. Bad Driver\Update:  BSOD, so there should be a minidump - no minidump so unlikely.
5. Power Loss: Bad PSU? Power loss and UPS didn't kick in? Also possible, consider changing PSU, does UPS report as healthy? Consider testing it thoroughly.

Lastly, stop teh PC from going into repair mode. Code supplied:
bcdedit /set {default} bootstatuspolicy ignoreallfailures

Open in new window

You stated this is already part of the standard build, however you went to repair anyway so run it again, and add this as well:
bcdedit /set {default} recoveryenabled No 

Open in new window


Other than that... with no logs, no minidumps etc... everything else is pure guess work...

Regards

Guy

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
We_Support_ITAuthor Commented:
Sorry I have the image set to a bootstatuspolicy = IgnoreShutdownFailures.

I will test with the setting you recommended above.
nobusCommented:
do you have a minidmp - or not?
nobusCommented:
sorry - i missed it in the posts - getting long
did you run diags?
it can be wise to inspect the motherboard for swollen, or bad caps also
<<>>and clean all the fans
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.