Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Specs
i5 2500k 4,4 Ghz
Amd r9 290x tri x
8 gig
Windows 8.1
Would love to have a solution as well...
I can confirm that this solution prevents my system from crashing while using virtual desktop. I guess by switching off the direct mode, the common SteamVR funtions don't work anymore, right? At least the Headset seems to be in a standby mode as long as there is no application started.
Anyway thanks alot for this helpful workaround!!
I'm on a R290X.
Would be nice to get an update against that crash.
Would really like to see a solution here. The workaround may work but at the cost that some core functions are not working anymore (at least for me)
CPU: i5-4670k
GPU: R9 290X
OS: Win 8.1
RAM: 12 GB
I have linked this thread from AMDs forum after discovering, that someone there has the same problem:
https://community.amd.com/message/2719356#comment-2719356
@Aeon: could you upload a log of your crash from Bluescreendump? Maybe it helps, if we can collect some more data for that error.
Link to tool: http://www.nirsoft.net/utils/blue_screen_view.html
In the tool: rightclick on the relevant bluescreen -> HTML report - selected items
I have uploaded my log here:
http://s000.tinyupload.com/index.php?file_id=80283446432015119871
I hope we can get rid of this problem soon. Without direct mode my compositor often loses fullscreen focus which causes my screen to go red.
In most cases it is watchdog.sys (for example just starting holoball and running it for a few seconds or starting a video while using virtual desktop)
crashreport-----> http://pastebin.ca/3583968
sometimes its also caused by pcw.sys
cr -----> http://pastebin.ca/3583975
or by atapiex.sys
cr -----> http://pastebin.ca/3583981
I disabled them before, but that didn't help but unplugging did the trick.
@Aeon: Do you have any additional monitors plugged in which you could plug out for the time being?
How are your primary monitor and you Vive connected to the PC?
For me its: DVI for the monitor, HDMI for the Vive.