Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 14
Posts: 14   Pages: 2   [ 1 2 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 2061 times and has 13 replies Next Thread
JoeCyber
Cruncher
Joined: Apr 20, 2007
Post Count: 40
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Computationnal error ..:-/

hi

i swap another cpu to this machin and not it seems i got all errors ...
it is not the first time i swap cpu ... i reconfig it correctly i thing...
windoze xp runs day without problem, i ran memtest at least 2 complete pass without problem ...

but my units all busted

all seems to have address some bad place :-/
btw my others computers run fine :-)

any clue someone ?



HFCC_target-7_01842088_target-7_0001

HFCC_target-7_01844437_target-7_0001
HFCC_target-7_01844635_target-7_0001
HFCC_target-7_01841830_target-7_0001
HFCC_target-7_01841451_target-7_0000



here details for
HFCC_target-7_01842088_target-7_0001
----



Result Log

Result Name: HFCC_ target-7_ 01842088_ target-7_ 0001_ 0--
<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
Failed to get VersionInfo size: 1812
INFO:[18:44:10] Start AutoGrid...

autogrid: autogrid4: Successful Completion.
INFO:[18:44:58] End AutoGrid...
Beginning AutoDock...
INFO: Setting num_generations: 27000
_maxGenSeenSoFar changed: 6750
About to enter main loop...(dockings already completed: 0)
Updating Best Energy for WU: 0.00
Finished Docking number 0
Finished Docking number 1
Updating Best Energy for WU: -6.09
Finished Docking number 2
Finished Docking number 3
Finished Docking number 4
Finished Docking number 5
Updating Best Energy for WU: -6.82
Finished Docking number 6
Finished Docking number 7
Finished Docking number 8
Finished Docking number 9
Finished Docking number 10
Finished Docking number 11


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x04972F30 write attempt to address 0x0044298C

Engaging BOINC Windows Runtime Debugger...



********************


BOINC Windows Runtime Debugger Version 6.3.3


Dump Timestamp : 10/14/11 18:58:41
Install Directory : C:\Program Files\BOINC\
Data Directory : C:\Documents and Settings\All Users\Application Data\BOINC
Project Symstore :
Loaded Library : C:\Program Files\BOINC\\dbghelp.dll
Loaded Library : C:\Program Files\BOINC\\symsrv.dll
Loaded Library : C:\Program Files\BOINC\\srcsrv.dll
LoadLibraryA( C:\Program Files\BOINC\\version.dll ): GetLastError = 126
Loaded Library : version.dll
Debugger Engine : 4.0.5.0
Symbol Search Path: C:\Documents and Settings\All Users\Application Data\BOINC\slots\1;C:\Documents and Settings\All Users\Application Data\BOINC\projects\www.worldcommunitygrid.org;srv*C:\DOCUME~1\allo\LOCALS~1\Temp\symbols*http://msdl.microsoft.com/download/symbols;sr...inc.berkeley.edu/symstore


ModLoad: 00400000 0409c000 C:\Documents and Settings\All Users\Application Data\BOINC\projects\www.worldcommunitygrid.org\wcg_hfcc_autodock_6.40_windows_intelx86 (6.2.0.0) (-nosymbols- Symbols Loaded)
File Version : 6, 2, 0, 0
Company Name : The Scripps Research Institute and IBM Corporation
Product Name : AutoDock
Product Version :

ModLoad: 7c900000 000b2000 C:\WINDOWS\system32\ntdll.dll (5.1.2600.6055) (PDB Symbols Loaded)
File Version : 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 5.1.2600.6055

ModLoad: 7c800000 000f6000 C:\WINDOWS\system32\kernel32.dll (5.1.2600.5781) (PDB Symbols Loaded)
File Version : 5.1.2600.5781 (xpsp_sp3_gdr.090321-1317)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 5.1.2600.5781

ModLoad: 77c00000 00008000 C:\WINDOWS\system32\VERSION.dll (5.1.2600.5512) (PDB Symbols Loaded)
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 5.1.2600.5512

ModLoad: 7e410000 00091000 C:\WINDOWS\system32\USER32.dll (5.1.2600.5512) (PDB Symbols Loaded)
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 5.1.2600.5512

ModLoad: 77f10000 00049000 C:\WINDOWS\system32\GDI32.dll (5.1.2600.5698) (PDB Symbols Loaded)
File Version : 5.1.2600.5698 (xpsp_sp3_gdr.081022-1932)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 5.1.2600.5698

ModLoad: 77dd0000 0009b000 C:\WINDOWS\system32\ADVAPI32.dll (5.1.2600.5755) (PDB Symbols Loaded)
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 5.1.2600.5755

ModLoad: 77e70000 00093000 C:\WINDOWS\system32\RPCRT4.dll (5.1.2600.6022) (PDB Symbols Loaded)
File Version : 5.1.2600.6022 (xpsp_sp3_gdr.100813-1643)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 5.1.2600.6022

ModLoad: 77fe0000 00011000 C:\WINDOWS\system32\Secur32.dll (5.1.2600.5834) (PDB Symbols Loaded)
File Version : 5.1.2600.5834 (xpsp_sp3_gdr.090624-1305)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 5.1.2600.5834

ModLoad: 76390000 0001d000 C:\WINDOWS\system32\IMM32.DLL (5.1.2600.5512) (PDB Symbols Loaded)
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 5.1.2600.5512

ModLoad: 77690000 00021000 C:\WINDOWS\system32\NTMARTA.DLL (5.1.2600.5512) (PDB Symbols Loaded)
File Version : 5.1.2600.5512 (xpsp.080413-2113)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 5.1.2600.5512

ModLoad: 77c10000 00058000 C:\WINDOWS\system32\msvcrt.dll (7.0.2600.5512) (PDB Symbols Loaded)
File Version : 7.0.2600.5512 (xpsp.080413-2111)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 7.0.2600.5512

ModLoad: 774e0000 0013e000 C:\WINDOWS\system32\ole32.dll (5.1.2600.6010) (PDB Symbols Loaded)
File Version : 5.1.2600.6010 (xpsp_sp3_gdr.100712-1633)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 5.1.2600.6010

ModLoad: 71bf0000 00013000 C:\WINDOWS\system32\SAMLIB.dll (5.1.2600.5512) (PDB Symbols Loaded)
File Version : 5.1.2600.5512 (xpsp.080413-2113)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 5.1.2600.5512

ModLoad: 76f60000 0002c000 C:\WINDOWS\system32\WLDAP32.dll (5.1.2600.5512) (PDB Symbols Loaded)
File Version : 5.1.2600.5512 (xpsp.080413-2113)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 5.1.2600.5512

ModLoad: 77f60000 00076000 C:\WINDOWS\system32\SHLWAPI.dll (6.0.2900.5912) (PDB Symbols Loaded)
File Version : 6.00.2900.5912 (xpsp_sp3_gdr.091207-1454)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 6.00.2900.5912

ModLoad: 773d0000 00103000 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202\comctl32.dll (6.0.2900.6028) (PDB Symbols Loaded)
File Version : 6.0 (xpsp_sp3_qfe.100823-1643)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 6.00.2900.6028

ModLoad: 5d090000 0009a000 C:\WINDOWS\system32\comctl32.dll (5.82.2900.6028) (PDB Symbols Loaded)
File Version : 5.82 (xpsp_sp3_qfe.100823-1643)
Company Name : Microsoft Corporation
Product Name : Microsoft�Windows�Operating System
Product Version : 6.00.2900.6028

ModLoad: 0fcd0000 00115000 C:\Program Files\BOINC\dbghelp.dll (6.8.4.0) (PDB Symbols Loaded)
File Version : 6.8.0004.0 (debuggers(dbg).070515-1751)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version : 6.8.0004.0

ModLoad: 06410000 00048000 C:\Program Files\BOINC\symsrv.dll (6.8.4.0) (PDB Symbols Loaded)
File Version : 6.8.0004.0 (debuggers(dbg).070515-1751)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version : 6.8.0004.0

ModLoad: 0fef0000 0003b000 C:\Program Files\BOINC\srcsrv.dll (6.8.4.0) (PDB Symbols Loaded)
File Version : 6.8.0004.0 (debuggers(dbg).070515-1751)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version : 6.8.0004.0



*** Dump of the Process Statistics: ***

- I/O Operations Counters -
Read: 70137, Write: 0, Other 47715

- I/O Transfers Counters -
Read: 0, Write: 8744, Other 0

- Paged Pool Usage -
QuotaPagedPoolUsage: 166844, QuotaPeakPagedPoolUsage: 196604
QuotaNonPagedPoolUsage: 2448, QuotaPeakNonPagedPoolUsage: 3568

- Virtual Memory Usage -
VirtualSize: 272838656, PeakVirtualSize: 293711872

- Pagefile Usage -
PagefileUsage: 233725952, PeakPagefileUsage: 255201280

- Working Set Size -
WorkingSetSize: 154333184, PeakWorkingSetSize: 175509504, PageFaultCount: 1420688

*** Dump of thread ID 3872 (state: Waiting): ***

- Information -
Status: Wait Reason: UserRequest, , Kernel Time: 37187500.000000, User Time: 8307500032.000000, Wait Time: 175277.000000

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x04972F30 write attempt to address 0x0044298C

- Registers -
eax=04973198 ebx=064d633c ecx=00000001 edx=00000009 esi=0044298c edi=064d633c
eip=04972f30 esp=04972f48 ebp=049731f8
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246

- Callstack -
ChildEBP RetAddr Args to Child
049731f8 00442850 0497323c 0497323c 049731f8 049731fc !+0x0 SymFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '04972f30'
04973274 00406d4b 064d6324 65636572 726f7470 2e414e2e wcg_hfcc_autodock_6!+0x0 SymFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '00442850'
049736b8 004526dc 7c910060 ffffffff 7c91005d 7c911452 wcg_hfcc_autodock_6!+0x0 SymFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '00406d4b'
04c9fa38 00448a1b 04c9fd30 004bac58 004eb640 ffffffff wcg_hfcc_autodock_6!+0x0 SymFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '004526dc'
04c9fd3c 00444450 00000060 00000000 00000000 00320460 wcg_hfcc_autodock_6!+0x0 SymFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '00448a1b'
04c9fee4 004b719f 00000007 003229a8 00322a70 00000094 wcg_hfcc_autodock_6!+0x0 SymFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '00444450'
04c9ffc0 7c817077 005a2c88 00000000 7ffdf000 8054b6ed wcg_hfcc_autodock_6!+0x0 SymFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '004b719f'
04c9fff0 00000000 004b7033 00000000 00000000 00000000 kernel32!_BaseProcessStart@4+0x0 SymFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '7c817077'

*** Dump of thread ID 4000 (state: Waiting): ***

- Information -
Status: Wait Reason: ExecutionDelay, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 175271.000000

- Registers -
eax=f1394b92 ebx=00000000 ecx=00000001 edx=02376fac esi=00000000 edi=060aff70
eip=7c90e514 esp=060aff40 ebp=060aff98
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202

- Callstack -
ChildEBP RetAddr Args to Child
060aff3c 7c90d21a 7c8023f1 00000000 060aff70 00000000 ntdll!_KiFastSystemCallRet@0+0x0 FPO: [0,0,0]
060aff40 7c8023f1 00000000 060aff70 00000000 7c802446 ntdll!_NtDelayExecution@8+0x0 FPO: [2,0,0]
060aff98 7c802455 00000064 00000000 060affec 004a129b kernel32!_SleepEx@8+0x0
060affa8 004a129b 00000064 00000000 7c80b729 00000000 kernel32!_Sleep@4+0x0
060affec 00000000 004a1290 00000000 00000000 06260000 wcg_hfcc_autodock_6!+0x0


*** Debug Message Dump ****


*** Foreground Window Data ***
Window Name :
Window Class :
Window Process ID: 0
Window Thread ID : 0

Exiting...

</stderr_txt>
]]>
[Oct 14, 2011 11:19:10 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Computationnal error ..:-/

What model of cpu did you put in and is said cpu listed to be compatiable with the motherboard you put it in?
[Oct 14, 2011 11:44:31 PM]   Link   Report threatening or abusive post: please login first  Go to top 
JoeCyber
Cruncher
Joined: Apr 20, 2007
Post Count: 40
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Computationnal error ..:-/

Yes it is compatible ...

i just finish another test, near 3 hours of prime95 at full throttle ... no error
so WCG seems really be the problem ...

so i gonna try to remove WCG and the left over registry keys ...
and maybe retry tomorow ...



Tests
Processor: 2 GenuineIntel Pentium(R) Dual-Core CPU E6600 @ 3.06GHz [x86 Family 6 Model 23 Stepping 10]
Processor: 2.00 MB cache
Processor features: fpu tsc pae nx sse sse2 mmx
OS: Microsoft Windows XP: Home x86 Edition, Service Pack 3, (05.01.2600.00)
Memory: 1.87 GB physical, 5.71 GB virtual
Disk: 465.75 GB total, 442.88 GB free

Number of CPUs: 2
3218 floating point MIPS (Whetstone) per CPU
6613 integer MIPS (Dhrystone) per CPU
[Oct 15, 2011 3:14:10 AM]   Link   Report threatening or abusive post: please login first  Go to top 
retsof
Former Community Advisor
USA
Joined: Jul 31, 2005
Post Count: 6824
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Computationnal error ..:-/


Processor: 2 GenuineIntel Pentium(R) Dual-Core CPU E6600 @ 3.06GHz

That is a machine launched Q1 2010. XP is getting rather long in the tooth and would seem a rather old OS to be running on a dualie. You have SP3 on it which is good.

Some of the new projects are giving the machine a workout.

HFCC has run well here in the past on two machines with Vista and System 7.

Memory: 1.87 GB physical, 5.71 GB virtual

Physical memory may be adequate but could be a bit tight for some uses.
Memory is cheap.

This 32 bit 2 core here has 4 Gb virtual but Windows has its 3 Gb limit.

i just finish another test, near 3 hours of prime95 at full throttle ... no error
so WCG seems really be the problem ...
In some cases, some WCG projects are even more intense than prime95 from a few messages noted here so an error may not be a surprise.

Have you tried memtest86+?

http://en.wikipedia.org/wiki/Memtest86

Are the memory sticks identical brands and capability? If you have more than one, it might be worth trying it with the two sticks swapped also.
----------------------------------------
SUPPORT ADVISOR
Work+GPU i7 8700 12threads
School i7 4770 8threads
Default+GPU Ryzen 7 3700X 16threads
Ryzen 7 3800X 16 threads
Ryzen 9 3900X 24threads
Home i7 3540M 4threads50%
----------------------------------------
[Edit 4 times, last edit by retsof at Oct 15, 2011 4:22:48 AM]
[Oct 15, 2011 4:03:39 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Computationnal error ..:-/

BOINC is designed to check that the type of CPU that downloads is still valid when the result uploads. At least, I seem to remember that this can be a problem when using sneaker-net to download on one machine and compute on another machine.

I suspect that your computer is good. You just ran into a problem caused by the design of BOINC.

Lawrence
[Oct 15, 2011 4:43:37 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Chris Doran
Cruncher
Joined: Apr 28, 2007
Post Count: 4
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Computationnal error ..:-/

I've been getting these on XP and W2k for a long time. On my systems they happen when Internet Explorer (which seems to have a memory leak) gobbles up all the available memory and you open another tab which breaks the camel's back.

It looks as if the client fails to handle a memory allocation request failure cleanly, and just crashes, when it should really just suspend and try again later, as it does when the computation load is too heavy. Something for the wishlist.
[Oct 16, 2011 10:52:55 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Computationnal error ..:-/

Hello Chris Doran,
Memory leaks can bring down any OS. Which is why I try to reboot once a week and really try to reboot before applying the monthly Microsoft updates. I admit, I can be forgetful and several times this has hurt me during Windows updates.

Lawrence
[Oct 17, 2011 5:04:05 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Computationnal error ..:-/

Ah, memory leaks... can't say I've been suffering of any ML at all on Windows nor Linux, but 6.12 was iterated several point releases to 6.12.41 to take care of these [testing now]. In fact, there's talk of back-porting more bug fixes from the 6.13 alpha development branch to 6.12.

Nasty bit of 6.12.41, first red line after installation:

17/10/2011 09:16:53 | | BOINC can't access Internet - check network connection or proxy configuration.

In view of the "http error 0" also, that has started to show it's face since 6.12.34, I'd not go up to anything above 6.12.33 (also officially supported by the Linux distros) unless for testing purposes.

Computation errors occur when e.g. the core client has been obstructed to talk to the science app for longer than 30 seconds. Signals are Heartbeat and Zero Status type lines. Without the result log (status column link on Result Status page) and the client messages around the time a fail occurs it's really a dry finger in the air to guess from what direction the wind blows.

--//--

P.S. The hardest workout is grid computing and not prime95. Of all the grid projects probably some of PrimeGrid are toughest on th Integer part of the CPU... then it can get really hot if not cooled properly.
[Oct 17, 2011 7:34:17 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Computationnal error ..:-/

I'm new and am not sure where to post my issue, but this seems to be a reasonable place. It appears that all of my Eistein@home/Binary Radio Pulsar Search work units are finishing with a Computation Error status. The computer is a win7 64 bit machine with all updates, 4 gigs or dram, and an Intel dual core 3.0 gHz chip on an Intel board. I have other WCG projects that appear to finish correctly. What am I doing wrong, or what should I do to fix this?
[Dec 30, 2011 9:35:57 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Computationnal error ..:-/

Hello gdanaher,
Is this a one time problem with a batch of Einstein work units or a protracted problem? If one time, a reboot might cure it. If protracted, then you might want to experiment by suspending WCG and all projects except Einstein. This would let you see if your problem is caused by switching. If so, then you need to examine your detailed preferences. If not, then better start asking questions on the Einstein website.

Lawrence
[Dec 30, 2011 11:39:10 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 14   Pages: 2   [ 1 2 | Next Page ]
[ Jump to Last Post ]
Post new Thread