mcs04

wrote: Hope the ASRock works for ya, my second night with it went without a hitch!. Well.. Standout VR loaded, but none of the menus worked, I really wanna rule this as the game being faulty than the headset. Charging up battery as we speak for night 3! Success finally! This particular motherboard is working for me (so far). I switched from a MSI B450 Tomahawk to the Asrock AB350 PRO4 (with my original Ryzen 2600x and GTX 970) and I was able to burn through an entire battery pack with no BSOD, and I'm currently on the second pack with no crashing issues. I updated the bios to ver 5.00 and installed the latest AMD Chipset drivers. Have played Beat Saber, Space Pirate Trainer, The lab, Holopoint and Skyrim. The only problem I've had so far was when SteamVR suddenly dropped connection of the headset, lighthouses and controllers, and reconnected everything about 30 seconds later. Not sure why that happened, but was during the Budget cuts demo. Everything else has been smooth. I have the WiGig card installed in the top PCIe 1x slot, and my GPU in the 16x slot below that.

wrote: Ryzen 7 2700 on an Asus Prime B250 Plus Moving the card as close to my Video Card as possible let it load the 64 bit drivers instead of the 32 and this stoped it from locking up or BSOD from just having steam running. I made sure to update my BIOS and all software (there is a new VIVE Wireless application update) . I have still had a BSOD once since making this change but once I got everything updated (Steam VR Beta and Non-Beta tested) it has happened very rarely. Also I did have to go into the Divice management and force it to check for new drivers for the VIVE before it workes fully with Steam. Everything was really low res (so low I could not read any text) until I rebooted. It was a chore but the outcome seems to be a working system. I've tried every PCIe slot I have except for the one closest to my GPU (because it would partially block the fan) but I decided to give it a shot after your post. It actually worked close to 10 minutes this time before locking up with a BSOD. The dozens of previous attempts either locked up once SteamVR started or within 60 seconds of starting a game. Not sure if it's just a coincidence though because others seem to be able to play for hours where they think the problem has been fixed, and then suddenly BSODs again. The wireless update did nothing for me either - still BSOD after a minute of starting a game. I have an AsRock AB350 PRO4 that I'm going to try today as a last-ditch effort before finishing up my return since a few others seem to have some success, we'll see

wrote: I'm beginning my return process. This is unbelievable that they shipped this out without knowing that there would be such a huge issue such as this. And not only that, but they are STILL accepting purchases with ZERO official warning or notice that this may be an issue for Ryzen owners. Pathetic. Not that it will change anything but I have already sent in a complaint with the FTC about this and I urge others in the US to do the same. This entire situation has been incredibly deceptive from the beginning and like many others have said, very unlikely they were not aware of this issue before release. https://www.ftccomplaintassistant.gov/#crnt&panel1-1

wrote: , We're assessing your report and the few others you mentioned on/Vive - We're aware of your situation and we'll be sure to keep in communication as we work to understand the behavior you're seeing. If you are reading this thread and are currently experiencing a similar behavior, you can post here to receive a ping when we have additional updates. If possible, please share your CPU/Mobo model #'s and any "stop codes" that may be displayed if a BSOD occurs. , what happened to "keep in communication"? Nearing the end of the return window for a lot of people with this issue. Anyway, I've decided to initiate a return because I don't see this getting fixed any time soon. Also, with the overheating issues that are increasingly being reported I don't think it's worth gambling on this $300+ product actually working even if the Ryzen issue is fixed. Hopefully it lasts long enough for those that it does work for, because it's clear this was pushed out way too soon and with extremely poor QA testing. By the way, for those who will also be returning before the window ends: HTC stated to me that they will not refund your initial shipping cost or offer a prepaid label to return unless you escalate your case. It's just another shady BS move by a company that doesn't care about their customers.

wrote: AMD didn’t want to pay for the licensing for XMP memory profile support, this requires some alternative way to overclock the ram in the bios, if you are using ryzen and you ram is overclocked and you are seeing the BSOD check the timing settings for you ram, my bios had most the values correct except a few, for sometime this has not been a problem until the wireless adapter that is. I pulled the memory xmp settings from the bios tool memory SPD and enter each value that was different manually, I have not had a crash since. Unlike AMD, Intel uses XMP profiles automatically, if you are a lucky AMD user your mother board may have a better timing detection or your ram may be a more standard settings. Otherwise you are here waiting for a solution that may not come. I recommend carefully entering your rams XMP timing values into the bios if your motherboard supports it and see if that helps you as it did me. I tried both of the XMP profiles I have on my MB, and I also changed the timing values manually and all resulted in the same BSOD or total lock up either within 5 minutes of playing a game, or within seconds of SteamVR opening. The only weird thing this time was that even after the BSOD, my system hard locked again right as it got to the windows login screen just like it does when I start trying to play wireless.