WU 13456

Moderators: Site Moderators, FAHC Science Team

Neil-B
Posts: 2027
Joined: Sun Mar 22, 2020 5:52 pm
Hardware configuration: 1: 2x Xeon E5-2697v3@2.60GHz, 512GB DDR4 LRDIMM, SSD Raid, Win10 Ent 20H2, Quadro K420 1GB, FAH 7.6.21
2: Xeon E3-1505Mv5@2.80GHz, 32GB DDR4, NVME, Win10 Pro 20H2, Quadro M1000M 2GB, FAH 7.6.21 (actually have two of these)
3: i7-960@3.20GHz, 12GB DDR3, SSD, Win10 Pro 20H2, GTX 750Ti 2GB, GTX 1080Ti 11GB, FAH 7.6.21
Location: UK

Re: WU 13456

Post by Neil-B »

@JohnChodera ... Bit of feedback from Discord in case you haven't seen it ...

"firedfly — Today at 18:22
I have an nvidia 1660 running on Windows 10 that is completing p13456 via cuda without issue. I won't have time to post on the forums until tomorrow night, so feel free to report that if you want"

This supports your RTX30*0 hypothesis
2x Xeon E5-2697v3, 512GB DDR4 LRDIMM, SSD Raid, W10-Ent, Quadro K420
Xeon E3-1505Mv5, 32GB DDR4, NVME, W10-Pro, Quadro M1000M
i7-960, 12GB DDR3, SSD, W10-Pro, GTX1080Ti
i9-10850K, 64GB DDR4, NVME, W11-Pro, RTX3070

(Green/Bold = Active)
debs3759
Posts: 138
Joined: Fri Oct 07, 2011 3:29 am

Re: WU 13456

Post by debs3759 »

It ran the one I got last night with no problems. I have Visual C++ from Visual Studio 2019 Community installed, but not VC++ 2015 unless one of my other apps installed the files (which does seem very possible, as I have several optimisation and enhancement type apps, although they are all up to date).
Neil-B
Posts: 2027
Joined: Sun Mar 22, 2020 5:52 pm
Hardware configuration: 1: 2x Xeon E5-2697v3@2.60GHz, 512GB DDR4 LRDIMM, SSD Raid, Win10 Ent 20H2, Quadro K420 1GB, FAH 7.6.21
2: Xeon E3-1505Mv5@2.80GHz, 32GB DDR4, NVME, Win10 Pro 20H2, Quadro M1000M 2GB, FAH 7.6.21 (actually have two of these)
3: i7-960@3.20GHz, 12GB DDR3, SSD, Win10 Pro 20H2, GTX 750Ti 2GB, GTX 1080Ti 11GB, FAH 7.6.21
Location: UK

Re: WU 13456

Post by Neil-B »

@debs3759 ... what gpu? ... and do your logs show it running opencl or cuda?
2x Xeon E5-2697v3, 512GB DDR4 LRDIMM, SSD Raid, W10-Ent, Quadro K420
Xeon E3-1505Mv5, 32GB DDR4, NVME, W10-Pro, Quadro M1000M
i7-960, 12GB DDR3, SSD, W10-Pro, GTX1080Ti
i9-10850K, 64GB DDR4, NVME, W11-Pro, RTX3070

(Green/Bold = Active)
debs3759
Posts: 138
Joined: Fri Oct 07, 2011 3:29 am

Re: WU 13456

Post by debs3759 »

GTX 1060 3GB, CUDA, latest drivers.
JohnChodera
Pande Group Member
Posts: 470
Joined: Fri Feb 22, 2013 9:59 pm

Re: WU 13456

Post by JohnChodera »

@Neil-B: Now, that's odd. core22 0.0.13 was built with CUDA 9.2 and OpenMM 7.4.2.
core22 0.0.14 was built with CUDA 10.1 and OpenMM 7.5.1.

I definitely don't understand why CUDA 9.2 would work but 10.1 wouldn't.
If you have the time, perhaps we could invite you to the testing slack so we could run the next build by you next week?
If so, just private message me an email address we can use to send an invite.

~ John Chodera // MSKCC
WhitehawkEQ
Posts: 17
Joined: Sat May 14, 2011 11:50 pm

Re: WU 13456

Post by WhitehawkEQ »

Don't forget, my GTX 1080 cards fail with a popup error missing .dll's on 13456 core22 0.0.13 (all 10 cards) and my RTX 2080 cards run 13456 0.0.14 just fine (2 cards)
Image
JohnChodera
Pande Group Member
Posts: 470
Joined: Fri Feb 22, 2013 9:59 pm

Re: WU 13456

Post by JohnChodera »

@WhitehawkEQ: The missing DLL error occurs on 0.0.13? Which DLLs does it complain are missing?

~ John Chodera // MSKCC
Tashgan
Posts: 8
Joined: Fri May 15, 2020 1:27 pm

Re: WU 13456

Post by Tashgan »

The same here, for the Version 22.0.0.13 cuda is working with my RTX 3070 Ti. The Problem with the wrong GPU architecture appears with Version 22.0.0.14.

Below the log for a WU using 22.0.0.13 and cuda:

Code: Select all

...
04:49:58:WU01:FS01:Connecting to assign1.foldingathome.org:80
04:49:59:WU01:FS01:Assigned to work server 140.163.4.200
04:49:59:WU01:FS01:Requesting new work unit for slot 01: gpu:1:0 GA104 [GeForce RTX 3070 Ti] from 140.163.4.200
04:49:59:WU01:FS01:Connecting to 140.163.4.200:8080
04:50:00:WU01:FS01:Downloading 7.45MiB
04:50:03:WU01:FS01:Download complete
04:50:03:WU01:FS01:Received Unit: id:01 state:DOWNLOAD error:NO_ERROR project:17601 run:128 clone:0 gen:82 core:0x22 unit:0x0000000000000052000044c100000080
04:51:21:WU01:FS01:Starting
04:51:21:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\Markus\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/win/64bit/22-0.0.13/Core_22.fah/FahCore_22.exe -dir 01 -suffix 01 -version 706 -lifeline 12852 -checkpoint 15 -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu-vendor nvidia -gpu 0 -gpu-usage 100
04:51:21:WU01:FS01:Started FahCore on PID 13480
04:51:21:WU01:FS01:Core PID:15972
04:51:21:WU01:FS01:FahCore 0x22 started
04:51:21:WU01:FS01:0x22:*********************** Log Started 2021-07-31T04:51:21Z ***********************
04:51:21:WU01:FS01:0x22:*************************** Core22 Folding@home Core ***************************
04:51:21:WU01:FS01:0x22:       Core: Core22
04:51:21:WU01:FS01:0x22:       Type: 0x22
04:51:21:WU01:FS01:0x22:    Version: 0.0.13
04:51:21:WU01:FS01:0x22:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
04:51:21:WU01:FS01:0x22:  Copyright: 2020 foldingathome.org
04:51:21:WU01:FS01:0x22:   Homepage: https://foldingathome.org/
04:51:21:WU01:FS01:0x22:       Date: Sep 19 2020
04:51:21:WU01:FS01:0x22:       Time: 02:35:58
04:51:21:WU01:FS01:0x22:   Revision: 571cf95de6de2c592c7c3ed48fcfb2e33e9ea7d3
04:51:21:WU01:FS01:0x22:     Branch: core22-0.0.13
04:51:21:WU01:FS01:0x22:   Compiler: Visual C++ 2015
04:51:21:WU01:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
04:51:21:WU01:FS01:0x22:             -DOPENMM_GIT_HASH="\"189320d0\""
04:51:21:WU01:FS01:0x22:   Platform: win32 10
04:51:21:WU01:FS01:0x22:       Bits: 64
04:51:21:WU01:FS01:0x22:       Mode: Release
04:51:21:WU01:FS01:0x22:Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
04:51:21:WU01:FS01:0x22:             <peastman@stanford.edu>
04:51:21:WU01:FS01:0x22:       Args: -dir 01 -suffix 01 -version 706 -lifeline 13480 -checkpoint 15
04:51:21:WU01:FS01:0x22:             -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu-vendor
04:51:21:WU01:FS01:0x22:             nvidia -gpu 0 -gpu-usage 100
04:51:21:WU01:FS01:0x22:************************************ libFAH ************************************
04:51:21:WU01:FS01:0x22:       Date: Sep 7 2020
04:51:21:WU01:FS01:0x22:       Time: 19:09:56
04:51:21:WU01:FS01:0x22:   Revision: 44301ed97b996b63fe736bb8073f22209cb2b603
04:51:21:WU01:FS01:0x22:     Branch: HEAD
04:51:21:WU01:FS01:0x22:   Compiler: Visual C++ 2015
04:51:21:WU01:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
04:51:21:WU01:FS01:0x22:   Platform: win32 10
04:51:21:WU01:FS01:0x22:       Bits: 64
04:51:22:WU01:FS01:0x22:       Mode: Release
04:51:22:WU01:FS01:0x22:************************************ CBang *************************************
04:51:22:WU01:FS01:0x22:       Date: Sep 7 2020
04:51:22:WU01:FS01:0x22:       Time: 19:08:30
04:51:22:WU01:FS01:0x22:   Revision: 33fcfc2b3ed2195a423606a264718e31e6b3903f
04:51:22:WU01:FS01:0x22:     Branch: HEAD
04:51:22:WU01:FS01:0x22:   Compiler: Visual C++ 2015
04:51:22:WU01:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Ob3 /Zc:throwingNew /MT
04:51:22:WU01:FS01:0x22:   Platform: win32 10
04:51:22:WU01:FS01:0x22:       Bits: 64
04:51:22:WU01:FS01:0x22:       Mode: Release
04:51:22:WU01:FS01:0x22:************************************ System ************************************
04:51:22:WU01:FS01:0x22:        CPU: Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz
04:51:22:WU01:FS01:0x22:     CPU ID: GenuineIntel Family 6 Model 165 Stepping 5
04:51:22:WU01:FS01:0x22:       CPUs: 12
04:51:22:WU01:FS01:0x22:     Memory: 31.90GiB
04:51:22:WU01:FS01:0x22:Free Memory: 25.85GiB
04:51:22:WU01:FS01:0x22:    Threads: WINDOWS_THREADS
04:51:22:WU01:FS01:0x22: OS Version: 6.2
04:51:22:WU01:FS01:0x22:Has Battery: false
04:51:22:WU01:FS01:0x22: On Battery: false
04:51:22:WU01:FS01:0x22: UTC Offset: 2
04:51:22:WU01:FS01:0x22:        PID: 15972
04:51:22:WU01:FS01:0x22:        CWD: C:\Users\Markus\AppData\Roaming\FAHClient\work
04:51:22:WU01:FS01:0x22:************************************ OpenMM ************************************
04:51:22:WU01:FS01:0x22:   Revision: 189320d0
04:51:22:WU01:FS01:0x22:********************************************************************************
04:51:22:WU01:FS01:0x22:Project: 17601 (Run 128, Clone 0, Gen 82)
04:51:22:WU01:FS01:0x22:Unit: 0x00000000000000000000000000000000
04:51:22:WU01:FS01:0x22:Reading tar file core.xml
04:51:22:WU01:FS01:0x22:Reading tar file integrator.xml.bz2
04:51:22:WU01:FS01:0x22:Reading tar file state.xml.bz2
04:51:22:WU01:FS01:0x22:Reading tar file system.xml.bz2
04:51:22:WU01:FS01:0x22:Digital signatures verified
04:51:22:WU01:FS01:0x22:Folding@home GPU Core22 Folding@home Core
04:51:22:WU01:FS01:0x22:Version 0.0.13
04:51:22:WU01:FS01:0x22:  Checkpoint write interval: 50000 steps (2%) [50 total]
04:51:22:WU01:FS01:0x22:  JSON viewer frame write interval: 25000 steps (1%) [100 total]
04:51:22:WU01:FS01:0x22:  XTC frame write interval: 12500 steps (0.5%) [200 total]
04:51:22:WU01:FS01:0x22:  Global context and integrator variables write interval: disabled
04:51:22:WU01:FS01:0x22:There are 4 platforms available.
04:51:22:WU01:FS01:0x22:Platform 0: Reference
04:51:22:WU01:FS01:0x22:Platform 1: CPU
04:51:22:WU01:FS01:0x22:Platform 2: OpenCL
04:51:22:WU01:FS01:0x22:  opencl-device 0 specified
04:51:22:WU01:FS01:0x22:Platform 3: CUDA
04:51:22:WU01:FS01:0x22:  cuda-device 0 specified
04:51:26:WU01:FS01:0x22:Attempting to create CUDA context:
04:51:26:WU01:FS01:0x22:  Configuring platform CUDA
04:51:31:WU01:FS01:0x22:  Using CUDA and gpu 0
04:51:31:WU01:FS01:0x22:Completed 0 out of 2500000 steps (0%)
04:51:31:WU01:FS01:0x22:Checkpoint completed at step 0
04:52:34:WU01:FS01:0x22:Completed 25000 out of 2500000 steps (1%)
04:53:36:WU01:FS01:0x22:Completed 50000 out of 2500000 steps (2%)
...
WhitehawkEQ
Posts: 17
Joined: Sat May 14, 2011 11:50 pm

Re: WU 13456

Post by WhitehawkEQ »

JohnChodera wrote:@WhitehawkEQ: The missing DLL error occurs on 0.0.13? Which DLLs does it complain are missing?

~ John Chodera // MSKCC
MSVCP140.dll on both Win 7 and Win 10 PC's with GTX 1080 cards.
The GTX 1080's do fine on any WU using 0.0.13, it's when they get WU 13456 0.0.14 that they report missing .dll's, my RTX 2080's don't have any problems with ether 0.0.13 and 0.0.14.

F@H 12 GPU's (10 EVGA GTX 1080 SC, 2 EVGA RTX 2080 Super Black)
Image
WhitehawkEQ
Posts: 17
Joined: Sat May 14, 2011 11:50 pm

Re: WU 13456

Post by WhitehawkEQ »

Image
Neil-B
Posts: 2027
Joined: Sun Mar 22, 2020 5:52 pm
Hardware configuration: 1: 2x Xeon E5-2697v3@2.60GHz, 512GB DDR4 LRDIMM, SSD Raid, Win10 Ent 20H2, Quadro K420 1GB, FAH 7.6.21
2: Xeon E3-1505Mv5@2.80GHz, 32GB DDR4, NVME, Win10 Pro 20H2, Quadro M1000M 2GB, FAH 7.6.21 (actually have two of these)
3: i7-960@3.20GHz, 12GB DDR3, SSD, Win10 Pro 20H2, GTX 750Ti 2GB, GTX 1080Ti 11GB, FAH 7.6.21
Location: UK

Re: WU 13456

Post by Neil-B »

WhitehawkEQ wrote:
JohnChodera wrote:@WhitehawkEQ: The missing DLL error occurs on 0.0.13? Which DLLs does it complain are missing?

~ John Chodera // MSKCC
MSVCP140.dll on both Win 7 and Win 10 PC's with GTX 1080 cards.
The GTX 1080's do fine on any WU using 0.0.13, it's when they get WU 13456 0.0.14 that they report missing .dll's, my RTX 2080's don't have any problems with ether 0.0.13 and 0.0.14.

F@H 12 GPU's (10 EVGA GTX 1080 SC, 2 EVGA RTX 2080 Super Black)
You can either try to install the missing dll yourself (see below) or wait until the dev gets a chance to sort this out and repackage the core with the dll(s) included ... given that I believe the 13456/7 projects are on hold at the moment and may not be released to wider than beta before this is done being patient may well be the easiest option as even once the dll is installed you may not get a chance to test if it works.

If you want to try out patching one of the machines with the latest supportable MS Redistributable see https://support.microsoft.com/en-us/top ... f26a218cc0 ... believe you may need to patch both x86 and x64 of the Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 should install that dll for you.

@Severian used this approach and resolved the issue https://foldingforum.org/viewtopic.php?p=352578#p352598

If you look at "Programs" (add/remove) you should see the redistributable versions installed listed ... many people will have these because either they have patched MS O/S rigorously or have installed other software that needs these and installed them as part of another nstallation ... The listings should I believe read Microsoft Visual C++ 2015-2019 Redistributable (x86) followed by a version number and Microsoft Visual C++ 2015-2019 Redistributable (x64) also followed by a version number.
2x Xeon E5-2697v3, 512GB DDR4 LRDIMM, SSD Raid, W10-Ent, Quadro K420
Xeon E3-1505Mv5, 32GB DDR4, NVME, W10-Pro, Quadro M1000M
i7-960, 12GB DDR3, SSD, W10-Pro, GTX1080Ti
i9-10850K, 64GB DDR4, NVME, W11-Pro, RTX3070

(Green/Bold = Active)
JohnChodera
Pande Group Member
Posts: 470
Joined: Fri Feb 22, 2013 9:59 pm

Re: WU 13456

Post by JohnChodera »

If anyone who experienced the "missing DLL" issue with core22 0.0.14 has not installed the Visual Studio libraries manually to work around the issue, we could use your help testing a new core22 release! Please private message me an email address where we can reach you for details.

~ John Chodera // MSKCC
JohnChodera
Pande Group Member
Posts: 470
Joined: Fri Feb 22, 2013 9:59 pm

Re: WU 13456

Post by JohnChodera »

We have a fix for this in core22 0.0.15 that we're testing internally right now and hope to roll out in the next couple of days. Thanks so much for your patience, everyone!

~ John Chodera // MSKCC
PaulTV
Posts: 179
Joined: Mon Jan 25, 2021 4:53 pm
Location: Netherlands

Re: WU 13456

Post by PaulTV »

@JohnChodera, @Neil-B: I see the same as Neil.

For a p13456 job on 0.0.14:

Code: Select all

10:10:55:WU00:FS01:0x22:Project: 13456 (Run 303, Clone 20, Gen 0)
10:10:55:WU00:FS01:0x22:Unit: 0x00000000000000000000000000000000
10:10:55:WU00:FS01:0x22:Reading tar file core.xml
10:10:55:WU00:FS01:0x22:Reading tar file integrator.xml.bz2
10:10:55:WU00:FS01:0x22:Reading tar file state.xml.bz2
10:10:55:WU00:FS01:0x22:Reading tar file system.xml.bz2
10:10:55:WU00:FS01:0x22:Digital signatures verified
10:10:55:WU00:FS01:0x22:Folding@home GPU Core22 Folding@home Core
10:10:55:WU00:FS01:0x22:Version 0.0.14
10:10:55:WU00:FS01:0x22:  Checkpoint write interval: 50000 steps (5%) [20 total]
10:10:55:WU00:FS01:0x22:  JSON viewer frame write interval: 10000 steps (1%) [100 total]
10:10:55:WU00:FS01:0x22:  XTC frame write interval: 250000 steps (25%) [4 total]
10:10:55:WU00:FS01:0x22:  Global context and integrator variables write interval: 25000 steps (2.5%) [40 total]
10:10:55:WU00:FS01:0x22:There are 4 platforms available.
10:10:55:WU00:FS01:0x22:Platform 0: Reference
10:10:55:WU00:FS01:0x22:Platform 1: CPU
10:10:55:WU00:FS01:0x22:Platform 2: OpenCL
10:10:55:WU00:FS01:0x22:  opencl-device 0 specified
10:10:55:WU00:FS01:0x22:Platform 3: CUDA
10:10:55:WU00:FS01:0x22:  cuda-device 0 specified
10:11:03:WU00:FS01:0x22:Attempting to create CUDA context:
10:11:03:WU00:FS01:0x22:  Configuring platform CUDA
10:11:03:WU00:FS01:0x22:Failed to create CUDA context:
10:11:03:WU00:FS01:0x22:Error compiling program: nvrtc: error: invalid value for --gpu-architecture (-arch)
10:11:03:WU00:FS01:0x22:Attempting to create OpenCL context:
10:11:03:WU00:FS01:0x22:  Configuring platform OpenCL
10:11:09:WU00:FS01:0x22:  Using OpenCL on platformId 0 and gpu 0
For a p17601 job ob 0.0.13:

Code: Select all

06:13:31:WU01:FS01:0x22:Project: 17601 (Run 86, Clone 5, Gen 40)
06:13:31:WU01:FS01:0x22:Unit: 0x00000000000000000000000000000000
06:13:31:WU01:FS01:0x22:Reading tar file core.xml
06:13:31:WU01:FS01:0x22:Reading tar file integrator.xml.bz2
06:13:31:WU01:FS01:0x22:Reading tar file state.xml.bz2
06:13:31:WU01:FS01:0x22:Reading tar file system.xml.bz2
06:13:31:WU01:FS01:0x22:Digital signatures verified
06:13:31:WU01:FS01:0x22:Folding@home GPU Core22 Folding@home Core
06:13:31:WU01:FS01:0x22:Version 0.0.13
06:13:31:WU01:FS01:0x22:  Checkpoint write interval: 50000 steps (2%) [50 total]
06:13:31:WU01:FS01:0x22:  JSON viewer frame write interval: 25000 steps (1%) [100 total]
06:13:31:WU01:FS01:0x22:  XTC frame write interval: 12500 steps (0.5%) [200 total]
06:13:31:WU01:FS01:0x22:  Global context and integrator variables write interval: disabled
06:13:31:WU01:FS01:0x22:There are 4 platforms available.
06:13:31:WU01:FS01:0x22:Platform 0: Reference
06:13:31:WU01:FS01:0x22:Platform 1: CPU
06:13:31:WU01:FS01:0x22:Platform 2: OpenCL
06:13:31:WU01:FS01:0x22:  opencl-device 0 specified
06:13:31:WU01:FS01:0x22:Platform 3: CUDA
06:13:31:WU01:FS01:0x22:  cuda-device 0 specified
06:13:34:WU01:FS01:0x22:Attempting to create CUDA context:
06:13:34:WU01:FS01:0x22:  Configuring platform CUDA
06:13:38:WU01:FS01:0x22:  Using CUDA and gpu 0
From my sys info (same for both jobs mentioned above):

Code: Select all

08:59:42:          GPU 0: Bus:6 Slot:0 Func:0 NVIDIA:8 GA104 [GeForce RTX 3070]
08:59:42:  CUDA Device 0: Platform:0 Device:0 Bus:6 Slot:0 Compute:8.6 Driver:11.4
08:59:42:OpenCL Device 0: Platform:0 Device:0 Bus:6 Slot:0 Compute:3.0 Driver:471.41
Image

Ryzen 5800X / RTX 4090 / Windows 11
Ryzen 5600X / RTX 3070 Ti / Ubuntu 20.04
Ryzen 5600 / RTX 3060 Ti / Windows 11
Neil-B
Posts: 2027
Joined: Sun Mar 22, 2020 5:52 pm
Hardware configuration: 1: 2x Xeon E5-2697v3@2.60GHz, 512GB DDR4 LRDIMM, SSD Raid, Win10 Ent 20H2, Quadro K420 1GB, FAH 7.6.21
2: Xeon E3-1505Mv5@2.80GHz, 32GB DDR4, NVME, Win10 Pro 20H2, Quadro M1000M 2GB, FAH 7.6.21 (actually have two of these)
3: i7-960@3.20GHz, 12GB DDR3, SSD, Win10 Pro 20H2, GTX 750Ti 2GB, GTX 1080Ti 11GB, FAH 7.6.21
Location: UK

Re: WU 13456

Post by Neil-B »

@PaulTV ... They are working on another new version of the core to resolve this "No CUDA on RTX30*0 gpus" issue - and think have identified both the issue and how it can be easily sorted ... You may see wus running a newer 0.0.15 core (as John mentions above) with which you will most likely have the same issue - that one was focused on resolving the "missing dlls" issue ... It should be the next release after that - I won't guess the version might be 0.0.16 as someone will deliberately change it to make sure I am wrong ;) - and it shouldn't be very long before that arrives (but please don't hold breathe - these things can take days/weeks rather than minutes/hours).
2x Xeon E5-2697v3, 512GB DDR4 LRDIMM, SSD Raid, W10-Ent, Quadro K420
Xeon E3-1505Mv5, 32GB DDR4, NVME, W10-Pro, Quadro M1000M
i7-960, 12GB DDR3, SSD, W10-Pro, GTX1080Ti
i9-10850K, 64GB DDR4, NVME, W11-Pro, RTX3070

(Green/Bold = Active)
Post Reply