With new win7 ATI 1.28 app all tasks error

.clair.
.clair.
Joined: 20 Nov 06
Posts: 62
Credit: 1051176770
RAC: 0
Topic 196508

With the previous ATI app everything on this machine was valid.
With this new app 90% of tasks error out with a message like the one below.

01/09/2012 02:52:08 | Einstein@Home | Output file p2030.20110117.G194.66-02.22.S.b1s0g0.00000_368_1_2 for task p2030.20110117.G194.66-02.22.S.b1s0g0.00000_368_1 absent

The machine runs SETI ATI work without any errors,
(i am unable to get work from them atm)
the machine runs win 7 home 64 with ATI 7970 GPUs ccc 12:4, running one task per GPU
I have no idea what has caused the new APP to fail so badly.
After the 1.28 app was released i ran some tasks and they errored so i detached to clear all old stuff from the folder,
then SETI had work so i did that,
Well, SETI is having problems again so i am back here,
So, all new files in the E@H folder and it has not made any diferance, still lots of errors.
Any idea what i can do ??

My page of errors

Jord
Joined: 26 Jan 05
Posts: 2952
Credit: 5779100
RAC: 0

With new win7 ATI 1.28 app all tasks error

We can't see your errors like that. We can see them like this.

In a lot of your errors, it shows this:

Quote:

Error occured on Saturday, September 1, 2012 at 05:18:08.

C:\ProgramData\BOINC\projects\einstein.phys.uwm.edu\einsteinbinary_BRP4_1.28_windows_x86_64__opencl-ati.exe caused an Access Violation at location 69008d2d in module C:\Windows\system32\aticaldd64.dll Reading from location ffffffff.

Call stack:
69008D2D C:\Windows\system32\aticaldd64.dll:69008D2D calddiGetExport
69008B79 C:\Windows\system32\aticaldd64.dll:69008B79 calddiGetExport
69003E80 C:\Windows\system32\aticaldd64.dll:69003E80 calddiGetExport
E4764856 C:\Windows\system32\amdocl64.dll:E4764856 clGetSamplerInfo
E4766E7D C:\Windows\system32\amdocl64.dll:E4766E7D clGetSamplerInfo
E4762233 C:\Windows\system32\amdocl64.dll:E4762233 clGetSamplerInfo
E47623CC C:\Windows\system32\amdocl64.dll:E47623CC clGetSamplerInfo
E4776642 C:\Windows\system32\amdocl64.dll:E4776642 clGetSamplerInfo
E4764EFA C:\Windows\system32\amdocl64.dll:E4764EFA clGetSamplerInfo
E47313A5 C:\Windows\system32\amdocl64.dll:E47313A5 clGetSamplerInfo
E4731682 C:\Windows\system32\amdocl64.dll:E4731682 clGetSamplerInfo
E4728D41 C:\Windows\system32\amdocl64.dll:E4728D41 clGetSamplerInfo
7774F33D C:\Windows\system32\kernel32.dll:7774F33D BaseThreadInitThunk
77982CA1 C:\Windows\SYSTEM32\ntdll.dll:77982CA1 RtlUserThreadStart


As far as I can read that, it means that your videocard driver crashes. You may want to try an older, more stable driver than CC 12.4.

And by the way, what kind of CPU do you have? As an Intel Pentium 4 CPU 3.60GHz isn't a 64bit CPU.

Claggy
Claggy
Joined: 29 Dec 06
Posts: 560
Credit: 2694028
RAC: 0

RE: And by the way, what

Quote:
And by the way, what kind of CPU do you have? As an Intel Pentium 4 CPU 3.60GHz isn't a 64bit CPU.


According to WiKipedia a Pentium 4 Family 15 Model 4 Stepping 3 is a Prescott 2M with MMX, SSE, SSE2, SSE3, Hyper threading and Intel 64

Claggy

Jord
Joined: 26 Jan 05
Posts: 2952
Credit: 5779100
RAC: 0

Ah, that explains that. I

Ah, that explains that. I thought they would show as Pentium 4 Extreme Edition, or similar.

.clair.
.clair.
Joined: 20 Nov 06
Posts: 62
Credit: 1051176770
RAC: 0

I will try some different GPU

I will try some different GPU drivers and see what happens,
I use 12.4 as uses less CPU and more GPU, though not much use if it is errors the new app.
drivers before that seemed to be cpu hungry,
I am giving 12:8 a go now and will see what comes of it,
Any thoughts on what 12.5 to 12.7 are like for performance or bugs.

.clair.
.clair.
Joined: 20 Nov 06
Posts: 62
Credit: 1051176770
RAC: 0

I tried several drivers all

I tried several drivers all the way back to ccc11:12 that is on the CD in its box
It made little if any benifit not long after that in it started to BSOD
Then trying to fix that it began to reboot at the `safe mode` login window,
something is broke.
I did a roleback two days to fix that.
Long story short,
When i have time the next thing i will try is a full reinstall of win7 before atempting to run E@H again.
And the strange thing is I am back to using ccc12:4 on seti without any problems

Jord
Joined: 26 Jan 05
Posts: 2952
Credit: 5779100
RAC: 0

RE: it started to

Quote:
it started to BSOD


What did the BSOD say?
Normally the BSODs tell you what's wrong, and I'm sorry to say, but when you manage to return the same BSOD regularly, it's hardware earlier than software that's amiss.

.clair.
.clair.
Joined: 20 Nov 06
Posts: 62
Credit: 1051176770
RAC: 0

RE: What did the BSOD

Quote:
What did the BSOD say?


The colour of the air around me matched it, I don`t remember the text,
I accept that the BSOD screem does give information to help trace the problem,
generaly they convey one message - It`s broke` :(
Before i nuke it and start again i will see if i can repeat the fault condition to see if it is a traceable hardware fault,
Most of this box is new this year, the motherboard is the oldest part by a few years.

Richard Haselgrove
Richard Haselgrove
Joined: 10 Dec 05
Posts: 2142
Credit: 2776018000
RAC: 805376

RE: RE: What did the BSOD

Quote:
Quote:
What did the BSOD say?

The colour of the air around me matched it, I don`t remember the text,
I accept that the BSOD screem does give information to help trace the problem,
generaly they convey one message - It`s broke` :(
Before i nuke it and start again i will see if i can repeat the fault condition to see if it is a traceable hardware fault,
Most of this box is new this year, the motherboard is the oldest part by a few years.


You don't have to wait for another blue screen - you can revisit the previous one with BlueScreenViewer

.clair.
.clair.
Joined: 20 Nov 06
Posts: 62
Credit: 1051176770
RAC: 0

Thank you Richard i will have

Thank you Richard i will have a go with that.
Though it`s a bit like winning a `Ticket To Hell`
Hope it`s return paid ticket ;¬)

dskagcommunity
dskagcommunity
Joined: 16 Mar 11
Posts: 89
Credit: 1163831704
RAC: 245197

omg that remembering me as i

omg that remembering me as i try to test a "new generation" ati card in my workingpc for compatibiltytests on POEM...it ends up in BSOD on windows load. There was NO Hardware fault, the card runs now since some 24/7 months in another (boinconly)pc with a clean Windows&ATI 11.9 installation. problem was the 12.x driver taht i fear now like death for any other ati boxes. ATI and his silly & crazy Driversupport -_- it nearly broke an important windowsinstallation it was hard to recover it..plus i hated me i didnt make an actual Harddisk snapshot before.

as mentiond earlier in this thread, i would try a stable 11.x driver first.

DSKAG Austria Research Team: [LINK]http://www.research.dskag.at[/LINK]

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.