Unknown Enum Error

Moderators: Site Moderators, FAHC Science Team

Post Reply
Nert
Posts: 162
Joined: Wed Mar 26, 2014 7:46 pm

Unknown Enum Error

Post by Nert »

I received an unknown enum error. System is Windows 10 with a GTX750TI and a GTX970.

Here's the beginning of the log:

Code: Select all

*********************** Log Started 2016-03-27T20:24:12Z ***********************
20:24:12:************************* Folding@home Client *************************
20:24:12:      Website: http://folding.stanford.edu/
20:24:12:    Copyright: (c) 2009-2014 Stanford University
20:24:12:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
20:24:12:         Args: 
20:24:12:       Config: C:/Users/roger/AppData/Roaming/FAHClient/config.xml
20:24:12:******************************** Build ********************************
20:24:12:      Version: 7.4.4
20:24:12:         Date: Mar 4 2014
20:24:12:         Time: 20:26:54
20:24:12:      SVN Rev: 4130
20:24:12:       Branch: fah/trunk/client
20:24:12:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
20:24:12:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
20:24:12:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
20:24:12:     Platform: win32 XP
20:24:12:         Bits: 32
20:24:12:         Mode: Release
20:24:12:******************************* System ********************************
20:24:12:          CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
20:24:12:       CPU ID: GenuineIntel Family 6 Model 60 Stepping 3
20:24:12:         CPUs: 8
20:24:12:       Memory: 15.69GiB
20:24:12:  Free Memory: 13.76GiB
20:24:12:      Threads: WINDOWS_THREADS
20:24:12:   OS Version: 6.2
20:24:12:  Has Battery: false
20:24:12:   On Battery: false
20:24:12:   UTC Offset: -7
20:24:12:          PID: 7560
20:24:12:          CWD: C:/Users/roger/AppData/Roaming/FAHClient
20:24:12:           OS: Windows 10 Home
20:24:12:      OS Arch: AMD64
20:24:12:         GPUs: 2
20:24:12:        GPU 0: NVIDIA:4 GM107 [GeForce GTX 750 Ti]
20:24:12:        GPU 1: NVIDIA:5 GM204 [GeForce GTX 970]
20:24:12:         CUDA: 5.2
20:24:12:  CUDA Driver: 7050
20:24:12:Win32 Service: false
20:24:12:***********************************************************************
20:24:12:<config>
20:24:12:  <!-- Folding Slot Configuration -->
20:24:12:  <cause v='PARKINSONS'/>
20:24:12:
20:24:12:  <!-- Network -->
20:24:12:  <proxy v=':8080'/>
20:24:12:
20:24:12:  <!-- Slot Control -->
20:24:12:  <power v='full'/>
20:24:12:
20:24:12:  <!-- User Information -->
20:24:12:  <passkey v='********************************'/>
20:24:12:  <team v='165780'/>
20:24:12:  <user v='nert'/>
20:24:12:
20:24:12:  <!-- Folding Slots -->
20:24:12:  <slot id='0' type='CPU'/>
20:24:12:  <slot id='1' type='GPU'>
20:24:12:    <cuda-index v='1'/>
20:24:12:    <gpu-index v='0'/>
20:24:12:    <opencl-index v='1'/>
20:24:12:  </slot>
20:24:12:  <slot id='2' type='GPU'>
20:24:12:    <cuda-index v='2'/>
20:24:12:    <gpu-index v='1'/>
20:24:12:    <opencl-index v='2'/>
20:24:12:  </slot>
20:24:12:</config>
20:24:12:Trying to access database...
20:24:12:Successfully acquired database lock
20:24:12:Enabled folding slot 00: READY cpu:6
20:24:12:Enabled folding slot 01: READY gpu:0:GM107 [GeForce GTX 750 Ti]
20:24:12:Enabled folding slot 02: READY gpu:1:GM204 [GeForce GTX 970]
And here's the error message with surrounding log messages. I paused and restarted after the error:

Code: Select all

04:18:17:WU03:FS02:0x21:*********************** Log Started 2016-03-30T04:18:17Z ***********************
04:18:17:WU03:FS02:0x21:Project: 11402 (Run 3, Clone 16, Gen 70)
04:18:17:WU03:FS02:0x21:Unit: 0x000000588ca304f255ed4e663d0a1894
04:18:17:WU03:FS02:0x21:CPU: 0x00000000000000000000000000000000
04:18:17:WU03:FS02:0x21:Machine: 2
04:18:17:WU03:FS02:0x21:Reading tar file core.xml
04:18:17:WU03:FS02:0x21:Reading tar file system.xml
04:18:18:WU03:FS02:0x21:Reading tar file integrator.xml
04:18:18:WU03:FS02:0x21:Reading tar file state.xml
04:18:18:WU03:FS02:0x21:Digital signatures verified
04:18:18:WU03:FS02:0x21:Folding@home GPU Core21 Folding@home Core
04:18:18:WU03:FS02:0x21:Version 0.0.17
04:18:23:WU02:FS02:Upload 6.12%
04:18:29:WU02:FS02:Upload 10.35%
04:18:35:WU02:FS02:Upload 14.11%
04:18:41:WU02:FS02:Upload 18.35%
04:18:47:WU02:FS02:Upload 22.11%
04:18:53:WU02:FS02:Upload 26.34%
04:18:59:WU02:FS02:Upload 30.58%
04:19:05:WU02:FS02:Upload 34.34%
04:19:11:WU02:FS02:Upload 38.57%
04:19:17:WU02:FS02:Upload 42.81%
04:19:23:WU02:FS02:Upload 46.57%
04:19:29:WU02:FS02:Upload 50.81%
04:19:35:WU02:FS02:Upload 55.04%
04:19:41:WU02:FS02:Upload 58.80%
04:19:47:WU02:FS02:Upload 63.04%
04:19:53:WU02:FS02:Upload 66.80%
04:19:59:WU02:FS02:Upload 71.03%
04:20:01:WU00:FS00:0xa4:Completed 3900000 out of 5000000 steps  (78%)
04:20:05:WU02:FS02:Upload 75.27%
04:20:11:WU02:FS02:Upload 79.03%
04:20:17:WU02:FS02:Upload 83.26%
04:20:23:WU02:FS02:Upload 87.03%
04:20:29:WU02:FS02:Upload 91.26%
04:20:32:WARNING:WU03:FS02:FahCore returned an unknown error code which probably indicates that it crashed
04:20:32:WARNING:WU03:FS02:FahCore returned: UNKNOWN_ENUM (-1073740940 = 0xc0000374)
04:20:32:WU03:FS02:Starting
04:20:32:WU03:FS02:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/roger/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_21.fah/FahCore_21.exe -dir 03 -suffix 01 -version 704 -lifeline 7560 -checkpoint 15 -gpu 2 -gpu-vendor nvidia
04:20:32:WU03:FS02:Started FahCore on PID 8640
04:20:32:WU03:FS02:Core PID:8564
04:20:32:WU03:FS02:FahCore 0x21 started
04:20:33:WU03:FS02:0x21:*********************** Log Started 2016-03-30T04:20:32Z ***********************
04:20:33:WU03:FS02:0x21:Project: 11402 (Run 3, Clone 16, Gen 70)
04:20:33:WU03:FS02:0x21:Unit: 0x000000588ca304f255ed4e663d0a1894
04:20:33:WU03:FS02:0x21:CPU: 0x00000000000000000000000000000000
04:20:33:WU03:FS02:0x21:Machine: 2
04:20:33:WU03:FS02:0x21:Reading tar file core.xml
04:20:33:WU03:FS02:0x21:Reading tar file system.xml
04:20:33:WU03:FS02:0x21:Reading tar file integrator.xml
04:20:33:WU03:FS02:0x21:Reading tar file state.xml
04:20:34:WU03:FS02:0x21:Digital signatures verified
04:20:34:WU03:FS02:0x21:Folding@home GPU Core21 Folding@home Core
04:20:34:WU03:FS02:0x21:Version 0.0.17
04:20:35:WU02:FS02:Upload 95.49%
04:20:41:WU02:FS02:Upload 99.26%
04:20:45:WU03:FS02:0x21:Completed 0 out of 5000000 steps (0%)
04:20:45:WU03:FS02:0x21:Temperature control disabled. Requirements: single Nvidia GPU, tmax must be < 110 and twait >= 900
04:20:47:WU02:FS02:Upload complete
04:20:47:WU02:FS02:Server responded WORK_ACK (400)
04:20:47:WU02:FS02:Final credit estimate, 18078.00 points
04:20:47:WU02:FS02:Cleaning up
04:20:50:FS00:Paused
04:20:50:FS01:Paused
04:20:50:FS02:Paused
04:20:50:FS00:Shutting core down
04:20:50:FS01:Shutting core down
04:20:50:FS02:Shutting core down
04:20:51:WU03:FS02:0x21:WARNING:Console control signal 1 on PID 8564
04:20:51:WU01:FS01:0x21:WARNING:Console control signal 1 on PID 8336
04:20:51:WU03:FS02:0x21:Exiting, please wait. . .
04:20:51:WU01:FS01:0x21:Exiting, please wait. . .
04:20:51:WU03:FS02:FahCore returned: INTERRUPTED (102 = 0x66)
04:20:52:WU01:FS01:0x21:Folding@home Core Shutdown: INTERRUPTED
04:20:52:WU01:FS01:FahCore returned: INTERRUPTED (102 = 0x66)
04:20:54:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
04:20:57:FS00:Unpaused
04:20:57:FS01:Unpaused
04:20:57:FS02:Unpaused
04:20:57:WU01:FS01:Starting
04:20:57:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/roger/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_21.fah/FahCore_21.exe -dir 01 -suffix 01 -version 704 -lifeline 7560 -checkpoint 15 -gpu 1 -gpu-vendor nvidia
04:20:57:WU01:FS01:Started FahCore on PID 12700
04:20:57:WU01:FS01:Core PID:3300
04:20:57:WU01:FS01:FahCore 0x21 started
04:20:58:WU00:FS00:Starting
04:20:58:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/roger/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 00 -suffix 01 -version 704 -lifeline 7560 -checkpoint 15 -np 6
04:20:58:WU00:FS00:Started FahCore on PID 10296
04:20:58:WU00:FS00:Core PID:6092
Let me know if there's anything else I should provide.
Image
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Unknown Enum Error

Post by bruce »

The exception code 0xc0000374 is from Windows and indicates a heap corruption. FahCore_21 doesn't recognize it because it's no a problem that is internal to FahCore_21.

My first guess would be an unstable overclock, but if not, you'll have to dig deeper on your own.
Nert
Posts: 162
Joined: Wed Mar 26, 2014 7:46 pm

Re: Unknown Enum Error

Post by Nert »

All clocks are stock. I bought the cards specifically for that reason. <shrug>
Image
foldy
Posts: 2061
Joined: Sat Dec 01, 2012 3:43 pm
Hardware configuration: Folding@Home Client 7.6.13 (1 GPU slots)
Windows 7 64bit
Intel Core i5 2500k@4Ghz
Nvidia gtx 1080ti driver 441

Re: Unknown Enum Error

Post by foldy »

Looks like the error of WU03:FS02 occurred immidiately on core_21 initial start.
Then immidiately was restarting and this time successfully.

04:18:18:WU03:FS02:0x21:Folding@home GPU Core21 Folding@home Core
04:18:18:WU03:FS02:0x21:Version 0.0.17
04:20:32:WARNING:WU03:FS02:FahCore returned an unknown error code which probably indicates that it crashed
04:20:32:WARNING:WU03:FS02:FahCore returned: UNKNOWN_ENUM (-1073740940 = 0xc0000374)
04:20:32:WU03:FS02:Starting
04:20:32:WU03:FS02:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/roger/AppData/Roaming/FAHClient/cores/web.stanford.edu/~pande/Win32/AMD64/NVIDIA/Fermi/Core_21.fah/FahCore_21.exe -dir 03
04:20:45:WU03:FS02:0x21:Completed 0 out of 5000000 steps (0%)

May this be a nvidia driver on Windows 10 issue?
What is your driver version?

If you want to check your system is stable you can run:
* FurMark on your GPUs
* IntelBurnTest on your CPU
* Windows Memory Diagnostic on your RAM
Nert
Posts: 162
Joined: Wed Mar 26, 2014 7:46 pm

Re: Unknown Enum Error

Post by Nert »

Foldy,

Thanks for the reply. I appreciate your pointing out that the unit restarted successfully. I didn't know that. I'm not familiar with message formats in the logs and it's good to hear that the system recovered.

Here's a little more background info. I may have reported this problem before. It's very infrequent and occurs maybe once a month at most. I didn't take the time to track down any previous posts to cross reference and see if this occurrence was the same as the previous one. I report these things when they happen in case the event is important to the developers. I probably won't report any more "unknown enum" errors since Bruce seems to think there is something wrong with my system.

Here's some more information. Please bear with me if I don't get some of the following information right.

The driver version as shown in Computer management/ Driver properties is 10.18.13.5900 -Driver Provider: Nvidia, and Driver Date is 11/13/2015.

The Windows event log shows the following. I guessed that the time in the folding log is some kind of universal time and the the time stamps listed in the Event log viewer are in local time. I hope that this is the right one.

Code: Select all

- System 

  - Provider 

   [ Name]  Application Error 
 
  - EventID 1000 

   [ Qualifiers]  0 
 
   Level 2 
 
   Task 100 
 
   Keywords 0x80000000000000 
 
  - TimeCreated 

   [ SystemTime]  2016-03-30T04:18:30.466522800Z 
 
   EventRecordID 10527 
 
   Channel Application 
 
   Computer Z97A 
 
   Security 
 

- EventData 

   FahCore_21.exe 
   0.0.0.0 
   56750389 
   ntdll.dll 
   10.0.10586.122 
   56cbf9dd 
   c0000374 
   00000000000ee6dc 
   fb0 
   01d18a3b2f727f3c 
   C:\Users\roger\AppData\Roaming\FAHClient\cores\web.stanford.edu\~pande\Win32\AMD64\NVIDIA\Fermi\Core_21.fah\FahCore_21.exe 
   C:\WINDOWS\SYSTEM32\ntdll.dll 
   d4c643e9-a5dd-4581-8575-611475036d84 
I'll look into running some of those hardware diagnostics.
Image
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Unknown Enum Error

Post by bruce »

That's the right on. See "c0000374 " near the end.
Nert
Posts: 162
Joined: Wed Mar 26, 2014 7:46 pm

Re: Unknown Enum Error

Post by Nert »

Ran the long version of Windows memory test. Total run time ~ 8 hours. No errors. I'm looking at the Intel Burn program. Frankly I'm on the fence about running this. Just like I don't like to run cars at red line, I don't like stressing systems "just to find out." This is especially true since the problem is very intermittent and only occurs when folding. I've had no other lock ups or other problems with this system since I built it 8 months ago. I'm still thinking about it.
Image
7im
Posts: 10189
Joined: Thu Nov 29, 2007 4:30 pm
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
Location: Arizona
Contact:

Re: Unknown Enum Error

Post by 7im »

Please consider how unlikely It would be for Intel to publish a chip testing tool that would damage the chips they make.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
toTOW
Site Moderator
Posts: 6296
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France
Contact:

Re: Unknown Enum Error

Post by toTOW »

It's weird that it references a Windows component (ntdll.dll) in the application crash ... :?
Image

Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
bruce
Posts: 20910
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Unknown Enum Error

Post by bruce »

For others reading this topic, this is a known error for WIndowsXP but not for later OS versions (and the OP said he has WIn10)

It's past the time for folks to upgrade from WinXP to a more modern OS since officially it's no longer supported.

This doesn't explain what's going on here, though.
Post Reply