Installa Steam
Accedi
|
Lingua
简体中文 (cinese semplificato)
繁體中文 (cinese tradizionale)
日本語 (giapponese)
한국어 (coreano)
ไทย (tailandese)
Български (bulgaro)
Čeština (ceco)
Dansk (danese)
Deutsch (tedesco)
English (inglese)
Español - España (spagnolo - Spagna)
Español - Latinoamérica (spagnolo dell'America Latina)
Ελληνικά (greco)
Français (francese)
Indonesiano
Magyar (ungherese)
Nederlands (olandese)
Norsk (norvegese)
Polski (polacco)
Português (portoghese - Portogallo)
Português - Brasil (portoghese brasiliano)
Română (rumeno)
Русский (russo)
Suomi (finlandese)
Svenska (svedese)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraino)
Segnala un problema nella traduzione
Ok, I get it now. Have you tried just turning the overclocking off? Overclocking CAN lead to multiple problems even if it works for some games.
Edit: Did you also turn off Steam Cloud Save in the global Steam settings (NOT the individual game settings)?
yeah double checked the setting's in both, steam and valheim and its saving them by pressing OK.
ill do a test soon, as may of had a few windows updates after speaking to them about a old S-1-5 user showing up after re instillation not that this should be a problem.
my old account basically from what i can gather.
sorry if its been hard to follow i'm not a great at typing at the best of times and im trying to explain things as well as i can. i'm still learning about my PC every day, thanks for all the help so far.
English is actually not my native language, and although I do feel proficient at it, I sometimes have to ask again to make sure.
I would also not try to mess with any registry entries that you are not very familiar with. Please leave them alone for now. Thank you.
"unknown S-I-D" user (security identifier basically) is reminisce of malware/virus or could be a old user/account from rebooting, Either way that issue is fixed now and SID is now gone!
but still the same issue continues with this game!...
Seem's to only crash when i'm playing solo and crashing every hour roughly.
my mate with a 15 year old PC has 0 issue's.
I can play multiplayer FINE,with 0 issues!
The only thing i haven't tried is removing both down-clocking / overclocking a standard thing on most new/modern GPU's / CPU's nowadays.
This is the only suggestion i can find in other threads that i haven't tried!
(the things i find in common with other people with this issue) - (playing on a modern PC & having joined a multiplayer scenario and then have started experiencing the unity.DDL errors/crashes and do not have problems with other games that are much more demanding on the system).
Is this something a company should expect you to do because you own a up-to date PC?
is this possible to do for one specific game.
You still might want to run "Driver Verifier" to check if any of your drivers do misbehave (I know, you just re-installed your computer).
The only other thing I can think off right now is to check the event logs for info on why the game crashes.
Or you can check the "player.log" file, which you can reach by clicking on the button "Show Player.log" in the Valheim main menu.
I have recently went into my
- Power and sleep settings
- Additional power settings
- I am using the high performance option and "change plan setting"
- Changed advanced power setting
- Open the tab - Processor power management - Minimum power processor state - Change it from 100 % down to 95 % and do the same for the maximum processor state from 100% to down to 95%.
I have now been able to to play for the first time in months with out a crash so far in SOLO, as i never had any issue in multiplayer.
The reason i did this was due to getting (going medieval) another game handled by the unityplayer.dll causing crashes within the first few hours of game play.
This fix has also stopped all issues with both games although (Valheim) is still very stutters/fps drops way to often when roaming about.
I have only have these issue's with games using the unityplayer.dll and the only games to ever crash out on me.
just a side note : when playing on (Rust) another game handled by the unityplayer.dll it has never had a issues, But is server ran.so might be why i haven't had a issue so far.
sorry this has been such a long read just been trying to add as much information as possible.in the hope a dev might see it.
thanks to any one that has tried to help.
Just to indicate as I got a similar issue than you.
D3D.dll was unable to RenderTexture.
I tried many things, specially to change the graphisms effects.
I also trie your last solution as I'm am running in Windows' performance mode too.
Unfortunately it is still happening. Forcing a save with /save is working fine even if it induce a bit of stuttering (which is "normal").
So I'm still wondering what is happening.
I have find it is easier to replicate this freeze/crash on the moutain.
Saves and clouding seem fine for the Character and the World:
Specs:
- CPU: FX6300
- GPU: RADEON R9 NANO
- GPU: RADEON HD 7770 (unused for gaming, not detected by the game. I checked that)
MSI afterburner is running but only for the ventilation curves (and Valhei still crashes when it is not running anyway)GPU driver is up-to-date and alone (no old version installed).
At this point, I don't really know what is the issue (files are checked).
If the fault was really from Direct3D or Valheim, there would be a lot of people complaining.
It is a fairly small change to make, there may have been more in game setting i may have lowered that helped my situation but every setting is at medium and set to 60 fps 1920 x 1080p.
but make sure to undo the fix if it dose not work for you, kinda goes with out saying but it should only sacrifice a few fps overall if it is left at 95 %.
yes the d3d11 issue all points to outdated graphics drivers or Microsoft visual c++ when researching the problem but i am certain ALL my driver etc were up to date during this time.
- Windows updated
- Microsoft visuals c++ / direct x 11 (D3D11)
- NVIDIA drivers - clean install (this will reset some settings you may have set up for other games and possibly global settings) tried both ways Geforce updater & manually from the NVIDIA official pages.
- Valheim game files verified
I was able to play for 2 mouths fine when first purchasing the game and i could play solo or multiplayer with 0 issues getting to the 4th boss then left the game for a month.
It wasn't till returning to the game i started to face issue's. some updated around the time vulkan rending had been added had caused a bug and unfortunately crashed during a world save, corrupting the save,
It would load with everything explored on the map,but all 200 + hours of building had vanished.
I think i was just unlucky with the timing of the crash to desktop corrupting the world save.
but since said day.i have only been able to play multiplayer without crashing.
creating a new world in solo just ends with a unityplayer.dll crash to desktop happening.
even after a full reboot and both drives wiped and reinstalled/re partitioned EVERYTHING begin reinstalled.
The only other thing i have never tried is to remove all overclocks even the standard ones like the turbo boost features that on are most CPU's / GPU's nowadays.
This has been a fix for some in other forums, These people have also seemed to have tried pretty much everything and have gotten no where from what i have researched not just with the Valheim unityplayer.dll but in other unityplayer.dll ran/handled games like (going medieval) + (V rising) etc most steam games use it from what info can gather.
I run the standard feature's, never overclocked my system or ran MSI afterburner but have thought about it for the same reasons you have, for fan curve.
I may need to play Valheim more yet, i may have posted slightly prematurely but everything has stayed fairly stable so far in the few hours i have played.
i was never able to find the Valheim logs to see if the was a rendering issue, what yours looks like.i have seen some people having a issue with wolfs rendering in the game which would be in mountain biomes,but would have though they would name it a wolf and not (128 x 128 fmt 27 aa 1), error 0x887a0005 and not really quite sure what this is exactly other than a texture that cant render.
if you haven't already i would recommend
- Verify integratey of game files, (in steam)
- Disable apps to run in background from browsers like (google chrome,edge etc) usually in settings, system.
- Disable "background apps" in windows
- Disable steam cloud saves in both Valheim and steam and make sure to save the change's made by hitting the OK tab that is sometimes hidden by the page being to low on the desktop. NOT THE RED X this will not save any changes. (This can makes a slight difference to save times)
- Disable all overlays - steam , discord , Geforece / RADEON overlays.
- Reinstall Microsoft visuals c++ 2015 - 2018 i think the d3d11 could be part of this.
- Reinstalling graphics drivers, (maybe use a program like snappy driver just one that has been recommended to me in past) But this is a very controversial subject some say make sure to get all the latest drivers for everything using things like snappy driver etc, but these are sometimes not the most compatible and cause other problems with windows.
windows should download the most compatible drivers for your system automatically.
if its still not working you could also try
- Run command prompt as admin - SFC-ScanNow / SFC-HealthCheck-Up / SFC-RestoreHealth etc (this fixes missing/ corrupt windows files) you should also get a report if it has finds and replaces anything.
- Run command prompt as admin and run DISM cleanup.
you may have to look up the properly typed command.
but it sounds like you would have tried a lot of these methods if you are running it in windows 8 compatibility mode and full screen optimisations disabled and have even looked up some of the thing mentioned in this post.
have you ever ran mods in the past? i can see its not currently modded. just i know some file can be left outdated after some updates creating issues for people and read that a file might need to be deleted but not a subject i know a lot about as i a have never modded Valheim maybe something to look into if you do run mods.