Author Topic: x38g reports (Read 126180 times)

perryjay · « **Reply #255 on:** 28 Jul 2011, 04:10:43 pm »

Well, that was interesting. I ran the EVGA scanner for an hour. Afterward I checked it's log file. According to it I am running an ATI 6850 and I had artifacts out the ying yang. It also downclocked me way below anything that should be still running. I don't think I'll try that again.

And..... tried to get your version but it tells me my directx9 is not up to date and it blocks out GPU OCCT and power supply tests. I've got directx 11.

Jason G · « **Reply #256 on:** 28 Jul 2011, 09:04:46 pm »

Quote from: perryjay on 28 Jul 2011, 04:10:43 pm

And..... tried to get your version but it tells me my directx9 is not up to date and it blocks out GPU OCCT and power supply tests. I've got directx 11.

DirectX in your system will need an update. DirectX 9.0c update was published 18th April 2011.

http://www.microsoft.com/download/en/details.aspx?id=35

perryjay · « **Reply #257 on:** 29 Jul 2011, 10:39:33 am »

Well, that didn't take as long as I thought it would. I don't think I ever had DX9 on this machine. Hope it doesn't mess with anything else on here.

_heinz · « **Reply #258 on:** 29 Jul 2011, 02:57:25 pm »

I tried OCCT on my laptop.
the "Monitoring" part did not open on my i3
seems program is missing some latest chipsets

heinz

perryjay · « **Reply #259 on:** 29 Jul 2011, 04:31:47 pm »

I ran it for 30 minutes at default 0 shader complexity the first time and got a ton of errors then remembered one of the FAQs that said EVGA precision would cause errors so I stopped it and ran it again for your 6 minute test and set the shader complexity to 8 with no errors.

https://picasaweb.google.com/lh/photo/uFQ_UCQC5Ra7BCZtozmVBSbSZ_Aup0-RSRejz0fueJU?feat=directlink

https://picasaweb.google.com/lh/photo/eG8e5yUOsUAFkZ-fg-BOGybSZ_Aup0-RSRejz0fueJU?feat=directlink

https://picasaweb.google.com/lh/photo/vTDakos6ogUKQLJp0zHSPCbSZ_Aup0-RSRejz0fueJU?feat=directlink

https://picasaweb.google.com/lh/photo/hU2Qv8QKDHix7nBTAEnPXibSZ_Aup0-RSRejz0fueJU?feat=directlink

https://picasaweb.google.com/lh/photo/9RYN9UQs5luTfj2CjnyhISbSZ_Aup0-RSRejz0fueJU?feat=directlink

https://picasaweb.google.com/lh/photo/0sLNi2Pdejctj_P4nYzlAibSZ_Aup0-RSRejz0fueJU?feat=directlink

https://picasaweb.google.com/lh/photo/yi4S9r03UuULaEICDGRMMibSZ_Aup0-RSRejz0fueJU?feat=directlink

Jason G · « **Reply #260 on:** 29 Jul 2011, 04:43:04 pm »

OK,
looks like some optimised code can push things harder than previously thought for durations too short to detect with monitoring tools. That would explain a lot coupled with overoptimistic factory or user OC's, insufficient cooling or PSU. For now I'd advise backing off any OC if you see invalids not directly attributable to being stiffed by legacy wingmen apps. In the long run I may need to detect signs of instability, and devise a more purpose built stability check.

Stable for 6 mins OCCT on max complexity is good. An hour run would be more thorough, but probably get pretty warm.

Jason

perryjay · « **Reply #261 on:** 29 Jul 2011, 04:48:03 pm »

Hope I did those links right. After a half hour on the first run it only got up to 85c so temp doesn't seem to be a problem.

perryjay · « **Reply #262 on:** 03 Aug 2011, 09:23:10 am »

This one took awhile to decide. http://setiathome.berkeley.edu/workunit.php?wuid=763346130

glennaxl · « **Reply #263 on:** 06 Aug 2011, 12:20:05 pm »

Starting to get errors on gtx 570:
http://setiathome.berkeley.edu/result.php?resultid=2027743944
http://setiathome.berkeley.edu/result.php?resultid=2027727112
http://setiathome.berkeley.edu/result.php?resultid=2027722678
http://setiathome.berkeley.edu/result.php?resultid=2027713834
http://setiathome.berkeley.edu/result.php?resultid=2027666731
http://setiathome.berkeley.edu/result.php?resultid=2027666700

Code: [Select]

CUFFT error in file 'c:/[Projects]/X_CudaMB/client/cuda/cudaAcc_fft.cu' in line 125.
Cuda error 'cudaFree(dev_PowerSpectrumSumMax)' in file 'c:/[Projects]/X_CudaMB/client/cuda/cudaAcceleration.cu' in line 522 : unknown error.
Cuda error 'cudaFree(dev_outputposition)' in file 'c:/[Projects]/X_CudaMB/client/cuda/cudaAcceleration.cu' in line 524 : unknown error.
Cuda error 'cudaFree(dev_flagged)' in file 'c:/[Projects]/X_CudaMB/client/cuda/cudaAcceleration.cu' in line 526 : unknown error.
Cuda error 'cudaFree(dev_NormMaxPower)' in file 'c:/[Projects]/X_CudaMB/client/cuda/cudaAcceleration.cu' in line 528 : unknown error.
Cuda error 'cudaFree(dev_PoTPrefixSum)' in file 'c:/[Projects]/X_CudaMB/client/cuda/cudaAcceleration.cu' in line 530 : unknown error.
Cuda error 'cudaFree(dev_PoT)' in file 'c:/[Projects]/X_CudaMB/client/cuda/cudaAcceleration.cu' in line 532 : unknown error.
Cuda error 'cudaFree(dev_GaussFitResults)' in file 'c:/[Projects]/X_CudaMB/client/cuda/cudaAcceleration.cu' in line 534 : unknown error.
Cuda error 'cudaFree(dev_t_PowerSpectrum)' in file 'c:/[Projects]/X_CudaMB/client/cuda/cudaAcceleration.cu' in line 536 : unknown error.
Cuda error 'cudaFree(dev_PowerSpectrum)' in file 'c:/[Projects]/X_CudaMB/client/cuda/cudaAcceleration.cu' in line 538 : unknown error.
Cuda error 'cudaFree(dev_WorkData)' in file 'c:/[Projects]/X_CudaMB/client/cuda/cudaAcceleration.cu' in line 540 : unknown error.
Cuda error 'cudaFree(dev_flag)' in file 'c:/[Projects]/X_CudaMB/client/cuda/cudaAcceleration.cu' in line 542 : unknown error.
Cuda error 'cudaFree(dev_cx_ChirpDataArray)' in file 'c:/[Projects]/X_CudaMB/client/cuda/cudaAcceleration.cu' in line 546 : unknown error.
Cuda error 'cudaFree(dev_cx_DataArray)' in file 'c:/[Projects]/X_CudaMB/client/cuda/cudaAcceleration.cu' in line 548 : unknown error.
Cuda sync'd & freed.

Jason G · « **Reply #264 on:** 06 Aug 2011, 12:26:15 pm »

Eeh gads. If that's started recently then somethings come unstuck. Please reboot & report temperatures. I can see your driver is 280.19. If something let go, I'd like to find out what.

Jason

glennaxl · « **Reply #265 on:** 06 Aug 2011, 12:54:24 pm »

It all started yesterday - GPU load was 99% but temp was under 40C. Check with GPU-z, cuda-z and nvidia inspector if the GPU has down-clocked itself but it didn't. Reboot, change drivers, OC with EVGA pricision, OC thru bios, ran OCCT, ran EVGA OC Scanner - all these stuff didn't point to a single error. Right now load temps are @65C-70C. I also change the cuda count from .31/.34 to .50/.50 but still got an error on MB but surprisingly no error on AP.

Jason G · « **Reply #266 on:** 06 Aug 2011, 01:24:10 pm »

Please Ditch AP, aborting tasks as necessary, then after a reboot report to me x38g behaviour only. Thanks.

glennaxl · « **Reply #267 on:** 07 Aug 2011, 10:55:22 am »

Quote from: Jason G on 06 Aug 2011, 01:24:10 pm

Please Ditch AP, aborting tasks as necessary, then after a reboot report to me x38g behaviour only. Thanks.

After ditching all AP task, x38g is running smoothly.

Jason G · « **Reply #268 on:** 07 Aug 2011, 11:08:50 am »

Quote from: glennaxl on 07 Aug 2011, 10:55:22 am

After ditching all AP task, x38g is running smoothly.

Thanks for the information, and I apologise for the curtness of the recommendation. For the AP app, current advice being given is to run either Cuda 4.0 Drivers, or the Beta AP app, but not both together, as apparently it does not include any of the (boincApi) fixes for newer drivers, and the underlying OS/driver changes they address.

Jason

perryjay · « **Reply #269 on:** 07 Aug 2011, 02:03:19 pm »

Here's one that is interesting. Must say they tried their best to prove me wrong but finally gave up and gave me credit. http://setiathome.berkeley.edu/workunit.php?wuid=783092275

Author Topic: x38g reports (Read 126180 times)

perryjay

Re: x38g reports

Jason G

Re: x38g reports

perryjay

Re: x38g reports

_heinz

Re: x38g reports

perryjay

Re: x38g reports

Jason G

Re: x38g reports

perryjay

Re: x38g reports

perryjay

Re: x38g reports

glennaxl

Re: x38g reports

Jason G

Re: x38g reports

glennaxl

Re: x38g reports

Jason G

Re: x38g reports

glennaxl

Re: x38g reports

Jason G

Re: x38g reports

perryjay

Re: x38g reports