PC crashes when I start SteamVR

[mdinkov]

I’ve been trying to set-up my Vive system since last week with no luck. SteamVR finishes installing and I go through the room set-up successfully, but then my computer crashes when SteamVR starts up. When it crashes, I either get a black screen and it restarts or I get a blue screen with the error “WHEA_UNCORRECTABLE_ERROR”.

At first I thought that my GPU might be incompatable, so I spent $1050 on a GTX 1080ti and I still see the same issue! I tried reinstalling the Vive drivers (along with the NVIDIA drivers) with no luck. I’m using an i7-7820x processor on an ASUS TUF Mark 1 X299 board with 64GB of RAM. This system should be able to run the Vive EASILY.

I read through the forums and found out that people with ASUS motherboards were having a similar issue due to the USB ports. So I went to Best Buy and I spent more money on a PCIe USB3.0 card and I’m still seeing the issue...

I also made sure that my Windows is up to date. I’m running the 64-bit Windows Pro. If someone can help me out, I would be more than grateful.

[VibrantNebula]

     Hi @mdinkov,

     So, unfortunately this may be a difficult one to troubleshoot since it's a very uncommon error that can be highly specific to a single machine. We'll try out best to lend a hand. You may also want to contact SteamVR support who may be able to lend and hand in parallel. 

     First off, our team is curious about what will happen if you launch SteamVR with the Vive HMD unplugged. If it launches; what subsequently happens if you plug in the Vive (with SteamVR open). 

     Does your bluescreen list a crash dump location? If so, that dump file is by far our best lead. If you do have one, you can upload it to a service like pastebin for analysis. 

     Other ideas:

• Go into your BIOS settings and ensure that you have disabled all overclocking utilities and options. While there, look into your power options and ensure that there is no power throttling at play.
  • In windows, ensure that you're using a "high preformance" power plan. 
• What's your PSU wattage? One possible cause is that the GPU/CPU is underpowered.
• You can try running a memory check to verify that it isn't a RAM issue. You can access a memory debugging tool by typing in "mdsched.exe" into the searchbar.
• In your device manger, do you see any devices with a yellow "!" indicating an issue? (with and without the Vive plugged in)
• Which version of windows are you running? 8 or 10? This error can apply to both. 
  • Due to meltdown/specter OEM patching; having the latest version of windows could possibly be a trigger for this on the CPU side. See here.
• Have you tried bypassing the HDMI/USB from the linkbox and plugging the 3-in-1 directly into the computer? When doing this you must keep power connected through the linkbox.
• Are you using any sort of display adapter to connect the Vive to the GPU?

[VibrantNebula]

Additional idea: @mdinkov, if you're able to start SteamVR with the HMD unplugged; hop into the settings page and under the "camera" tab try disabling the camera. That can cause issues in some cases. 

[mdinkov]

I got it to work by disabling SteamVR Home. I would still like to have a better fix just so I don't start crashing in the middle of games.

I was unable to attach the crash dump to pastebin, but here is some info that might help from it:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffff830083307028, f2000000, 70005}

Probably caused by : GenuineIntel

Followup:     MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff830083307028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000070005, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.16299.192 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  0702

BIOS_DATE:  08/08/2017

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  TUF X299 MARK 1

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: ffff830083307028

BUGCHECK_P3: f2000000

BUGCHECK_P4: 70005

BUGCHECK_STR:  0x124_GenuineIntel

CPU_COUNT: 10

CPU_MHZ: e10

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 55

CPU_STEPPING: 4

CPU_MICROCODE: 6,55,4,0 (F,M,S,R)  SIG: 2000026'00000000 (cache) 2000026'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  steamtours.

CURRENT_IRQL:  f

ANALYSIS_SESSION_HOST:  DESKTOP-KQ3220J

ANALYSIS_SESSION_TIME:  02-08-2018 21:00:48.0146

ANALYSIS_VERSION: 10.0.17074.1002 amd64fre

STACK_TEXT:  
ffffe600`c726bde8 fffff801`bf525f1f : 00000000`00000124 00000000`00000000 ffff8300`83307028 00000000`f2000000 : nt!KeBugCheckEx
ffffe600`c726bdf0 fffff804`7eaa148a : ffff8300`83307028 ffff8300`7ef814e0 ffff8300`7ef814e0 ffff8300`7ef814e0 : hal!HalBugCheckSystem+0xcf
ffffe600`c726be30 fffff801`bee9aab1 : ffff8300`83307028 00000000`00000000 ffff8300`7ef814e0 ffff8300`7ef814e0 : PSHED!PshedBugCheckSystem+0xa
ffffe600`c726be60 fffff801`bf526460 : 00000000`00000728 00000000`00000002 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x261
ffffe600`c726bec0 fffff801`bf5267c0 : 00000000`00000010 00000000`00000002 ffffe600`c726c068 00000000`00000002 : hal!HalpMcaReportError+0x50
ffffe600`c726c010 fffff801`bf5266ae : ffff8300`7ef82160 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe0
ffffe600`c726c060 fffff801`bf5268f2 : 00000000`00000010 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
ffffe600`c726c0a0 fffff801`bf526a80 : ffff8300`7ef82160 ffffe600`c726c2d0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffe600`c726c0d0 fffff801`bed9aa3b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffe600`c726c100 fffff801`bed9a6bd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffe600`c726c240 00007ff9`81f315ab : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x47d
00000081`310d7710 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`81f315ab


THREAD_SHA1_HASH_MOD_FUNC:  a23b7d765df95ae34e5a10fad949ea2e4c0373b0

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  9d4877dc8bbb2df07ac176134a97f279382d2646

THREAD_SHA1_HASH_MOD:  156f1337245e21f523efe2d6f6d05bb3ab59ca82

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE

PRIMARY_PROBLEM_CLASS:  0x124_GenuineIntel_PROCESSOR_MAE

TARGET_TIME:  2018-02-08T00:25:33.000Z

OSBUILD:  16299

OSSERVICEPACK:  192

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-01-01 06:07:05

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.16299.192

ANALYSIS_SESSION_ELAPSED_TIME:  38b

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_mae

FAILURE_ID_HASH:  {7c95de0c-286c-8226-45c2-422b4de101d6}

Followup:     MachineOwner

Answer to Questions:

• Go into your BIOS settings and ensure that you have disabled all overclocking utilities and options. While there, look into your power options and ensure that there is no power throttling at play
  I believe my board is overclocking my CPU slightly by default. I'm not sure what settings to change to disable it. :\ 
  • In windows, ensure that you're using a "high preformance" power plan.
    I just checked and it is already on High Performance.
• What's your PSU wattage? One possible cause is that the GPU/CPU is underpowered.
  1300 watts
• You can try running a memory check to verify that it isn't a RAM issue. You can access a memory debugging tool by typing in "mdsched.exe" into the searchbar.
  I will do that and let you know how it goes.
• In your device manger, do you see any devices with a yellow "!" indicating an issue? (with and without the Vive plugged in)
  Nope
• Which version of windows are you running? 8 or 10? This error can apply to both.
  10 Pro 
  • Due to meltdown/specter OEM patching; having the latest version of windows could possibly be a trigger for this on the CPU side. See here.
    Good to know... I will also try rolling back Windows.
• Have you tried bypassing the HDMI/USB from the linkbox and plugging the 3-in-1 directly into the computer? When doing this you must keep power connected through the linkbox.
  I have not tried this, but I'll give it a whirl.
• Are you using any sort of display adapter to connect the Vive to the GPU?
  Nope, straight into the HDMI slot of the graphics card.

[dorianv]

I'm having the exact same issue on 2 brand new PC's with the same motherboard. DigitalStorm is the PC manufacturer we ordered from. We went thru neary 16 hours of trouble shooting with them trying to find what was causing the crash, but wound up RMA'ing both machines. They sent 2 NEW brand-new pc's and guess what ... both blue screen opening steamVR. 

Has there been any resolution to this? I'm getting desperate over here and DS will not replace them for software problems.

I've tried with both Vive and Vive Pro ... wired and wireless ... HMD on and HMD off. Crash every time.

Please help.