Forum > Windows

Massive Errors with SSE2 generic client

<< < (2/3) > >>

casketizr:
Same problem with 5.8.6 im going to use standard seti client now, this thing doesnt wok, unless someone tells me whats wrong. my quota is down to 23!!! already. last night it made 1(!) good result then this thing started again and about 20 jobs died with the same error as above within a  few minutes.
something is terribly wrong here or with this sse2 client.

Josef W. Segur:

--- Quote from: casketizr on 30 Jan 2007, 07:10:52 am ---Same problem with 5.8.6 im going to use standard seti client now, this thing doesnt wok, unless someone tells me whats wrong. my quota is down to 23!!! already. last night it made 1(!) good result then this thing started again and about 20 jobs died with the same error as above within a  few minutes.
something is terribly wrong here or with this sse2 client.
--- End quote ---

I have to admit I'm stumped. There are several thousand users of the SSE2 builds, so I think it points to a conflict with something else on your system. Obviously the standard application would be more productive.

OTOH if you're inclined to try one more thing you might try one of the graphics 2.0 builds if what you previously tried was non-graphic, or vice versa.
                                                                              Joe

casketizr:
It always gives the same exit code:
exit code -1073741795 (0xc000001d))
Do you happen to know what this stands for?

Kna:

--- Quote from: casketizr on 30 Jan 2007, 02:36:35 pm ---It always gives the same exit code:
exit code -1073741795 (0xc000001d))
Do you happen to know what this stands for?

--- End quote ---

Hello

I'm not programmer, but in Windows language, this seems to mean "STATUS_ILLEGAL_INSTRUCTION", that don't help too much..  :-\

If you do some googling with exit code 1073741795 (0xc000001d), you can see that your error can occur related to various Boinc projects, Boinc versions and apps.
So, don't seems to be strictly related to Chicken's apps.

Google didn't show me THE solution, but try it if you're better with english language than me.

Good luck

Jason G:
Hi there,
     I had that 0xc000001d error code a few times too, system not overclocked at the time, but is a little now :)

In my case i had the occassional BSOD as well (aghh). This was with the Intel SSE2 client... I would expect this app to push ram harder than the stock client. The BSOD symptom sometimes manifested with more agressively optimised media players also ( probably also SSE2)

What it turned out to be for me is that the SPD automatic memory timings ( preset to Auto in BIOS) were a little suspect. Now, mind you, under Memtest86+, the RAM seemed OK even after about 8 hours test ( on automatic timings, I would bet that memtest86+ doesn't use SSE2 Instructions).

what I found somehow was that my cheap mobo's timings weren't setting to what they said they were :0, so I manually set them ( to the same as what Auto should have chosen) and all was OK, no more BSODs or 0xc... errors. ( What? a lying BIOS? )

Now the clincher is that the RAM chip datasheet confirmed what cpu-z and everst told me, that ram timings were reporting right ... It just works right on Manual Setting ... Not on Auto... wierd eh? ( Both my Manual settings & the AUTO say the same numbers)

All A-OK on Manual :)

It has been so rock stable since that I juiced the GHz up 5% Just for a test,  six weeks now , no "client errors" or BSODs.

Jason
[ Oh By the way, Mine is a P4 Northwood 2.0"A" ( pre hyperthreading)]

Navigation

[0] Message Index

[#] Next page

[*] Previous page