Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
Yeah its not literally ancient but a good few folks consider anything from more than 2 generations ago as 'ancient' for a gaming pc lol. I was expecting my PSU to not be able to cut it when I upgraded from a 1070 to a 3080 as a 750W PSU is the minimum recommended and I was expecting that all my RGB goodness and 6 drives to push it past what my PSU could deliver but it's been perfectly fine thankfully
Ed:Typo
Thats because the CPU is 95W +/- and the 3080 is around 350W
SSDs dont use much energy, HDDs use anywhere from 6-9W each, so lets say 60W for 6 HDDs, add some RGB and its still plenty under. 750W recommended is for total system wattage to be on the safe side, so you are pretty much within range
I definitely feel like it was a driver issue for me. Still not really sure how or why. But I wanted to post this as a possible solution for others.
Ryzen 5 5800X3D
AMD 6900xt (latest drivers)
32GB ram
playing from Nvme ssd
Never happened with other games, only with Starfield and only in Neon so far.
Dunno if it's a driver problem or it's Bethesda fault but stop saying it's a faulty hardware issue, too many ppl are struggling with this.
Same could be said for the socket the PC in plugged into, aged power sockets can cause similar issues.
It happened once when coming out from the menu, in the streets, once after a loading screen coming out of a store and once just walking down the streets. 3 times in the last 24h.
The PC just shuts down like it was a power cut, then when I turn it on again is like nothing happened.
I looked in the eventviewer logs of the last 24h but i couldn't find anything relevant in the times of the shut downs. I have only one kernel error "Session Microsoft.Windows.Remediation failed to start with the following error: 0xC0000035" but the time doesn't match.
If it happens again today I'll check the eventviewer more thoroughly.
You can prevent this by limiting your FPS in AMD Software menu, undervolting your GPU and disabling and kinds of overclocking things.
Expensive PSU with Titanium certification (6 years old, bought along RX Vega 64 GPU), AMD RX 6900XT GPU (bought in february 2021) and this is first and only game (or program) that is triggering system shutdown. I was unable to reproduce it in any other scenario (even to the point when I've overheated VRMs on MB to 115*C (B350 MB with 3800XT CPU) the system was still stable).
But I'm also an electronic engineer and I will not BS myself - it's a PSU problem. Current spikes generated by GPU are the most probably cause.
Why PC shutdown is triggered only in Starfield? I don't know.
I've tried many software solutions (default GPU settings, reducing it's Power Limits) and I've found solution that works for me (on RX 6900XT GPU) - reducing Max Frequency to 2500MHz (while undervoltaged to 1110mV). It allowed me to maintain VRAM 2130MHz and Power Limit +15%. No more PC shutdown in Starfield. If I raise the GPU Max Frequency even by 50MHz - shutdowns are back.
So for AMD 6900XT GPU I'm recommending reducing Max Frequency to reduce current spikes. 2500MHz max frequency limit (with 1.110mV UV) works for my setup, but for other PC builds this values will surelly needs to be tweaked.