deacon: I didn't say that your RAM has anything to do with your drives. But problems with either your RAM or with your hard drives, I think, would be the most likely cause of this error. And I don't see how
Linux has no access on these drives...
- how are you running Linux, then?
Last Edit: Jul 23, 2007 17:40:45 GMT -5 by patrickp
Deacon, your memory access error is much more likely to be a system problem than a pSX one. That's why we want you to test your RAM; it might be an idea to run some sort of diagnostic on your drive, as well. Where is your swap partition and how big is it?
Post by Gamesoul Master on Jul 30, 2007 8:20:22 GMT -5
deacon: Dude... a memory access error could be quite serious, especially if it keeps happening consistantly like it apparently is. You should really take the advice to check things out. It'd be more than worth it if you find something wrong. Problems like that usually tend to start out small, and if that ends up being the case here... you'll eventually end up with a problem you won't be able to fix anymore, possibly at a cost.
Could simply be a case of canary in a coal mine. Just because the problem occurs while running pSX doesn't mean pSX is the cause; it could mean pSX detected problems with the system and exhibited odd symptoms from the problems.
What have RAM with HDD to do....?
Not much, but I seriously doubt you've got 1TB of memory too. Memory != hard drive space. You never really took patrickp's advice to try running MemTest86+ (preferably, overnight) to see if there are any problems. If pSX is complaining about a memory access error, a pretty obvious move for you to make would be to check the integrity of your RAM, and that's exactly what patrickp told you to do by running MemTest86+.
Could simply be a case of canary in a coal mine. Just because the problem occurs while running pSX doesn't mean pSX is the cause; it could mean pSX detected problems with the system and exhibited odd symptoms from the problems. .