SteamVR

SteamVR

fgevans Apr 17, 2016 @ 12:27pm
Video scheduler internal error and pc crash on room setup
my system keeps on crashing BLSOD today after i tried changing my room set up as i increased my room space. worked fine last night (first time i set it up)

now everytime i select room set up and put controls on floor to calibrate it crashes with same error message Video scheduler internal error

all other non vive games work without any probs

running a amd 290x which is oced but not had any issues with other games

any ideas
< >
Showing 1-15 of 31 comments
Antar3z Apr 22, 2016 @ 6:28am 
(almost) the same here.. the same result occurs if I am opening virtual desktop and try to start a video or smt.

Specs

i5 2500k 4,4 Ghz
Amd r9 290x tri x
8 gig
Windows 8.1

Would love to have a solution as well...
Antar3z Apr 22, 2016 @ 9:43am 
Edit: I am using the driver version: Crimson Edition 16.4.1 Hotfix. OP, which one are you using in addition which Win version?

TheVirus Apr 22, 2016 @ 1:36pm 
Same here. Just got my Vive today and I can't even finish the setup. As soon as I launch the Room Scale setup, it BSOD's with VIDEO_SCHEDULER_INTERAL_ERROR. Freshish install of Windows 8.1, R9 390. I'm not too happy with this.
TheVirus Apr 22, 2016 @ 2:10pm 
Disabling Direct Mode fixed it. Launch Steam VR, right click the VR icon, go to Devices and uncheck Direct Mode. It'll popup a warning, click OK.
Antar3z Apr 23, 2016 @ 4:24am 
@TheVirus

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!!
Last edited by Antar3z; Apr 23, 2016 @ 4:25am
Asgatoril Apr 25, 2016 @ 12:45pm 
Same problem here, same workaround working.
I'm on a R290X.
Would be nice to get an update against that crash.
Antar3z Apr 26, 2016 @ 5:05am 
@Asgatoril can you pls post ur other specs to make it easier to pinpoint the problem? Thx!
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)
Asgatoril Apr 26, 2016 @ 7:06am 
Sure:
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.
Antar3z Apr 26, 2016 @ 9:05am 
sure i can! Will get to it if I am home from work! very good idea...
Last edited by Antar3z; Apr 26, 2016 @ 9:05am
Antar3z Apr 26, 2016 @ 9:41am 
So i checked this viewer and it seems there are like 3 different files causing these errors.

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
Asgatoril Apr 26, 2016 @ 1:33pm 
I think I'm on to something. I just unplugged my 2nd monitor and my tv from my pc and suddently I don't get any crashes in direct mode anymore.
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?
Antar3z Apr 26, 2016 @ 4:11pm 
Actually yes, I have my TV plugged in, its most of the time switched off completely though! Anyhow i will check this out tomorrow and get back to you, Sounds promising!!!
Last edited by Antar3z; Apr 26, 2016 @ 4:11pm
Antar3z Apr 27, 2016 @ 6:31am 
Unfortunately the failure is still taking place, even when I am unplugging my TV. It was worth the try though ;)
Asgatoril Apr 27, 2016 @ 6:40am 
Interesting...
How are your primary monitor and you Vive connected to the PC?
For me its: DVI for the monitor, HDMI for the Vive.
Antar3z Apr 27, 2016 @ 8:27am 
yea exactly like that
< >
Showing 1-15 of 31 comments
Per page: 1530 50

Date Posted: Apr 17, 2016 @ 12:27pm
Posts: 31