1073741819 (0xC0000005) Error in Seti

Message boards : Number crunching : 1073741819 (0xC0000005) Error in Seti
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile zoom3+1=4
Volunteer tester
Avatar

Send message
Joined: 30 Nov 03
Posts: 65738
Credit: 55,293,173
RAC: 49
United States
Message 480414 - Posted: 11 Dec 2006, 23:06:25 UTC
Last modified: 11 Dec 2006, 23:07:36 UTC

1073741819 (0xC0000005) Error in Seti, I'm getting this error and I've recently flashed the Bios to a more recent Bios for My P5W DH(1305 to 1601), I reset the project and this hasn't happened before and My PC is even overclocked to 3.2GHz before and after the flash. My Boinc client is Crunch3r's 5.7.64 and I'm using Test6(SSE3) from DeNitro.

This error doesn't always happen as Seti does still make successful WU's.
The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's
ID: 480414 · Report as offensive
Profile zoom3+1=4
Volunteer tester
Avatar

Send message
Joined: 30 Nov 03
Posts: 65738
Credit: 55,293,173
RAC: 49
United States
Message 480440 - Posted: 11 Dec 2006, 23:42:18 UTC
Last modified: 11 Dec 2006, 23:56:42 UTC

I found this thread and so far some may not apply here:
No screen saver is being used.
Video driver is 91.47 for XP x64.
New PC, Only 2 days old.
cpu is running at 36C while running SetiBoinc(Vigor Monsoon II hsf-tec)
Have not run Memtest, Ram is new as is the PC, Bios was flashed recently from 1305 to 1601.

I only began having this error when I flashed the bios to 1601.

http://setiathome.berkeley.edu/forum_thread.php?id=35366

Pooh Bear 27 wrote:

The error you get is a generic error that usually means some type of hardware issue.

Some of the questions are:

Do you run the screen saver? If so, try running without it. Make sure your video drivers are up to date, including DirectX.

Have you cleaned out the dirt? Make sure you are not overheating for any reason. Do a CPU test (Prime95 is one that is recommended).

Have you run a Memory Test (Memtest86+ is a recommended one), to make sure something has not gone faulty there.

These steps will usually help you find your problem. If not, let us know, and we can give some more suggestions.

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's
ID: 480440 · Report as offensive
W-K 666 Project Donor
Volunteer tester

Send message
Joined: 18 May 99
Posts: 19048
Credit: 40,757,560
RAC: 67
United Kingdom
Message 480589 - Posted: 12 Dec 2006, 2:34:41 UTC

You might want to read this page in the BOINC Wiki. And possibly follow on to the link for the MS KB.

Andy
ID: 480589 · Report as offensive
Profile zoom3+1=4
Volunteer tester
Avatar

Send message
Joined: 30 Nov 03
Posts: 65738
Credit: 55,293,173
RAC: 49
United States
Message 480630 - Posted: 12 Dec 2006, 3:49:10 UTC - in response to Message 480589.  
Last modified: 12 Dec 2006, 3:53:08 UTC

WinterKnight wrote:
You might want to read this page in the BOINC Wiki. And possibly follow on to the link for the MS KB.

Andy


I think I solved the error, So far the error hasn't happened again as I updated all My other drivers and the Bios to 1506 from 1305 on My P5WDHes QX6700 cpu, Now I get a ucode error press F1 to do anything and I have the usual settings set for updating the Bios, But other than that It works.
The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's
ID: 480630 · Report as offensive
Profile ChrisJay

Send message
Joined: 5 Aug 02
Posts: 35
Credit: 843,487
RAC: 0
United Kingdom
Message 483480 - Posted: 16 Dec 2006, 17:32:10 UTC

Hi, this is exactly the type of message you get when there is a problem with a memory module. Either you have a program that has allocated that memory slot, or your memory stick in slot 1 is faulty. try removing this memory stick see what happens then

Chris
ID: 483480 · Report as offensive
Profile zoom3+1=4
Volunteer tester
Avatar

Send message
Joined: 30 Nov 03
Posts: 65738
Credit: 55,293,173
RAC: 49
United States
Message 520268 - Posted: 20 Feb 2007, 4:50:00 UTC - in response to Message 483480.  

Hi, this is exactly the type of message you get when there is a problem with a memory module. Either you have a program that has allocated that memory slot, or your memory stick in slot 1 is faulty. try removing this memory stick see what happens then

Chris

I only get this error with Boinc 5.8.11, even if the client is now 5.9.0.32 which is on top of 5.8.11. I liked 5.4.11 better with 5.9.0.32 It never made this error, I don't think the ram has much to do with It, I've updated the chipset driver, Since I use the Chickens seti app I don't use a screen saver so the video driver doesn't apply, direct x is at 9.0c and that is all XP x64 can do.

And what are image links?
And what do they have to do with Boinc?

http://boincfaq.mundayweb.com/index.php?language=1&view=98&sessionID=47d605fc55585496e2970969d118011b
The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's
ID: 520268 · Report as offensive

Message boards : Number crunching : 1073741819 (0xC0000005) Error in Seti


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.