win7 cant run this game ?

[zomblekingdom]

when i click play the game crush instantly and display stop responding error screen

[-shhfiftyfive]

if only steam achievements worked.
if only steam screenshots worked.
if only steam could track how many hours played...

i mean this is a steam game. those should work. i do hope cdpr fixes it soon.

i feel cheated, i don't want to play without the ability to take screenshots and complete achievements.

[Bloodycrow]

This is anecdotal, but I was able to play without experiencing more crashes by turning VSYNC on to 60. I had also turned volumetrics down to high and all shadows to medium.
Dunno why VSYNC would matter since I only have windowed or borderless window options, but it's what worked for me. Best of luck.

EDIT: That was 1.03, now crashing very often again on 1.04.

[HellSlayer]

IronsteffL님이 먼저 게시:

I'm playing on Win7 too and it runs pretty fine, but only on about medium settings. The biggest problem is some kind of corruption of the UserSettings.json in Appdata/Local/CD Projekt Red/Cyberpunk 2077 after changing options ingame. If I delete the file, enter the game and set Graphics on medium, I can play just fine without any glitches or crashes.

But if I decide to tweak graphic options (like shadow detail or dynamic resolution), it will show a black screen ingame and crash soon after, and the game starts crashing with a driver-error (AMD) right at the CDPR-logo. Until I delete the UserConfig.json, that is! Maybe that helps some of you.

This!!!
So much thanks bro.

I in menu reduced graphics to my liking aka all low.. and now not a single crash in almost 2hours, while before i couldnt play for a minute!!! im on win7 1070vga. im on gog version. I can use OVERLAYS and still no crashing. This solution is almost perfect i think.

[Mr blue]

Dayradon님이 먼저 게시:

Win 7 pro, 64b 32G ram, 8core 4Ghz proc. 1070ti, updated to latest vid drivers, Runs/Ran.

It does crash. it seems randomly. Made char, played first mission after training tutorial, crashed a 2nd time as soon as I picked up the body from the tub and told to carry her.

reboot, crashed as soon as trying to load, Nvidia overlay on top right hadn't finished displaying.
It is always a hard system lock. Have task manager/services open on 3rd screen, and all usage of anything freezes.

Found it. Guess their hotfix is causing unkown crashes in GPU's

ie:

Registered crash info file...
InternalVersion: 3.0.3214677 P4CL: 4155897 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
Line: 40

* also not sure why it's trying to use a DX12 file, since there is no DX12 card installed, no DX12 drivers loaded, and no DX12 features enabled in the game settings?

That was the second crash. The first one seems to be related to watchdog (that's their anti-cheat stuff isn't it?)

Registered crash info file...
InternalVersion: 3.0.3214677 P4CL: 4155897 Stream: /R6.Root/R6.Patch0Hotfix2
!!!CRASHED!!!
Error Reason: Assert
Expression:
Message: Watchdog timeout! (120 seconds)
File: e:\r6.patch0hotfix2\dev\src\common\engine\src\enginewatchdog.cpp
Line: 198

The third has no info as the game hadn't even loaded yet.

on these system specs it only say windows 7 under 1080p low so if it can only be played on low with windows 7 try playing on low

https://cdn-l-mkt.cdprojektred.com/image/16_9_EN_3-_02qt7qdkx3b50kqk.jpg

[-shhfiftyfive]

Mr blue님이 먼저 게시:

Dayradon님이 먼저 게시:

Win 7 pro, 64b 32G ram, 8core 4Ghz proc. 1070ti, updated to latest vid drivers, Runs/Ran.

It does crash. it seems randomly. Made char, played first mission after training tutorial, crashed a 2nd time as soon as I picked up the body from the tub and told to carry her.

reboot, crashed as soon as trying to load, Nvidia overlay on top right hadn't finished displaying.
It is always a hard system lock. Have task manager/services open on 3rd screen, and all usage of anything freezes.

Found it. Guess their hotfix is causing unkown crashes in GPU's

ie:

Registered crash info file...
InternalVersion: 3.0.3214677 P4CL: 4155897 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
Line: 40

* also not sure why it's trying to use a DX12 file, since there is no DX12 card installed, no DX12 drivers loaded, and no DX12 features enabled in the game settings?

That was the second crash. The first one seems to be related to watchdog (that's their anti-cheat stuff isn't it?)

Registered crash info file...
InternalVersion: 3.0.3214677 P4CL: 4155897 Stream: /R6.Root/R6.Patch0Hotfix2
!!!CRASHED!!!
Error Reason: Assert
Expression:
Message: Watchdog timeout! (120 seconds)
File: e:\r6.patch0hotfix2\dev\src\common\engine\src\enginewatchdog.cpp
Line: 198

The third has no info as the game hadn't even loaded yet.

on these system specs it only say windows 7 under 1080p low so if it can only be played on low with windows 7 try playing on low

https://cdn-l-mkt.cdprojektred.com/image/16_9_EN_3-_02qt7qdkx3b50kqk.jpg

that is failed logic.
i play on ultra with my windows 7.
windows 7 is supported, else it wouldn't be included in the minimum. of course it isn't recommended because it is old. that is all.

[- Guarana]

i refunded with 4h of game time and actually got my money within hours!
i like that CD project!
i will try the game again once the issues are resolved!

[joviper]

After the update, I tried it again by launching the game directly and skipping the launcher as admin, managed to get past the mirror crash and save the game, only crashed once after leaving V's apartment, no further crashes.

[L00]

Win7 pro / GTX1080 / 16gb, mostly everything on High some on Ultra, found that the random crash to desktop I had (460.79 Nvidia drivers crashing) occurs much less if I delete the cache file in : C:\Users\**your_username**\AppData\Local\CD Projekt Red\Cyberpunk 2077\cache
Also, I disabled my secondary monitor which seems to have helped a whole lot

[Metabunker]

L00님이 먼저 게시:

Win7 pro / GTX1080 / 16gb, mostly everything on High some on Ultra, found that the random crash to desktop I had (460.79 Nvidia drivers crashing) occurs much less if I delete the cache file in : C:\Users\**your_username**\AppData\Local\CD Projekt Red\Cyberpunk 2077\cache
Also, I disabled my secondary monitor which seems to have helped a whole lot

Same specs as you; never managed to launch the game. Not with the launcher, not with the game exe, not normally, not in Win 7 compatibility mode, not as administrator, not before the patch, not after...

The game freezes on CDPR logo every time and leaves a process (1,8 Gb) that cannot be removed even with task manager so I have to reboot the computer.

[0x57A1CFA117]

so I tried this game on my desktop (Win. 8.1 with all available updates), and "WOAH" message shortly after clicking play (and I've tried all of the various suggestions), I rtied it on my laptop (Win 7 with all available updates) and I don't get the "WOAH" message, it just acts like it never runs.

I deciding to try running it through WinDBG to see if there was some stupid simple setting somewhere that somehow got activated that shouldn't be. I did a couple of things and found something that MAY indicate a direction of interest...

CommandLine: "F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\Cyberpunk2077.exe"

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred http://msdl.microsoft.com/download/symbols
Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
ModLoad: 00000001`3f370000 00000001`442e7000 cpLauncher.exe
ModLoad: 00000000`77950000 00000000`77aef000 ntdll.dll
ModLoad: 00000000`77830000 00000000`7794f000 C:\Windows\system32\kernel32.dll
ModLoad: 000007fe`fd720000 000007fe`fd787000 C:\Windows\system32\KERNELBASE.dll
ModLoad: 00000000`77730000 00000000`7782b000 C:\Windows\system32\USER32.dll
ModLoad: 000007fe`ff7b0000 000007fe`ff817000 C:\Windows\system32\GDI32.dll
ModLoad: 000007fe`fe620000 000007fe`fe62e000 C:\Windows\system32\LPK.dll
ModLoad: 000007fe`ff820000 000007fe`ff8eb000 C:\Windows\system32\USP10.dll
ModLoad: 000007fe`fdcc0000 000007fe`fdd5f000 C:\Windows\system32\msvcrt.dll
ModLoad: 000007fe`deec0000 000007fe`df0a3000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\dbghelp.dll
ModLoad: 000007fe`f0960000 000007fe`f0964000 C:\Windows\system32\api-ms-win-crt-string-l1-1-0.dll
ModLoad: 000007fe`f09d0000 000007fe`f0ac4000 C:\Windows\system32\ucrtbase.DLL
ModLoad: 000007fe`f09c0000 000007fe`f09c3000 C:\Windows\system32\api-ms-win-core-timezone-l1-1-0.dll
ModLoad: 000007fe`f09b0000 000007fe`f09b3000 C:\Windows\system32\api-ms-win-core-file-l2-1-0.dll
ModLoad: 000007fe`f09a0000 000007fe`f09a3000 C:\Windows\system32\api-ms-win-core-localization-l1-2-0.dll
ModLoad: 000007fe`fc1e0000 000007fe`fc1e3000 C:\Windows\system32\api-ms-win-core-synch-l1-2-0.dll
ModLoad: 000007fe`f0990000 000007fe`f0993000 C:\Windows\system32\api-ms-win-core-processthreads-l1-1-1.dll
ModLoad: 000007fe`f0980000 000007fe`f0983000 C:\Windows\system32\api-ms-win-core-file-l1-2-0.dll
ModLoad: 000007fe`f0920000 000007fe`f0923000 C:\Windows\system32\api-ms-win-crt-time-l1-1-0.dll
ModLoad: 000007fe`f0870000 000007fe`f0873000 C:\Windows\system32\api-ms-win-crt-locale-l1-1-0.dll
ModLoad: 000007fe`f0ad0000 000007fe`f0ad4000 C:\Windows\system32\api-ms-win-crt-runtime-l1-1-0.dll
ModLoad: 000007fe`f9890000 000007fe`f98a0000 C:\Windows\system32\api-ms-win-crt-private-l1-1-0.dll
ModLoad: 000007fe`f9850000 000007fe`f9854000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\api-ms-win-downlevel-kernel32-l2-1-0.dll
ModLoad: 000007fe`fd3d0000 000007fe`fd3dc000 C:\Windows\system32\VERSION.dll
ModLoad: 00000000`000d0000 00000000`000ee000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\XINPUT1_3.dll
ModLoad: 000007fe`ffb60000 000007fe`ffc3b000 C:\Windows\system32\ADVAPI32.dll
ModLoad: 000007fe`fdde0000 000007fe`fddff000 C:\Windows\SYSTEM32\sechost.dll
ModLoad: 000007fe`fd970000 000007fe`fda9c000 C:\Windows\system32\RPCRT4.dll
ModLoad: 000007fe`ff920000 000007fe`ffaf7000 C:\Windows\system32\SETUPAPI.dll
ModLoad: 000007fe`fd4c0000 000007fe`fd4f6000 C:\Windows\system32\CFGMGR32.dll
ModLoad: 000007fe`fdb40000 000007fe`fdc1b000 C:\Windows\system32\OLEAUT32.dll
ModLoad: 000007fe`ff5b0000 000007fe`ff7af000 C:\Windows\system32\ole32.dll
ModLoad: 000007fe`fd840000 000007fe`fd85a000 C:\Windows\system32\DEVOBJ.dll
ModLoad: 000007fe`ceb00000 000007fe`ced88000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\icuin.dll
ModLoad: 000007fe`dbf80000 000007fe`dc154000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\icuuc.dll
ModLoad: 000007fe`f97c0000 000007fe`f97c3000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\icudt.dll
ModLoad: 000007fe`f0880000 000007fe`f091b000 C:\Windows\system32\MSVCP140.dll
ModLoad: 000007fe`f0ae0000 000007fe`f0af5000 C:\Windows\system32\VCRUNTIME140.dll
ModLoad: 000007fe`f0970000 000007fe`f0973000 C:\Windows\system32\api-ms-win-crt-heap-l1-1-0.dll
ModLoad: 000007fe`f0950000 000007fe`f0954000 C:\Windows\system32\api-ms-win-crt-stdio-l1-1-0.dll
ModLoad: 000007fe`f0940000 000007fe`f0944000 C:\Windows\system32\api-ms-win-crt-convert-l1-1-0.dll
ModLoad: 000007fe`f0860000 000007fe`f0865000 C:\Windows\system32\api-ms-win-crt-math-l1-1-0.dll
ModLoad: 000007fe`f0850000 000007fe`f0853000 C:\Windows\system32\api-ms-win-crt-filesystem-l1-1-0.dll
ModLoad: 000007fe`f0930000 000007fe`f0933000 C:\Windows\system32\api-ms-win-crt-environment-l1-1-0.dll
ModLoad: 000007fe`f0840000 000007fe`f0843000 C:\Windows\system32\api-ms-win-crt-utility-l1-1-0.dll
ModLoad: 000007fe`cde20000 000007fe`ceafe000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\Galaxy64.dll
ModLoad: 000007fe`fe7d0000 000007fe`fe81d000 C:\Windows\system32\WS2_32.dll
ModLoad: 000007fe`fe630000 000007fe`fe638000 C:\Windows\system32\NSI.dll
ModLoad: 000007fe`fcd80000 000007fe`fcda2000 C:\Windows\system32\bcrypt.dll
ModLoad: 000007fe`fde00000 000007fe`fe2ac000 C:\Windows\system32\WININET.dll
ModLoad: 000007fe`fd700000 000007fe`fd704000 C:\Windows\system32\api-ms-win-downlevel-user32-l1-1-0.dll
ModLoad: 000007fe`fd6f0000 000007fe`fd6f4000 C:\Windows\system32\api-ms-win-downlevel-shlwapi-l1-1-0.dll
ModLoad: 000007fe`fdd60000 000007fe`fddd1000 C:\Windows\system32\shlwapi.DLL
ModLoad: 000007fe`fd6e0000 000007fe`fd6e4000 C:\Windows\system32\api-ms-win-downlevel-version-l1-1-0.dll
ModLoad: 000007fe`fd790000 000007fe`fd793000 C:\Windows\system32\api-ms-win-downlevel-normaliz-l1-1-0.dll
ModLoad: 00000000`77b00000 00000000`77b03000 C:\Windows\system32\normaliz.DLL
ModLoad: 000007fe`fe2b0000 000007fe`fe57c000 C:\Windows\system32\iertutil.dll
ModLoad: 000007fe`fd710000 000007fe`fd715000 C:\Windows\system32\api-ms-win-downlevel-advapi32-l1-1-0.dll
ModLoad: 000007fe`fd510000 000007fe`fd52f000 C:\Windows\system32\USERENV.dll
ModLoad: 000007fe`fd4b0000 000007fe`fd4bf000 C:\Windows\system32\profapi.dll
ModLoad: 000007fe`fd570000 000007fe`fd6dd000 C:\Windows\system32\CRYPT32.dll
ModLoad: 000007fe`fd4a0000 000007fe`fd4af000 C:\Windows\system32\MSASN1.dll
ModLoad: 000007fe`f9430000 000007fe`f9457000 C:\Windows\system32\IPHLPAPI.DLL
ModLoad: 000007fe`f9420000 000007fe`f942b000 C:\Windows\system32\WINNSI.DLL
ModLoad: 000007fe`fe820000 000007fe`ff5ab000 C:\Windows\system32\SHELL32.dll
ModLoad: 000007fe`fcb80000 000007fe`fcbd5000 C:\Windows\system32\MSWSOCK.dll
ModLoad: 000007fe`f96a0000 000007fe`f96ab000 C:\Windows\system32\HID.DLL
ModLoad: 000007fe`f9740000 000007fe`f97bd000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\bink2w64.dll
ModLoad: 000007fe`f9ec0000 000007fe`f9efb000 C:\Windows\system32\WINMM.dll
ModLoad: 000007fe`cf2f0000 000007fe`cf4e9000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\PhysX3Common_x64.dll
ModLoad: 000007fe`dc480000 000007fe`dc50f000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\PhysX3CharacterKinematic_x64.dll
ModLoad: 000007fe`dbef0000 000007fe`dbf7b000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\PxFoundation_x64.dll
ModLoad: 000007fe`dbbb0000 000007fe`dbc55000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\PhysX3Cooking_x64.dll
ModLoad: 000007fe`cd5f0000 000007fe`cd873000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\PhysX3_x64.dll
ModLoad: 000007fe`d9850000 000007fe`d9a51000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\NRD.dll
ModLoad: 000007fe`ed920000 000007fe`ed93e000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\redlexer_native.dll
ModLoad: 000007fe`fb8a0000 000007fe`fb8cc000 C:\Windows\system32\POWRPROF.dll
ModLoad: 000007fe`f8f00000 000007fe`f90d5000 C:\Windows\system32\d3d11.dll
ModLoad: 000007fe`f8ea0000 000007fe`f8efd000 C:\Windows\system32\dxgi.dll
ModLoad: 000007fe`fb880000 000007fe`fb898000 C:\Windows\system32\dwmapi.dll
ModLoad: 000007fe`ed870000 000007fe`ed8db000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\libcurl.dll
ModLoad: 000007fe`ffb00000 000007fe`ffb52000 C:\Windows\system32\WLDAP32.dll
ModLoad: 000007fe`ee1f0000 000007fe`ee21d000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\amd_ags_x64.dll
ModLoad: 000007fe`cf1b0000 000007fe`cf2e3000 F:\GoG Galaxy\Games\Cyberpunk 2077\bin\x64\oo2ext_7_win64.dll
(4104.6254): Break instruction exception - code 80000003 (first chance)
ntdll!LdrpDoDebuggerBreak+0x30:
00000000`779f6bb0 cc int 3

0:000> gn

ModLoad: 000007fe`fd350000 000007fe`fd3a7000 C:\Windows\system32\apphelp.dll
ModLoad: 000007fe`ff8f0000 000007fe`ff91e000 C:\Windows\system32\IMM32.DLL
ModLoad: 000007fe`fd860000 000007fe`fd96b000 C:\Windows\system32\MSCTF.dll
ModLoad: 000007fe`fd3e0000 000007fe`fd410000 C:\Windows\system32\nvinitx.dll
ModLoad: 00000000`747a0000 00000000`747a6000 C:\Program Files\NVIDIA Corporation\CoProcManager\detoured.dll
ModLoad: 000007fe`f8be0000 000007fe`f8c18000 C:\Program Files\NVIDIA Corporation\CoProcManager\nvd3d9wrapx.dll
ModLoad: 000007fe`f8770000 000007fe`f8794000 C:\Program Files\NVIDIA Corporation\CoProcManager\nvdxgiwrapx.dll
ModLoad: 000007fe`fd2a0000 000007fe`fd2af000 C:\Windows\system32\cryptbase.dll
ModLoad: 000007fe`fd350000 000007fe`fd3a7000 C:\Windows\system32\apphelp.dll
ModLoad: 00000000`00510000 00000000`00556000 REDEngineErrorReporter.exe
ModLoad: 000007fe`fe580000 000007fe`fe619000 C:\Windows\system32\CLBCatQ.DLL
ModLoad: 000007fe`f9b60000 000007fe`f9b6e000 C:\Windows\system32\wbem\wbemprox.dll
ModLoad: 000007fe`f9ae0000 000007fe`f9b5d000 C:\Windows\system32\wbemcomn2.dll
ModLoad: 000007fe`fcbe0000 000007fe`fcbf8000 C:\Windows\system32\CRYPTSP.dll
ModLoad: 000007fe`fc8e0000 000007fe`fc927000 C:\Windows\system32\rsaenh.dll
ModLoad: 000007fe`fd3b0000 000007fe`fd3c4000 C:\Windows\system32\RpcRtRemote.dll
ModLoad: 000007fe`eea00000 000007fe`eea14000 C:\Windows\system32\wbem\wbemsvc.dll
ModLoad: 000007fe`eea20000 000007fe`eeaf4000 C:\Windows\system32\wbem\fastprox.dll
ModLoad: 000007fe`eed00000 000007fe`eed27000 C:\Windows\system32\NTDSAPI.dll
ModLoad: 000007fe`fbeb0000 000007fe`fbf06000 C:\Windows\system32\uxtheme.dll
ModLoad: 000007fe`e6c10000 000007fe`e6cf9000 C:\Program Files (x86)\Stardock\Fences\FencesMenu64.dll
ModLoad: 000007fe`fc660000 000007fe`fc671000 C:\Windows\system32\WTSAPI32.dll
ModLoad: 000007fe`fb470000 000007fe`fb689000 C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.24542_none_1459e0f08b91b367\gdiplus.dll
ModLoad: 000007fe`ef590000 000007fe`ef5ba000 C:\Program Files (x86)\Stardock\Multiplicity\MPHlp64.dll
ntdll!ZwTerminateProcess+0xa:
00000000`779b9a6a c3 ret

0:000> knL

# Child-SP RetAddr Call Site
00 00000000`0031fb38 00000000`7798c1bb ntdll!ZwTerminateProcess+0xa
*** ERROR: Symbol file could not be found. Defaulted to export symbols for cpLauncher.exe -
01 00000000`0031fb40 00000001`41c6b4b5 ntdll!RtlExitUserProcess+0x9b
02 00000000`0031fb70 00000001`41c6b46b cpLauncher!AK::WriteBytesMem::Clear+0x2143f35
03 00000000`0031fba0 00000001`3f51a8a8 cpLauncher!AK::WriteBytesMem::Clear+0x2143eeb
04 00000000`0031fc00 00000001`3f51af6e cpLauncher+0x1aa8a8
05 00000000`0031fc30 00000000`7784556d cpLauncher+0x1aaf6e
06 00000000`0031fc70 00000000`779a372d kernel32!BaseThreadInitThunk+0xd
07 00000000`0031fca0 00000000`00000000 ntdll!RtlUserThreadStart+0x1d

0:000> .fnent 00000001`41c6b46b

Debugger function entry 00000000`04e5c278 for:
(00000001`3fb27580) cpLauncher!AK::WriteBytesMem::Clear+0x2143eeb | (00000001`41d898b0) cpLauncher!NVSDK_NGX_Parameter_GetD

BeginAddress = 00000000`028fb3b0
EndAddress = 00000000`028fb46c
UnwindInfoAddress = 00000000`0375e4a8

Unwind info at 00000001`42ace4a8, c bytes
version 1, flags 0, prolog 16, codes 4
00: offs 16, unwind op 4, op info 3 UWOP_SAVE_NONVOL FrameOffset: 60 reg: rbx.
02: offs 16, unwind op 2, op info 9 UWOP_ALLOC_SMALL.
03: offs f, unwind op 0, op info 5 UWOP_PUSH_NONVOL reg: rbp.

When I look up "NVSDK_NGX_Parameter_GetD" (looking at the naming convention, I knew it was some sort of nVidia related SDK) I wind up with:
https://docs.nvidia.com/rtx/ngx/programming-guide/index.html#setting-parms
[/quote]

(For those that don't know) apparently, as per: https://docs.nvidia.com/rtx/ngx/programming-guide/index.html#introduction

NVIDIA NGX makes it easy for you to integrate pre-built AI based features into your applications. NVIDIA will be adding new features and also updating the existing ones over time. When an existing feature is updated, the NGX infrastructure will update the feature on all clients that uses it.

There are three main components that make up the system:
NGX SDK
The NGX SDK provides CUDA and DX11/12 APIs for applications to access the AI features.
NGX Core Runtime
All runtime modules are provided with the NVIDIA Graphics Driver that supports RTX hardware. During an advanced driver installation the module is called NGX Core.
NGX Update Module
This module ensures that NGX integrated applications always use the latest version of the NGX features.

I wouldn't have made the connection between AI, and raytracing, but it seems it has something to do with their RTX code (and it even actually makes sense -- the overlap between the two I mean).

I even already have Raytracing (all settings of it) off, as well as DLSS
(the options.json file located in F:\GoG Galaxy\Games\Cyberpunk 2077\r6\config\settings\platform\pc -- the location for MY settings, different for others).

When I look more through the documentation (under the 5. NGX Features -- https://docs.nvidia.com/rtx/ngx/programming-guide/index.html#dlss), I see

5.1 DLSS -- Deep Learning SUper Sampling (DirectX only) and see this description:

DLSS is a new technique developed by NVIDIA Research to apply very high quality image sharpening, enhancement, and optionally, super-resolution to frames rendered by 3D engines and games. This technique uses an autoencoder to extract high dimensional features from the frame and then reconstructs the image with added details and with increased resolution.

DLSS is currently in a closed beta release. NVIDIA is working with partners to enable DLSS in a range of DirectX games. For more information, contact us at [e-mail].

Apparently, (I say apparently, because I'm not familiar with nVidia's NGX sdk), the NGX framework uses AI to perform sharpening of an image. With all of this disabled in options.json, I feel like this shouldn't even be an issue. I also find it interesting, it says DLSS is currently in closed beta release. Cool, so we're LITERALLY being beta testers (unless this is old documentation but I don't think it is)...

[Forevermuffins]

0x57A1CFA117님이 먼저 게시:

...

Game is messed up, but it can only run on windows 7 and 10 , which was your initial issue.

[0x57A1CFA117]

Yeah, that was something I was wondering about... It's a weird situation... Win 8.1 won't work because MS never back-ported DX12 to 8, but they did for 7. Which suuuucks because my main desktop has a 1050 TI (Granted it's not a 1080) and my laptop is on a GTX 980m (which is nice but being a mobile version is most likely not nearly the same as a 1050 Ti.

I'd also like to add, if it hasn't been said already, that reasons for the INVALID_INSTRUCTION exception is DIFFERENT than the ACCESS_VIOLATION. Two SEPARATE issues. Invalid instruction (as has been mentioned) is because the CPU it's being run on doesn't contain the circuitry and micro-code to support the AVX instruction set (think MMX only much newer), hence the invalid instruction bit. The ACCESS_VIOLATION error I'm not sure where that's coming from, and I think that's the million dollar question :/

[fun guy]

0x57A1CFA117님이 먼저 게시:

Yeah, that was something I was wondering about... It's a weird situation... Win 8.1 won't work because MS never back-ported DX12 to 8, but they did for 7. Which suuuucks because my main desktop has a 1050 TI (Granted it's not a 1080) and my laptop is on a GTX 980m (which is nice but being a mobile version is most likely not nearly the same as a 1050 Ti.

I'd also like to add, if it hasn't been said already, that reasons for the INVALID_INSTRUCTION exception is DIFFERENT than the ACCESS_VIOLATION. Two SEPARATE issues. Invalid instruction (as has been mentioned) is because the CPU it's being run on doesn't contain the circuitry and micro-code to support the AVX instruction set (think MMX only much newer), hence the invalid instruction bit. The ACCESS_VIOLATION error I'm not sure where that's coming from, and I think that's the million dollar question :/

980m is faster than the 1050 Ti

[0x57A1CFA117]

Damn... Is it really? lol Sweet! I take that as one win :P Now if only the game could actually start lol

I always thought the mobile versions had shredded core counts (i.e. < cores than desktop -- within reason obviously).

[fun guy]

I have not tested this yet, but this appears to fix 8.x compatiblity, and might fix crashes, at least for AMD users. Maybe Nvidia Vulkan beta drivers could work too, but idk.
https://msfn.org/board/topic/182104-directx-12-update/?tab=comments#comment-1192461