Upgraded to RTX 4080. Now crashing.

[Spin-Around Boy]

I upgraded from a GTX 1080 to a RTX 4080 and now I'm getting crashes to the desktop quite regularly. Roughly after 30-mins to an hour.

I get an Unreal Engine report to send after the crash. Wondering if anyone else is experiencing this and possibly notifying of an issue, as I was totally fine with the GTX 1080.

I did a clean driver install. Other games seem to be working OK, so far, so I don't think it's the card... I hope... I even disabled the slight under-volt to my CPU as the 4080 will be demanding a bit more effort from it.

Ryzen 7 5800X (Stock settings)
32GB RAM
Windows 10

[Raptor85]

what's the report say? it should have info on what's causing the crash. I've played about 20 hours on a 4090/linux and had no issues so I don't think it's anything with the 4xxx series cards. Possibly bad shader cache due to the different card? try disabling shader caching and run it.

[Judas Iscariot]

What's the version of your NVIDIA drivers atm?

[Spin-Around Boy]

Originally posted by Raptor85:

what's the report say? it should have info on what's causing the crash. I've played about 20 hours on a 4090/linux and had no issues so I don't think it's anything with the 4xxx series cards. Possibly bad shader cache due to the different card? try disabling shader caching and run it.

There was a lot of shader compilation stutters after my first boot, with the new card, so I assumed it did it, itself, but I'll give it a try it manually.

Originally posted by Judas Iscariot:

What's the version of your NVIDIA drivers atm?

The newest drivers. 551.61. Did a clean install with the new card.

[КрендельФигов]

https://steamcommunity.com/app/1458140/discussions/0/4348858679334697657#c4348858679334744602

[Buzzzz]

I was going to say, check your virt mem.

[Spin-Around Boy]

Originally posted by Raptor85:

what's the report say? it should have info on what's causing the crash. I've played about 20 hours on a 4090/linux and had no issues so I don't think it's anything with the 4xxx series cards. Possibly bad shader cache due to the different card? try disabling shader caching and run it.

Thanks for the suggestion, but this didn't work.

Originally posted by КрендельФигов:

https://steamcommunity.com/app/1458140/discussions/0/4348858679334697657#c4348858679334744602

Yikes! Not too keen on eating up 32GB of my SSD for virtual memory, despite having 32GB of RAM, but I'll give this a try.

[Spin-Around Boy]

Originally posted by КрендельФигов:

https://steamcommunity.com/app/1458140/discussions/0/4348858679334697657#c4348858679334744602

I changed my virtual memory to 32GB and thought it might have worked but now I'm getting this message after a crash *facepalm*

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000030

user32
nvwgf2umx
D3D12Core
dxgi
gameoverlayrenderer64
RTSSHooks64
PenDriverPro_Win64_Shipping
kernel32
ntdll

[КрендельФигов]

1) I hope you increased the swapfile as I wrote above, exactly in FIXED SIZE MODE. (in other 'dynamic' mode the problem will remain).
2) Verify game in Steam. (mandatory)
3) Disable all kinds of upscale, DLSS and similar (RayTrace and similar). This can be an independent cause of the problem. (This is the main point)
3.1) Clarify all kinds of your graphics in-game settings.
4) It would be a good idea to take a screenshot of the error next time.
5) Before running Pacific Drive, it is advisable to close all unnecessary programs to save Ram.

PS Try to run in DX11 mode. The probability that it will help is great. {major point}

6) Remove all kinds of overclocking.
7) GPU can be checked via Furmark (10-15 minutes of test is enough), but I think that's not the point.

8) As a last resort: try to roll back drivers to the June drivers 536.40.
Moreover, problems with drivers older than 536.40 occur on both WIN10 and WIN11, and with the Resizable Bar disabled, and in general in any combination. 'There is an opinion' that problems are caused by the CPU side.
Drivers older than this version still seem to be 'compromised' in 'certain circles' of communication.

PSS
8) What kind of RAM do you have? What's the spec (full, full marketing name)? How many modules, frequency timings etc
Have you ever Testmem5 (1usmus v3 config) one test cycle?
9) Remove all under-volt. All components should be set to default modes and voltages.
The error you mentioned can be caused by similar actions with the specified frequency of occurrence (30 minutes to an hour). However, this temporal pattern can also be a sign of Ram instability.

[simon]

How did you remove the old drives for the 1080? If you just used the NVIDIA tool that could be the issue. You should safe boot your PC then use DDU to un-install the old drivers.

[Paul]

Guys, there is nothing wrong with his or anyone's computer.
It's a game bug.

[КрендельФигов]

Originally posted by Paul:

Guys, there is nothing wrong with his or anyone's computer.
It's a game bug.

I haven't had a single crash in 30 hours of play and most importantly, not a single bug even from those that became known.
WIN7 (DX11->Vulkan translator), GPU Drivers mid 2022; 5800X3D;
64GB DDR4-3600(2 modules), Fury (overclocked 16-19-19-39) {TestMem5 checked}; swapfile =16MB {to correctly terminate WIN7 in case of BSOD, which I don't have}; Sapphire 6750XT Nitro {Furmark checked}.
So everything is fine with the game.

[simon]

Originally posted by Paul:

Guys, there is nothing wrong with his or anyone's computer.
It's a game bug.

Its a possibility but the fact he just fitted a new GPU is also a likely cause of the issue.

[Spin-Around Boy]

Originally posted by КрендельФигов:

1) I hope you increased the swapfile as I wrote above, exactly in FIXED SIZE MODE. (in other 'dynamic' mode the problem will remain).
2) Verify game in Steam. (mandatory)
3) Disable all kinds of upscale, DLSS and similar (RayTrace and similar). This can be an independent cause of the problem. (This is the main point)
3.1) Clarify all kinds of your graphics in-game settings.
4) It would be a good idea to take a screenshot of the error next time.
5) Before running Pacific Drive, it is advisable to close all unnecessary programs to save Ram.

PS Try to run in DX11 mode. The probability that it will help is great. {major point}

6) Remove all kinds of overclocking.
7) GPU can be checked via Furmark (10-15 minutes of test is enough), but I think that's not the point.

8) As a last resort: try to roll back drivers to the June drivers 536.40.
Moreover, problems with drivers older than 536.40 occur on both WIN10 and WIN11, and with the Resizable Bar disabled, and in general in any combination. 'There is an opinion' that problems are caused by the CPU side.
Drivers older than this version still seem to be 'compromised' in 'certain circles' of communication.

PSS
8) What kind of RAM do you have? What's the spec (full, full marketing name)? How many modules, frequency timings etc
Have you ever Testmem5 (1usmus v3 config) one test cycle?
9) Remove all under-volt. All components should be set to default modes and voltages.
The error you mentioned can be caused by similar actions with the specified frequency of occurrence (30 minutes to an hour). However, this temporal pattern can also be a sign of Ram instability.

I did the virtual memory set exactly as you said. Fixed size. I've tried everything you've suggested above, except rolling back drivers. I've removed under volts and I'm now going to troubleshoot potential memory incompatibilities.

BUT...... Other games have started crashing, now, too... :( So, it's not a Pacific Drive issue, it seems. I have a lot of troubleshooting to do. Hope I don't have to RMA.

I should probably delete this post, soon, as it's nothing to do with Pacific Drive. Thanks for all the suggestions/help, so far, though.

[Buzzzz]

Originally posted by Spin-Around Boy:

Originally posted by КрендельФигов:

1) I hope you increased the swapfile as I wrote above, exactly in FIXED SIZE MODE. (in other 'dynamic' mode the problem will remain).
2) Verify game in Steam. (mandatory)
3) Disable all kinds of upscale, DLSS and similar (RayTrace and similar). This can be an independent cause of the problem. (This is the main point)
3.1) Clarify all kinds of your graphics in-game settings.
4) It would be a good idea to take a screenshot of the error next time.
5) Before running Pacific Drive, it is advisable to close all unnecessary programs to save Ram.

PS Try to run in DX11 mode. The probability that it will help is great. {major point}

6) Remove all kinds of overclocking.
7) GPU can be checked via Furmark (10-15 minutes of test is enough), but I think that's not the point.

8) As a last resort: try to roll back drivers to the June drivers 536.40.
Moreover, problems with drivers older than 536.40 occur on both WIN10 and WIN11, and with the Resizable Bar disabled, and in general in any combination. 'There is an opinion' that problems are caused by the CPU side.
Drivers older than this version still seem to be 'compromised' in 'certain circles' of communication.

PSS
8) What kind of RAM do you have? What's the spec (full, full marketing name)? How many modules, frequency timings etc
Have you ever Testmem5 (1usmus v3 config) one test cycle?
9) Remove all under-volt. All components should be set to default modes and voltages.
The error you mentioned can be caused by similar actions with the specified frequency of occurrence (30 minutes to an hour). However, this temporal pattern can also be a sign of Ram instability.

I did the virtual memory set exactly as you said. Fixed size. I've tried everything you've suggested above, except rolling back drivers. I've removed under volts and I'm now going to troubleshoot potential memory incompatibilities.

BUT...... Other games have started crashing, now, too... :( So, it's not a Pacific Drive issue, it seems. I have a lot of troubleshooting to do. Hope I don't have to RMA.

I should probably delete this post, soon, as it's nothing to do with Pacific Drive. Thanks for all the suggestions/help, so far, though.

Keep the post up.. It might help others...

Checking your ram is a good step.

[simon]

Originally posted by Spin-Around Boy:

I did the virtual memory set exactly as you said. Fixed size. I've tried everything you've suggested above, except rolling back drivers. I've removed under volts and I'm now going to troubleshoot potential memory incompatibilities.

BUT...... Other games have started crashing, now, too... :( So, it's not a Pacific Drive issue, it seems. I have a lot of troubleshooting to do. Hope I don't have to RMA.

I should probably delete this post, soon, as it's nothing to do with Pacific Drive. Thanks for all the suggestions/help, so far, though.

How did you uninstall are install the new GPU drivers when you put the new card in? Also i assume you actually un-installed the 1080 through device manger before putting in the new card.