Bad memory?

Isn''t that usually when writing outside of legal space? A la out of bounds array or bad pointer errors?

quote:

---

Original post by kordova
Isn't that usually when writing outside of legal space? A la out of bounds array or bad pointer errors?

---

Yea I think so. I'd definetly run the suspect code through a debugger. I would run it until it crashes to find out where, and then check my pointers at that point.

EDIT: I assumed this was the OP's code, but it might not be. But still, if this is from a commercial program, the error should mean the same thing.



-=Peon=- : A Poorly Implement Forum Bot ------
© Kordova, 2003


[edited by - Peon on November 19, 2003 7:46:23 PM]

Could be, try this program. I think this is the one I used:
http://oca.microsoft.com/en/windiag.asp

It's a simple bootable memory tester. It just goes through memory and writes and reads stuff. It should detect a bad block of memory, unless it's and intermittent problem, then it will be harder to detect.

[EDIT] It doesn't seem like a program would do that if it's occuring in different programs.

[edited by - Cold_Steel on November 19, 2003 7:49:03 PM]

Well, when it happend today it was while running my own badly coded program so that might be the case... sure hope so, memory is such a borring thing to buy. Can''t remember (now my own memory is failing me if it happend in any commercial app before. It was just that I''ve never seen that dialog box before, but maybe they just changed it in XP

quote:

---

Original post by geekster
Well, when it happend today it was while running my own badly coded program so that might be the case... sure hope so, memory is such a borring thing to buy. Can''t remember (now my own memory is failing me if it happend in any commercial app before. It was just that I''ve never seen that dialog box before, but maybe they just changed it in XP

---

Well, at least in my small scale (hobby) projects, it''s really easy to find the source of the error if I run it through the debugger. I don''t know how other debuggers compare, but I really like the .NET one.



-=Peon=- : A Poorly Implement Forum Bot ------
© Kordova, 2003

quote:

---

Original post by geekster
Well, when it happend today it was while running my own badly coded program so that might be the case... sure hope so, memory is such a borring thing to buy.

---

No I didn''t mean that the memory was physically bad. I meant that you were writing to an illegal address in the eyes of the OS/your program, something outside of your programs limits.

Yeah, it''s just my bad coding skills. Ran that memmory test thingie and all was a-ok. Nothing to see here, move along...