When I press afterburner my system crashes. I got rid of Catalyst Control Center a while back.

Probably you mean "When I press Reset button in MSI Afterburner my system crashes"

System crash is always scary, so only in case you want to continue:

0) what MHz are shown by MSI Afterburner (in left and right) just after you started it after a reboot?

1) Try different version of MSI Afterburner

2) see that no other (monitoring) tool (e.g. from XFX or GPU-Z) that accesses GPU runs (they may conflict) (best if you exit all other programs that can be exited)

3) do the changes on idle GPU (right graph in MSI Afterburner will show low MHz)

4) Uncheck Synchronize ... here (and choose which GPU to tweak):
(I don't have 2 GPUs and am unsure how it will look and work)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I downloaded the latest version of msi overclocker and unsynchronized the gpu's. I set it to overclock at 483MHz and it crashed again with some kind of clocking error from win8.1 with a new pastel blue screen and a smiley face on it. For now I think I just hold with the progress we've made so far. See ya down the road.

I have been running my gpu's for about a day at 430MHz core clock and 470 MHz memory clock and my system runs excellent. I guess I just bought the worst possible HD 6570 available. Is there any other way to try and fix, jigger or mod
my problem. It seem strange that the ati core rating is 650MHz and all I can get out of it is 430MHz. Thanks, everybody.

Just bought a new msi hd 7770. Looks like a good quality card. Now I'll run three gpu's.

DUH!!!
I found a catalyst install manager still running which I thought was just a install mgr, not actual catalyst pgms.
After uninstall, I am running at 500 MHz now and it has been running good for
seven minutes.

I am guilty! You told me twice to make sure my catalyst was not running. Sorry, sorry.

now seti won't send any cpu tasks to me and reports that one of my two gpu's keeps generating computer errors. My oh my! I even tried collatz and they say one of my gpu's reports errors.

OK, I started over from scratch and everything is running now. Everything is back to square one - all stock seti. I may or may not restart my lunatics et. al. but I have to wait until I get my new msi 7770. I may need all the power I have available with my psu to just run everything stock no pushing anything.

I discovered two settings in the bios that needed to be adjusted. Now the gpu's are running at 650 MHz. I should have checked that earlier. Sorry folks!

I discovered two settings in the bios that needed to be adjusted.

I wonder which BIOS settings that may be?

P.S.
Using the opportunity to present you another good monitoring/info program:
SIV - System Information Viewer (you need only siv.zip)
http://rh-software.com/

 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I didn't realize I had these parameters in my asrock bios and it's embarrassing but here it is:

chipset configuration:
1) primary graphics adapter - pci or pcie (boot priority) defaults to pci

2) pcie max payload size (TLP -transaction layer packet)128B or 256B, defaults to 128B

After resetting to pcie and 256B, everything ran correctly at 650MHz.
Sorry about that. I should have checked it from the beginning and thanks for the tip on that system info pgm. Looks good. I'll have to check it out.

The gpu's will run very hot very fast when overclocking make sure that the heat sinks are clean and that the fans set to high get a water cooler if you can.

or second box no drive 12 dollar dummy plug network boot 2 used cheap mid range gpu's replace as needed.

also must monitor and throttle cpu and gpu I use tthrottle.

---

thanks but I missed this part:

or second box no drive 12 dollar dummy plug network boot 2 used cheap mid range gpu's replace as needed.

I have three more questions for this group:

My card listed by catalyst ctl ctr say Min 400 Max 675. The card is supposed to have a core clock of 650. At what point do you consider a card is being overclocked over 400 or over 650?

TThrottle only show one of my two gpu temps. Why?

My cpu's show a range in the low sixties. What temp is considered to high?

At what point do you consider a card is being overclocked over 400 or over 650?

Of course over 650

TThrottle only show one of my two gpu temps. Why?

Which graph?
Check 'Logging' tab in Debug mode
What is shown by SIV ?

My cpu's show a range in the low sixties. What temp is considered to high?

Depend on the CPU
For your Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
http://ark.intel.com/products/37147/Intel-Core-i7-920-Processor-8M-Cache-2_66-GHz-4_80-GTs-Intel-QPI

TCASE 67.9°C

http://www.cpu-world.com/CPUs/Core_i7/Intel-Core%20i7-920%20AT80601000741AA%20(BX80601920%20-%20BXC80601920).html

Maximum operating temperature 67.9°C

This is the Maximum operating temperature as measured on the center-top of the CPU case/package (where heatsink sits)

You may see 3 different CPU temperature measurement sensors/readings (not all are available in every case):
- 'core' (internal CPU sensors - 1 per core)
- 'package' (internal CPU sensor - 1 per CPU chip, somewhere in the silicon of the chip)
- 'CPU' (external sensor on the motherboard under the CPU - SIV can read and show these at the rightmost + real CPU voltage and fan speed)

(not every program names the sensors/readings the same, there is no standard)


To understand how Intel CPU sensors work read all my posts here:
http://setiathome.berkeley.edu/forum_thread.php?id=63650&postid=1094579#1094579

 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Thanks BilBg. You sure have been around all this stuff. MY tthrottle shows 4 temp sensors and max case temp of 67.9 degrees C. All the graphs show only one gpu. I have another gpu temp pgm which shows both gpu's and their temp but it only shows it up to 100 minutes so tthrottle is better for the long term.

Okay now let me ask this. Is there a benefit it performance/points in using lunatics and are there downsides to using it? Unstable? What sort of improvement will I find with lunatics? Do I have to simply test my machine using both lunatics and stock-seti to find out?

Thanks again. I can see how much of a newbie I am here.

 
For the TThrottle problem maybe you have to contact the author:
http://setiathome.berkeley.edu/show_user.php?userid=8906489

He probably will want to see the info from Logging tab with Debug checked


Lunatics:
Stock GPU apps are (almost) identical these days to the optimized (= lab accepted to use the Lunatics as stock)
- see my post with screenshots:
http://setiathome.berkeley.edu/forum_thread.php?id=75115&postid=1541308#1541308

Unstable? No

Improvement:
- CPU apps are faster (150-200%)
- you can choose which exactly apps to run:
    e.g. on CPU I run only MultiBeam (SETI@home v7) SSE2
    on ATI AMD GPU I run only AstroPulse (the most effective use of ATI)
- you may install newer Lunatics versions (manually, or wait for the next installer) without waiting for the lab for years to update the stock apps
(e.g. newer ATI AMD apps do not need a free CPU core per every task (I think 1 free CPU core is enough for many running GPU tasks))

Downsides:
Apps are not auto-updated (in fact I see this as an Improvement ;) )


P.S.
Is this "another gpu temp pgm" Open Hardware Monitor?

 

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

It's at gputemp.com.
Thanks, I'll reinput lunatics and use astropulse for my gpu's.

I am having trouble reestablishing myself with lunatics. My app_config file reads:
<app_config>
<app>
<name>setiathome_v7</name>
<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>
</app_config>

but now seti won't sent me anymore gpu work. Maybe because I had some aborts and failures. Do I just wait until seti decides to send me the gpu work? Is my app_config file OK? Thanks.

after so many aborts or invalids, Seti will restrict how many a day you get until you produce valid results. If you don't have ANY work units then you can try resetting the project and that should cause seti to send you some work units to test your system. If you do have any work units, don't reset as this will abort all of them. Wait till you finish then try resetting.


Zalster