I have got 4 systems now working fine on Windows 10. All were upgrades from Win 7, and all have 2 GPUs (1 AMD and 1 NVIDIA).
I did have some fun getting them to work - see viewtopic.php?f=96&t=28015 for the gory details
D
Search found 5 matches
- Wed Aug 26, 2015 7:34 am
- Forum: Windows 10 + NVidia
- Topic: Any success with Windows 10?
- Replies: 13
- Views: 29717
- Mon Jul 29, 2013 2:04 pm
- Forum: GPU Projects and FahCores
- Topic: core_16 WUs fail on an HD 7790
- Replies: 5
- Views: 1856
Re: core_16 WUs fail on an HD 7790
I installed the 13.6 beta drivers. According to the custom install, the AMD APP level is the same as in the 13.4 drivers, but the beta did install some microsoft C runtime libraries that weren't installed before. Unfortunately made no difference - same failure. No big deal - the only issue is when c...
- Sat Jul 27, 2013 1:20 pm
- Forum: GPU Projects and FahCores
- Topic: core_16 WUs fail on an HD 7790
- Replies: 5
- Views: 1856
Re: core_16 WUs fail on an HD 7790
AFAIK, FahCore_16 works great with 12.8 or lower. With the newer drivers, it can be a hit or miss. However, FahCore_17 can work pretty well with the newer WHQL Driver releases. Not sure of any method which would help you to optimize for both FahCores in a single system. Thanks - I think 7790 is too...
- Sat Jul 27, 2013 6:56 am
- Forum: GPU Projects and FahCores
- Topic: core_16 WUs fail on an HD 7790
- Replies: 5
- Views: 1856
core_16 WUs fail on an HD 7790
I've recently built a new Win 7 64 system with an HD 7790 (Catalyst 13.4). All core_16 WUs fail (see log) until the slot is marked as "Failed". *********************** Log Started 2013-07-21T13:52:10Z *********************** 13:52:10:************************* Folding@home Client **********...
- Tue Jul 23, 2013 3:04 am
- Forum: GPU Projects and FahCores
- Topic: Stuck on core updating
- Replies: 60
- Views: 18416
Repeated FahCore returned: CORE_OUTDATED (110 = 0x6e)
Mod: Merged with existing topic on problem Hi, Successfully processed one new Core_17 WU. Following that, the client appeared to go into a loop thinking that the core was out of date, downloading a new one, finding that it wasn't out of date, starting the core, the core thinking it was out of date,...