something really strange happens today, every time i run oculus app windows crashes with portcls.sys error... i read around that is driver related, so i opened app without usb plugged and app works..once i plug in back pc crashes....
i always have trouble in letting pc recognise rift S at every boot but usually usb simply dont work and have to unplug and plug few times...
nothing in pc is changed, i didnt change drivers of anything, windows update installed nothing (im on dev preview with same build since 20 days ) only updated things are defender database and a game but im pretty sure they are not involved hehe
any idea? im running with an Asmedia usb controller, worked with lates drivers wich im using now
well yesterday i managed to let it "works" installing beta, reverting back and oculus app lets me to install again his usb divers....then rift s was working but software was saying usb c connection was broken ,but everything was right except some little glithces in tracking.
switched on pc today...not working anymore with same error.... not only oculus prevents windows to going in sleep state (wow guys u are genius) but now i cant even reboot without pass a day to try to fix it?
Edit : i forgot to say, i discovered i recieved 17.0 update but notify window was not showing any update, so the problem is the new release
Hi, since April 29 I'm having this problem too. Windows BSOD on portcls.sys randomly right after system starts, but I don't have my CV1 plugged in.
Windows dump file points to portcls.sys IRQ not less or equal error, after called by the oculusvd driver. It's weird because my CV1 works fine when I plug it in, but the PC BSOD when nothing Oculus related is connected and I start the system.
@Xarstealth: I have an AMD motherboard, Gigabyte Aorus Master X570. My Oculus App is 17.0.0.128.462
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: oculusvad.sys (Oculus Virtual Audio Driver, Windows (R) Win 7 DDK provider). . product: Windows (R) Win 7 DDK driver
I've been getting this lately as well. My PC has been stable for about 3-4 yrs now with no hardware changes. Also no software changes other than Win10 stuff and the ongoing onslaught of Oculus "updates".
My event logs have been showing hundreds of these errors...............
Session "OculusVadApoEventTrace" failed to start with the following error: 0xC0000035
........... even when I'm not using my CV1.
I'm opting out of this beta thing again. (Edit: Just saw another update has arrived without release notes. I'll monitor it for a couple of days before going back to the public release.)
