Steam 설치
로그인
|
언어
简体中文(중국어 간체)
繁體中文(중국어 번체)
日本語(일본어)
ไทย(태국어)
Български(불가리아어)
Čeština(체코어)
Dansk(덴마크어)
Deutsch(독일어)
English(영어)
Español - España(스페인어 - 스페인)
Español - Latinoamérica(스페인어 - 중남미)
Ελληνικά(그리스어)
Français(프랑스어)
Italiano(이탈리아어)
Bahasa Indonesia(인도네시아어)
Magyar(헝가리어)
Nederlands(네덜란드어)
Norsk(노르웨이어)
Polski(폴란드어)
Português(포르투갈어 - 포르투갈)
Português - Brasil(포르투갈어 - 브라질)
Română(루마니아어)
Русский(러시아어)
Suomi(핀란드어)
Svenska(스웨덴어)
Türkçe(튀르키예어)
Tiếng Việt(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
Thanks again by the way for the help.
Which vary from config to config...
You will want to fully Disable the WHQL Checking in WinOS before attempting to use any Beta / Non-WHQL Drivers firstly though. Here's how to do that:
https://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers
Then be sure to fully wipe out current Drivers using the DDU app.
https://www.wagnardsoft.com/forums/viewtopic.php?f=5&t=921
Please note that when you wipe out Drivers with DDU, while it is mainly just for clean wiping all GPU Drivers to avoid issues, it can wipe out Motherboard Chipset Drivers as well. Which is not a problem, just install the latest for the Chipset Driver as well, which you can easily get directly from Intel or AMD.
Intel Chipsets (9-series up to current)
https://downloadcenter.intel.com/download/20775
AMD Chipsets (9xx series / Ryzen / ThreadRipper)
http://support.amd.com/en-us/download/chipset?os=Windows%2010%20-%2064
Personally I've never had to use DDU when updating drivers but always use it when downgrading. This might change after my last experience.
The OS does that automatically, u never have to do that.
Every instance of anything installing or uninstall auto triggers a separate restore point save.
Use DDU each and ever single GPU driver change, thats what its for. It makes that process faster and easier and ensures other drivers/software related to GPUs can't be an issue/conflict in anyways. Like when folks update GPU drivers. NEVER update GPU drivers, always wipe out and do fresh.
Also DDU will wipe monitor profiles apparently so not everyone wants that, and If we were using winXP I'd agree with you 100%. Now in the world of Win10 using DDU shouldn't be necessary for updating. You're right that it's a good idea albeit slower vs an over the top udate.
Seriously, thanks for the help, I will download that DDU and make sure I watch what it does and read how to use it properly. And make sure to first make a manual restore point.
Wiping Monitor Profiles is optional, it's in the DDU options.
And DDU even also does a system restore point save when used.
Actually it's mostly due to Win10 we need things like DDU, cause users are letting WU handle Drivers, which does that all wrong. But that also hasn't changed really since the days of WinXP, in terms of MS wanting to handle Drivers.
I just had to rollback to the WHQL in order to play State Of Decay YOSE. The game would crash every time. I would get a DXGI_ERROR_DEVICE_RESET fatal error. Saints Row 3 and Saints Row 4 would crash like that also. Now State Of Decay is running perfectly.
I read a lot of nonsense ideas about hardware failing and factory overclocks being bad etc. etc. etc. Rolled back to the 17.7.2 driver and now it works fine.
The WHQL are the drivers that are verified by Microsoft to work. So if you have any games that black screen or crash then rollback to the last WHQL driver. That being said, I had 37 other games that ran just fine on the NON-WHQL drivers. When you go to download the drivers manually the filename will start with NON-WHQL or WHQL.
non-WHQL stamped ones are "Beta"
The developer of State Of Decay says to use the WHQL drivers if you are having problems with the game.