virtual display driver does not seem working well with booter process only -- FYI only

H

hhspiny

Member
Use booter process only (i.e. remotly does not run in user's account) and remotely virtual display driver installed. when the monitor is turned off, get blank screen and failed to connect msg, most of the time. sometimes, for a short period after rebooting, can connect.

works fine with a dummy HDMI dongle.

not a problem for me. just FYI. as everything else seems to run very well using the booter process only.
 
mirillis

mirillis

Administrator
Staff member
Hi hhspiny!

Thank you for reporting this. We will try to fix it in 1.32.0 (it's almost ready and will be released this week).

In 1.32.0 it is possible to send files on other accounts using the booter/service account (currently only using SendTo context menu but at least it is now possible).

Another new feature (there will be a lot of improvements) is that after pressing "next diaplay" you will also see all displays in one video (with remote control of course).
For example when you have two displays A and B the sequence will be A, B, AB...
 
H

hhspiny

Member
seems to be working now, but the virtual display and file transfer with booter process only. thanks for the update.

will test more and report back. in previous versions, sometimes it worked right after rebooting, but after a while, got blank screen.
 
H

hhspiny

Member
spoke too early. the virtual display driver causes crashing about 15 minutes after booting. the error was. version 1.32

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000001 (0x00007ffd9cc04cb4, 0x0000000000000000, 0x0000000000000001, 0xffffc989c1b5f4e0).

Uninstall and reinstall without virtual display (and audio) driver, does not crash anymore. reinstall with virtual display driver, crashes again.

running booter process only.
 
H

hhspiny

Member
it might be that the virtual display driver has conflict with something in my computer. but the crash was surely resulted from the presence of virtual display driver.
 
Last edited:
mirillis

mirillis

Administrator
Staff member
We are checking this on two different setups as we speak. If it will work for 30 minutes on both of them then it must be something machine specific. It may be something with initializing the driver for SYSTEM user (where booter runs and there are no users logged in).
 
mirillis

mirillis

Administrator
Staff member
One question. Do you have more than one GPU in this system? If yes, which GPU is selected as the renderer for virtual diaplay.
 
mirillis

mirillis

Administrator
Staff member
Is there any chance you can see in which driver the crash occured? the name is visible on the BSOD screen.
 
mirillis

mirillis

Administrator
Staff member
There will also be an information in the System Event Monitor. Can you check what it says?
 
H

hhspiny

Member
after crashes, it reboots. was not able to see BSOD screen. this is from minidump (from whocrashed)
1747511614017.png
 
You must log in or register to reply here.
Top