Unsolved
This post is more than 5 years old
127 Posts
0
6332
May 19th, 2008 19:00
memory errors
Last night, while playing World of Warcraft, I recieved a sudden game shutdown, with an error stating that "somesuch" memory block: could not be accessed. This caused a corruption that's going to require me to reinstall the game.
I ran 7 passes of memtest, and that turned up the same two blocks each time. I ran the Windows Memory test and it told me all was fine. I've experienced inexplicable issues with this machine; random bluescreens, various shutdowns, etc. I've never had anything specific enough to pinpoint the memory.
My question is: short of swapping in one board at a time, is there any way to pinpoint which memory board is failed? With the way the machine is set up, it's a huge pain to open it, swap a board then hook it all up to test over and over. I've already spent far too much time inside this machine.
As always, I really appreciate the input I get on these message boards. Thanks in advance!


Boyd B
552 Posts
0
May 20th, 2008 16:00
Raelf
127 Posts
0
May 21st, 2008 01:00
Thank you, Boyd!
Yes, it is as I feared... a total reinstall. In order to use my warrantee, Dell is requiring that I run their memory utility to test the boards and the sockets... good practice, just annoying. Upside is, Dell will send me 4 new boards if any fail... downside is, I don't trust them. I am going to have to swap in one at a time, and test each of the new ones.
I'll post back when it's complete. Thanks again for the input!
Raelf
127 Posts
0
May 30th, 2008 12:00
Just a final update for those who responded to this post, and anyone else experiencing intermittent, or a single, memory error(s).
I called Dell and they insist that if the dell diagnostic doesn't show it, it didn't happen. So I ran the Dell tool, and of course, no error. For laughs, I re-ran memtest... 10 passes overnight, and no errors!
The only thing I can figure is heat. The error did occur after a 6+ hour gaming session in a rather graphics intense encounter. The 720 H2C leaves the memory in a small passively cooled area with lots of unruly cables and no direct air flow. If not heat, an errant driver that might have locked down a cell or two on the memory (yeah, it's a stretch)...
Given that I wanted to do it anyhow, I re-routed all the cables I could and tiewrapped them back, reseated the memory, tuned the OC back to factory for CPU and memory, zero'd the drives with DBAN, repartitioned with Acronis Disk Director, reloaded Vista 64-bit and SP1, reloaded all drivers (including the Creative drivers from heck), left the PCCillin until afer I loaded all apps, and re-ran memtest. Clean. Probably extreme, but I know my hardware is ok, or I am as sure of it as I can be. My partitions are pretty now, too! :smileyvery-happy:
Before I re-up the OC, I am installing the corsair cooling fans over the memory. I just do not trust the air-flow in the memory area, even though I already installed an exhaust fan. This design begs for another 120MM fan behind the front drive slots blowing directly on the memory and rear drive slots, but as it would have a slightly obstructed intake and outflow, it would probably roar and need to be MB controlled... and I've been told there is no port on the MB to add a fan sync'd to the lower one, so the corsair cooler is my last option.
As always, comments are welcome and encouraged. If you read this far, I appreciate it!
Boyd B
552 Posts
0
May 30th, 2008 13:00