BAD_WORK_UNIT (114 = 0x72) 2080 Super

It seems that a lot of GPU problems revolve around specific versions of drivers. Though NVidia has their own support structure, you can often learn from information reported by others who fold.

Moderators: Site Moderators, FAHC Science Team

Post Reply
tarka_dahl
Posts: 4
Joined: Thu Mar 26, 2020 11:33 am

BAD_WORK_UNIT (114 = 0x72) 2080 Super

Post by tarka_dahl »

Got a 2080 super not long ago but only just got round to setting up, it is in an old i7 2600K ITX system, have put in a new hard drive today and a fresh install of windows along with the newest drivers from nvidia. Also reset the bios.

Checked it is seated properly, doesn't even start processing the unit before saying it is faulty.

No other systems to try the card in until I get back to work, any ideas to try?

Code: Select all

*********************** Log Started 2020-03-26T10:23:08Z ***********************
10:23:08:************************* Folding@home Client *************************
10:23:08:        Website: https://foldingathome.org/
10:23:08:      Copyright: (c) 2009-2018 foldingathome.org
10:23:08:         Author: Joseph Coffland <[email protected]>
10:23:08:           Args: --open-web-control
10:23:08:         Config: C:\Users\folding\AppData\Roaming\FAHClient\config.xml
10:23:08:******************************** Build ********************************
10:23:08:        Version: 7.5.1
10:23:08:           Date: May 11 2018
10:23:08:           Time: 13:06:32
10:23:08:     Repository: Git
10:23:08:       Revision: 4705bf53c635f88b8fe85af7675557e15d491ff0
10:23:08:         Branch: master
10:23:08:       Compiler: Visual C++ 2008
10:23:08:        Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
10:23:08:       Platform: win32 10
10:23:08:           Bits: 32
10:23:08:           Mode: Release
10:23:08:******************************* System ********************************
10:23:08:            CPU: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
10:23:08:         CPU ID: GenuineIntel Family 6 Model 42 Stepping 7
10:23:08:           CPUs: 8
10:23:08:         Memory: 7.93GiB
10:23:08:    Free Memory: 5.83GiB
10:23:08:        Threads: WINDOWS_THREADS
10:23:08:     OS Version: 6.2
10:23:08:    Has Battery: false
10:23:08:     On Battery: false
10:23:08:     UTC Offset: 0
10:23:08:            PID: 3512
10:23:08:            CWD: C:\Users\folding\AppData\Roaming\FAHClient
10:23:08:             OS: Windows 10 Enterprise
10:23:08:        OS Arch: AMD64
10:23:08:           GPUs: 1
10:23:08:          GPU 0: Bus:1 Slot:0 Func:0 NVIDIA:8 TU104 [GeForce RTX 2080 Super]
10:23:08:  CUDA Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:7.5 Driver:11.0
10:23:08:OpenCL Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:1.2 Driver:445.75
10:23:08:  Win32 Service: false
10:23:08:***********************************************************************
10:23:08:<config>
10:23:08:  <!-- Network -->
10:23:08:  <proxy v=':8080'/>
10:23:08:
10:23:08:  <!-- Slot Control -->
10:23:08:  <power v='full'/>
10:23:08:
10:23:08:  <!-- User Information -->
10:23:08:  <passkey v='********************************'/>
10:23:08:  <team v='35947'/>
10:23:08:  <user v='tarka_dahl'/>
10:23:08:
10:23:08:  <!-- Folding Slots -->
10:23:08:  <slot id='1' type='GPU'/>
10:23:08:</config>
10:23:08:Trying to access database...
10:23:08:Successfully acquired database lock
10:23:08:Enabled folding slot 01: READY gpu:0:TU104 [GeForce RTX 2080 Super]
10:23:08:WU00:FS01:Connecting to 65.254.110.245:8080
10:23:09:WARNING:WU00:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
10:23:09:WU00:FS01:Connecting to 18.218.241.186:80
10:23:09:WU00:FS01:Assigned to work server 13.90.152.57
10:23:09:WU00:FS01:Requesting new work unit for slot 01: READY gpu:0:TU104 [GeForce RTX 2080 Super] from 13.90.152.57
10:23:09:WU00:FS01:Connecting to 13.90.152.57:8080
10:23:30:WARNING:WU00:FS01:WorkServer connection failed on port 8080 trying 80
10:23:30:WU00:FS01:Connecting to 13.90.152.57:80
10:24:05:WU00:FS01:Downloading 51.20MiB
10:24:11:WU00:FS01:Download 4.88%
10:24:17:WU00:FS01:Download 17.34%
10:24:23:WU00:FS01:Download 33.82%
10:24:29:WU00:FS01:Download 47.00%
10:24:35:WU00:FS01:Download 62.75%
10:24:41:WU00:FS01:Download 78.38%
10:24:47:WU00:FS01:Download 89.49%
10:24:51:WU00:FS01:Download complete
10:24:51:WU00:FS01:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:11780 run:0 clone:2000 gen:22 core:0x22 unit:0x0000001c0d5a98395e73c571f606e155
10:24:51:WU00:FS01:Downloading core from http://cores.foldingathome.org/v7/win/64bit/Core_22.fah
10:24:51:WU00:FS01:Connecting to cores.foldingathome.org:80
10:24:51:WU00:FS01:FahCore 22: Downloading 4.04MiB
10:24:54:WU00:FS01:FahCore 22: Download complete
10:24:54:WU00:FS01:Valid core signature
10:24:55:WU00:FS01:Unpacked 13.49MiB to cores/cores.foldingathome.org/v7/win/64bit/Core_22.fah/FahCore_22.exe
10:24:55:WU00:FS01:Starting
10:24:55:WU00:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\folding\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/v7/win/64bit/Core_22.fah/FahCore_22.exe -dir 00 -suffix 01 -version 705 -lifeline 3512 -checkpoint 15 -gpu-vendor nvidia -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu 0
10:24:55:WU00:FS01:Started FahCore on PID 5192
10:24:55:WU00:FS01:Core PID:11232
10:24:55:WU00:FS01:FahCore 0x22 started
10:24:55:WU00:FS01:0x22:*********************** Log Started 2020-03-26T10:24:55Z ***********************
10:24:55:WU00:FS01:0x22:*************************** Core22 Folding@home Core ***************************
10:24:55:WU00:FS01:0x22:       Type: 0x22
10:24:55:WU00:FS01:0x22:       Core: Core22
10:24:55:WU00:FS01:0x22:    Website: https://foldingathome.org/
10:24:55:WU00:FS01:0x22:  Copyright: (c) 2009-2018 foldingathome.org
10:24:55:WU00:FS01:0x22:     Author: John Chodera <[email protected]> and Rafal Wiewiora
10:24:55:WU00:FS01:0x22:             <[email protected]>
10:24:55:WU00:FS01:0x22:       Args: -dir 00 -suffix 01 -version 705 -lifeline 5192 -checkpoint 15
10:24:55:WU00:FS01:0x22:             -gpu-vendor nvidia -opencl-platform 0 -opencl-device 0 -cuda-device
10:24:55:WU00:FS01:0x22:             0 -gpu 0
10:24:55:WU00:FS01:0x22:     Config: <none>
10:24:55:WU00:FS01:0x22:************************************ Build *************************************
10:24:55:WU00:FS01:0x22:    Version: 0.0.2
10:24:55:WU00:FS01:0x22:       Date: Dec 6 2019
10:24:55:WU00:FS01:0x22:       Time: 21:30:31
10:24:55:WU00:FS01:0x22: Repository: Git
10:24:55:WU00:FS01:0x22:   Revision: abeb39247cc72df5af0f63723edafadb23d5dfbe
10:24:55:WU00:FS01:0x22:     Branch: HEAD
10:24:55:WU00:FS01:0x22:   Compiler: Visual C++ 2008
10:24:55:WU00:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
10:24:55:WU00:FS01:0x22:   Platform: win32 10
10:24:55:WU00:FS01:0x22:       Bits: 64
10:24:55:WU00:FS01:0x22:       Mode: Release
10:24:55:WU00:FS01:0x22:************************************ System ************************************
10:24:55:WU00:FS01:0x22:        CPU: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
10:24:55:WU00:FS01:0x22:     CPU ID: GenuineIntel Family 6 Model 42 Stepping 7
10:24:55:WU00:FS01:0x22:       CPUs: 8
10:24:55:WU00:FS01:0x22:     Memory: 7.93GiB
10:24:55:WU00:FS01:0x22:Free Memory: 5.77GiB
10:24:55:WU00:FS01:0x22:    Threads: WINDOWS_THREADS
10:24:55:WU00:FS01:0x22: OS Version: 6.2
10:24:55:WU00:FS01:0x22:Has Battery: false
10:24:55:WU00:FS01:0x22: On Battery: false
10:24:55:WU00:FS01:0x22: UTC Offset: 0
10:24:55:WU00:FS01:0x22:        PID: 11232
10:24:55:WU00:FS01:0x22:        CWD: C:\Users\folding\AppData\Roaming\FAHClient\work
10:24:55:WU00:FS01:0x22:         OS: Windows 10 Pro
10:24:55:WU00:FS01:0x22:    OS Arch: AMD64
10:24:55:WU00:FS01:0x22:********************************************************************************
10:24:55:WU00:FS01:0x22:Project: 11780 (Run 0, Clone 2000, Gen 22)
10:24:55:WU00:FS01:0x22:Unit: 0x0000001c0d5a98395e73c571f606e155
10:24:55:WU00:FS01:0x22:Reading tar file core.xml
10:24:55:WU00:FS01:0x22:Reading tar file integrator.xml
10:24:55:WU00:FS01:0x22:Reading tar file state.xml
10:24:56:WU00:FS01:0x22:Reading tar file system.xml
10:24:56:WU00:FS01:0x22:Digital signatures verified
10:24:56:WU00:FS01:0x22:Folding@home GPU Core22 Folding@home Core
10:24:56:WU00:FS01:0x22:Version 0.0.2
10:25:10:WU00:FS01:0x22:ERROR:exception: Error compiling kernel: 
10:25:10:WU00:FS01:0x22:Saving result file ..\logfile_01.txt
10:25:10:WU00:FS01:0x22:Saving result file science.log
10:25:10:WU00:FS01:0x22:Folding@home Core Shutdown: BAD_WORK_UNIT
10:25:10:WARNING:WU00:FS01:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
10:25:10:WU00:FS01:Sending unit results: id:00 state:SEND error:FAULTY project:11780 run:0 clone:2000 gen:22 core:0x22 unit:0x0000001c0d5a98395e73c571f606e155
10:25:11:WU00:FS01:Uploading 8.00KiB to 13.90.152.57
10:25:11:WU00:FS01:Connecting to 13.90.152.57:8080
10:25:11:WU01:FS01:Connecting to 65.254.110.245:8080
10:25:11:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
10:25:11:WU01:FS01:Connecting to 18.218.241.186:80
10:25:12:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
10:25:12:ERROR:WU01:FS01:Exception: Could not get an assignment
10:25:12:WU01:FS01:Connecting to 65.254.110.245:8080
10:25:13:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
10:25:13:WU01:FS01:Connecting to 18.218.241.186:80
10:25:13:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
10:25:13:ERROR:WU01:FS01:Exception: Could not get an assignment
10:25:51:WU00:FS01:Upload complete
10:25:51:WU00:FS01:Server responded WORK_ACK (400)
10:25:51:WU00:FS01:Cleaning up
10:26:12:WU01:FS01:Connecting to 65.254.110.245:8080
10:26:13:WARNING:WU01:FS01:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
10:26:13:WU01:FS01:Connecting to 18.218.241.186:80
10:26:13:WARNING:WU01:FS01:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
10:26:13:ERROR:WU01:FS01:Exception: Could not get an assignment
Top
Jertzuu
Posts: 31
Joined: Wed Mar 25, 2020 6:25 pm
Hardware configuration: Ryzen 5 2600 @ 4,1GHz
G.Skill Trident Z RGB 3200mHz CL14 32Gb
Asus Prime X470-PRO
Zotac AMP! Extreme 1080 Ti
Samsung Evo 970 250Gb NVMe M.2
Samsung Evo 860 500Gb SSD
WD Black 1Tb 7200RPM HDD
Location: Ulvila, FInland

Re: BAD_WORK_UNIT (114 = 0x72) 2080 Super

Post by Jertzuu »

Following, I have the same problem with my GTX 1080 Ti
Image

Ryzen 5 2600 @ 4,1GHz
Zotac AMP! Extreme 1080 Ti
Top
MrFrizzy
Posts: 123
Joined: Fri Feb 14, 2020 4:48 am

Re: BAD_WORK_UNIT (114 = 0x72) 2080 Super

Post by MrFrizzy »

Jertzuu wrote:Following, I have the same problem with my GTX 1080 Ti
Jertzuu, many different errors can cause the "BAD_WORK_UNIT" message. After checking your other post, the error message you have been getting about the "Bad State detected... attempting to resume from last good checkpoint. Is your system overclocked?" and "Following exception occured: Particle coordinate is nan" is a different error than what Tarka_dahl is getting. If you look in the posted log, the specific error Tarka is getting is "ERROR:exception: Error compiling kernel:".

Tarka_dahl, the only suggestion I have for getting the 2080 Super working is doing a clean install of the most recent drivers. If that does not work, perhaps someone else can chime in with some further ideas.
S1: AMD R5 3600 & Sapphire RX 5700 XT Reference @2.1GHz under water
S2: Intel Xeon E5-2620v3 & MSI GTX 1650

RX 5700 XT Project & PPD Tracking Spreadsheet

Image
Top
tarka_dahl
Posts: 4
Joined: Thu Mar 26, 2020 11:33 am

Re: BAD_WORK_UNIT (114 = 0x72) 2080 Super

Post by tarka_dahl »

MrFrizzy, tried that along with a clean install of Windows. Also tried older drivers. I'll try another set today and see because why not. Until lockdown here is finished I can't plug the card into another machine.
Top
tarka_dahl
Posts: 4
Joined: Thu Mar 26, 2020 11:33 am

Re: BAD_WORK_UNIT (114 = 0x72) 2080 Super

Post by tarka_dahl »

tarka_dahl wrote:MrFrizzy, tried that along with a clean install of Windows. Also tried older drivers. I'll try another set today and see because why not. Until lockdown here is finished I can't plug the card into another machine.
Just tried even older drivers, same issue. May go and try Ubuntu, that would confirm it is hardware at least.

I do wonder if using an OLD motherboard/cpu is causing the issue. The 2600k and itx board it is in will be around 10 years old.
Top
ursmii
Posts: 5
Joined: Fri Mar 27, 2020 3:19 pm

Re: BAD_WORK_UNIT (114 = 0x72) 2080 Super

Post by ursmii »

I had the same error every time when I tried to rise (not really overclock ;)) memory and GPU-clock
now I'm back to: memory 6900MHz (+100), GPU 2010MHz (+50), power 100%
GPU: EVGA 2080 TI FTW3
CPU: Ryzen 3950X(4.1GHz)
AMD Ryzen 3950X, EVGA 2080 TI FTW3, Gigabyte X570 Aorus xtreme, G.Skill TridentZneo (4x16GB, DDR4-3600), Corsair MP600 (1000GB, M.2 2280), CoolerMaster H500P Mesh, beQuiet DarkRock pro 4, Win10 pro, F@H, R@H & dist.comp (Moo!Wrapper, Milkyway)
Image
Top
florinandrei
Posts: 16
Joined: Fri Feb 12, 2010 12:16 am
Location: California
Contact:
Contact florinandrei

Re: BAD_WORK_UNIT (114 = 0x72) 2080 Super

Post by florinandrei »

Same error with a GTX 1060 on Ubuntu 16.04 with the 430.64 drivers.

No idea where to even begin troubleshooting it. It's an old system, but 100% stock, no overclocking.
Top
Jertzuu
Posts: 31
Joined: Wed Mar 25, 2020 6:25 pm
Hardware configuration: Ryzen 5 2600 @ 4,1GHz
G.Skill Trident Z RGB 3200mHz CL14 32Gb
Asus Prime X470-PRO
Zotac AMP! Extreme 1080 Ti
Samsung Evo 970 250Gb NVMe M.2
Samsung Evo 860 500Gb SSD
WD Black 1Tb 7200RPM HDD
Location: Ulvila, FInland

Re: BAD_WORK_UNIT (114 = 0x72) 2080 Super

Post by Jertzuu »

MrFrizzy wrote:
Jertzuu wrote:Following, I have the same problem with my GTX 1080 Ti
Jertzuu, many different errors can cause the "BAD_WORK_UNIT" message. After checking your other post, the error message you have been getting about the "Bad State detected... attempting to resume from last good checkpoint. Is your system overclocked?" and "Following exception occured: Particle coordinate is nan" is a different error than what Tarka_dahl is getting. If you look in the posted log, the specific error Tarka is getting is "ERROR:exception: Error compiling kernel:".

Tarka_dahl, the only suggestion I have for getting the 2080 Super working is doing a clean install of the most recent drivers. If that does not work, perhaps someone else can chime in with some further ideas.
My bad :biggrin: But do you know where I could start troubleshooting? Already reinstalled the drivers and lower clocks on the GPU. I'm really struggling to find a solution

*Edit* Reinstalled the client and made sure all previous data was deleted from my PC. So far so good, and seems to be working fine so far

*Edit 2* Did not help, got a project going for 30min after which it crashed again. Any help is appreciated
Last edited by Jertzuu on Thu Apr 02, 2020 3:28 pm, edited 1 time in total.
Image

Ryzen 5 2600 @ 4,1GHz
Zotac AMP! Extreme 1080 Ti
Top
tarka_dahl
Posts: 4
Joined: Thu Mar 26, 2020 11:33 am

Re: BAD_WORK_UNIT (114 = 0x72) 2080 Super

Post by tarka_dahl »

Tried the card in another system last night, same issue. Tried furmark and I get a shit load of artifacts and terrible coil whine. RMA started!
Top
toTOW
Site Moderator
Posts: 6359
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France
Contact:
Contact toTOW

Re: BAD_WORK_UNIT (114 = 0x72) 2080 Super

Post by toTOW »

It's unfortunate, but FAH is one of the best stability test for hardware.

Luckily, you can get it replaced ! :)
Image

Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
Top
Post Reply

Return to “Problems with NVidia drivers”