Welcome to MilkyWay@home

Posts by zablociak

1) Message boards : News : Scheduled Maintenance Concluded (Message 65783)
Posted 14 Nov 2016 by zablociak

Is there any objection to this plan?

I'm OK with this idea.
2) Message boards : News : Scheduled Maintenance Concluded (Message 65651)
Posted 11 Nov 2016 by zablociak
Hi Jake!
Unfortunately all tasks (both ATI and NVIDIA) fail immidiately after start with -1073741515 (0xffffffffc0000135) Unknown error number
3) Message boards : Number crunching : Is this project OVER, semi abandoned or DYING? (Message 65626)
Posted 9 Nov 2016 by zablociak
I have E@H set to 0% on my 280x plus I setup a script to pause E@H every 15min and resume

Can you share this script with us, please?
4) Message boards : Number crunching : Incorrect function. (0x1) - exit code 1 (0x1) (Message 62089)
Posted 27 Jul 2014 by zablociak
I assume that your 7950 is not faulty and not overheating.

Then goes:

This was probably caused by the following module: atikmdag.sys (atikmdag+0x28ECE)

I've experienced tons of BSODs caused by atikmdag.sys while crunching MW (and other projects, but not E@H BRPs).

Combination of method described here: http://forums.guru3d.com/showthread.php?t=363233 and disabling Aero in Win7 worked for me.

Reinstalling drivers, using Driver Sweeper, adjusting clocks most probably will not help you.

5) Message boards : News : New N-Body Runs (6/28) (Message 61970)
Posted 30 Jun 2014 by zablociak
I've got already 3 WUs with "196 (0xc4) EXIT_DISK_LIMIT_EXCEEDED":

Additionally this WU http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=568120857 runs one-threaded and took >400k seconds on the other machine.

6) Message boards : Number crunching : Setting not respected - Frequency (in Hz) that should try to complete individual work chunks (Message 61720)
Posted 16 May 2014 by zablociak
Hi guys!

I'm running "Modified Fit" on my AMD HD7970 GPU with app_config.xml (only in order to run 2 tasks in parallel, no CPU tasks) and I've got a separate venue for this machine (as I run also a few CPU-only machines).
The problem is that when I set a target frequency for individual work chunks (let's say "40" instead of default "60"), this setting is not respected and all WUs are being sent with 'Using a target frequency of 60.0' all the time.

So, 2 questions:
- does it make sense to change the default value at all?
- is it possible to add <cmdline>--gpu-target-frequency 40</cmdline> into app_config.xml?


©2023 Astroinformatics Group