NEO Z64-W: HDMI is not working and BIOS not accessible

#1
Dear forum participants,
since last Windows 10 update, HDMI has stopped working (the only way to access and modify something is using TeamViewer or similar remote applications), really I don't know if it could be something physical (HW failure), because I was changing to basic drivers (as recommended in several posts), changing cable and monitors, and there is no signal at all.
So, there is no way to see MINIX on a monitor or TV.

I was also trying to access BIOS (low resolution screen) pressing F11 (wireless USB keyboard, pending with a USB wired one) or pressing (10 sec) bottom reset button (with a clip), while booting, with no chance. Probably is not working due to W10 UEFI integration and the boot sequence must be very precise.

Any recommendation or advice will be welcome. By the way the warranty is finalized.

Thanks in advance for any tip or suggestion.

Belmy
 

ArcticWolf

Trusted Helper
#2
Dear forum participants,
since last Windows 10 update, HDMI has stopped working (the only way to access and modify something is using TeamViewer or similar remote applications), really I don't know if it could be something physical (HW failure), because I was changing to basic drivers (as recommended in several posts), changing cable and monitors, and there is no signal at all.
So, there is no way to see MINIX on a monitor or TV.

I was also trying to access BIOS (low resolution screen) pressing F11 (wireless USB keyboard, pending with a USB wired one) or pressing (10 sec) bottom reset button (with a clip), while booting, with no chance. Probably is not working due to W10 UEFI integration and the boot sequence must be very precise.

Any recommendation or advice will be welcome. By the way the warranty is finalized.

Thanks in advance for any tip or suggestion.

Belmy
If this behaviour began directly after a Win Update or after you've made an attempt to manually alter certain drivers, then unfortunately in all likelihood you have your culprit right there rather than a hardware failure.

If you can still remotely access the device via TeamViewer etc., have you tried rolling back the Win update or use a sys restore point?
 
#3
If this behaviour began directly after a Win Update or after you've made an attempt to manually alter certain drivers, then unfortunately in all likelihood you have your culprit right there rather than a hardware failure.

If you can still remotely access the device via TeamViewer etc., have you tried rolling back the Win update or use a sys restore point?
Thanks a lot for you answer, probably the origin is in the recent (regular) W10 update, I was trying to revert the Intel driver with the basic one without success. In addition, remote control with TeamViewer is not working in a reliable way (I'm trying to fix it or to install another one).

As explained, BIOS can be not accessed, probably because UEFI is now controlled by W10, but, if the reset button is pressed during 10 seconds at boot, something should be seen and is not the case, it is the reason because I thought could be a HW issue with HDMI interface.

I can try rolling back the update or use a restore point, when the remote control is working in a more stable way.
 

ArcticWolf

Trusted Helper
#5
Thanks a lot for you answer, probably the origin is in the recent (regular) W10 update, I was trying to revert the Intel driver with the basic one without success. In addition, remote control with TeamViewer is not working in a reliable way (I'm trying to fix it or to install another one).

As explained, BIOS can be not accessed, probably because UEFI is now controlled by W10, but, if the reset button is pressed during 10 seconds at boot, something should be seen and is not the case, it is the reason because I thought could be a HW issue with HDMI interface.

I can try rolling back the update or use a restore point, when the remote control is working in a more stable way.
I'd also advise backing up any important data/files etc. you have stored on the device just in case if you haven't already Having the remote access should aid you there too.

If you still can't rollback the changes when your remote access has stabilized or found another workaround, you may possibly have to consider a completely fresh install of the most recent official MINIX Win 10 image. (There are also means available to block certain updates as well to stop this happening again, & if you can remember which one it was definitely avoid the Intel driver package you tried in this instance.)
 
#6
I've got a more stable remote access with TW and AnyDesk, so, I can do more testing and debugging (while W10 and remote connection can be kept).

The information in the "Windows Update" settings (after several tries) is:
There were problems installing some updates, but we'll try again later.
2020-07 Cumulative Update for Windows 10 Version 1809 for x86-based Systems (KB4558998) - Error 0x8007065e
You’re currently running a version of Windows that’s nearing the end of service. We recommend you update to the most recent version of Windows 10 to get the latest features and security improvements.
2020-07-29.png
Rolling back (to a previous W10 version) is not possible, as update was done more than 10 days ago.

I could try a "Fresh Start" but the risk is a loss of a working remote access, so, equivalent to have a brick if something is wrong and HDMI is still not working.

With "Windows" key plus "P" should be possible to duplicate or extend virtual monitor to HDMI monitor, but, as HDMI is not detected at all, again this option is not working, in addition, is breaking the remote connection.
 

ArcticWolf

Trusted Helper
#7
I've got a more stable remote access with TW and AnyDesk, so, I can do more testing and debugging (while W10 and remote connection can be kept).

The information in the "Windows Update" settings (after several tries) is:
There were problems installing some updates, but we'll try again later.
2020-07 Cumulative Update for Windows 10 Version 1809 for x86-based Systems (KB4558998) - Error 0x8007065e
You’re currently running a version of Windows that’s nearing the end of service. We recommend you update to the most recent version of Windows 10 to get the latest features and security improvements.
Rolling back (to a previous W10 version) is not possible, as update was done more than 10 days ago.

I could try a "Fresh Start" but the risk is a loss of a working remote access, so, equivalent to have a brick if something is wrong and HDMI is still not working.

With "Windows" key plus "P" should be possible to duplicate or extend virtual monitor to HDMI monitor, but, as HDMI is not detected at all, again this option is not working, in addition, is breaking the remote connection.
OK, see how you go & what you can do :).

If you can at least get that level of access to backup your important files/data then you really have nothing to lose by fresh installing the latest official MINIX Win 10 image if you still can't get anywhere with this.

Your call. Fingers crossed either way :).
 

blue

New member
#8
OK, see how you go & what you can do :).

If you can at least get that level of access to backup your important files/data then you really have nothing to lose by fresh installing the latest official MINIX Win 10 image if you still can't get anywhere with this.

Your call. Fingers crossed either way :).
I have the same issue.. after a Windows 10 update the minix doesnt work with HDMI, only with remote access.
I´m trying reinstalling the latest official MINIX Win 10 image following this guide:

https://theminixforum.com/index.php...w-firmware-installation-instructions-pdf.200/

However, since remote access doesnt work on the BIOS, I just can´t see my screen.

Can anyone help me with a video of this process so I can follow it even without seeing whats on my screen by timing the buttons on the keyboard?
 

ArcticWolf

Trusted Helper
#9
I have the same issue.. after a Windows 10 update the minix doesnt work with HDMI, only with remote access.
I´m trying reinstalling the latest official MINIX Win 10 image following this guide:

https://theminixforum.com/index.php...w-firmware-installation-instructions-pdf.200/

However, since remote access doesnt work on the BIOS, I just can´t see my screen.

Can anyone help me with a video of this process so I can follow it even without seeing whats on my screen by timing the buttons on the keyboard?
So to be clear, you also can't access your BIOS at all by immediately spamming the delete key on power on?

Obviously, the BIOS itself is a pre-boot environment so it shouldn't be affected by Win updates or anything Win does.

Can you not get any boot options to display on power on either to allow you to boot into safe mode? (Which may get your display & syatem functioning enough to allow you to uninstall the latest Intel display driver package.)
 

blue

New member
#10
So to be clear, you also can't access your BIOS at all by immediately spamming the delete key on power on?

Obviously, the BIOS itself is a pre-boot environment so it shouldn't be affected by Win updates or anything Win does.

Can you not get any boot options to display on power on either to allow you to boot into safe mode? (Which may get your display & syatem functioning enough to allow you to uninstall the latest Intel display driver package.)
Hi ArticWolf,

1) Probably I am indeed entering the BIOS (blindfully however), but since I cannot see anything on my TV Screen I can´t tell :(
What I´m sure is that when I press the delete key on power on, remote access with TightVNC doesn´t work anymore (so this might confirm that I´m able to enter the BIOS). After this test, when I force shutdown the minix using the power button and tur it on again, remote access and file server work again.

2) No, I can´t see anything :(

PS: What´s worst, I recently uninstalled the display drivers from device manager when i was connected toTightVNC and now no only only see a black screen on my TV but on TightVNC too... However I know the minix is still working because I can access the file server I set up there from my local network. Do you know any method to reinstall the display/video driver remotely??

minixBlackScreen.JPG

Thank you!
 
Last edited:
Top