Page 1 of 1
Urgent: NO Vodeo Signal on AK2 after SleepMode
Posted: Wed Feb 24, 2021 8:06 am
by shurik
Hi!
I got 2 AK2 here. Both have same Problem.
When Monitor goes into Sleepmode, it will NOT come back. Stays black, whatever I am doing.
Over Teamviewer i can reach the machine. tried some drivers from Intel Support, Intel HD 500, newset beta already tried...
what can I do?
Re: Urgent: NO Vodeo Signal on AK2 after SleepMode
Posted: Wed Feb 24, 2021 11:12 am
by shurik
Testing yet - with AK Series Intel Video Drivers from 2016 1 PC seems to wake up
Re: Urgent: NO Vodeo Signal on AK2 after SleepMode
Posted: Wed Feb 24, 2021 5:55 pm
by gblenston
I have the same issue. Looked at AK series drivers and the currently installed video is newer on the machine than in package so I didn't revert it. But it could be a whole mix of things not waking up HDMI.
Re: Urgent: NO Vodeo Signal on AK2 after SleepMode
Posted: Thu Feb 25, 2021 3:47 am
by admin
Hello, this is a bug in the Microsoft system. We are currently looking for a solution. Please be patient. If you urgently need to solve the problem, we recommend that you refresh the home version of the system.
Re: Urgent: NO Vodeo Signal on AK2 after SleepMode
Posted: Tue Mar 02, 2021 5:19 pm
by sparkstan66
I have the same issue with ACEPC AK1 - no other crashes but system will not display video when returning from sleep mode. Device is not asleep but video does not return - system provides no video signal after returning from sleep mode. Blue power light is on during this stage so device is awake but does not trigger the video signal to return. Hitting keyboard (space bar, enter, windows key, etc does not work)
Re: Urgent: NO Vodeo Signal on AK2 after SleepMode
Posted: Thu Mar 04, 2021 9:03 am
by admin
My suggestion for this is to turn off sleep mode.
Re: Urgent: NO Vodeo Signal on AK2 after SleepMode
Posted: Sun Mar 07, 2021 6:58 pm
by AJC
I have had this on several PC's of various makes over the last year or so. Seems to be common with Windows 10. It is usually possible to hibernate as another option. I have never found a good fix. Probably connected to graphics drivers.