Jump to content
Happy Holidays! Limited Staff Responses: 1/20 - 1/31 ×

PC crashes when I start SteamVR


mdinkov
 Share

Recommended Posts

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.

Link to comment
Share on other sites

     Hi ,

     

     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?
Link to comment
Share on other sites

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 : GenuineIntelFollowup:     MachineOwner---------
2: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: 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: 1TIMELINE_ANALYSIS: 1DUMP_CLASS: 1DUMP_QUALIFIER: 400BUILD_VERSION_STRING:  10.0.16299.192 (WinBuild.160101.0800)SYSTEM_MANUFACTURER:  System manufacturerSYSTEM_PRODUCT_NAME:  System Product NameSYSTEM_SKU:  SKUSYSTEM_VERSION:  System VersionBIOS_VENDOR:  American Megatrends Inc.BIOS_VERSION:  0702BIOS_DATE:  08/08/2017BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.BASEBOARD_PRODUCT:  TUF X299 MARK 1BASEBOARD_VERSION:  Rev 1.xxDUMP_TYPE:  2BUGCHECK_P1: 0BUGCHECK_P2: ffff830083307028BUGCHECK_P3: f2000000BUGCHECK_P4: 70005BUGCHECK_STR:  0x124_GenuineIntelCPU_COUNT: 10CPU_MHZ: e10CPU_VENDOR:  GenuineIntelCPU_FAMILY: 6CPU_MODEL: 55CPU_STEPPING: 4CPU_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:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  steamtours.CURRENT_IRQL:  fANALYSIS_SESSION_HOST:  DESKTOP-KQ3220JANALYSIS_SESSION_TIME:  02-08-2018 21:00:48.0146ANALYSIS_VERSION: 10.0.17074.1002 amd64freSTACK_TEXT:  ffffe600`c726bde8 fffff801`bf525f1f : 00000000`00000124 00000000`00000000 ffff8300`83307028 00000000`f2000000 : nt!KeBugCheckExffffe600`c726bdf0 fffff804`7eaa148a : ffff8300`83307028 ffff8300`7ef814e0 ffff8300`7ef814e0 ffff8300`7ef814e0 : hal!HalBugCheckSystem+0xcfffffe600`c726be30 fffff801`bee9aab1 : ffff8300`83307028 00000000`00000000 ffff8300`7ef814e0 ffff8300`7ef814e0 : PSHED!PshedBugCheckSystem+0xaffffe600`c726be60 fffff801`bf526460 : 00000000`00000728 00000000`00000002 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x261ffffe600`c726bec0 fffff801`bf5267c0 : 00000000`00000010 00000000`00000002 ffffe600`c726c068 00000000`00000002 : hal!HalpMcaReportError+0x50ffffe600`c726c010 fffff801`bf5266ae : ffff8300`7ef82160 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe0ffffe600`c726c060 fffff801`bf5268f2 : 00000000`00000010 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xdaffffe600`c726c0a0 fffff801`bf526a80 : ffff8300`7ef82160 ffffe600`c726c2d0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffe600`c726c0d0 fffff801`bed9aa3b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffe600`c726c100 fffff801`bed9a6bd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffe600`c726c240 00007ff9`81f315ab : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x47d00000081`310d7710 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`81f315abTHREAD_SHA1_HASH_MOD_FUNC:  a23b7d765df95ae34e5a10fad949ea2e4c0373b0THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  9d4877dc8bbb2df07ac176134a97f279382d2646THREAD_SHA1_HASH_MOD:  156f1337245e21f523efe2d6f6d05bb3ab59ca82FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0STACK_COMMAND:  .thread ; .cxr ; kbFAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAEBUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAEPRIMARY_PROBLEM_CLASS:  0x124_GenuineIntel_PROCESSOR_MAETARGET_TIME:  2018-02-08T00:25:33.000ZOSBUILD:  16299OSSERVICEPACK:  192SERVICEPACK_NUMBER: 0OS_REVISION: 0SUITE_MASK:  272PRODUCT_TYPE:  1OSPLATFORM_TYPE:  x64OSNAME:  Windows 10OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTSOS_LOCALE:  USER_LCID:  0OSBUILD_TIMESTAMP:  2018-01-01 06:07:05BUILDDATESTAMP_STR:  160101.0800BUILDLAB_STR:  WinBuildBUILDOSVER_STR:  10.0.16299.192ANALYSIS_SESSION_ELAPSED_TIME:  38bANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_maeFAILURE_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.
Link to comment
Share on other sites

  • 11 months later...

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.

Link to comment
Share on other sites

  • 1 month later...

THANK GOD I AM NOT THE ONLY ONE WITH THIS PROBLEM!

 

I have the exact same problem with a brandnew Hyrican Striker 6110.

I got BSODs all the time with

WHEA_UNCORRECTABLE_ERROR.

So I went to the store and got a new same Hyrican. Same problem again!

PLEASE help!

 

Did anyone find a solution yet?

Link to comment
Share on other sites

  • 1 month later...

I've had my vive for the last 4-5months or so and have run every game on it at max as I have a high-end VR ready gaming desktop and recently I have been having the same problems. it's weird because this never came up for me and suddenly when I am playing mid game my whole computer crashes. like my computers CPU and GPU suddenly overload. this problem started happening today, after playing for about 2 hours my computer crashes and i don't really think much of it but for the last 30 min or so 3min after loading up a game i crash. i have tried all the tips vive posted in the thread, tried making sure every app that i was not going to use was closed to maybe loosen on the load my computer should not have to take. in game, my computer runs at around 30% so i dont understand what is happening.

Link to comment
Share on other sites

Update

while trying to troubleshoot my vive it crashed my computer without the application even being open.

 

this is getting absurd. i don't know if it has to do with a recent "hotfix" that i might have missed even though i am up to date on everything or my computer just doesnt like the application anymore

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...