Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://support.microsoft.com/en-us/topic/the-latest-supported-visual-c-downloads-2647da03-1eea-4433-9aff-95f26a218cc0
Visual Studio 2015, 2017 and 2019
Download the Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019. The following updates are the latest supported Visual C++ redistributable packages for Visual Studio 2015, 2017 and 2019. Included is a baseline version of the Universal C Runtime see MSDN for details.
Try the first 2 on 64bit you need both.
x86: vc_redist.x86.exe
x64: vc_redist.x64.exe
----------------------------------------
ARM64: vc_redist.arm64.exe
Lets see if thats enough. with only Visual Studio 2015, 2017 and 2019
this was a cross search last time 0xc00007b with another steam user , and found solution on Origin and user got its game to work again. so ofc i accect that as first ID or VC++ issue before that it was all diffrent no point on something
did you reboot after this is just a check. so MS OS dont have correct it ( see it as old most reboot after apply even it dont say so. )
dont forget we have seen no other ID then VC++ issue.
ps.
Try old tech ways unintstall them and then ass Repair it instead.
do it on Both x86 & x64
feel free to contact own Bethesda, its actual games devs job whats going on with thirdpart app they using, same can be said with steam support with common steam redistibutable files.
and one of them including MS visual studio is the culprint.
and it make sense why user have hard to ID what that code cover.
im just a user like you, check other games might be wish from saem release era and hope you can get more crash issue with game. because if you dont, all this will be seen as user faulth. yeap its hard words , but dont forget 1 billion steam user and yuor feel alone right now,
then under 100 steam user this is not even a minor issue.
this is my point it seem to work for all other except 1 or 2 every month or so.
dont have forgot the i have game requirements or installed graphic card . even that will trigger that code if your pc cant handle it.
even that is also seen with this bug code.
i bet oldrim is working.
dont feel shame if thats the case , even that will help all helpers here tell it as it is.
because with no information from user and you also help all other next time.
its sign off user pc cant do it. ( even this make sense , then through a piece of code at ppl face noone knows what stand for.) we dont have MS code book or app that complain over it.
check up on all GPU Related issue, ask again if you dont understand what i write , i bet other Helper here has a idea what im trying to say.
Here are my system specs from the system information:
Computer Information:
Manufacturer: System manufacturer
Model: System Product Name
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
CPU Family: 0x6
CPU Model: 0x9e
CPU Stepping: 0xa
CPU Type: 0x0
Speed: 3696 Mhz
12 logical processors
6 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Unsupported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Windows 10 (64 bit)
NTFS: Supported
Crypto Provider Codes: Supported 311 0x0 0x0 0x0
Video Card:
Driver: Radeon (TM) RX 480 Graphics
DirectX Driver Name: aticfx32.dll
Driver Version: 27.20.14501.18003
DirectX Driver Version: 27.20.14501.18003
Driver Date: 11 13 2020
OpenGL Version: 4.6
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 75 Hz
DirectX Card: Radeon (TM) RX 480 Graphics
VendorID: 0x1002
DeviceID: 0x67df
Revision: 0xc7
Number of Monitors: 2
Number of Logical Video Cards: 2
No SLI or Crossfire Detected
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 3840 x 1080
Primary Display Size: 21.42" x 11.93" (24.49" diag)
54.4cm x 30.3cm (62.2cm diag)
Primary Bus Type Not Detected
Primary VRAM Not Detected
Supported MSAA Modes: 2x 4x 8x
Sound card:
Audio device: Lautsprecher (Realtek High Defi
Memory:
RAM: 16325 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
Media Type: Undetermined
Total Hard Disk Space Available: 3814800 Mb
Largest Free Hard Disk Block: 1906413 Mb
OS Install Date: Jan 01 1970
Game Controller: None detected
MAC Address hash: cd0046f1a15405977d0ee34cca437fd0bbdccf7a
Disk serial number hash: c96e61ea
There's also the following if SFC returns without any answers: "DISM /Online /Cleanup-Image /CheckHealth"
And, just because command prompt freaks out some people, neither of these can damage anything - they are basically diagnostic tools. These might point you into a better direction if there is a deeper WIn10 related issue and some of those Win10 can fix itself. If you decide to reinstall Windows this might give you an idea of where things went pearshaped.
Edit: Oh and to get to Command Prompt, the fastest way is just to search for "cmd" in the taskbar and run it as administrator.
now let us try debug it , and thx to bee for join. if we even can help
I need to check mine. I wasn't even born then...time travel...is real...
Number of Logical Video Cards: 2 <------ 2 cards or another IGPU )
No SLI or Crossfire Detected <---- have you update GPU driver that disable its croosfire
i did not say it is a issue, try ruleout its not that, might help you better,
1 monitor + what is other card or combi card maybe ?.
dont forget , seen odd multi monitor issue before , and somtimes its old ways that can be a issue.
point is check with 1 Monitor only , and whatever that is 2 GPU card you have ?
in the old days this was know as factory bios
and most of them requre update for all later bugs they discover. ( or support for new hardware )
i had same issue with my 2 sli nvidia card on every update it turn off sli. from the past
but i never get 0xc00007b just laggy game
this was to oldrim , some of use out of the blue got issue with game and later it bite our butt with them on.