I recently assembled a pc and I'm using 4 sticks of 256 RDRAM PC800 (Kingston). Thing is when I preview my rendered Targa files in fcheck. An application error happens something like "memory write failure". I noticed that the memory usage rockets to its highest point before every error. This is the first time that this has happened to me after a month of rendering other projects. Is there a diagnostic tool I can use to check the RD sticks? Any kind of help will be appreciated! Thanks
Do a google search for sandra memory tester. There is also an app called membench. Both are free and will run a bunch of tests on your ram.
Also since you have the 4 ram modules, feel free to take two out and attempt to render and see if you get the error message. Swap modules around accordingly and see if you find the right mix, that could be your best bet for finding the problem module. Make sense? If not lemme know and i will take another stab at explaining it.
Best of luck.
Ok I'll try that. Thanks man! It might take some time though. I'm gonna back up the files then maybe try to reformat.
Yeh keep us posted. Also email me if you like and i can try to provide some additional assistance.
Good luck (again) =D
Pieces,
john
Just curious. What is the effect of running fcheck on the the memory? Ive tried playing other scenes with only 120 frames and it doesn't seem to have any noticeable effect on the memory usage. I've tried playing the same 1800 frames shrinked 1:2 and it doesn't seem to have any problem.
I just did a reformat of the whole system. The fcheck program just hangs, no memory error pops up. I brought it back to the store but they are claiming that it is just a program error.
I tried this at my school and it lasted and previewed 2000 frames!
What should I do?
software memory testers are kind of iffy at best from what i have found. I usually do the swap ram and test method. For you, remove 2 pieces at a time. Test your scene with fcheck and see if the problem crops up. Eventually with the swapping you should be able to test all of your ram, essentially down to a single piece of ram to see if it reveals which one(s) are bad or slightly _ucked up.
Also you might want to send your file your using to test and have a friend render it on their box to make sure they can render it okay. It is a long shot but in the past i have trouble shooted what i thought were memory problems only to realize later that i was attempting to work with a bad or damaged file that consistently produced "memory like" errors on other "known good" computers.
Food for thought...