Instruction at "0x69726952" referenced memory at "0x00000008"

Questions and Answers : Windows : Instruction at "0x69726952" referenced memory at "0x00000008"
Message board moderation

To post messages, you must log in.

AuthorMessage
petereque

Send message
Joined: 9 Jun 99
Posts: 4
Credit: 16,492,152
RAC: 48
United States
Message 230243 - Posted: 12 Jan 2006, 20:38:20 UTC


I'm getting the following error message from Windows:

The instruction at "0x69726951" references memory at "0x00000008". The memory could not be "written". press OK to terminate.

Work units seem to transfer properly.

Seti version 3.08, Windows XP Pro SP2, Pentium 4 2.66 gHz.
ID: 230243 · Report as offensive
J D K
Volunteer tester
Avatar

Send message
Joined: 26 May 04
Posts: 1295
Credit: 311,371
RAC: 0
United States
Message 230280 - Posted: 12 Jan 2006, 21:40:41 UTC

SETI ver 3.08 has no where to transfer to, Classic SETI is shut down, so I am at a lost as to what you are referring to....
And the beat goes on
Sonny and Cher

BOINC Wiki

ID: 230280 · Report as offensive
Cookie Monster

Send message
Joined: 25 May 99
Posts: 1
Credit: 6,012,332
RAC: 0
Canada
Message 232391 - Posted: 17 Jan 2006, 0:47:58 UTC - in response to Message 230280.  
Last modified: 17 Jan 2006, 0:48:47 UTC

SETI ver 3.08 has no where to transfer to, Classic SETI is shut down, so I am at a lost as to what you are referring to....


I am having a similar problem with Seti 4.18 x86 ("The instruction at foo referenced memory at foo2. The memory could not be read."). I am running dual monitors on an old Radeon 8500LE card with fairly up-to-date drivers.

This error seems to consistently happen if the screen saver is running (graphs are being drawn &c.) and I move the mouse. The screen saver image freezes on the primary monitor, and I can watch the mouse cursor move over the frozen image, but I'm unable to see any Windows desktop. The secondary monitor works fine (it actually goes black when the screen saver activates). If I use ATi's Catalyst control panel to resize the primary screen then it will be reset. I'll be returned back to the normal desktop and I'll see the above error message.

This problem does not occur when the screen saver has moved onto the blank screen and I move the mouse (the displays wake up normally then).
ID: 232391 · Report as offensive
petereque

Send message
Joined: 9 Jun 99
Posts: 4
Credit: 16,492,152
RAC: 48
United States
Message 238374 - Posted: 27 Jan 2006, 21:16:35 UTC - in response to Message 230280.  

SETI ver 3.08 has no where to transfer to, Classic SETI is shut down, so I am at a lost as to what you are referring to....


ID: 238374 · Report as offensive
petereque

Send message
Joined: 9 Jun 99
Posts: 4
Credit: 16,492,152
RAC: 48
United States
Message 238377 - Posted: 27 Jan 2006, 21:21:27 UTC - in response to Message 238374.  

SETI ver 3.08 has no where to transfer to, Classic SETI is shut down, so I am at a lost as to what you are referring to....



I must have misunderstood the BOINC instructions. However, I have now used Add/remove to get rid of Seti 3.08 and still get a very similar message:

Setiathome_4.18_windows_intel86.exe - application error
0x69726951 referenced memory at 0x00000008 which could not be "written"

Note that the first address is one less than the previous msg.

Thanks,
Pete

ID: 238377 · Report as offensive
mikeb

Send message
Joined: 26 Nov 05
Posts: 3
Credit: 11,483
RAC: 0
United Kingdom
Message 239573 - Posted: 29 Jan 2006, 23:10:26 UTC

You haven't done anything wrong, and essentially your installation works fine. This issue has been around for some time now and whilst that's the case nobody at SETI really gives a sh.... just try and pretend it didn't happen
ID: 239573 · Report as offensive
Profile MJKelleher
Volunteer tester
Avatar

Send message
Joined: 1 Jul 99
Posts: 2048
Credit: 1,575,401
RAC: 0
United States
Message 239576 - Posted: 29 Jan 2006, 23:16:03 UTC
Last modified: 29 Jan 2006, 23:17:32 UTC

The error is referenced here in the Wiki. A part of that page says:
This Message means that the BOINC Client Software, Science Application, or Operating System encountered a severe error. It should be noted that these errors may not indicate a specific problem with the software, but may be the result of a confluence of stray interactions that produces, um, a negative effect.

Check out some of the problems it talks about, you'll be improving your computer in general.

Also, you're using BOINC version 4.25, which has been superceded several times. Current version is 5.2.13. This may not have any effect with this error, but there were other bug fixes along the way.

MJ

ID: 239576 · Report as offensive
mikeb

Send message
Joined: 26 Nov 05
Posts: 3
Credit: 11,483
RAC: 0
United Kingdom
Message 239619 - Posted: 30 Jan 2006, 0:25:00 UTC

good one MJ. Probably 1,2 & 3 of the "General" section then;
1. Overstressed hardware; Thrashing the processor at 100% for an extended period of time is probably covered there then
2. Flaky device drivers; Almost: Try flaky "use" of device drivers (as there is not commonality across reporters of this issue)
3. An actual problem in the software; Well duh! D'ya think it could be ?? A problem that has only manifested itself since BOINC came along ... a clue perhaps ? Hit the nail on the head there then.
Well glad we cleared that up then.
p.s. I fully expect that we're all using BOINC 5.x The error comes from Setiathome_4.18. Not quite sure where you got 4.25 from.
ID: 239619 · Report as offensive
Profile MJKelleher
Volunteer tester
Avatar

Send message
Joined: 1 Jul 99
Posts: 2048
Credit: 1,575,401
RAC: 0
United States
Message 239624 - Posted: 30 Jan 2006, 0:36:10 UTC - in response to Message 239619.  
Last modified: 30 Jan 2006, 0:46:12 UTC

good one MJ. Probably 1,2 & 3 of the "General" section then;
1. Overstressed hardware; Thrashing the processor at 100% for an extended period of time is probably covered there then
Processors are intended to be able to work at 100%, but some ancillary parts can hold heat beyond the ability of the processor to deal with.
2. Flaky device drivers; Almost: Try flaky "use" of device drivers (as there is not commonality across reporters of this issue)
Have you been keeping stats on the reporting of bad device drivers? I'd like to see your data to show this lack of commonality. There have been reports where updating drivers has resolved problems, so it's a place to look.
3. An actual problem in the software; Well duh! D'ya think it could be ?? A problem that has only manifested itself since BOINC came along ... a clue perhaps ? Hit the nail on the head there then.
Well glad we cleared that up then.
Disregarding, of course, the thousands of users that are running the same software on the same operating system with no problems, of course it must be the software? I don't think so.
p.s. I fully expect that we're all using BOINC 5.x The error comes from Setiathome_4.18. Not quite sure where you got 4.25 from.
From one of petereque's results:
<core_client_version>4.25</core_client_version>
Can't expect that everybody's gone to the 5.x.x BOINC, because some haven't. SETI 4.18 is automatic, BOINC takes action on the part of the user.

Let us know when you've got something to contribute to the help desk, mikeb.

MJ

ID: 239624 · Report as offensive

Questions and Answers : Windows : Instruction at "0x69726952" referenced memory at "0x00000008"


 
©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.