Delete

Status
Not open for further replies.
Sorry to say but Windows is not the platform you want if you want a stable operation. Reboots will be forced by Microsoft (or just by Windows becoming unstable with time) and there's nothing you can do about it.

Of course one reason for crashes might be insufficient power delivery to the compute stick. But I'd start by ditching Windows in this use.
 
Basically I have 2 Intel compute sticks plugged into 2 different TV’s. These run marketing material 24/7 and are only touched by those of us in IT. Ever since we installed them then have rebooted periodically which takes it back to the login. Our customer isn’t happy with that and I’m trying to figure out what could be causing it.

Ive done the typical disable windows updates, but other than that what else could be promoting a reboot? To the best of our knowledge there is no power issues as nothing else seems to be having issues.

Event viewer just shows a lot of “distributedCOM” warnings about the machine-default permission settings do not grant Local Activation permission for the COM server.....

The only errors are AppModel-Runtime and Kernel-EventTracing.

Anything else I can look at to try and pinpoint the reboots?

I'd wager like 90% of digital signage is running windows, so you're not the first person to come across this. Physical security > device security in these cases. You just need to setup your device to auto login under a user with no real access to anything, and have it start your signage software upon login. As long as your CS stick is in a location where someone can't get at it or plug anything into it (Locked box) there isn't too much to worry about. In most cases your device is going to already be logged in anyway, so there's no real difference between just letting the device auto login and not.

As for the reboots you just want to find the actual restart event. Filter the log by one of the event IDs shown from the link below:

https://www.tenforums.com/tutorials/78335-read-shutdown-logs-event-viewer-windows.html

A typical restart event is going to be a 1074, it looks like a 41 and / or 6008 is going to happen if it was an unexpected reboot. You can also just filter for only criticals as you'll have those generated if it wasn't a clean restart. If you don't see criticals there should hopefully be a 1074 event showing what caused the device to restart.
 
Well to be honest it’s nothing major that we’re running for this marketing project. It’s basically a slideshow of pics on a loop.

And I agree that a Windows related system wasn’t the best, but I was told we needed something to be able to remote in to remotely and maintain.
You can do that with linux easily and it will never boot up the stick unless you tell it to.
 
Operating Service pack sounds like it got the 2004 or the 20H2 upgrade applied to it. There are certain updates which cannot be deferred / turned off after so long, so that is probably one of them. But that's something that is only going to happen like once or twice a year, so it's not really the end of the world. The fact that the system is capable of downloading it means the system has access to the internet, so it definitely should be receiving security updates then. The only time I'd say you can get away with not updating it is if the system were stand alone / not connected to the network at all.
 
In the limited experience I have with these sticks I've found that disk utilization (due to have very small storage capacity), overheating, and bad drivers are the culprit. Some of them can also only run 32 bit OS.

I'd start with a clean install.
 
I’ll have to look into that. Can Windows bypass the non password option for the ”user”, open the app along with the files, and make them fullscreen?
What app are you using for the display?
 
Status
Not open for further replies.
Back
Top