Cyberpunk 2077 PC Crash Issues

[earthdrowned]

They just didn't test the game on wide variety of system configurations the game is shipping on.
A lot of these problems have to do with the game running on directX 12 ONLY!
Generally a lot of games that are exclusively using DX12 had as shaky of a launch as this one.

All we can do is wait.

 

[Armando_Scilinguo]

I told you my experience. Dual boot, same components

Windows 10: crash on startup, nothing worked, tried everything suggested here

Windows 7: random crashes during play, every 15/20 minutes

So it is NOT hardware related 100% in my case

 

[Angry_Amadeus]

I have identified "crash boxes" - small areas (I would guess 100' x 100' in-game) where if I cross an invisible line, I crash.

I have replicated this in two different areas: one during a Cyberpsycho hunt, directly around the center of the Cyberpsycho spawn point. The other while driving back from a mission.

I can walk around the "crash boxes" without issue and continue exploring in-game, only until I stumble upon another "crash box". I'm keeping a list and noting where they are on the map so that I don't cross over the invisible line and crash.

Trace:

Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0xFFFFFFFFFFFFFFFF.
File: <Unknown>(0)

 

[callofduty1]

my xbox one controller keeps not working or i get stick circular drift or the sticks not working it needs patching cod

Post automatically merged: Dec 14, 2020

anyone having trouble with their xbox one controllers?

 

[VanyanVulpes]

Hey folks,

So I finally fixed the Gpu Crash for unknown reasons! for me at least. I've been basically throwing everything I could think of at it. What finally did it was installing the latest chipset & soundcard drivers, along with flashing the BIOS with the latest update, and also using my second monitor instead.

One of them has sorted it as I no longer crash at all. For reference, my rig:

GPU: Gigabyte GeForce RTX 3080
CPU: AMD Ryzen 7 3700X
Motherboard: Gigabyte B550 Aorus Elite

Up until I did the above, I got the GPU crash every few minutes constantly, never really got past the Character creation. So, maybe worth trying.

 

[Dominik_Lesn]

it says:
Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0xFFFFFFFFFFFFFFFF.
File: <Unknown>(0)

I just deleted my .exe and .exe.bak and now it seems like there are no more crashes.. for now..


(PS: I'm using the .exe hexcode mod for better cpu utilization)

 

[televators]

Just to confirm, on my end, I was absolutely unable to play without constant crashing. Until yesterday. I upgraded from Win7 to Windows 10, version 19042.685.

Even so, personally I think that Win update isn't an option.

Unless we are speaking about ancient builds, it should be fine to use any version which supports DX12. Win update is huge pain for many users (come there are too much programs, drivers, compatibilities and so on) and I really can't understand why such crucials parts as DirectX has so much differences between literally EACH step version of the Windows 10.

 

[vuzuela]

dealing with same issue

 

[Darkbaz]

I just deleted my .exe and .exe.bak and now it seems like there are no more crashes.. for now..


(PS: I'm using the .exe hexcode mod for better cpu utilization)

Did you reacquire the .exe afterwards or just leave it deleted? And if the latter, how do you launch the game? (Sorry if stupid question)

 

[Dominik_Lesn]

Did you reacquire the .exe afterwards or just leave it deleted? And if the latter, how do you launch the game? (Sorry if stupid question)

Yes I reacquired the .exe and yeah.. I launch the game through GOG or my desk .exe..

____________________________________________________________________________________

Now after about 1 1/2 hrs of playing without crashes.. it crashed again.. and this time with a different report:

Version=1
EventType=REDEngineErrorReport
EventTime=0
ReportIdentifier=ffffffff-ffffffff-00000001-00000000
Sig[0].Name=StackHash
Sig[0].Value=0x0000000000000000
Sig[1].Name=ErrorReason
Sig[1].Value=Unhandled exception
Sig[2].Name=InternalVersion
Sig[2].Value=3.0.3217599 P4CL: 4158334 Stream: //R6.Root/R6.Patch0Hotfix2
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.19042.2.0.0.256.1
LoadedModule[0]=Cyberpunk2077.exe
LoadedModule[1]=ntdll.dll
LoadedModule[2]=KERNEL32.DLL
LoadedModule[3]=KERNELBASE.dll
LoadedModule[4]=apphelp.dll
LoadedModule[5]=USER32.dll
LoadedModule[6]=win32u.dll
LoadedModule[7]=GDI32.dll
LoadedModule[8]=gdi32full.dll
LoadedModule[9]=msvcp_win.dll
LoadedModule[10]=ucrtbase.dll
LoadedModule[11]=ADVAPI32.dll
LoadedModule[12]=msvcrt.dll
LoadedModule[13]=sechost.dll
LoadedModule[14]=RPCRT4.dll
LoadedModule[15]=VERSION.dll
LoadedModule[16]=SHELL32.dll
LoadedModule[17]=ole32.dll
LoadedModule[18]=combase.dll
LoadedModule[19]=SETUPAPI.dll
LoadedModule[20]=cfgmgr32.dll
LoadedModule[21]=bcrypt.dll
LoadedModule[22]=WS2_32.dll
LoadedModule[23]=OLEAUT32.dll
LoadedModule[24]=icuuc.dll
LoadedModule[25]=XINPUT1_3.dll
LoadedModule[26]=HID.DLL
LoadedModule[27]=icuin.dll
LoadedModule[28]=dbghelp.dll
LoadedModule[29]=bink2w64.dll
LoadedModule[30]=PhysX3CharacterKinematic_x64.dll
LoadedModule[31]=PhysX3Cooking_x64.dll
LoadedModule[32]=PhysX3Common_x64.dll
LoadedModule[33]=NRD.dll
LoadedModule[34]=PxFoundation_x64.dll
LoadedModule[35]=POWRPROF.dll
LoadedModule[36]=d3d11.dll
LoadedModule[37]=PhysX3_x64.dll
LoadedModule[38]=redlexer_native.dll
LoadedModule[39]=libcurl.dll
LoadedModule[40]=WLDAP32.dll
LoadedModule[41]=CRYPT32.dll
LoadedModule[42]=Normaliz.dll
LoadedModule[43]=WINMM.dll
LoadedModule[44]=MSVCP140.dll
LoadedModule[45]=VCRUNTIME140.dll
LoadedModule[46]=dxgi.dll
LoadedModule[47]=amd_ags_x64.dll
LoadedModule[48]=Galaxy64.dll
LoadedModule[49]=IPHLPAPI.DLL
LoadedModule[50]=WININET.dll
LoadedModule[51]=MSWSOCK.dll
LoadedModule[52]=oo2ext_7_win64.dll
LoadedModule[53]=icudt.dll
LoadedModule[54]=IMM32.DLL
LoadedModule[55]=UMPDC.dll
LoadedModule[56]=CRYPTBASE.DLL
LoadedModule[57]=bcryptPrimitives.dll
LoadedModule[58]=kernel.appcore.dll
LoadedModule[59]=windows.storage.dll
LoadedModule[60]=Wldp.dll
LoadedModule[61]=SHCORE.dll
LoadedModule[62]=shlwapi.dll
LoadedModule[63]=clbcatq.dll
LoadedModule[64]=wbemprox.dll
LoadedModule[65]=wbemcomn.dll
LoadedModule[66]=wbemsvc.dll
LoadedModule[67]=fastprox.dll
LoadedModule[68]=amsi.dll
LoadedModule[69]=USERENV.dll
LoadedModule[70]=profapi.dll
LoadedModule[71]=MpOav.dll
LoadedModule[72]=uxtheme.dll
LoadedModule[73]=GameServicesGOG.dll
LoadedModule[74]=CRYPTSP.dll
LoadedModule[75]=rsaenh.dll
LoadedModule[76]=napinsp.dll
LoadedModule[77]=pnrpnsp.dll
LoadedModule[78]=wshbth.dll
LoadedModule[79]=NLAapi.dll
LoadedModule[80]=DNSAPI.dll
LoadedModule[81]=NSI.dll
LoadedModule[82]=winrnr.dll
LoadedModule[83]=mdnsNSP.dll
LoadedModule[84]=fwpuclnt.dll
LoadedModule[85]=rasadhlp.dll
LoadedModule[86]=secur32.dll
LoadedModule[87]=SSPICLI.DLL
LoadedModule[88]=d3d12.dll
LoadedModule[89]=GFSDK_Aftermath_Lib.x64.dll
LoadedModule[90]=nvwgf2umx.dll
LoadedModule[91]=dxcore.dll
LoadedModule[92]=msasn1.dll
LoadedModule[93]=cryptnet.dll
LoadedModule[94]=WINTRUST.DLL
LoadedModule[95]=imagehlp.dll
LoadedModule[96]=nvspcap64.dll
LoadedModule[97]=ntmarta.dll
LoadedModule[98]=nvapi64.dll
LoadedModule[99]=nvldumdx.dll
LoadedModule[100]=D3DSCache.dll
LoadedModule[101]=twinapi.appcore.dll
LoadedModule[102]=iertutil.dll
LoadedModule[103]=ondemandconnroutehelper.dll
LoadedModule[104]=winhttp.dll
LoadedModule[105]=WINNSI.DLL
LoadedModule[106]=schannel.DLL
LoadedModule[107]=MMDevApi.dll
LoadedModule[108]=DEVOBJ.dll
LoadedModule[109]=mskeyprotect.dll
LoadedModule[110]=NTASN1.dll
LoadedModule[111]=ncrypt.dll
LoadedModule[112]=ncryptsslp.dll
LoadedModule[113]=dinput8.dll
LoadedModule[114]=inputhost.dll
LoadedModule[115]=wintypes.dll
LoadedModule[116]=PROPSYS.dll
LoadedModule[117]=CoreMessaging.dll
LoadedModule[118]=CoreUIComponents.dll
LoadedModule[119]=Wtsapi32.dll
LoadedModule[120]=AUDIOSES.DLL
LoadedModule[121]=MSCTF.dll
LoadedModule[122]=resourcepolicyclient.dll
LoadedModule[123]=textinputframework.dll
LoadedModule[124]=Windows.Perception.Stub.dll
LoadedModule[125]=gpapi.dll
LoadedModule[126]=nvngx.dll
LoadedModule[127]=DEVRTL.dll
LoadedModule[128]=drvstore.dll
LoadedModule[129]=SPINF.dll
LoadedModule[130]=nvngx_dlss.dll
LoadedModule[131]=nvcuda.dll
LoadedModule[132]=nvcuda64.dll
LoadedModule[133]=dcomp.dll
LoadedModule[134]=dwmapi.dll
LoadedModule[135]=TextShaping.dll
LoadedModule[136]=WINSTA.dll
LoadedModule[137]=nvrtum64.dll
LoadedModule[138]=nvptxJitCompiler64.dll
AppName=Cyberpunk2077.exe

Stacktrace:
Error reason: Unhandled exception
Expression: EXCEPTION_PRIV_INSTRUCTION (0xC0000096)
Message: The thread tried to execute an instruction whose operation is not allowed in the current machine mode.
File: <Unknown>(0)

 

[Hakashis-MJZ]

My rig:

• CPU: i5 4690K @ 4.6GHz OC
• GPU: ASUS ROG 1080Ti StriX
• RAM: 16GB DDR3
• Game on SSD, Windows on same SSD

I tried all the other roubleshooting, DDU, clean boot, MSI, AVX fix and so on, game still crashed just like usual, 5-15min tops.

What I did was reset my CPU OC that I had for 3 years at 4.6GHz back to 3.9Ghz, Just had a 2 hour session without any crashes.

Anybody else willing to test this out on their rig with a similar hardware ?

 

[Combatxlemming]

I have been fix testing for 4 hours for this game, think I'm done really game worked perfectly on 1.03 (played 12 hours) for me and little to zeros crashes yet this error on 1.04

Error reason: Assert
Expression: <Unknown>
Message: Watchdog timeout! (120 seconds)
File: e:\r6.patch0hotfix2\dev\src\common\engine\src\enginewatchdog.cpp(198)

Little to zero fixes for it if your googling at find this my advice give up till they fix it.

 

[Missilebean]

The RAM switching is not a fix for the game. That's a test to see if there's anything physically wrong with one of your RAM sticks. If that test somehow works, that means that you have a damaged RAM stick. (Which isn't so bad, really, as many RAM manufactorers guarantee their RAM for life, so with or without a warranty, you can probably get a replacement for nothing but shipping.)

That problem and solution would be a hardware issue. It has nothing to do with the game if it works -- it's just that CP2077 may have been the only game you play that put your PC in a situation to manifest the issue.

Look, I see you're doing your best to help a lot of people amongst many posts and lots of questions and frustrations, but you're missing the point of my comments entirely.

There are almost 100 pages to this troubleshooting thread full of issues and there are still a very disproportionate number of solutions. I don't think it was fair to nitpick one small example in a larger comment about the state of the game right now.

(And while this is not my specific problem afaik, if CP2077 causes an issue by not playing nice with a stable piece of my hardware that was never a problem for any other game - CP2077 and its build is the issue)

The issues that people are experiencing that can not be fixed by normal, user accessible methods are what I'm talking about. No one should have to be doing some of the things in this thread to get a game like this to run. Even so, a lot of the people in this thread have done them, myself included, and STILL none of them solved our issue.

Further than that, and the point I made as well: why in the world would I try some of the solutions that require tinkering at a deep system or hardware level just to LAUNCH the game, when I can see 100 pages of issues that people are experiencing IN the game, with STILL no solution? Out of one mess, into the next.

Personally speaking, if my issue was fixed tomorrow, I'd boot the game up in a heartbeat and try it out for myself, as I'm sure a lot of other people would. I'm incredibly frustrated that there is nothing I can do to get the game to launch. It did not at all help that CDPR rushed to release a PR statement for damage control on consoles, a situation they put themselves in, while giving PC gamers in situations like myself barely a glancing thought at the end of the post.

I'm not attacking you or anyone else in this forum. Again, you and the other mods have been great. Everyone here has been nothing but helpful. We need solutions, and if not that, updates on progress or reassurance that our issues have been seen and are being investigated.

 

[Avierr]

Heads up: To those of you there were flatlining at the logo screen, I may have a fix for you.

I was getting the following error when I started the game:
Message: Gpu Crash for unknown reasons! Callstack here is probably irrelevant. Check if Breadcrumbs or Aftermath logged anything useful.
File: e:\r6.patch0hotfix2\dev\src\common\gpuapi\src\dx12\gpuapidx12error.cpp
Line: 40

I have an RTX 2060 Mobile and i7-9750H

The game was working fine up until I installed the hotfix. I'm not sure what changed between the patches to cause this, but I was then crashing at the logo screen over and over. What helped me was flashing the updated BIOS. For my model, there was an update released back in October. Check online to find and flash your latest BIOS version, if you are still having the same issue I was.

Hope this helps!

I should not have to flash my BIOS just to play a game. That is ridiculous and I'm not risking my only working rig for that.

 

[windows7dx11]

Literally just made this account just to post this here, so bear with me for a moment.

I have read the entirety of 98 pages of comments on this thread (if you can believe it), as well as many other internet forum posts, and have come to a conclusion that this game CANNOT RUN without directX 12 which can only be installed on a windows 10. As you can allude from my name, I run a fully updated windows 7 64bit ultimate with DX11, but I am unable to play this game.

To elaborate, it's not that I can't even start it, on the contrary -- I most certainly can. I can even start a new game and get in character creation. But past that, after the first loading screen and during the first few in-game frames (regardless of the chosen start as nomad, streetkid or corpo), my GPU driver gets nuked from orbit -- it crashes and never recovers forcing me to do a hard reset of my PC and reinstall my drivers after (because somehow they become permanently corrupted making me unable to play any other game). Lowering every graphic setting to the lowest and capping frames does nothing, same thing happens every time.

For the record, my specs are:

nvidia 1080TI 11GB
intel i7 7700k 4.2 GHz
32 GB DDR5 RAM
Windows 7 Ultimate 64bit 7601 (latest build version)

I know for a fact that it's not a hardware issue because there hasn't been a single game thus far (RDR2, Kingdom Come, Doom Eternal, etc.) that I couldn't smoothly run on ultra settings with zero issues whatsoever. Except this one (which I can't run at all). Why? Because no DX12 that's why!

It's not a "flatline" error. I have the exact same error as the user Alphract above, who also runs windows 7, which is this:

InternalVersion: 3.0.3217599  P4CL: 4158334  Stream: //R6.Root/R6.Patch0Hotfix2
!!!CRASHED!!!
Error Reason: Assert
Expression:
Message: Gpu Crash for unknown reasons! Callstack here is probably irrelevant. Check if Breadcrumbs or Aftermath logged anything useful.
File: e:\r6.patch0hotfix2\dev\src\common\gpuapi\src\dx12\gpuapidx12error.cpp

Note the file name "gpuapidx12error.cpp" above. Yeah...

I love CDPR, but to release a game which ABSOLUTELY REQUIRES THE LATEST SOFTWARE POSSIBLE is absurd at best. Not to mention that, from what I've read (and I've read A LOT these past few days), DX12 is reported to be buggy and unstable, so basing your game solely upon it is completely irresponsible. This is confirmed by an absolute MOUNTAIN of other bugs that are reported here (which I can't even experience since I can't run the game). And I don't even want to go into the console debacle, that's another topic on its own.

I get that the game was rushed to meat the deadline, but I wouldn't mind CDPR pushing back the release for another year or two if it meant we'd get a stable and optimized game for which this studio is known for. Alas, the bosses on top most likely wanted this game to be on the game awards list this year and have as a result, not only crunched their workers to death, but also missed the game awards as well! You have ruined your reputation and disappointed many faithful supporters like myself, as is evident from the posts on this forum. Was it worth it, CDPR?

 

[Luciferos90]

InternalVersion: 3.0.3217599  P4CL: 4158334  Stream: //R6.Root/R6.Patch0Hotfix2 
!!!CRASHED!!!
Error Reason: Assert
Expression: 
Message: Gpu Crash for unknown reasons! Callstack here is probably irrelevant. Check if Breadcrumbs or Aftermath logged anything useful.
File: e:\r6.patch0hotfix2\dev\src\common\gpuapi\src\dx12\gpuapidx12error.cpp

Any update for Pc version? the game still unplayable

My spec:

• CPU: I7 7700k
• GPU: ZOTAC GTX 1080ti Amp Edition
• RAM: 16gb Corsair DDR4 3200mhz
• Game on SSD same for Windows 10

All is update

 

[SigilFey]

Even so, personally I think that Win update isn't an option.

Unless we are speaking about ancient builds, it should be fine to use any version which supports DX12. Win update is huge pain for many users (come there are too much programs, drivers, compatibilities and so on) and I really can't understand why such crucials parts as DirectX has so much differences between literally EACH step version of the Windows 10.

This whole mindset is a direct path to frustration and disappointment.

I'm the first person to say: "If you want a stable gaming environment, do not update or change anything constantly. Change absolutely nothing unless there is a reason."

But the way software and hardware work, developers will release updates to solve particular issues. If an update is needed to fix a particular issue, then that's the reason to get that update and make those changes. Thinking, "It just shouldn't be like that," doesn't make it any less necessary if that's what is needed. (Not a big fan of gravity or taxes, either.)

My rig:

• CPU: i5 4690K @ 4.6GHz OC
• GPU: ASUS ROG 1080Ti StriX
• RAM: 16GB DDR3
• Game on SSD, Windows on same SSD

I tried all the other roubleshooting, DDU, clean boot, MSI, AVX fix and so on, game still crashed just like usual, 5-15min tops.

What I did was reset my CPU OC that I had for 3 years at 4.6GHz back to 3.9Ghz, Just had a 2 hour session without any crashes.

Anybody else willing to test this out on their rig with a similar hardware ?

Yes -- overclocking or underclocking are known to cause stability issues. (Especially with games that are suffering from bugs.) If the need to troubleshoot something ever arrives, one of the first things to do is return all clock speeds and voltage settings to factory defaults.

Look, I see you're doing your best to help a lot of people amongst many posts and lots of questions and frustrations, but you're missing the point of my comments entirely.

There are almost 100 pages to this troubleshooting thread full of issues and there are still a very disproportionate number of solutions. I don't think it was fair to nitpick one small example in a larger comment about the state of the game right now.

(And while this is not my specific problem afaik, if CP2077 causes an issue by not playing nice with a stable piece of my hardware that was never a problem for any other game - CP2077 and its build is the issue)

The issues that people are experiencing that can not be fixed by normal, user accessible methods are what I'm talking about. No one should have to be doing some of the things in this thread to get a game like this to run. Even so, a lot of the people in this thread have done them, myself included, and STILL none of them solved our issue.

Further than that, and the point I made as well: why in the world would I try some of the solutions that require tinkering at a deep system or hardware level just to LAUNCH the game, when I can see 100 pages of issues that people are experiencing IN the game, with STILL no solution? Out of one mess, into the next.

Personally speaking, if my issue was fixed tomorrow, I'd boot the game up in a heartbeat and try it out for myself, as I'm sure a lot of other people would. I'm incredibly frustrated that there is nothing I can do to get the game to launch. It did not at all help that CDPR rushed to release a PR statement for damage control on consoles, a situation they put themselves in, while giving PC gamers in situations like myself barely a glancing thought at the end of the post.

I'm not attacking you or anyone else in this forum. Again, you and the other mods have been great. Everyone here has been nothing but helpful. We need solutions, and if not that, updates on progress or reassurance that our issues have been seen and are being investigated.

Sure! And no one is denying that the game has issues. There are many, and I'm very sure they'll be sorted out over time. I'm not sure if you remember TW3 at launch, but there were all sorts of crashes, NPCs completely disappearing, enemies that would stop taking damage, broken quests and dialogue loops, inventory issues, shopkeepers who would suddenly stop selling things, huge performance slowdowns and stuttering...but...look at where it is today. Cyberpunk will be no different.

In the meantime, we have to troubleshoot as best we can and use whatever works. If people just don't want to be bothered with that, that's totally fine! And I fully understand the disappointment and frustration. But all the bitterness and upset in the world will not fix a single bug.

 

[SigilFey]

I have read the entirety of 98 pages of comments on this thread (if you can believe it), as well as many other internet forum posts, and have come to a conclusion that this game CANNOT RUN without directX 12 which can only be installed on a windows 10. As you can allude from my name, I run a fully updated windows 7 64bit ultimate with DX11, but I am unable to play this game.

Yup. That's precisely the situation that I had. Exactly the same manifestation of the bug. Whatever was done to bring DX12 to Windows 7, it isn't working universally, and there's no more support to be had for Win7.

Hence, yes, rather than continue fumbling around with it, I just upgraded to Windows 10. That did the trick (...and I must admit that Windows 10 is pretty dang slick. I couldn't stand Windows 8 / 8.1. I couldn't stand Windows 10 when it first came out. But this was the easiest Windows update / reinstall I've ever done. And things are working beautifully across the board.)

 

[abyssalsmoke]

You're right, many may have same issue but related to something different, but I think I learned quite a lot about my PC in last 3 days, I did Win update, driver reinstall, then DDU wipe, I disassembled my PC to check out my GPU and see if connection to PSU is proper, then switched my RAM slots on motherboard, updated my chipset, tried to boost my fan speed thinking that maybe cooling fan is an issue, I tried NVidia Debug mode, I did clean install on my Win10, I tried various fixes from AVX and Hex ones to the one where I change variables in config file. Nothing worked. Pc is 1 year old, and none of components were preowned, straight out of the box.

And its always this error:

Error reason: Unhandled exception
Expression: EXCEPTION_ACCESS_VIOLATION (0xC0000005)
Message: The thread attempted to read inaccessible data at 0x25C86BDDE60.
File: <Unknown>(0)

I'm frankly really tired of trying to figure out what does game precisely trying to access. I appreciate your and dev's work but I'm really at my wits end atm.

When you say you changed ram slots, did you try launching the game one piece of ram at a time.

 

[Missilebean]

Sure! And no one is denying that the game has issues. There are many, and I'm very sure they'll be sorted out over time. I'm not sure if you remember TW3 at launch, but there were all sorts of crashes, NPCs completely disappearing, enemies that would stop taking damage, broken quests and dialogue loops, inventory issues, shopkeepers who would suddenly stop selling things, huge performance slowdowns and stuttering...but...look at where it is today. Cyberpunk will be no different.

In the meantime, we have to troubleshoot as best we can and use whatever works. If people just don't want to be bothered with that, that's totally fine! And I fully understand the disappointment and frustration. But all the bitterness and upset in the world will not fix a single bug.

I don't disagree with you, and you make fair points! I played W3 at launch, and it's why I'm disappointed but not surprised by the CP2077 bugs. For some reason releasing a game in this condition, saying sorry, and taking a year to update it seems to be an acceptable practice in the industry now, and I have no idea why. Sure wouldn't fly at my job!

Can't change that though, so patience seems to be the only reasonable option...mostly because 5 days of troubleshooting has gotten me nothing