sure enough, this capri unit that was still on the server crashed..or was it aborted by rosie?

9/18/2007 8:25:34 PM|rosetta@home|Reason: Unrecoverable error for result 1g4u__BOINC_CAPRI14_DOCK_FIXBACKBONE_POSE_LOOPS-1g4u_-lig_plexinmonomer__2085_9252_1 ( - exit code -1073741819 (0xc0000005))
9/18/2007 8:25:34 PM|rosetta@home|Computation for task 1g4u__BOINC_CAPRI14_DOCK_FIXBACKBONE_POSE_LOOPS-1g4u_-lig_plexinmonomer__2085_9252_1 finished

---

My preferences are set to 21,000 seconds (6 hours).
This WU took over 28,000 seconds (nearly 8 hours) but still validated.

It was still successful and reported as Valid.
I claimed 98.93 for the time taken and the work done but was granted just 5.38.

What is the go with that?

I suspect the WU locked up during processing and this is why the time is so long, but as it is still valid I should get full credit.

There is an error report in this result but at the end all came out valid and successful.

Please I would like to know the reason for this result.

---

I see that the server applications are all disabled (as of about 9:30PM PDT) -- what's with that?

---

OK -- one of those planned but unmentioned 'quickies' I guess -- it is up and running now.

I see that the server applications are all disabled (as of about 9:30PM PDT) -- what's with that?

---

well i see most of you had problems running CAPRI14_DOCK_FIXBACKBONE WU's although i ran 4 of them in aproxemetly 3 hours without errors. https://boinc.bakerlab.org/rosetta/results.php?userid=205058

i run stuff on my AMD Athlon(tm) 64 Processor 3200+ most of you seem to have trouble running on a Q6600 thingie maybe the problem lies somewere in there?

We discovered that the result files of the now infamous capri were quite large which has caused some problems. We are looking into this issue now, but rest assured, no more of these jobs are being sent out. So things should be back to normal now that none of these jobs are in the queue.

---

We discovered that the result files of the now infamous capri were quite large which has caused some problems. We are looking into this issue now, but rest assured, no more of these jobs are being sent out. So things should be back to normal now that none of these jobs are in the queue.

I have a 2 day queue so I guess 'I'll Be Back'
https://boinc.bakerlab.org/rosetta/result.php?resultid=106031266

---

Jmarks

We discovered that the result files of the now infamous capri were quite large which has caused some problems. We are looking into this issue now, but rest assured, no more of these jobs are being sent out. So things should be back to normal now that none of these jobs are in the queue.

Hello Ingemar, I was wondering if you can have a look at message 46564 in this thread and explain to me what happened please, as I would like to know.

---

This is the "real world", and even with Ralph@Home you're going to be learning what can be done better.

My posting of 5.80 Capri14 problems was to alert the Project as to what was happening.

Even with a higher than average failure rate, if it benefits the Project, I'm still willing to run these wu's, even at the risk of no credit.

Whatever helps Rosie, and she knows best what that is...

We discovered that the result files of the now infamous capri were quite large which has caused some problems. We are looking into this issue now, but rest assured, no more of these jobs are being sent out. So things should be back to normal now that none of these jobs are in the queue.

We discovered that the result files of the now infamous capri were quite large which has caused some problems. We are looking into this issue now, but rest assured, no more of these jobs are being sent out. So things should be back to normal now that none of these jobs are in the queue.

Ya! 483 decoys in a 24hr WU! It was like a 3+MB upload. No WONDER the file server has been busy :)

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

Hi Conan, I think you're exactly right -- the WU must have frozen at some time. We previously saw a high rate of watchdog kills for this type of workunit due to freezing, so that supports your hypothesis. There's clearly some problem with these jobs -- we've discontinued them until we can fix the issue!

My preferences are set to 21,000 seconds (6 hours).
This WU took over 28,000 seconds (nearly 8 hours) but still validated.

It was still successful and reported as Valid.
I claimed 98.93 for the time taken and the work done but was granted just 5.38.

What is the go with that?

I suspect the WU locked up during processing and this is why the time is so long, but as it is still valid I should get full credit.

There is an error report in this result but at the end all came out valid and successful.

Please I would like to know the reason for this result.

---

Also, I think this has been posted elsewhere: if you have jobs marked CAPRI, you should feel free to abort them. Although most of these workunits are running fine and we are using the incoming data, there is a small possibility of the workunits being frozen or of the output files being so large that the file transfer can get bungled. No more of these workunits are being sent out!

---

Just a theory here.

I noticed that the cpu usage increased to above 50%. I was told that this might happen with graphics running but it seems it continues to do that after the graphics are shut down. The cpu usage is erratic and despite showing high usage the time and results seem to be going slower. This only seems to happen with the capri workunits though, the last one just finished after which things returned to normal. I know there was a graphics problem that is supposed to be fixed in the new versions. Is there any chance that another problem was introduced where the graphics thread continues to run after exiting the graphics?

Spoke too soon. :/
cpu usage is 2/3 on one unit and 1/3 on the other. This after viewing both.

---

BBLounge - Broadband and Technology forum

I don't really know if this is a 5.8 problem, a BOINC problem, or what..so..if I'm in the wrong thread, feel free to move this elsewhere.

Just happened to notice that a WU had just completed, so went to my results page to check credit, and in less than 5 minutes, the result was nowhere to be found. All my prior WU's from today's work are there, and my "in progress" work is there, but not this one. Here's the log (edited for brevity):

9/19/2007 2:33:13 PM|rosetta@home|Starting 1a68__SEARCH_PAIRINGS_ROUND2_RESCORE_150_SAVE_ALL_OUT_-1a68_-_BARCODE__2050_7166_0
9/19/2007 2:33:14 PM|rosetta@home|Starting task 1a68__SEARCH_PAIRINGS_ROUND2_RESCORE_150_SAVE_ALL_OUT_-1a68_-_BARCODE__2050_7166_0 using rosetta_beta version 580
9/19/2007 5:28:31 PM|rosetta@home|Computation for task 1a68__SEARCH_PAIRINGS_ROUND2_RESCORE_150_SAVE_ALL_OUT_-1a68_-_BARCODE__2050_7166_0 finished
9/19/2007 5:28:33 PM|rosetta@home|[file_xfer] Started upload of file 1a68__SEARCH_PAIRINGS_ROUND2_RESCORE_150_SAVE_ALL_OUT_-1a68_-_BARCODE__2050_7166_0_0
9/19/2007 5:28:40 PM|rosetta@home|[file_xfer] Finished upload of file 1a68__SEARCH_PAIRINGS_ROUND2_RESCORE_150_SAVE_ALL_OUT_-1a68_-_BARCODE__2050_7166_0_0
9/19/2007 5:28:40 PM|rosetta@home|[file_xfer] Throughput 4223 bytes/sec
9/19/2007 5:28:46 PM|rosetta@home|Sending scheduler request: To report completed tasks
9/19/2007 5:28:46 PM|rosetta@home|Reporting 1 tasks
9/19/2007 5:28:51 PM|rosetta@home|Scheduler RPC succeeded [server version 509]
9/19/2007 5:28:51 PM|rosetta@home|Deferring communication for 4 min 2 sec
9/19/2007 5:28:51 PM|rosetta@home|Reason: requested by project

By 5:33PM (PDT)(i.e., 00:33 UTC) this WU was not in my results list. Since I've never had one disappear THAT fast before, I'm wondering if something is amiss. Unfortunately I have no way to know the result # or WU#...

Thoughts, anyone?

Hi Conan, I think you're exactly right -- the WU must have frozen at some time. We previously saw a high rate of watchdog kills for this type of workunit due to freezing, so that supports your hypothesis. There's clearly some problem with these jobs -- we've discontinued them until we can fix the issue!

My preferences are set to 21,000 seconds (6 hours).
This WU took over 28,000 seconds (nearly 8 hours) but still validated.

It was still successful and reported as Valid.
I claimed 98.93 for the time taken and the work done but was granted just 5.38.

What is the go with that?

I suspect the WU locked up during processing and this is why the time is so long, but as it is still valid I should get full credit.

There is an error report in this result but at the end all came out valid and successful.

Please I would like to know the reason for this result.

Thanks for that Ingemar and for your response so quickly.

---

I don't really know if this is a 5.8 problem, a BOINC problem, or what..so..if I'm in the wrong thread, feel free to move this elsewhere.

Just happened to notice that a WU had just completed, so went to my results page to check credit, and in less than 5 minutes, the result was nowhere to be found. All my prior WU's from today's work are there, and my "in progress" work is there, but not this one. Here's the log (edited for brevity):

9/19/2007 2:33:13 PM|rosetta@home|Starting 1a68__SEARCH_PAIRINGS_ROUND2_RESCORE_150_SAVE_ALL_OUT_-1a68_-_BARCODE__2050_7166_0
9/19/2007 2:33:14 PM|rosetta@home|Starting task 1a68__SEARCH_PAIRINGS_ROUND2_RESCORE_150_SAVE_ALL_OUT_-1a68_-_BARCODE__2050_7166_0 using rosetta_beta version 580
9/19/2007 5:28:31 PM|rosetta@home|Computation for task 1a68__SEARCH_PAIRINGS_ROUND2_RESCORE_150_SAVE_ALL_OUT_-1a68_-_BARCODE__2050_7166_0 finished
9/19/2007 5:28:33 PM|rosetta@home|[file_xfer] Started upload of file 1a68__SEARCH_PAIRINGS_ROUND2_RESCORE_150_SAVE_ALL_OUT_-1a68_-_BARCODE__2050_7166_0_0
9/19/2007 5:28:40 PM|rosetta@home|[file_xfer] Finished upload of file 1a68__SEARCH_PAIRINGS_ROUND2_RESCORE_150_SAVE_ALL_OUT_-1a68_-_BARCODE__2050_7166_0_0
9/19/2007 5:28:40 PM|rosetta@home|[file_xfer] Throughput 4223 bytes/sec
9/19/2007 5:28:46 PM|rosetta@home|Sending scheduler request: To report completed tasks
9/19/2007 5:28:46 PM|rosetta@home|Reporting 1 tasks
9/19/2007 5:28:51 PM|rosetta@home|Scheduler RPC succeeded [server version 509]
9/19/2007 5:28:51 PM|rosetta@home|Deferring communication for 4 min 2 sec
9/19/2007 5:28:51 PM|rosetta@home|Reason: requested by project

By 5:33PM (PDT)(i.e., 00:33 UTC) this WU was not in my results list. Since I've never had one disappear THAT fast before, I'm wondering if something is amiss. Unfortunately I have no way to know the result # or WU#...

Thoughts, anyone?

This workunit by any chance?
It hasn't disappeared, it's on page 3. The workunits are ordered by wu# not date. You got an earlier workunit later than you normally should if you look at the date and so you'e likely to miss it without digging deeper. :) Funny this usually only happens when a workunit is reassigned after the deadline.

---

BBLounge - Broadband and Technology forum

This workunit by any chance?
It hasn't disappeared, it's on page 3. The workunits are ordered by wu# not date. You got an earlier workunit later than you normally should if you look at the date and so you'e likely to miss it without digging deeper. :) Funny this usually only happens when a workunit is reassigned after the deadline.

Well, duhhhhhhhhhhh...:)

Never thought to look all that far back..I've not seen R@H do that, thought that behavior was limited to S@H...thanks.

Result ID 106047623
Name t030__BOINC_CAPRI14_DOCK_FIXBACKBONE_POSE_LOOPS-t030_-plexinmonomer__2083_6224_0
Workunit 96261079
Created 16 Sep 2007 14:15:43 UTC
Sent 16 Sep 2007 14:34:53 UTC
Received 20 Sep 2007 3:58:44 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 510574
Report deadline 26 Sep 2007 14:34:53 UTC
CPU time 23419.390625
stderr out <core_client_version>5.10.20</core_client_version>
<![CDATA[
<stderr_txt>
# cpu_run_time_pref: 21600
# random seed: 3549877
# cpu_run_time_pref: 21600
**********************************************************************
Rosetta score is stuck or going too long. Watchdog is ending the run!
Stuck at score -207.662 for 1800 seconds
**********************************************************************
GZIP SILENT FILE: .xxt030.out

</stderr_txt>
]]>


Validate state Valid
Claimed credit 97.7521869214656
Granted credit 20
application version 5.80

This WU ran for 23,419 secs for only 20 credits, is this right?

---

OOPS, sorry, have just seen correspondence on this sort of WU. No answer to my query is needed.

---

Since I've updated 5.10 version I have problems with the software. My Laptop is running Windows Vista 32Bit and I have a server, too, running Windows 2003 Server EE. On both machines the service is crashing. I must start the service again and then it works again until it crashes.

I've found a text file in the Boinc-folder called stderrdae.txt. It contains:





Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0035BED3 read attempt to address 0x00000008

Engaging BOINC Windows Runtime Debugger...



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


BOINC Windows Runtime Debugger Version 5.10.20


Dump Timestamp : 09/19/07 07:01:36
Debugger Engine : 4.0.5.0
Symbol Search Path: F:AnwendungenBoinc;F:AnwendungenBoinc;srv*C:DOKUME~1ADMINI~1LOKALE~1Tempsymbols*http://msdl.microsoft.com/download/symbols;srv*C:DOKUME~1ADMINI~1LOKALE~1Tempsymbols*http://boinc.berkeley.edu/symstore


ModLoad: 00400000 000b6000 F:AnwendungenBoincboinc.exe (5.10.20.0) (-nosymbols- Symbols Loaded)
File Version : 5.10.20
Company Name : Space Sciences Laboratory
Product Name : BOINC client
Product Version: 5.10.20

ModLoad: 7c920000 000c6000 C:WINDOWSsystem32ntdll.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft® Windows®
Product Version: 5.2.3790.3959

ModLoad: 7c800000 00115000 C:WINDOWSsystem32kernel32.dll (5.2.3790.4062) (-exported- Symbols Loaded)
File Version : 5.2.3790.4062 (srv03_sp2_gdr.070417-0203)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft® Windows®
Product Version: 5.2.3790.4062

Get Company Name Failed.
ModLoad: 10000000 00013000 F:AnwendungenBoinczlib1.dll (1.2.3.0) (-exported- Symbols Loaded)
File Version : 1.2.3
Company Name :
Product Name : zlib
Product Version: 1.2.3

ModLoad: 78130000 0009b000 F:AnwendungenBoincMSVCR80.dll (8.0.50727.762) (-exported- Symbols Loaded)
File Version : 8.00.50727.762
Company Name : Microsoft Corporation
Product Name : Microsoft® Visual Studio® 2005
Product Version: 8.00.50727.762

ModLoad: 77b70000 0005a000 C:WINDOWSsystem32msvcrt.dll (7.0.3790.3959) (-exported- Symbols Loaded)
File Version : 7.0.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version: 7.0.3790.3959

ModLoad: 00340000 00030000 F:AnwendungenBoinclibcurl.dll (7.16.4.0) (-exported- Symbols Loaded)
File Version : 7.16.4
Company Name : The cURL library, http://curl.haxx.se/
Product Name : The cURL library
Product Version: 7.16.4

ModLoad: 719c0000 0000a000 C:WINDOWSsystem32WSOCK32.dll (5.2.3790.0) (-exported- Symbols Loaded)
File Version : 5.2.3790.0 (srv03_rtm.030324-2048)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft® Windows®
Product Version: 5.2.3790.0

ModLoad: 71a10000 00017000 C:WINDOWSsystem32WS2_32.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version: 5.2.3790.3959

ModLoad: 71a00000 00008000 C:WINDOWSsystem32WS2HELP.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft® Windows®
Product Version: 5.2.3790.3959

ModLoad: 77f30000 000ab000 C:WINDOWSsystem32ADVAPI32.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft® Windows®
Product Version: 5.2.3790.3959

ModLoad: 77c20000 0009f000 C:WINDOWSsystem32RPCRT4.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version: 5.2.3790.3959

ModLoad: 76e40000 00013000 C:WINDOWSsystem32Secur32.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version: 5.2.3790.3959

ModLoad: 76990000 0002e000 C:WINDOWSsystem32WINMM.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft® Windows®
Product Version: 5.2.3790.3959

ModLoad: 77e20000 00092000 C:WINDOWSsystem32USER32.dll (5.2.3790.4033) (-exported- Symbols Loaded)
File Version : 5.2.3790.4033 (srv03_sp2_gdr.070228-0030)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft® Windows®
Product Version: 5.2.3790.4033

ModLoad: 77bd0000 00048000 C:WINDOWSsystem32GDI32.dll (5.2.3790.4033) (-exported- Symbols Loaded)
File Version : 5.2.3790.4033 (srv03_sp2_gdr.070228-0030)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version: 5.2.3790.4033

ModLoad: 004c0000 000fd000 F:AnwendungenBoincLIBEAY32.dll (0.9.8.5) (-exported- Symbols Loaded)
File Version : 0.9.8e
Company Name : The OpenSSL Project, http://www.openssl.org/
Product Name : The OpenSSL Toolkit
Product Version: 0.9.8e

ModLoad: 00380000 00030000 F:AnwendungenBoincSSLEAY32.dll (0.9.8.5) (-exported- Symbols Loaded)
File Version : 0.9.8e
Company Name : The OpenSSL Project, http://www.openssl.org/
Product Name : The OpenSSL Toolkit
Product Version: 0.9.8e

ModLoad: 7c420000 00087000 F:AnwendungenBoincMSVCP80.dll (8.0.50727.762) (-exported- Symbols Loaded)
File Version : 8.00.50727.762
Company Name : Microsoft Corporation
Product Name : Microsoft® Visual Studio® 2005
Product Version: 8.00.50727.762

ModLoad: 76180000 0001d000 C:WINDOWSsystem32IMM32.DLL (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version: 5.2.3790.3959

ModLoad: 719d0000 00008000 C:WINDOWSsystem32rdpsnd.dll (5.2.3790.0) (-exported- Symbols Loaded)
File Version : 5.2.3790.0 (srv03_rtm.030324-2048)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft® Windows®
Product Version: 5.2.3790.0

ModLoad: 779b0000 00011000 C:WINDOWSsystem32WINSTA.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version: 5.2.3790.3959

ModLoad: 71a50000 00057000 C:WINDOWSsystem32NETAPI32.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version: 5.2.3790.3959

ModLoad: 76a60000 0000b000 C:WINDOWSsystem32PSAPI.DLL (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version: 5.2.3790.3959

ModLoad: 00b00000 00008000 F:AnwendungenBoincboinc.dll (5.10.20.0) (-exported- Symbols Loaded)
File Version : 5.10.20
Company Name : Space Sciences Laboratory
Product Name : BOINC Core Client
Product Version: 5.10.20

ModLoad: 71930000 00042000 C:WINDOWSSystem32mswsock.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft® Windows®
Product Version: 5.2.3790.3959

ModLoad: 76dc0000 0002b000 C:WINDOWSsystem32DNSAPI.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft® Windows®
Product Version: 5.2.3790.3959

ModLoad: 76e60000 00007000 C:WINDOWSSystem32winrnr.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version: 5.2.3790.3959

ModLoad: 76e00000 0002f000 C:WINDOWSsystem32WLDAP32.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft® Windows®
Product Version: 5.2.3790.3959

ModLoad: 76e70000 00005000 C:WINDOWSsystem32rasadhlp.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version: 5.2.3790.3959

ModLoad: 68000000 00035000 C:WINDOWSsystem32rsaenh.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version: 5.2.3790.3959

ModLoad: 76810000 000c4000 C:WINDOWSsystem32USERENV.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft® Windows®
Product Version: 5.2.3790.3959

ModLoad: 073e0000 0005b000 C:WINDOWSsystem32hnetcfg.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft® Windows®
Product Version: 5.2.3790.3959

ModLoad: 718f0000 00008000 C:WINDOWSSystem32wshtcpip.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version: 5.2.3790.3959

ModLoad: 03000000 00115000 F:AnwendungenBoincdbghelp.dll (6.6.7.5) (-exported- Symbols Loaded)
File Version : 6.6.0007.5 (debuggers(dbg).051021-1446)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version: 6.6.0007.5

ModLoad: 01d00000 00083000 F:AnwendungenBoincsymsrv.dll (6.6.7.5) (-exported- Symbols Loaded)
File Version : 6.6.0007.5 (debuggers(dbg).051021-1446)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version: 6.6.0007.5

ModLoad: 00e40000 0003a000 F:AnwendungenBoincsrcsrv.dll (6.6.7.5) (-exported- Symbols Loaded)
File Version : 6.6.0007.5 (debuggers(dbg).051021-1446)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version: 6.6.0007.5

ModLoad: 77b60000 00008000 C:WINDOWSsystem32version.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version: 5.2.3790.3959



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

- I/O Operations Counters -
Read: 14315, Write: 0, Other 69318

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

- Paged Pool Usage -
QuotaPagedPoolUsage: 22084, QuotaPeakPagedPoolUsage: 24288
QuotaNonPagedPoolUsage: 36384, QuotaPeakNonPagedPoolUsage: 40536

- Virtual Memory Usage -
VirtualSize: 31211520, PeakVirtualSize: 32260096

- Pagefile Usage -
PagefileUsage: 6230016, PeakPagefileUsage: 7655424

- Working Set Size -
WorkingSetSize: 8196096, PeakWorkingSetSize: 9461760, PageFaultCount: 18857

*** Dump of the thread (1aa4): ***

- Information -
Status: Waiting, Wait Reason: Executive, Kernel Time: 1250000.000000, User Time: 781250.000000, Wait Time: 195426816.000000

- Registers -
eax=00000070 ebx=00000000 ecx=00000003 edx=0012f758 esi=00000000 edi=000000d8
eip=7c9485ec esp=0012fb14 ebp=0012fb7c
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246

- Callstack -
ChildEBP RetAddr Args to Child
0012fb7c 77f45edb 000000d8 0012fc40 0000021a 0012fba4 ntdll!KiFastSystemCallRet+0x0
0012fba8 77f45f82 000000d8 0012fc40 0000021a 0012fbfc ADVAPI32!LookupPrivilegeValueW+0x0
0012fc1c 77f975af 000000d8 0012fc40 0000021a 003e4c20 ADVAPI32!LookupPrivilegeValueW+0x0
0012fe60 00430414 0012fe84 0046fc58 00000001 0012ffc0 ADVAPI32!StartServiceCtrlDispatcherA+0x0
0012fe90 78136d6c 96365185 003e27cc 003e27b8 7c94758b boinc!+0x0
00000000 00000000 00000000 00000000 00000000 00000000 MSVCR80!_msize+0x0

*** Dump of the thread (1cfc): ***

- Information -
Status: Waiting, Wait Reason: ExecutionDelay, Kernel Time: 10000000.000000, User Time: 11562500.000000, Wait Time: 195428176.000000

- Registers -
eax=01c7fa7a ebx=00465db0 ecx=27f08631 edx=01c7fa7a esi=00000000 edi=00affe68
eip=7c9485ec esp=00affe28 ebp=00affe90
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202

- Callstack -
ChildEBP RetAddr Args to Child
00affe90 7c8024ed 0000000a 00000000 00afff30 0043f7c2 ntdll!KiFastSystemCallRet+0x0
00affea0 0043f7c2 0000000a 0000000a 00000000 0040c9bd kernel32!Sleep+0x0
00afff30 004300a1 00000000 3ff00000 77f46253 00000000 boinc!+0x0
00afff98 004397b7 00000000 00156650 77f45e91 00000001 boinc!+0x0
00afffb8 7c824829 00156650 00000000 00000000 00156650 boinc!+0x0
00afffec 00000000 77f45e70 00156650 00000000 00905a4d kernel32!GetModuleHandleA+0x0

*** Dump of the thread (1bc0): ***

- Information -
Status: Waiting, Wait Reason: UserRequest, Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 195428176.000000

- Registers -
eax=003e20b0 ebx=015cfb00 ecx=00000004 edx=003e219c esi=000000b4 edi=00000000
eip=7c9485ec esp=015cf7e4 ebp=015cf854
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246

- Callstack -
ChildEBP RetAddr Args to Child
015cf854 7c821c8d 000000b4 ffffffff 00000000 015cfad8 ntdll!KiFastSystemCallRet+0x0
015cf868 00444937 000000b4 ffffffff 00000000 7c88b7c0 kernel32!WaitForSingleObject+0x0
015cfad8 7c8392a3 015cfb00 7c821ac1 015cfb08 00000000 boinc!+0x0
015cffec 00000000 781329e1 00b387f0 00000000 000000c8 kernel32!QueryMemoryResourceNotification+0x0

*** Dump of the thread (160c): ***

- Information -
Status: Waiting, Wait Reason: EventPairLow, Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 195428176.000000

- Registers -
eax=719358ab ebx=c0000000 ecx=00000000 edx=00000000 esi=00000000 edi=719691fc
eip=7c9485ec esp=00e3ff80 ebp=00e3ffb8
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246

- Callstack -
ChildEBP RetAddr Args to Child
00e3ffb8 7c824829 00159490 00000000 00000000 00159490 ntdll!KiFastSystemCallRet+0x0
00e3ffec 00000000 719358ab 00159490 00000000 00905a4d kernel32!GetModuleHandleA+0x0


*** Debug Message Dump ****


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

Exiting...

---