core 16 crashes

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

Moderators: Site Moderators, FAHC Science Team

Post Reply
benj1989
Posts: 9
Joined: Wed Jan 16, 2008 3:21 am

core 16 crashes

Post by benj1989 »

Hi,

I've setup a new gaming computer with a gigabyte 7970 and i5-4670k
I've folded succesfully on core 17, but core 16 instantly crashes even on minimum clock speeds.
Here's the log:

Code: Select all

*********************** Log Started 2013-09-04T14:12:04Z ***********************
14:12:04:************************* Folding@home Client *************************
14:12:04:      Website: http://folding.stanford.edu/
14:12:04:    Copyright: (c) 2009-2013 Stanford University
14:12:04:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
14:12:04:         Args: --open-web-control
14:12:04:       Config: C:/ProgramData/FAHClient/config.xml
14:12:04:******************************** Build ********************************
14:12:04:      Version: 7.3.6
14:12:04:         Date: Feb 18 2013
14:12:04:         Time: 15:25:17
14:12:04:      SVN Rev: 3923
14:12:04:       Branch: fah/trunk/client
14:12:04:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
14:12:04:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
14:12:04:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl
14:12:04:     Platform: win32 XP
14:12:04:         Bits: 32
14:12:04:         Mode: Release
14:12:04:******************************* System ********************************
14:12:04:          CPU: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz
14:12:04:       CPU ID: GenuineIntel Family 6 Model 60 Stepping 3
14:12:04:         CPUs: 4
14:12:04:       Memory: 7.89GiB
14:12:04:  Free Memory: 6.11GiB
14:12:04:      Threads: WINDOWS_THREADS
14:12:04:  Has Battery: false
14:12:04:   On Battery: false
14:12:04:   UTC offset: 2
14:12:04:          PID: 2688
14:12:04:          CWD: C:/ProgramData/FAHClient
14:12:04:           OS: Windows 7 Ultimate
14:12:04:      OS Arch: AMD64
14:12:04:         GPUs: 1
14:12:04:        GPU 0: ATI:5 Tahiti XT [Radeon HD 7970]
14:12:04:         CUDA: Not detected
14:12:04:Win32 Service: false
14:12:04:***********************************************************************
14:12:04:<config>
14:12:04:  <service-description v='Folding@home Client'/>
14:12:04:  <service-restart v='true'/>
14:12:04:  <service-restart-delay v='5000'/>
14:12:04:
14:12:04:  <!-- Client Control -->
14:12:04:  <client-threads v='4'/>
14:12:04:  <cycle-rate v='4'/>
14:12:04:  <cycles v='-1'/>
14:12:04:  <data-directory v='.'/>
14:12:04:  <disable-sleep-when-active v='true'/>
14:12:04:  <exec-directory v='C:\Program Files (x86)\FAHClient'/>
14:12:04:  <exit-when-done v='false'/>
14:12:04:  <fold-anon v='false'/>
14:12:04:  <open-web-control v='true'/>
14:12:04:
14:12:04:  <!-- Configuration -->
14:12:04:  <config-rotate v='true'/>
14:12:04:  <config-rotate-dir v='configs'/>
14:12:04:  <config-rotate-max v='16'/>
14:12:04:
14:12:04:  <!-- Debugging -->
14:12:04:  <assignment-servers>
14:12:04:    assign3.stanford.edu:8080 assign4.stanford.edu:80
14:12:04:  </assignment-servers>
14:12:04:  <capture-directory v='capture'/>
14:12:04:  <capture-on-error v='false'/>
14:12:04:  <capture-packets v='false'/>
14:12:04:  <capture-requests v='false'/>
14:12:04:  <capture-responses v='false'/>
14:12:04:  <capture-sockets v='false'/>
14:12:04:  <debug-sockets v='false'/>
14:12:04:  <exception-locations v='true'/>
14:12:04:  <gpu-assignment-servers>
14:12:04:    assign-GPU.stanford.edu:80 assign-GPU.stanford.edu:8080
14:12:04:  </gpu-assignment-servers>
14:12:04:  <stack-traces v='false'/>
14:12:04:
14:12:04:  <!-- Error Handling -->
14:12:04:  <max-slot-errors v='5'/>
14:12:04:  <max-unit-errors v='5'/>
14:12:04:
14:12:04:  <!-- Folding Core -->
14:12:04:  <checkpoint v='15'/>
14:12:04:  <core-dir v='cores'/>
14:12:04:  <core-priority v='idle'/>
14:12:04:  <cpu-affinity v='false'/>
14:12:04:  <cpu-usage v='100'/>
14:12:04:  <gpu-usage v='100'/>
14:12:04:  <no-assembly v='false'/>
14:12:04:
14:12:04:  <!-- Folding Slot Configuration -->
14:12:04:  <cause v='ANY'/>
14:12:04:  <client-subtype v='STDCLI'/>
14:12:04:  <client-type v='normal'/>
14:12:04:  <cpu-species v='X86_PENTIUM_II'/>
14:12:04:  <cpu-type v='AMD64'/>
14:12:04:  <cpus v='-1'/>
14:12:04:  <cuda-index v='0'/>
14:12:04:  <gpu v='true'/>
14:12:04:  <max-packet-size v='normal'/>
14:12:04:  <opencl-index v='0'/>
14:12:04:  <os-species v='UNKNOWN'/>
14:12:04:  <os-type v='WIN32'/>
14:12:04:  <power v='full'/>
14:12:04:  <project-key v='0'/>
14:12:04:  <smp v='true'/>
14:12:04:
14:12:04:  <!-- HTTP Server -->
14:12:04:  <allow v='127.0.0.1'/>
14:12:04:  <connection-timeout v='60'/>
14:12:04:  <deny v='0/0'/>
14:12:04:  <http-addresses v='0:7396'/>
14:12:04:  <https-addresses v=''/>
14:12:04:  <max-connect-time v='900'/>
14:12:04:  <max-connections v='800'/>
14:12:04:  <max-request-length v='52428800'/>
14:12:04:  <min-connect-time v='300'/>
14:12:04:  <threads v='4'/>
14:12:04:
14:12:04:  <!-- Logging -->
14:12:04:  <log v='log.txt'/>
14:12:04:  <log-color v='false'/>
14:12:04:  <log-crlf v='true'/>
14:12:04:  <log-date v='false'/>
14:12:04:  <log-date-periodically v='21600'/>
14:12:04:  <log-debug v='true'/>
14:12:04:  <log-domain v='false'/>
14:12:04:  <log-header v='true'/>
14:12:04:  <log-level v='true'/>
14:12:04:  <log-no-info-header v='true'/>
14:12:04:  <log-redirect v='false'/>
14:12:04:  <log-rotate v='true'/>
14:12:04:  <log-rotate-dir v='logs'/>
14:12:04:  <log-rotate-max v='16'/>
14:12:04:  <log-short-level v='false'/>
14:12:04:  <log-simple-domains v='true'/>
14:12:04:  <log-thread-id v='false'/>
14:12:04:  <log-thread-prefix v='true'/>
14:12:04:  <log-time v='true'/>
14:12:04:  <log-to-screen v='true'/>
14:12:04:  <log-truncate v='false'/>
14:12:04:  <verbosity v='5'/>
14:12:04:
14:12:04:  <!-- Network -->
14:12:04:  <proxy v=':8080'/>
14:12:04:  <proxy-enable v='false'/>
14:12:04:  <proxy-pass v=''/>
14:12:04:  <proxy-user v=''/>
14:12:04:
14:12:04:  <!-- Process Control -->
14:12:04:  <child v='false'/>
14:12:04:  <daemon v='false'/>
14:12:04:  <pid v='false'/>
14:12:04:  <pid-file v='Folding@home Client.pid'/>
14:12:04:  <respawn v='false'/>
14:12:04:  <service v='false'/>
14:12:04:
14:12:04:  <!-- Remote Command Server -->
14:12:04:  <command-address v='0.0.0.0'/>
14:12:04:  <command-allow-no-pass v='127.0.0.1'/>
14:12:04:  <command-deny-no-pass v='0/0'/>
14:12:04:  <command-port v='36330'/>
14:12:04:
14:12:04:  <!-- Slot Control -->
14:12:04:  <idle v='false'/>
14:12:04:  <max-shutdown-wait v='60'/>
14:12:04:  <pause-on-battery v='true'/>
14:12:04:  <pause-on-start v='false'/>
14:12:04:
14:12:04:  <!-- User Information -->
14:12:04:  <machine-id v='0'/>
14:12:04:  <passkey v='********************************'/>
14:12:04:  <team v='105987'/>
14:12:04:  <user v='bhunt'/>
14:12:04:
14:12:04:  <!-- Web Server -->
14:12:04:  <session-timeout v='3600'/>
14:12:04:  <web-allow v='127.0.0.1'/>
14:12:04:  <web-deny v='0/0'/>
14:12:04:
14:12:04:  <!-- Work Unit Control -->
14:12:04:  <dump-after-deadline v='true'/>
14:12:04:  <max-queue v='16'/>
14:12:04:  <max-units v='0'/>
14:12:04:  <next-unit-percentage v='99'/>
14:12:04:
14:12:04:  <!-- Folding Slots -->
14:12:04:  <slot id='0' type='GPU'>
14:12:04:    <max-packet-size v='big'/>
14:12:04:    <next-unit-percentage v='100'/>
14:12:04:    <opencl-index v='0'/>
14:12:04:  </slot>
14:12:04:  <slot id='1' type='CPU'>
14:12:04:    <cpus v='-1'/>
14:12:04:    <max-packet-size v='big'/>
14:12:04:    <next-unit-percentage v='100'/>
14:12:04:  </slot>
14:12:04:</config>
14:12:04:Trying to access database...
14:12:04:Successfully acquired database lock
14:12:04:Enabled folding slot 00: READY gpu:0:Tahiti XT [Radeon HD 7970]
14:12:04:Enabled folding slot 01: READY cpu:3
14:12:04:Started thread 5 on PID 2688
14:12:04:WU02:FS01:Starting
14:12:04:Started thread 4 on PID 2688
14:12:04:Started thread 6 on PID 2688
14:12:04:Started thread 7 on PID 2688
14:12:04:WU02:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/ProgramData/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/Core_a3.fah/FahCore_a3.exe -dir 02 -suffix 01 -version 703 -lifeline 2688 -checkpoint 15 -np 3
14:12:04:WU02:FS01:Started FahCore on PID 2192
14:12:04:Started thread 8 on PID 2688
14:12:04:WU02:FS01:Core PID:5028
14:12:04:WU02:FS01:FahCore 0xa3 started
14:12:04:WU01:FS00:Starting
14:12:04:WU01:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/ProgramData/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_16.fah/FahCore_16.exe -dir 01 -suffix 01 -version 703 -lifeline 2688 -checkpoint 15 -gpu 0 -gpu-vendor ati
14:12:04:WU01:FS00:Started FahCore on PID 4124
14:12:04:Started thread 9 on PID 2688
14:12:04:WU01:FS00:Core PID:3960
14:12:04:WU01:FS00:FahCore 0x16 started
14:12:05:WU02:FS01:0xa3:
14:12:05:WU02:FS01:0xa3:*------------------------------*
14:12:05:WU02:FS01:0xa3:Folding@Home Gromacs SMP Core
14:12:05:WU02:FS01:0xa3:Version 2.27 (Dec. 15, 2010)
14:12:05:WU02:FS01:0xa3:
14:12:05:WU02:FS01:0xa3:Preparing to commence simulation
14:12:05:WU02:FS01:0xa3:- Looking at optimizations...
14:12:05:WU02:FS01:0xa3:- Files status OK
14:12:05:WU02:FS01:0xa3:- Expanded 3810721 -> 4169428 (decompressed 109.4 percent)
14:12:05:WU02:FS01:0xa3:Called DecompressByteArray: compressed_data_size=3810721 data_size=4169428, decompressed_data_size=4169428 diff=0
14:12:05:WU02:FS01:0xa3:- Digital signature verified
14:12:05:WU02:FS01:0xa3:
14:12:05:WU02:FS01:0xa3:Project: 6097 (Run 0, Clone 3, Gen 169)
14:12:05:WU02:FS01:0xa3:
14:12:05:WU02:FS01:0xa3:Assembly optimizations on if available.
14:12:05:WU02:FS01:0xa3:Entering M.D.
14:12:05:WU01:FS00:0x16:
14:12:05:WU01:FS00:0x16:*------------------------------*
14:12:05:WU01:FS00:0x16:Folding@Home GPU Core
14:12:05:WU01:FS00:0x16:Version 2.11 (Thu Dec 9 15:00:14 PST 2010)
14:12:05:WU01:FS00:0x16:
14:12:05:WU01:FS00:0x16:Compiler  : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for 80x86 
14:12:05:WU01:FS00:0x16:Build host: user-f6d030f24f
14:12:05:WU01:FS00:0x16:Board Type: AMD/OpenCL
14:12:05:WU01:FS00:0x16:Core      : x=16
14:12:05:WU01:FS00:0x16: Window's signal control handler registered.
14:12:05:WU01:FS00:0x16:Preparing to commence simulation
14:12:05:WU01:FS00:0x16:- Ensuring status. Please wait.
14:12:11:WU02:FS01:0xa3:Using Gromacs checkpoints
14:12:11:WU02:FS01:0xa3:Mapping NT from 3 to 3 
14:12:11:WU02:FS01:0xa3:Resuming from checkpoint
14:12:11:WU02:FS01:0xa3:Verified 02/wudata_01.log
14:12:11:WU02:FS01:0xa3:Verified 02/wudata_01.trr
14:12:11:WU02:FS01:0xa3:Verified 02/wudata_01.edr
14:12:11:WU02:FS01:0xa3:Completed 5490 out of 500000 steps  (1%)
14:12:14:WU01:FS00:0x16:- Looking at optimizations...
14:12:14:WU01:FS00:0x16:- Working with standard loops on this execution.
14:12:14:WU01:FS00:0x16:- Previous termination of core was improper.
14:12:14:WU01:FS00:0x16:- Going to use standard loops.
14:12:14:WU01:FS00:0x16:- Files status OK
14:12:14:WU01:FS00:0x16:sizeof(CORE_PACKET_HDR) = 512 file=<>
14:12:14:WU01:FS00:0x16:- Expanded 45201 -> 171163 (decompressed 378.6 percent)
14:12:14:WU01:FS00:0x16:Called DecompressByteArray: compressed_data_size=45201 data_size=171163, decompressed_data_size=171163 diff=0
14:12:14:WU01:FS00:0x16:- Digital signature verified
14:12:14:WU01:FS00:0x16:
14:12:14:WU01:FS00:0x16:Project: 11292 (Run 8, Clone 93, Gen 39)
14:12:14:WU01:FS00:0x16:
14:12:14:WU01:FS00:0x16:Entering M.D.
14:12:16:WU01:FS00:0x16:Tpr hash 01/wudata_01.tpr:  2561775053 3879319204 1577966071 1030111370 3458052092
14:12:16:WU01:FS00:0x16:Working on ALZHEIMER DISEASE AMYLOID
14:12:16:WU01:FS00:0x16:Client config unavailable.
14:12:16:WU01:FS00:0x16:Starting GUI Server
14:12:18:Started thread 10 on PID 2688
14:12:21:WARNING:WU01:FS00:FahCore returned an unknown error code which probably indicates that it crashed
14:12:21:WARNING:WU01:FS00:FahCore returned: UNKNOWN_ENUM (-1073741819 = 0xc0000005)
14:12:22:WU01:FS00:Starting
14:12:22:WU01:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/ProgramData/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_16.fah/FahCore_16.exe -dir 01 -suffix 01 -version 703 -lifeline 2688 -checkpoint 15 -gpu 0 -gpu-vendor ati
14:12:22:WU01:FS00:Started FahCore on PID 4396
14:12:22:Started thread 11 on PID 2688
14:12:22:WU01:FS00:Core PID:4476
14:12:22:WU01:FS00:FahCore 0x16 started
14:12:22:WU01:FS00:0x16:
14:12:22:WU01:FS00:0x16:*------------------------------*
14:12:22:WU01:FS00:0x16:Folding@Home GPU Core
14:12:22:WU01:FS00:0x16:Version 2.11 (Thu Dec 9 15:00:14 PST 2010)
14:12:22:WU01:FS00:0x16:
14:12:22:WU01:FS00:0x16:Compiler  : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for 80x86 
14:12:22:WU01:FS00:0x16:Build host: user-f6d030f24f
14:12:22:WU01:FS00:0x16:Board Type: AMD/OpenCL
14:12:22:WU01:FS00:0x16:Core      : x=16
14:12:22:WU01:FS00:0x16: Window's signal control handler registered.
14:12:22:WU01:FS00:0x16:Preparing to commence simulation
14:12:22:WU01:FS00:0x16:- Ensuring status. Please wait.
14:12:31:WU01:FS00:0x16:- Looking at optimizations...
14:12:31:WU01:FS00:0x16:- Working with standard loops on this execution.
14:12:31:WU01:FS00:0x16:- Previous termination of core was improper.
14:12:31:WU01:FS00:0x16:- Going to use standard loops.
14:12:31:WU01:FS00:0x16:- Files status OK
14:12:31:WU01:FS00:0x16:sizeof(CORE_PACKET_HDR) = 512 file=<>
14:12:31:WU01:FS00:0x16:- Expanded 45201 -> 171163 (decompressed 378.6 percent)
14:12:31:WU01:FS00:0x16:Called DecompressByteArray: compressed_data_size=45201 data_size=171163, decompressed_data_size=171163 diff=0
14:12:31:WU01:FS00:0x16:- Digital signature verified
14:12:31:WU01:FS00:0x16:
14:12:31:WU01:FS00:0x16:Project: 11292 (Run 8, Clone 93, Gen 39)
14:12:31:WU01:FS00:0x16:
14:12:31:WU01:FS00:0x16:Entering M.D.
14:12:33:WU01:FS00:0x16:Tpr hash 01/wudata_01.tpr:  2561775053 3879319204 1577966071 1030111370 3458052092
14:12:33:WU01:FS00:0x16:Working on ALZHEIMER DISEASE AMYLOID
14:12:33:WU01:FS00:0x16:Client config unavailable.
14:12:33:WU01:FS00:0x16:Starting GUI Server
14:12:42:WARNING:WU01:FS00:FahCore returned an unknown error code which probably indicates that it crashed
14:12:42:WARNING:WU01:FS00:FahCore returned: UNKNOWN_ENUM (-1073741819 = 0xc0000005)
I've seen some crashes on core17 and driver 13.4 when i game, not only with my card but some other video cards too.

Have a nice day,
bhunt
Top
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: core 16 crashes

Post by bruce »

Turning on verbosity=5 is not helpful. We recommend setting it back to the default of 3.

The 0xc0000005 error is often a hardware error (overclocking? bad drivers? etc.) but they're not easy to diagnose. AMD seems to still be working on their drivers and the latest version may or may not be backwards compatible with core_16. A different version may help but nobody else has reported this problem.

Project: 11292 (Run 8, Clone 93, Gen 39) has not been returned by anyone yet, so we'll have to wait and see what happens when it is reassigned.
Top
7im
Posts: 10179
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:
Contact 7im

Re: core 16 crashes

Post by 7im »

The last driver to work well with core 16 was 12.8.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Top
benj1989
Posts: 9
Joined: Wed Jan 16, 2008 3:21 am

Re: core 16 crashes

Post by benj1989 »

I've tried the 12.8, 13.4 and 13.8b2 drivers without any luck.
I clocked my gpu to 300mhz core and 150mhz memory and it still crashes almost directly

This is some extra crash info:

Code: Select all

 Problem Event Name:	APPCRASH
  Application Name:	FahCore_16.exe
  Application Version:	0.0.0.0
  Application Timestamp:	4d015f84
  Fault Module Name:	OclCpuBackEnd.dll
  Fault Module Version:	3.0.1.1420
  Fault Module Timestamp:	517681a3
  Exception Code:	c0000005
  Exception Offset:	00244f86
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	2067
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789
Top
7im
Posts: 10179
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:
Contact 7im

Re: core 16 crashes

Post by 7im »

Have you used one of the driver cleaner type utilites to clean the system between version changes?
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Top
benj1989
Posts: 9
Joined: Wed Jan 16, 2008 3:21 am

Re: core 16 crashes

Post by benj1989 »

yes, i used the amd cleanup utility
i'm going to run a complete memtest86. i did run it for a while some time ago and didn't let it finish, but it showed no errors then
Top
7im
Posts: 10179
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:
Contact 7im

Re: core 16 crashes

Post by 7im »

Also try memtestG80 for the GPU. http://folding.stanford.edu/home/download-utilities/
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Top
benj1989
Posts: 9
Joined: Wed Jan 16, 2008 3:21 am

Re: core 16 crashes

Post by benj1989 »

cool
memtest86+ did run more than 1 pass without any errors
i will try your gpu memtest, thank you :)

so the cpu folds fine for now
and i just got the core 16 running, it completed the first % already
i uninstalled the intel 2013 opencl sdk and that solved the problem, i guess this is more a fah problem?

i still will need to investigate why the gpu crashes when i fold on it while gaming (it has a lot of reserves since most games have an option to lock on 60fps)
Top
benj1989
Posts: 9
Joined: Wed Jan 16, 2008 3:21 am

Re: core 16 crashes

Post by benj1989 »

ok right, i ran memtestCL (memtestG80 crashes directly). It gives my a lot of errors on the random blocks on 12.8 and 13.8b2 so i guess my card is bad..

gaming and folding also makes my machine crash with 3 other 7950's, maybe 550W isn't enough after all..
Top
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: core 16 crashes

Post by bruce »

When it's fully developed, OpenCL is expected to work on a variety of devices. Here at FAH, we're only concerned about OpenCL on NVidia GPUs and on ATI/AMD GPUs since that's the only devices that we've successfully tested with the FahCores. Drivers provided by NVidia and AMD are required, of course, and as new GPUs are developed, the driver developers often have to make challenging changes to their drivers.

There's no logical reason why OpenCL won't run on an Intel GPU or, for that matter, on and Intel CPU. In your case, you installed the Intel OpenCL drivers so Core_16 might have been trying to use your Intel hardware when it encountered problems -- at least it wasn't running successfully on your Radeon HD 7970. The word from FAH's developers are that they may support Intel hardware someday but at the present time, either the Intel hardware or the Intel drivers still have enough unresolved issues that it's not something they're ready to develop. Given that information, the Intel OpenCL SDK isn't useful for FAH, and if it happens to present an additional device that FahCore_xx might try to use, you would need to be sure to avoid having it try to use that device.

Though I don't recommend it for everyone, if you do wish to do additional experimentation with Intel, you can reinstall the sdk along side of the necessary AMD or NV drivers and experiment with FAHBench. It can provide a great deal of information about the recognizeable drivers and devices on your system. You can test each one separately since the necessary device numbers are reported.

MemtestG80 is not expected to work on Radeon hardware. It will be expecting a G80 device with NV drivers and you don't have either one in your system.

In your case, you probably now have only one device with OpenCL drivers so the right device will be selected using the right API.
Top
benj1989
Posts: 9
Joined: Wed Jan 16, 2008 3:21 am

Re: core 16 crashes

Post by benj1989 »

having the intel opencl installed causes fah choosing that instead of the amd one

on memtestCL i have huge amounts of errors on the random blocks tests on 12.8 and 13.8b2, i will krank my case open soon and test it with a 7950
Top
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: core 16 crashes

Post by bruce »

FAH does have problems when it is forced to choose between various OpenCL devices. The only method that works is to manually adjust the value of opencl-index so that it points to the correct device. FAHBench CAN help you determine in what order that the devices are detected ... or you can use trial-and-error, with the additional knowledge that <opencl-index v='0'/> currently points to (one of) the Intel device(s) in your system.

Running Linux or Windows or MacOS with exactly that hardware may very well configure those same devices in a different order, requiring V7 to be smart enough to figure that all out, and there are open tickets associated with the latest client version.
Top
benj1989
Posts: 9
Joined: Wed Jan 16, 2008 3:21 am

Re: core 16 crashes

Post by benj1989 »

i tried to adjust the opencl index to 0, 1 and -1 and it didn't make any difference
and for the memtestCL errors, apperently they are normal for the 79xx series
Top
P5-133XL
Posts: 2948
Joined: Sun Dec 02, 2007 4:36 am
Hardware configuration: Machine #1:

Intel Q9450; 2x2GB=8GB Ram; Gigabyte GA-X48-DS4 Motherboard; PC Power and Cooling Q750 PS; 2x GTX 460; Windows Server 2008 X64 (SP1).

Machine #2:

Intel Q6600; 2x2GB=4GB Ram; Gigabyte GA-X48-DS4 Motherboard; PC Power and Cooling Q750 PS; 2x GTX 460 video card; Windows 7 X64.

Machine 3:

Dell Dimension 8400, 3.2GHz P4 4x512GB Ram, Video card GTX 460, Windows 7 X32

I am currently folding just on the 5x GTX 460's for aprox. 70K PPD
Location: Salem. OR USA

Re: core 16 crashes

Post by P5-133XL »

I must be missing something for my read of the original post is that Core_16 is the problem not Core_17 and/or OpenCL (other than while gaming). All the reply posts seem to be dealing with Core_17 and OpenCL. Core_16 does not use OpenCL. Gaming (or watching GPU-accelerated videos) while simultaneously GPU folding is generally problematic. So I am confused as to what the actual subject of the thread/issue is.
Image
Top
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: core 16 crashes

Post by bruce »

ATI only supports OpenCL beginning with the HD 5000 series. Prior to that, they supported Brook. [The HD 4000 series is a bit of an anomaly, but that's not significant in your case.] ATI's OpenCL API is supplied with the drivers for your Radeon HD 7970.

FahCore_15 uses OpenMM plus CUDA for NV
FahCore_16 uses OpenMM plus ATI OpenCL
FahCore_17 uses OPENMM for NV (possibly using CUDA/possibly using OpenCL) and OpenCL for ATI.

Core_17 seems to work best with the latest drivers (including the latest version of OpenCL). Core_16 was developed using earlier versions, so there seem to be various opinions about which drivers might be the best. Unfortunately, OpenCL is still a bit of a moving target but ATI is a very ardent developer.
Top
Post Reply

Return to “Problems with AMD/ATI drivers”