V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Moderators: Site Moderators, PandeGroup

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby Eagle » Tue Nov 22, 2011 1:53 pm

Not within the next 3-4 hours. Afterwards, it should be possible.
Michael Jordan: “I can accept failure — But I can’t accept not trying.”
Image
User avatar
Eagle
 
Posts: 157
Joined: Sun Feb 17, 2008 1:06 am
Location: » Earth » Europe » Germany

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby gwildperson » Tue Nov 22, 2011 4:11 pm

That's true. There's a lot of errors that would be different using fahcore_16 and fahcore_11. Let's be sure we're all talking about the same one.
gwildperson
 
Posts: 726
Joined: Tue Dec 04, 2007 8:36 pm

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby Fallen-Angel » Sat Nov 26, 2011 2:45 pm

During the two days of folding, nothing happened (all WUs were successful). I have the Catalyst 11.10 now. All clients had beta flags. Now I set as planned the SMP on beta, first GPU on beta and the second one one advanced.

@Eagle, let us know what's going on at your side, as soon as you can ^^
Image
Image
User avatar
Fallen-Angel
 
Posts: 35
Joined: Sat Sep 24, 2011 11:41 am
Location: Germany

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby Eagle » Sat Nov 26, 2011 6:29 pm

Everything's fine after 4 days of folding - with client-type set to "nornal".
I've changed this to "advanced" now.

The GPU-client will finish its current WU within one hour and I'll be able to tell you more afterwards since the SMP-client never ran into any issues..
User avatar
Eagle
 
Posts: 157
Joined: Sun Feb 17, 2008 1:06 am
Location: » Earth » Europe » Germany

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby Eagle » Sat Nov 26, 2011 9:05 pm

It failed. Heavily. :(

Here's the log:
Code: Select all
19:06:15:Unit 00:Completed 99%
19:06:16:Connecting to assign-GPU.stanford.edu:80
19:06:16:News: Welcome to Folding@Home
19:06:16:Assigned to work server 171.64.65.56
19:06:16:Requesting new work unit for slot 00: RUNNING gpu:0:"Radeon HD 5870 (Cypress)" from 171.64.65.56
19:06:16:Connecting to 171.64.65.56:8080
19:06:17:Slot 00: Downloading 44.12KiB
19:06:18:Slot 00: Download complete
19:06:18:Received Unit: id:02 state:DOWNLOAD error:OK project:11294 run:7 clone:365 gen:50 core:0x16 unit:0x000000340a3b1e5c4d9a1d14f5e5c2e4
19:08:15:Unit 01:Completed 5900000 out of 10000000 steps  (59%)
19:08:50:Unit 00:Completed 100%
19:08:50:Unit 00:Successful run
19:08:50:Unit 00:DynamicWrapper: Finished Work Unit: sleep=10000
19:09:00:Unit 00:Reserved 218912 bytes for xtc file; Cosm status=0
19:09:00:Unit 00:Allocated 218912 bytes for xtc file
19:09:00:Unit 00:- Reading up to 218912 from "00/wudata_01.xtc": Read 218912
19:09:00:Unit 00:Read 218912 bytes from xtc file; available packet space=786211552
19:09:00:Unit 00:xtc file hash check passed.
19:09:00:Unit 00:Reserved 33528 33528 786211552 bytes for arc file=<00/wudata_01.trr> Cosm status=0
19:09:00:Unit 00:Allocated 33528 bytes for arc file
19:09:00:Unit 00:- Reading up to 33528 from "00/wudata_01.trr": Read 33528
19:09:00:Unit 00:Read 33528 bytes from arc file; available packet space=786178024
19:09:00:Unit 00:trr file hash check passed.
19:09:00:Unit 00:Allocated 560 bytes for edr file
19:09:00:Unit 00:Read bedfile
19:09:00:Unit 00:edr file hash check passed.
19:09:00:Unit 00:Allocated 0 bytes for logfile
19:09:00:Unit 00:Could not open/read logfile=<00/wudata_01.log>; Cosm status=-1
19:09:00:Unit 00:GuardedRun: success in DynamicWrapper
19:09:00:Unit 00:GuardedRun: done
19:09:00:Unit 00:Run: GuardedRun completed.
19:09:02:Unit 00:- Writing 253512 bytes of core data to disk...
19:09:02:Unit 00:Done: 253000 -> 251978 (compressed to 99.5 percent)
19:09:02:Unit 00:  ... Done.
19:09:02:Unit 00:- Shutting down core
19:09:02:Unit 00:
19:09:02:Unit 00:Folding@home Core Shutdown: FINISHED_UNIT
19:09:02:FahCore, running Unit 00, returned: FINISHED_UNIT (100 = 0x64)
19:09:02:Sending unit results: id:00 state:SEND error:OK project:5732 run:2 clone:562 gen:911 core:0x11 unit:0x72dd550a4ed0fbed038f023200021664
19:09:02:Unit 00: Uploading 246.57KiB to 171.64.65.102
19:09:02:Connecting to 171.64.65.102:8080
19:09:02:Starting Unit 02
19:09:02:Running core: "X:/My Projects/Folding At Home/cores/www.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_16.fah/FahCore_16.exe" -dir 02 -suffix 01 -lifeline 3960 -version 701 -checkpoint 15 -gpu 0
19:09:02:Started core on PID 6336
19:09:02:FahCore 0x16 started
19:09:03:Unit 02:
19:09:03:Unit 02:*------------------------------*
19:09:03:Unit 02:Folding@Home GPU Core
19:09:03:Unit 02:Version 2.11 (Thu Dec 9 15:00:14 PST 2010)
19:09:03:Unit 02:
19:09:03:Unit 02:Compiler  : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for 80x86
19:09:03:Unit 02:Build host: user-f6d030f24f
19:09:03:Unit 02:Board Type: AMD/OpenCL
19:09:03:Unit 02:Core      : x=16
19:09:03:Unit 02: Window's signal control handler registered.
19:09:03:Unit 02:Preparing to commence simulation
19:09:03:Unit 02:- Looking at optimizations...
19:09:03:Unit 02:DeleteFrameFiles: successfully deleted file=02/wudata_01.ckp
19:09:03:Unit 02:- Created dyn
19:09:03:Unit 02:- Files status OK
19:09:03:Unit 02:sizeof(CORE_PACKET_HDR) = 512 file=<>
19:09:03:Unit 02:- Expanded 44671 -> 169787 (decompressed 380.0 percent)
19:09:03:Unit 02:Called DecompressByteArray: compressed_data_size=44671 data_size=169787, decompressed_data_size=169787 diff=0
19:09:03:Unit 02:- Digital signature verified
19:09:03:Unit 02:
19:09:03:Unit 02:Project: 11294 (Run 7, Clone 365, Gen 50)
19:09:03:Unit 02:
19:09:03:Unit 02:Assembly optimizations on if available.
19:09:03:Unit 02:Entering M.D.
19:09:05:Unit 02:Tpr hash 02/wudata_01.tpr:  732400167 1965635053 3035110118 1400899485 3606576971
19:09:05:Unit 02:Working on PEPTIDE (1-42)
19:09:05:Unit 02:Client config unavailable.
19:09:05:Unit 02:Starting GUI Server
19:09:08:Unit 00: 74.62%
19:09:10:Unit 00: Upload complete
19:09:10:Server responded WORK_ACK (400)
19:09:10:Cleaning up Unit 00
19:09:22:FahCore, running Unit 02, returned: UNKNOWN_ENUM (-1073740777 = 0xc0000417)
19:09:22:Starting Unit 02
19:09:22:Running core: "X:/My Projects/Folding At Home/cores/www.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_16.fah/FahCore_16.exe" -dir 02 -suffix 01 -lifeline 3960 -version 701 -checkpoint 15 -gpu 0
19:09:22:Started core on PID 8992
19:09:22:FahCore 0x16 started
19:09:22:Unit 02:
19:09:22:Unit 02:*------------------------------*
19:09:22:Unit 02:Folding@Home GPU Core
19:09:22:Unit 02:Version 2.11 (Thu Dec 9 15:00:14 PST 2010)
19:09:22:Unit 02:
19:09:22:Unit 02:Compiler  : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for 80x86
19:09:22:Unit 02:Build host: user-f6d030f24f
19:09:22:Unit 02:Board Type: AMD/OpenCL
19:09:22:Unit 02:Core      : x=16
19:09:22:Unit 02: Window's signal control handler registered.
19:09:22:Unit 02:Preparing to commence simulation
19:09:22:Unit 02:- Ensuring status. Please wait.
19:09:32:Unit 02:- Looking at optimizations...
19:09:32:Unit 02:- Working with standard loops on this execution.
19:09:32:Unit 02:- Previous termination of core was improper.
19:09:32:Unit 02:- Files status OK
19:09:32:Unit 02:sizeof(CORE_PACKET_HDR) = 512 file=<>
19:09:32:Unit 02:- Expanded 44671 -> 169787 (decompressed 380.0 percent)
19:09:32:Unit 02:Called DecompressByteArray: compressed_data_size=44671 data_size=169787, decompressed_data_size=169787 diff=0
19:09:32:Unit 02:- Digital signature verified
19:09:32:Unit 02:
19:09:32:Unit 02:Project: 11294 (Run 7, Clone 365, Gen 50)
19:09:32:Unit 02:
19:09:32:Unit 02:Entering M.D.
19:09:34:Unit 02:Tpr hash 02/wudata_01.tpr:  732400167 1965635053 3035110118 1400899485 3606576971
19:09:34:Unit 02:Working on PEPTIDE (1-42)
19:09:34:Unit 02:Client config unavailable.
19:09:37:FahCore, running Unit 02, returned: UNKNOWN_ENUM (-1073740777 = 0xc0000417)


So, to me it seems like a problem of core 16 with the driver only.
User avatar
Eagle
 
Posts: 157
Joined: Sun Feb 17, 2008 1:06 am
Location: » Earth » Europe » Germany

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby MtM » Sun Nov 27, 2011 12:57 am

Eagle am I wrong with thinking that client type 'normal' you've been running fahcore_11 work unit's?

And with 'advanced' you're getting fahcore_16 work units which fail on start?

If so, could you download this, extract and run V7-Diagnostic as admin. Post the report here. ( download is labeled as depreciated since I planned on making some more changes to it, ignore that )

It will show some system information including cal and opencl device enumeration and driver info, maybe it can help seeing why it is going wrong.
MtM
 
Posts: 3054
Joined: Fri Jun 27, 2008 2:20 pm
Location: The Netherlands

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby Fallen-Angel » Sun Nov 27, 2011 1:53 am

I must admit that during the time, when my ENUM-error appeared, programs (like Firefox, Winamp etc.) and games crashed after some time. I still didn't find any answer or solution to that UNKNOWN_ENUM (-1073740777 = 0xc0000417)-error on the Internet. We still need more details.

The only website which gives a little bit of information is wiki-errors.com. Here you find a general description of that "phenomenon" and some links (which have no description at all) to similar errors. Unfortunately their repair tool wont work on win7. As I mentioned before, I would reinstall the Catalyst driver (by completely deleting the display device in hardware manager) and the whole F@H client.
User avatar
Fallen-Angel
 
Posts: 35
Joined: Sat Sep 24, 2011 11:41 am
Location: Germany

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby bruce » Sun Nov 27, 2011 2:24 am

All errors with values greater than 0xc0000000 are Windows errors. The first places to look for the causes is Drivers and Hardware. They can also be caused by bad programming. I don't THINK there's any of that in FAH but it's impossible to prove a negative. the fact that you've had problems with Firefox/Winamp/etc. also tends to support the idea that it's not FAH, itself, but something that's common to multiple programs .... like Drivers or Hardware.
bruce
 
Posts: 22322
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby Eagle » Sun Nov 27, 2011 12:13 pm

MtM wrote:Eagle am I wrong with thinking that client type 'normal' you've been running fahcore_11 work unit's?

No, you're absolutely right.

MtM wrote:And with 'advanced' you're getting fahcore_16 work units which fail on start?

Correct.

MtM wrote:If so, could you download this, extract and run V7-Diagnostic as admin. Post the report here. ( download is labeled as depreciated since I planned on making some more changes to it, ignore that )

Done. No deprecation-warning seen so far..

MtM wrote:It will show some system information including cal and opencl device enumeration and driver info, maybe it can help seeing why it is going wrong.

Done. See. below (I didn't change the German (error) messages; if you need one translated, please let me know - I'll be glad to help) for 289 errors regarding FAH V7 with core 16:
Code: Select all
[2011-11-27] - 04:25:09 - V7-Diagnostic V7-Diagnostic 1.0.0.0 logging started

[2011-11-27] - 04:25:09 - Starting diagnostic run
[2011-11-27] - 04:25:10 - Os: Microsoft Windows NT 6.1.7601 Service Pack 1 (x86)
[2011-11-27] - 04:25:10 -
Open Hardware Monitor Report

--------------------------------------------------------------------------------

Version: 0.3.0.2

--------------------------------------------------------------------------------

Common Language Runtime: 2.0.50727.5448
Operating System: Microsoft Windows NT 6.1.7601 Service Pack 1
Process Type: 32-Bit

--------------------------------------------------------------------------------

Ring0

Status: Installing driver "R:\tmp9A43.tmp" failed and file exists

Exception: Der Treiber konnte nicht geladen werden. (Ausnahme von HRESULT: 0x800704FB)

--------------------------------------------------------------------------------

Sensors

|
+- Gigabyte GA-890FXA-UD7 (/mainboard)
|
+- AMD Phenom II X4 955 Processor (/amdcpu/0)
|  +- CPU Core #1    :  3214.66  3214.66  3214.66 (/amdcpu/0/clock/1)
|  +- CPU Core #2    :  3214.66  3214.66  3214.66 (/amdcpu/0/clock/2)
|  +- CPU Core #3    :  3214.66  3214.66  3214.66 (/amdcpu/0/clock/3)
|  +- CPU Core #4    :  3214.66  3214.66  3214.66 (/amdcpu/0/clock/4)
|  +- CPU Total      :      100      100      100 (/amdcpu/0/load/0)
|  +- CPU Core #1    :      100      100      100 (/amdcpu/0/load/1)
|  +- CPU Core #2    :      100      100      100 (/amdcpu/0/load/2)
|  +- CPU Core #3    :      100      100      100 (/amdcpu/0/load/3)
|  +- CPU Core #4    :      100      100      100 (/amdcpu/0/load/4)
|
+- ATI Radeon HD 5800 Series (/atigpu/0)
|  +- GPU Core       :    1.163    1.163    1.163 (/atigpu/0/voltage/0)
|  +- GPU Core       :      875      875      875 (/atigpu/0/clock/0)
|  +- GPU Memory     :     1225     1225     1225 (/atigpu/0/clock/1)
|  +- GPU Core       :     61.5     61.5     61.5 (/atigpu/0/temperature/0)
|  +- GPU Core       :       54       54       54 (/atigpu/0/load/0)
|  +- GPU Fan        :       47       47       47 (/atigpu/0/control/0)

--------------------------------------------------------------------------------

Parameters

|
+- Gigabyte GA-890FXA-UD7 (/mainboard)
|
+- AMD Phenom II X4 955 Processor (/amdcpu/0)
|
+- ATI Radeon HD 5800 Series (/atigpu/0)

--------------------------------------------------------------------------------

Mainboard

SMBIOS Version: 2.4

BIOS Vendor: Award Software International, Inc.
BIOS Version: F4

Mainboard Manufacturer: Gigabyte Technology Co., Ltd.
Mainboard Name: GA-890FXA-UD7
Mainboard Version:


[2011-11-27] - 04:25:10 - Ati Display Library

Status: OK

Number of GPUs: 3
Driver Version:  Release:


Adapter report (0)


Present: True
Active: True
AdapterID: 0x297F740
AdapterIndex: 0
AdapterName: AdapterName: ATI Radeon HD 5800 Series
Bus: 0
DeviceID: 0x6898
Device Number: 0
Function Number: 0
UDID: UDID: PCI_VEN_1002&DEV_6898&SUBSYS_22891787&REV_00_4&34A7DA13&0&0010A
VendorID: 0x1002



Adapter report (1)


Present: True
Active: False
AdapterID: 0x297F740
AdapterIndex: 1
AdapterName: AdapterName: ATI Radeon HD 5800 Series
Bus: 0
DeviceID: 0x6898
Device Number: 0
Function Number: 0
UDID: UDID: PCI_VEN_1002&DEV_6898&SUBSYS_22891787&REV_00_4&34A7DA13&0&0010&02A
VendorID: 0x1002



Adapter report (2)


Present: True
Active: False
AdapterID:
AdapterIndex: 2
AdapterName: AdapterName: ATI Radeon HD 5800 Series
Bus: 0
DeviceID: 0x6898
Device Number: 0
Function Number: 0
UDID: UDID: PCI_VEN_1002&DEV_6898&SUBSYS_22891787&REV_00_4&34A7DA13&0&0010&03A
VendorID: 0x1002




[2011-11-27] - 04:25:10 - Opencl enumeration:- 1 platforms
platform:- 0
:-- AMD Accelerated Parallel Processing - Advanced Micro Devices, Inc.- OpenCL 1.1 AMD-APP-SDK-v2.5 (793.1)
Extensions:- cl_khr_icd cl_amd_event_callback cl_amd_offline_devices cl_khr_d3d10_sharing

Number of devices:- 1
Index:- 1
Attribute_count:= 50
Type:- GPU
VendorID:- 4098
MaxComputeUnits:- 20
MaxWorkItemDimensions:- 3
MaxWorkGroupSize:- 256
MaxWorkItemSizes:- 256
PreferredVectorWidthChar:- 16
PreferredVectorWidthShort:- 8
PreferredVectorWidthInt:- 4
PreferredVectorWidthLong:- 2
PreferredVectorWidthFloat:- 4
PreferredVectorWidthDouble:- 2
MaxClockFrequency:- 875
AddressBits:- 32
MaxReadImageArgs:- 128
MaxWriteImageArgs:- 8
MaxMemAllocSize:- 536870912
Image2DMaxWidth:- 8192
Image2DMaxHeight:- 8192
Image3DMaxWidth:- 2048
Image3DMaxHeight:- 2048
Image3DMaxDepth:- 2048
ImageSupport:- True
MaxParameterSize:- 1024
MaxSamplers:- 16
MemBaseAddrAlign:- 32768
MinDataTypeAlignSize:- 128
SingleFPConfig:- 62
GlobalMemCacheType:- 0
GlobalMemCacheLineSize:- 0
GlobalMemCacheSize:- 0
GlobalMemSize:- 1073741824
MaxConstantBufferSize:- 65536
MaxConstantArgs:- 8
LocalMemType:- 0
LocalMemSize:- 32768
ErrorCorrectionSupport:- False
ProfilingTimerResolution:- 1
EndianLittle:- True
Available:- True
CompilerAvailable:- True
ExecutionCapabilities:- 1
QueueProperties:- 2
Name:- Cypress
Vendor:- Advanced Micro Devices, Inc.
DriverVersion:- CAL 1.4.1607 (VM)
Profile:- FULL_PROFILE
Version:- OpenCL 1.1 AMD-APP-SDK-v2.5 (793.1)
Extensions:- cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_atomic_counters_32 cl_amd_device_attribute_query cl_amd_vec3 cl_amd_printf cl_amd_media_ops cl_amd_popcnt cl_khr_d3d10_sharing
Platform:- 1619043572


[2011-11-27] - 04:25:10 - CAL Runtime:- 1.4.1607
Ordinal:- 0
Device_info_maxResource1DWidth:- 16384
Device_info_maxResource2DHeight :- 16384
Device_info_maxResource2DWidth:- 16384
Target:- CAL_TARGET_CYPRESS
b3dProgramGrid:- CAL_TRUE
bUAVMemExport:- CAL_FALSE
cachedRemoteram:- 2047
computeShader:- CAL_TRUE
doublePrecision:- CAL_TRUE
engineClock:- 875
globalDataShare:- CAL_TRUE
globalGPR:- CAL_TRUE
localDataShare:- CAL_TRUE
localRam:- 1024
localMemExport:- CAL_TRUE
localMemoryClock:- 1225
numberOfShaderEngines:- 2
numberOfSIMD:- 20
numberOfUAVs:- 12
pitch_alignment:- 256
surface_alignment:- 4096
target:- CAL_TARGET_CYPRESS
targetRevision:- 2
uncachedRemoteRAM:- 2047
wavefrontSize:- 64


[2011-11-27] - 04:25:10 - Openining registry root LOCAL_MACHINE
[2011-11-27] - 04:25:10 - Trying 'Software\Microsoft\Windows\CurrentVersion\Uninstall\FAHClient'
[2011-11-27] - 04:25:10 - Key openend succesfully!
[2011-11-27] - 04:25:10 - Found 'DisplayName' value='FAHClient'
[2011-11-27] - 04:25:10 - Found 'UninstallString' value='C:\Program Files (x86)\Folding At Home\Uninstall.exe'
[2011-11-27] - 04:25:10 - Found 'DisplayIcon' value='C:\Program Files (x86)\Folding At Home\FAHClient.ico'
[2011-11-27] - 04:25:10 - FAHClient location set to C:\Program Files (x86)\Folding At Home
[2011-11-27] - 04:25:10 - Found 'URLInfoAbout' value='http://folding.stanford.edu/'
[2011-11-27] - 04:25:10 - Found 'Publisher' value='Stanford University'
[2011-11-27] - 04:25:10 - Found 'DisplayVersion' value='7.1.38'
[2011-11-27] - 04:25:10 - Found 'DataDirectory' value='M:\Eigene Projekte\Folding At Home'
[2011-11-27] - 04:25:10 - DataLocation set to M:\Eigene Projekte\Folding At Home
[2011-11-27] - 04:25:10 - Reading Config.xml file.
[2011-11-27] - 04:25:10 - Reading client configuration: True
[2011-11-27] - 04:25:10 - Client config report
Remote command server, port: 36330 Password length(!): 0
User configaration, name: Eagle3386 Team: 34361 passkey length: 32 valid: True
Number of folding slots: 1
Slot: 0 - GPU
-slot: 1
User count: 1
Additional configuration sections: 2
 Logging
-log-rotate-max: 5
 Network
-proxy: :8080

[2011-11-27] - 04:25:10 - Running -lspci: False
[2011-11-27] - 04:25:10 -
[2011-11-27] - 04:25:10 - Client info:
[2011-11-27] - 04:25:10 - FAHCLient --info
Website: http://folding.stanford.edu/
Copyright: (c) 2009-2011 Stanford University
Author: Joseph Coffland <joseph@cauldrondevelopment.com>
Args: --info
Version: 7.1.38
Date: Oct 6 2011
Time: 19:57:04
SVN Rev: 3080
Branch: fah/trunk/client
Compiler: Intel(R) C++ MSVC 1500 mode 1200
Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
Platform: win32 XP
Bits: 32
Mode: Release
CPU: AMD Phenom(tm) II X4 955 Processor
CPU ID: AuthenticAMD Family 16 Model 4 Stepping 2
CPUs: 4
Memory: 16.00GiB
Free Memory: 9.25GiB
Threads: WINDOWS_THREADS
On Battery: false
UTC offset: 1
PID: 5672
CWD: C:/Program Files (x86)/Folding At Home
OS: Windows 7 Ultimate
OS Arch: AMD64
GPUs: 1
GPU 0: ATI:4 Radeon HD 5870 (Cypress)
CUDA: Not detected
Win32 Service: false

[2011-11-27] - 04:25:10 - Query event log..
[2011-11-27] - 04:25:22 - Reporting 289 event log entries.

Log entry-265
2011-11-26 20:09:06 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x18c0
Startzeit der fehlerhaften Anwendung: 0x01ccac6edc3b4832
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 1c28654c-1862-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-266
2011-11-26 20:09:33 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x2320
Startzeit der fehlerhaften Anwendung: 0x01ccac6ee7d1e9b2
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 2c71a3f8-1862-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-267
2011-11-26 20:10:34 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x25ac
Startzeit der fehlerhaften Anwendung: 0x01ccac6f0bb01bf5
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 505358b8-1862-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-268
2011-11-26 20:12:11 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x2200
Startzeit der fehlerhaften Anwendung: 0x01ccac6f45970a20
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 8a395c80-1862-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-269
2011-11-26 20:14:48 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0xf2c
Startzeit der fehlerhaften Anwendung: 0x01ccac6fa339d4fd
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: e7fb6fa2-1862-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-270
2011-11-26 20:16:09 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x2130
Startzeit der fehlerhaften Anwendung: 0x01ccac6fd943054a
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 183f7d4e-1863-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-271
2011-11-26 20:16:35 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x1fbc
Startzeit der fehlerhaften Anwendung: 0x01ccac6fe33c928e
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 27f30979-1863-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-272
2011-11-26 20:17:35 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x15cc
Startzeit der fehlerhaften Anwendung: 0x01ccac70071e956f
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 4bbc05bd-1863-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-273
2011-11-26 20:19:13 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x23a8
Startzeit der fehlerhaften Anwendung: 0x01ccac7041114396
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 85b1730e-1863-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-274
2011-11-26 20:21:50 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x1d8c
Startzeit der fehlerhaften Anwendung: 0x01ccac709ed579a1
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: e38316cb-1863-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-275
2011-11-26 20:22:11 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x224c
Startzeit der fehlerhaften Anwendung: 0x01ccac70b0d71d20
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: efcae273-1863-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-276
2011-11-26 20:22:26 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x19ec
Startzeit der fehlerhaften Anwendung: 0x01ccac70b41e1709
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: f8bce6eb-1863-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-277
2011-11-26 20:23:26 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x1d08
Startzeit der fehlerhaften Anwendung: 0x01ccac70d7fc494c
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 1c9a55db-1864-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-278
2011-11-26 20:25:03 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x1304
Startzeit der fehlerhaften Anwendung: 0x01ccac7111dcf5cf
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 567c13d3-1864-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-279
2011-11-26 20:32:30 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x2158
Startzeit der fehlerhaften Anwendung: 0x01ccac721c11d8db
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 60fd915e-1865-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-280
2011-11-26 20:32:49 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x1d20
Startzeit der fehlerhaften Anwendung: 0x01ccac722d5e0c62
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 6c518395-1865-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-281
2011-11-26 20:33:04 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x14f0
Startzeit der fehlerhaften Anwendung: 0x01ccac7230a5f0af
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 7542c4ba-1865-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-282
2011-11-26 20:34:04 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0xb00
Startzeit der fehlerhaften Anwendung: 0x01ccac725481b1e8
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 992081cb-1865-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-283
2011-11-26 20:35:41 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x11b0
Startzeit der fehlerhaften Anwendung: 0x01ccac728e606294
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: d2fc9a5d-1865-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-284
2011-11-26 20:50:28 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x176c
Startzeit der fehlerhaften Anwendung: 0x01ccac749de55735
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: e38b13a1-1867-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-285
2011-11-26 20:50:47 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x1d44
Startzeit der fehlerhaften Anwendung: 0x01ccac74b00e3257
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: ef09e708-1867-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-286
2011-11-26 20:51:02 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x2264
Startzeit der fehlerhaften Anwendung: 0x01ccac74b358fcde
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: f7fa3dca-1867-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-287
2011-11-26 20:52:03 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x1f90
Startzeit der fehlerhaften Anwendung: 0x01ccac74d73a3c6c
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 1bd9f6b3-1868-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-288
2011-11-26 20:53:40 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x17b0
Startzeit der fehlerhaften Anwendung: 0x01ccac75111f7ce1
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: 55c37cf7-1868-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000
Log entry-289
2011-11-26 21:19:30 : Name der fehlerhaften Anwendung: FahCore_16.exe, Version: 0.0.0.0, Zeitstempel: 0x4d015f84
Name des fehlerhaften Moduls: amdocl.dll, Version: 2.5.793.1, Zeitstempel: 0x4ea76e79
Ausnahmecode: 0xc0000417
Fehleroffset: 0x006dd4f5
ID des fehlerhaften Prozesses: 0x233c
Startzeit der fehlerhaften Anwendung: 0x01ccac78ac29a408
Pfad der fehlerhaften Anwendung: M:\Eigene Projekte\Folding At Home\cores\www.stanford.edu\~pande\Win32\AMD64\ATI\R600\Core_16.fah\FahCore_16.exe
Pfad des fehlerhaften Moduls: C:\Windows\system32\amdocl.dll
Berichtskennung: f1d6daa0-186b-11e1-9876-1c6f65921f9d
Category : Anwendungsabsturzereignisse
InstanceID : 1000

[2011-11-27] - 04:25:22 - Closing diagnostics


Note: Log entry #1 to 264 got cut due to
The submitted form was invalid. Try submitting again.
Your message contains 205881 characters. The maximum number of allowed characters is 60000.


bruce wrote:All errors with values greater than 0xc0000000 are Windows errors. The first places to look for the causes is Drivers and Hardware. They can also be caused by bad programming. I don't THINK there's any of that in FAH but it's impossible to prove a negative. the fact that you've had problems with Firefox/Winamp/etc. also tends to support the idea that it's not FAH, itself, but something that's common to multiple programs .... like Drivers or Hardware.

I've never experienced such problems. However, I do agree that it's a driver-problem. Hardware could be a problem, but I don't know any way of proving this, because I don't have a replacement for each component.

However, I've got a slightly off-topic question regarding my next machine-setup (Q1/Q2 in 2012): is an FX-8150 because of its multi-thread architecture better than a i7-2600 / i7-3930 in FAH? Because if so, I'd stay with AMD. Otherwise, after more than 11 years of loyalty, I'd switch platforms (again).

Thanks in advance,
Martin
User avatar
Eagle
 
Posts: 157
Joined: Sun Feb 17, 2008 1:06 am
Location: » Earth » Europe » Germany

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby toTOW » Sun Nov 27, 2011 1:24 pm

I wonder if that's the same problem I'm seeing here : viewtopic.php?p=200048#p200048 ...

I'll give it a try with no beta flags to see if I'm able to start the core ...
Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.

FAH-Addict : latest news, tests and reviews about Folding@Home project.

Image
User avatar
toTOW
Site Moderator
 
Posts: 8689
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby MtM » Sun Nov 27, 2011 1:50 pm

Those errors all point to the opencl driver dll.

First of all, have you tried running memtestCL? It might run, I'm not 100% sure it uses all of the api calls the core's make to the runtime but if it doesn't run either we're sure it's the driver.

If the driver is broken, below is a suggested downgrade but I would like to rule something else out before you do that as the driver shouldn't cause this. Run a malwarebyte antimalware scan, see if it detects anything. If it's clean, try this: source
I'd do this:

1. download driver sweeper (google)

2. open device manager (control panel), right click on the video card and select uninstall

3. open task manager (CTRL+SHIFT+ESC) and end all ati2evxx.exe processes

4. clean all ATI files with driver sweeper

5. reboot and '*added note-> run the diagnostics and ensure everything is gone and then..' install new driver


Try first with the same drivers ( 11.11 ), if that doesn't work repeat previous step and try downgrading to the 11.7 catalyst drivers to downgrade your openCL package from OpenCL 1.1 AMD-APP-SDK-v2.5 (793.1) to OpenCL 1.1 AMD-APP-SDK-v2.4 (650.9)

Not saying this will definitively work, but it's what I'd do.

Edit: toTow do you have any crash log entries to compare? Point to the same amdopencl.dll? What dll version? Also I'm not sure but I think 11.7 is the 'newest' one still based on the app-sdk 2.4 openCL drivers, anything later is 2.5 but with increasing build numbers. Also, does memtestCL run?
MtM
 
Posts: 3054
Joined: Fri Jun 27, 2008 2:20 pm
Location: The Netherlands

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby toTOW » Sun Nov 27, 2011 2:02 pm

All the log I have is from the client, which doesn't log many things actually ...

Anyway, as soon as I start an OpenCL application (and not only FAH), my card goes into VPU Recover loop that leads to either VGA mode, a BSOD on ATI driver or no more access to advanced functions (3D / OpenCL / CAL / Video acceleration).

I'll test more things tonight (including MemtestCL) ...

And I'm thinking more and more a driver issue (in both 11.10 and 11.11), with this thread also pointing to it (a downgrade to 11.9 solved his issue) : viewtopic.php?f=51&t=20104
User avatar
toTOW
Site Moderator
 
Posts: 8689
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby MtM » Sun Nov 27, 2011 2:15 pm

Sorry 11.7 = SDK 2.3, 11.9 was sdk 2.4

http://forums.amd.com/forum/messageview ... erthread=y seems SETI is also broken with 10.10 and upwards.
MtM
 
Posts: 3054
Joined: Fri Jun 27, 2008 2:20 pm
Location: The Netherlands

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby Eagle » Sun Nov 27, 2011 2:26 pm

I assume I can confirm it's the driver - the random blocks-iteration #38 failed with 995 (!) errors.

Should I downgrade or does FAH contact AMD to resolve the issue?
If that means I have to stay on "normal" GPU-WUs for a couple of weeks then that's fine with me.. :)
User avatar
Eagle
 
Posts: 157
Joined: Sun Feb 17, 2008 1:06 am
Location: » Earth » Europe » Germany

Re: V7.1.38 cause UNKNOWN_ENUM (-10 = 0xfffffff6) on ATI

Postby toTOW » Sun Nov 27, 2011 2:36 pm

MtM wrote:Sorry 11.7 = SDK 2.3, 11.9 was sdk 2.4

http://forums.amd.com/forum/messageview ... erthread=y seems SETI is also broken with 10.10 and upwards.


Great that it was reported by Raistmer. He's the developer of Lunatics optimized SETI applications for GPU (Astropulse and Multibeam which uses OpenCL on AMD GPUs).

I sent an email to Mike Houston to point him to our issues ...
User avatar
toTOW
Site Moderator
 
Posts: 8689
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France

PreviousNext

Return to V7.1.52 Windows/Linux

Who is online

Users browsing this forum: No registered users and 1 guest

cron