Posts by mesyn191

1) Message boards : Number crunching : AMD R9 290X does not receive any GPU work (Message 63466) Posted 26 Apr 2015 by mesyn191 Post: Why would a new server be needed to update the list of acceptable GPU's? That doesn't make any sense at all. Nor is a lot of testing needed. They're not rewriting any major parts of the database or code to update a list of acceptable GPU's! And I've donated before in the past.
2) Message boards : Number crunching : AMD R9 290X does not receive any GPU work (Message 63382) Posted 15 Apr 2015 by mesyn191 Post: Geez its been like 6 months+ and this issue still isn't fixed?! C'mon guys...
3) Message boards : Number crunching : Updated GPU Requirements (Currently not supporting GPU tasks) (Message 62851) Posted 16 Dec 2014 by mesyn191 Post: Hey all, I actually mentioned working on GPU identification on the server around the office recently in another context. It is definitely on my list of things I plan on doing in the near future. Jake W. So its been around 2 months now and this issue still doesn't seem to be fixed and haven't seen anything in the way of news about it either in a while....
4) Message boards : Number crunching : R9 290 (Message 62607) Posted 21 Oct 2014 by mesyn191 Post: This problem still exists over a month later. Anyone have an idea when it will be fixed? If ever? The silence is kinda deafening here.
5) Message boards : Number crunching : 4x HD7990 in one PC? (Message 61134) Posted 16 Feb 2014 by mesyn191 Post: Yeah it depends on the project. Milkyway is not bandwidth intensive or even particularly data intensive (in terms of memory required). It is however extremely math intensive which is why AMD GPU's do so well at crunching it. You can test this by down clocking your VRAM quite a bit and it'll hardly effect or no effect on crunch time for your WU. Doesn't save a lot of power though so its usually not worth bothering with unless you have a dedicated 24/7 crunching card. OP: You can do it with one machine, barring weird BIOS issues with that workstation mobo which ASUS is known for, but its soooo much easier to do it with those cards spread across 2 machines.
6) Message boards : Number crunching : Benchmark results - times wanted for any hardware, CPU or GPU, old or new! (Message 61133) Posted 16 Feb 2014 by mesyn191 Post: AMD7970 (GPU: 1Ghz, VRAM: 1.4Ghz), factory OC'ed video card Catalyst ver: 14.1 CPU: Intel i7-2700K @ 4.3Ghz, slight over volt, 24/7 stable for last few years Mobo chipset: z68 BOINC ver: 7.2.39 x64 OS: Win7 x64 Run time for avg. of 5 WU with a 213.76 credit: 77.762 I've been using the 14.1 Catalyst drivers for over a week and while perfectly stable they seem to have increased my run time a bit. Maybe 3-5 seconds. In game performance is a smidge better though.
7) Message boards : News : Separation Modified Fit v1.28 Release (Message 59928) Posted 19 Sep 2013 by mesyn191 Post: Errors went down but still getting a decent amount of invalids and heaps of "validation inconclusive". Error: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=566505800 Some invalids, have 18 ATM: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=568001955 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=567946689 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=567917941 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=567885234 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=567656642 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=567542566 Some "validation inconclusive", have 163 ATM: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=568060057 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=568054361 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=568052940 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=568051751 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=568049969 http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=568046771 Currently using AMD's beta 13.10 drivers which actually seemed to improve things a bit over the 13.8b betas and the driver before that one too, can't remember what I was using.
8) Message boards : Number crunching : ARM Devices (Message 57804) Posted 5 Apr 2013 by mesyn191 Post: You are correct on ALL counts, but I would like to point out that when Boinc, or more exactly Seti, first began it started with a handful of Scientists and then grew into the millions of users. There is certainly a lot of potential in the future for ARM chips to become significant contributors. I just don't think its going to come from portable/battery operate ARM devices nor other integrated ARM devices. I would love to have something like a HPC many core ARM chip in desktop form to crunch on but those don't exist on the consumer level of buying power and aren't likely too either any time soon. A RAC of 660 - is that poor? Depends on your definition of poor of course. In terms of performance vs power consumption or performance vs price on a chip to chip basis its great. In terms of total performance vs modern-ish x86 chips IMO it'd be poor. Running power hungry apps on devices that are very power limited is unlikely to take off in a big way... Really I swear I'm not trying to piss on your guys enthusiasm/dreams here but there must be at least some thought given to practicality when forming your expectations.
9) Message boards : Number crunching : ARM Devices (Message 57796) Posted 4 Apr 2013 by mesyn191 Post: There is already available, and released, Boinc software for the ARM devices and it is working right this minute. Here is a link to the release forum showing the changes from version to version: http://boinc.berkeley.edu/dev/forum_thread.php?id=8203 That won't work on autoclave, car, washing machine ARM micro controllers, etc. which are still the vast overwhelming majority of ARM devices out there. Most of them don't even have a OS per se much less Android running on them or are even capable of running Android. If they have a OS at all it'll be something like QNX RTOS and stripped to the bare bones with only a command line interface. A straight forward recompile won't even work half the time since many are semi-custom CPU's with no public documentation out there. I have no doubt you could eventually get something running on these sorts of devices, that isn't in question, but the effort vs. reward isn't there even if you got BOINC running on dozens of them for every PC you had. And even if you were still willing to go through with it that would apply to you and a few other dedicated crunchers. Almost no one else is willing to go through that effort to crunch a handful more WU a day. Most people can't even be bothered to mod chip their own console and that is way easier than what you're talking about doing. For that matter most people aren't even bothering to run BOINC on their home PC which is pretty damn easy to do. Several projects have ARM devices actively crunching right this minute for them. That doesn't mean much of anything though and certainly wasn't in dispute either. None of these projects are even close to having billions of ARM devices running BOINC of any sort for a reason.
10) Message boards : Number crunching : ARM Devices (Message 57793) Posted 4 Apr 2013 by mesyn191 Post: You are correct, but we are at the typical business model scenario...is it better to make a 1 dollar profit on 100 items or a 100 dollar profit on 1 item? Depends on the item of course. Many of these ARM CPU's are effectively inaccessible to anyone but the most dedicated number cruncher. We're talking about stuff like micro controllers for autoclaves, washing machines, cars, etc. The vast overwhelming majority of people won't even have a clue as to how you'd even begin getting BOINC up and running on such a device. In many cases not only would drastic software rewrites be required but you'd probably be forced to do some soldering to access the buses and/or BIOS chips on the devices to even begin communicating with them. With the bar set so very high the only model that could work ("1 dollar profit on 100 items") is now ruled out for accomplishing significant work, much less surpassing or even equaling the number crunching power of current PC's/GPU's.
11) Message boards : Number crunching : ARM Devices (Message 57775) Posted 2 Apr 2013 by mesyn191 Post: Yes BUT, there is ALWAYS one of those I think, with some umpteen BILLION cellphones in the World together they could easily surpass the crunching power of the current number of pc's crunching! The key again is to get people interested so they will at least try it. Most of those ARM CPU's are pretty weak, meant to use almost no power for dedicated tasks which don't require much at all, a 386 would probably be far faster. Its only with the modern "super phones" you're going to get anything resembling "decent" performance. Due to "super phone" cost not many in the world actually can afford to have one...
12) Message boards : Number crunching : AMD 4890 still supported? (Message 57749) Posted 1 Apr 2013 by mesyn191 Post: In that link it looks like the versions you're talking about are still very much beta. Not interested in beta testing BOINC itself.
13) Message boards : Number crunching : ARM Devices (Message 57735) Posted 30 Mar 2013 by mesyn191 Post: Moreover the numbers of ARM, and other chip based mobiles well exceeds the combined PC and Mac desktop/laptop numbers. Most of the ARM chips out there are dog slow though. Modern cellphone ARM CPU's are the near pinnacle of commonly available ARM CPU's too BTW. Not really worth the effort from a performance stand point but would be a good learning experience for those looking to try their first recompile I guess.
14) Message boards : Number crunching : AMD 4890 still supported? (Message 57734) Posted 30 Mar 2013 by mesyn191 Post: I did a uninstall and ran CCleaner prior to each driver install. Currently I'm back to the 13.1's. When I had the 7970 in I was using the 13.2 and 13.3 beta's without issue prior to RMA'ing it for quite a while.
15) Message boards : Number crunching : AMD 4890 still supported? (Message 57732) Posted 30 Mar 2013 by mesyn191 Post: Is this the WU info. that was needed? Name ps_separation_10_3s_sSgr_3_1358941502_30143188_0 Workunit 330662496 Created 30 Mar 2013 \| 11:10:33 UTC Sent 30 Mar 2013 \| 11:11:32 UTC Received 30 Mar 2013 \| 11:13:36 UTC Server state Over Outcome Computation error Client state Compute error Exit status -1073741819 (0xffffffffc0000005) Unknown error number Stderr output <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> - exit code -1073741819 (0xc0000005) </message> <stderr_txt> <search_application> milkyway_separation 1.02 Windows x86_64 double OpenCL </search_application> Unrecognized XML in project preferences: nvidia_block_amount Skipping: 128 Skipping: /nvidia_block_amount Guessing preferred OpenCL vendor 'Advanced Micro Devices, Inc.' Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4' Error reading astronomy parameters from file 'astronomy_parameters.txt' Trying old parameters file Using AVX path Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x000007FEE52046D5 read attempt to address 0x00000000 Engaging BOINC Windows Runtime Debugger... ****************** BOINC Windows Runtime Debugger Version 6.13.0 Dump Timestamp : 03/30/13 05:11:45 Install Directory : Data Directory : C:\ProgramData\BOINC Project Symstore : LoadLibraryA( C:\ProgramData\BOINC\dbghelp.dll ): GetLastError = 126 Loaded Library : dbghelp.dll LoadLibraryA( C:\ProgramData\BOINC\symsrv.dll ): GetLastError = 126 LoadLibraryA( symsrv.dll ): GetLastError = 126 LoadLibraryA( C:\ProgramData\BOINC\srcsrv.dll ): GetLastError = 126 LoadLibraryA( srcsrv.dll ): GetLastError = 126 LoadLibraryA( C:\ProgramData\BOINC\version.dll ): GetLastError = 126 Loaded Library : version.dll Debugger Engine : 4.0.5.0 Symbol Search Path: C:\ProgramData\BOINC\slots\9;C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway ModLoad: 000000003fbf0000 0000000000123000 C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\milkyway_separation_1.02_windows_x86_64__opencl_amd_ati.exe (-nosymbols- Symbols Loaded) Linked PDB Filename : ModLoad: 00000000776f0000 00000000001a9000 C:\Windows\SYSTEM32\ntdll.dll (6.1.7601.17725) (-exported- Symbols Loaded) Linked PDB Filename : ntdll.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 0000000077010000 000000000011f000 C:\Windows\system32\kernel32.dll (6.1.7601.18015) (-exported- Symbols Loaded) Linked PDB Filename : kernel32.pdb File Version : 6.1.7601.18015 (win7sp1_gdr.121129-1432) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7601.18015 ModLoad: 00000000fddf0000 000000000006b000 C:\Windows\system32\KERNELBASE.dll (6.1.7601.18015) (-exported- Symbols Loaded) Linked PDB Filename : kernelbase.pdb File Version : 6.1.7601.18015 (win7sp1_gdr.121129-1432) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7601.18015 ModLoad: 00000000fb880000 0000000000013000 C:\Windows\system32\OpenCL.dll (1.2.11.0) (-exported- Symbols Loaded) Linked PDB Filename : c:\workarea\12.10.17\stream\opencl\api\opencl\khronos\icd\build\w864a\B_rel\OpenCL.pdb File Version : 1.2.11.0 Company Name : Khronos Group Product Name : Khronos OpenCL ICD Product Version : ModLoad: 00000000ff440000 00000000000db000 C:\Windows\system32\ADVAPI32.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : advapi32.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000ff620000 000000000009f000 C:\Windows\system32\msvcrt.dll (7.0.7601.17744) (-exported- Symbols Loaded) Linked PDB Filename : msvcrt.pdb File Version : 7.0.7601.17744 (win7sp1_gdr.111215-1535) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 7.0.7601.17744 ModLoad: 00000000fecb0000 000000000001f000 C:\Windows\SYSTEM32\sechost.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : sechost.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000ff7d0000 000000000012d000 C:\Windows\system32\RPCRT4.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : rpcrt4.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000f7340000 000000000003b000 C:\Windows\system32\WINMM.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : winmm.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000775f0000 00000000000fa000 C:\Windows\system32\USER32.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : user32.pdb File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7601.17514 ModLoad: 00000000ff5b0000 0000000000067000 C:\Windows\system32\GDI32.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : gdi32.pdb File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7601.17514 ModLoad: 00000000ff6c0000 000000000000e000 C:\Windows\system32\LPK.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : lpk.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000ff370000 00000000000c9000 C:\Windows\system32\USP10.dll (1.626.7601.18009) (-exported- Symbols Loaded) Linked PDB Filename : usp10.pdb File Version : 1.0626.7601.18009 (win7sp1_gdr.121121-1431) Company Name : Microsoft Corporation Product Name : Microsoft(R) Uniscribe Unicode script processor Product Version : 1.0626.7601.18009 ModLoad: 00000000ff900000 000000000002e000 C:\Windows\system32\IMM32.DLL (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : imm32.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000feeb0000 0000000000109000 C:\Windows\system32\MSCTF.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : msctf.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000e51a0000 0000000001c4c000 C:\Windows\system32\amdocl64.dll (10.0.1124.2) (-exported- Symbols Loaded) Linked PDB Filename : c:\workarea\12.10.17\stream\opencl\api\opencl\amdocl\build\w864a\B_rel\amdocl64.pdb File Version : 10, 0, 1124, 2 Company Name : Advanced Micro Devices Inc. Product Name : OpenCL 1.1 AMD-APP (1124.2) Product Version : 10, 0, 1124, 2 ModLoad: 00000000fb760000 000000000011d000 C:\Windows\system32\OPENGL32.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : opengl32.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fb730000 000000000002d000 C:\Windows\system32\GLU32.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : glu32.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fb630000 00000000000f1000 C:\Windows\system32\DDRAW.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : ddraw.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fbb30000 0000000000008000 C:\Windows\system32\DCIMAN32.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : dciman32.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fecd0000 00000000001d7000 C:\Windows\system32\SETUPAPI.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : setupapi.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fdc00000 0000000000036000 C:\Windows\system32\CFGMGR32.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : cfgmgr32.pdb File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7601.17514 Get Product Name Failed. ModLoad: 00000000ff080000 00000000000d7000 C:\Windows\system32\OLEAUT32.dll (6.1.7601.17676) (-exported- Symbols Loaded) Linked PDB Filename : oleaut32.pdb File Version : 6.1.7601.17676 Company Name : Microsoft Corporation Product Name : Product Version : 6.1.7601.17676 ModLoad: 00000000ff160000 0000000000203000 C:\Windows\system32\ole32.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : ole32.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fdf00000 000000000001a000 C:\Windows\system32\DEVOBJ.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : devobj.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fbc80000 0000000000018000 C:\Windows\system32\dwmapi.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : dwmapi.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000e9120000 0000000000125000 C:\Windows\system32\dbghelp.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : dbghelp.pdb File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7601.17514 ModLoad: 00000000fb620000 000000000000e000 C:\Windows\system32\atig6txx.dll (8.14.1.6264) (-exported- Symbols Loaded) Linked PDB Filename : c:\workarea\8.97.100.7\drivers\pxproxy\ogl\thunkpx\build\w864a\B_rel\atig6txx.pdb File Version : 8.14.01.6264 Company Name : Advanced Micro Devices, Inc. Product Name : Advanced Micro Devices, Inc PowerXpress Vista OpenGL (thunk) Driver Product Version : 8.14.01.6264 ModLoad: 00000000fcb30000 000000000000c000 C:\Windows\system32\VERSION.dll (6.1.7600.16385) (-exported- Symbols Loaded) Linked PDB Filename : version.pdb File Version : 6.1.7600.16385 (win7_rtm.090713-1255) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7600.16385 ModLoad: 00000000fdc40000 0000000000039000 C:\Windows\system32\WINTRUST.dll (6.1.7601.17940) (-exported- Symbols Loaded) Linked PDB Filename : wintrust.pdb File Version : 6.1.7601.17940 (win7sp1_gdr.120824-0334) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7601.17940 ModLoad: 00000000fdc80000 000000000016a000 C:\Windows\system32\CRYPT32.dll (6.1.7601.17856) (-exported- Symbols Loaded) Linked PDB Filename : crypt32.pdb File Version : 6.1.7601.17856 (win7sp1_gdr.120601-1505) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7601.17856 ModLoad: 00000000fdbf0000 000000000000f000 C:\Windows\system32\MSASN1.dll (6.1.7601.17514) (-exported- Symbols Loaded) Linked PDB Filename : msasn1.pdb File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850) Company Name : Microsoft Corporation Product Name : Microsoftï¿½ Windowsï¿½ Operating System Product Version : 6.1.7601.17514 * Dump of the Process Statistics: * - I/O Operations Counters - Read: 0, Write: 0, Other 0 - I/O Transfers Counters - Read: 0, Write: 0, Other 0 - Paged Pool Usage - QuotaPagedPoolUsage: 0, QuotaPeakPagedPoolUsage: 0 QuotaNonPagedPoolUsage: 0, QuotaPeakNonPagedPoolUsage: 0 - Virtual Memory Usage - VirtualSize: 0, PeakVirtualSize: 0 - Pagefile Usage - PagefileUsage: 0, PeakPagefileUsage: 0 - Working Set Size - WorkingSetSize: 0, PeakWorkingSetSize: 0, PageFaultCount: 0 * Dump of thread ID 6816 (state: Initialized): * - Information - Status: Base Priority: Normal, Priority: Normal, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 0.000000 - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x000007FEE52046D5 read attempt to address 0x00000000 - Registers - rax=0000000000000005 rbx=0000000000010000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000003efd8c0 rdi=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=0000000000a5df60 r12=0000000003efd6b0 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 rip=00000000e52046d5 rsp=0000000000a5d8b0 rbp=0000000000a5da20 cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202 - Callstack - ChildEBP RetAddr Args to Child 00a5dee0 e51f1fc2 03ed1a50 00000001 00000000 0000000e amdocl64!+0x0 00a5df70 e51ad1a9 03efc6c0 03efc6c0 00a5e059 00000000 amdocl64!+0x0 00a5e0b0 e51ad22b 03edfee0 00000000 00000001 00000001 amdocl64!+0x0 00a5e0e0 e5337a20 00ae12f0 00000001 03edfee0 e5dce1be amdocl64!+0x0 00a5e130 e53389c5 00000000 00000000 00000000 00000000 amdocl64!clGetSamplerInfo+0x0 00a5e160 e533915e 03edfee0 00000000 00000000 00000000 amdocl64!clGetSamplerInfo+0x0 00a5e190 e5342989 03edfee0 00000000 ffffffff 00000001 amdocl64!clGetSamplerInfo+0x0 00a5e1e0 e5342b2e 03edfee0 00000000 00a5e2b9 00000000 amdocl64!clGetSamplerInfo+0x0 00a5e210 e532ef9d 0032aa33 000000ff 00000000 00000000 amdocl64!clGetSamplerInfo+0x0 00a5e310 e532f2cb 00000000 fffffffe 00000000 00000000 amdocl64!clGetSamplerInfo+0x0 00a5e340 e530c306 00a5e4b0 00000000 00000000 00000000 amdocl64!clGetSamplerInfo+0x0 00a5e370 e530b376 0000005b e6311e98 00000000 0000005b amdocl64!clGetSamplerInfo+0x0 00a5e3b0 e52fa817 e6c86a94 00a5eaf0 001e001d fb889288 amdocl64!clGetSamplerInfo+0x0 00a5e3e0 fb8810a8 00000001 00000000 00000000 ff44d6b6 amdocl64!clIcdGetPlatformIDsKHR+0x0 00a5e450 fb88388d 00000000 00000000 00000074 00000000 OpenCL!+0x0 00a5e8c0 fb88101c 00000000 00000004 00000004 0000000c OpenCL!clGetExtensionFunctionAddress+0x0 00a5e8f0 fb8812ac 00b1a420 00b10000 36577297 7774413d OpenCL!+0x0 00a5e920 3fc3cfd1 00a5eaf0 00a5e9b0 00000000 00b14620 OpenCL!clGetPlatformIDs+0x0 00a5e950 3fc3b716 00b19040 00000000 00000000 00a5eab0 milkyway_separation_1.02_window!+0x0 00a5e990 3fc3b853 00000003 ff4e5bb0 00000000 00000000 milkyway_separation_1.02_window!+0x0 00a5e9e0 3fbf96a1 ff4e5bb0 3fc47dda 00b14580 00a5eab0 milkyway_separation_1.02_window!+0x0 00a5ea60 3fbf4a30 00b14580 00a5f350 00000000 00b14620 milkyway_separation_1.02_window!+0x0 00a5f270 3fbf16a8 00b14580 00b19040 00b14580 00a5f4c0 milkyway_separation_1.02_window!+0x0 00a5f450 3fbf1b0c 3fc7cb38 00b12988 00000000 c0e95bf7 milkyway_separation_1.02_window!+0x0 00a5fea0 3fc47f8b 00000000 00000000 00000000 00000000 milkyway_separation_1.02_window!+0x0 00a5fee0 7702652d 00000000 00000000 00000000 00000000 milkyway_separation_1.02_window!+0x0 00a5ff10 7771c521 00000000 00000000 00000000 00000000 kernel32!BaseThreadInitThunk+0x0 00a5ff60 00000000 00000000 00000000 00000000 00000000 ntdll!RtlUserThreadStart+0x0 * Dump of thread ID 7888 (state: Initialized): * - Information - Status: Base Priority: Normal, Priority: Normal, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 0.000000 - Registers - rax=0000000003e5e0c0 rbx=0000000000000000 rcx=0000000001aa0000 rdx=0000000000000000 rsi=0000000000000064 rdi=0000000000000000 r8=000000000000007f r9=0000000000000230 r10=0000000000bab090 r11=0000000000000018 r12=0000000003e5f7a0 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 rip=000000007774165a rsp=0000000003e5f778 rbp=0000000000000000 cs=0033 ss=002b ds=0000 es=0000 fs=0000 gs=0000 efl=00000246 - Callstack - ChildEBP RetAddr Args to Child 03e5f770 fddf1203 03e5f838 00000000 00000000 00000000 ntdll!ZwDelayExecution+0x0 03e5f810 3fc0f4cb 00000000 00000000 00000000 00000000 KERNELBASE!SleepEx+0x0 03e5f970 7702652d 00000000 00000000 00000000 00000000 milkyway_separation_1.02_window!+0x0 03e5f9a0 7771c521 00000000 00000000 00000000 00000000 kernel32!BaseThreadInitThunk+0x0 03e5f9f0 00000000 00000000 00000000 00000000 00000000 ntdll!RtlUserThreadStart+0x0 * Debug Message Dump ** * Foreground Window Data *** Window Name : Window Class : Window Process ID: 0 Window Thread ID : 0 Exiting...
16) Message boards : Number crunching : AMD 4890 still supported? (Message 57731) Posted 30 Mar 2013 by mesyn191 Post: You should un-hide your computers (at least temporarily) when you're looking for help troubleshooting. Only you can see the personally identifying/private account and host info, but it lets the rest of us look at the basic characteristics of the host and the tasks it has been working on. That saves a lot of time and asking you questions we could have figured out for ourselves! ;-) They're unhidden now. I'll leave them that way for a couple of days at least.
17) Message boards : Number crunching : AMD 4890 still supported? (Message 57729) Posted 30 Mar 2013 by mesyn191 Post: It could help to see a log of a WU that errored out. How do I show that? Where is the log located? Selecting a WU and hitting the properties button under the task tab just shows the WU name along with a start time and such with a state of "computation error" FWIW. Also trying older drivers had no effect.
18) Message boards : Number crunching : AMD 4890 still supported? (Message 57665) Posted 26 Mar 2013 by mesyn191 Post: I'm using the 13.1's since AFAIK that is the newest driver that supports the 4xxx series graphics cards. I might install some older drivers and see if that changes anything later this week. My OS is 64bit Win7.
19) Message boards : Number crunching : AMD 4890 still supported? (Message 57649) Posted 25 Mar 2013 by mesyn191 Post: So that problem still hasn't gone away and I guess no one else is sure what is up too. In the mean time I'm running Collatz. That still seems to run just fine on the GPU without issue for over a day now.
20) Message boards : Number crunching : AMD 4890 still supported? (Message 57621) Posted 22 Mar 2013 by mesyn191 Post: Of course. Same thing happens with new WU's.

Next 20