Holy crap - I woke up after going to bed, and found my computer... running! And crunching!
Printable View
Holy crap - I woke up after going to bed, and found my computer... running! And crunching!
Did you mess with it again or did it just "fix" itself?
Haven't touched it again. After the computer has run without erroring for about 18 hours now, I'm so giddy I'm afraid to touch anything. I might get back to this tonight or tomorrow, depending on how things go.
But this clearly seems to have been some RAM timing issue. No clue how or why it happened.
If it is working then, as my doctor keeps telling me............DONT PLAY WITH IT!
The Silver Hammer passed all tests except one, and the resulting error is the name of the thread. It ran on MW for a day and a half without erroring out - that made me happy. I had backed the RAM speed down to 1066, with timings of 7, 7, 7, 19. When I put it on Collatz, crash. Put RAM back to stock settings. Crash.
So now I need help (again) - what should I try next? I'm a little scared of changing things willy-nilly in BIOS, and need some suggestions of where to go...
Again, I'm rocking this RAM. Current timings and SPD page from CPU-Z below.
http://i1194.photobucket.com/albums/.../SH-Memory.png
http://i1194.photobucket.com/albums/...n82/SH-SPD.jpg
This is the last thing I can think of as far as memory goes. Manually set your Command Rate down to 2T.
Done. Didn't fix it. Bah.Quote:
Originally Posted by joker
So is there a way to adjust the GPU RAM settings, aside from the RAM clock? I ask because I can get my machine stable on MW, but not on Collatz. MW loads heavier on the GPU than Collatz, so I don't think load is the issue. But since Collatz uses the GPU RAM so differently than the other ATI projects, is there some setting I should adjust there?
Note again, that I've got everything running at stock settings...
Errrr..... Hmmmmmmm, I have an idea.
You have 2x sticks of RAM. Pull one out and run Collatz. Your system will probably run a little slower. After the test, pass or fail, replace the installed stick with the one you pulled. Test again.
Reasoning: It is rare to have all the RAM sticks go bad. And since it is fairly easy and painless to install/remove RAM, this will be a fast way of physically testing for bad RAM. So one of the sticks should be able to run Collatz. That would be the "Good Stick".
The "Bad Stick" is therefore possessed. Call for a Priest and have the silicon exorcised. Then burn it at the stake just to be sure.......
And punch a few more children.......
Quote:
Originally Posted by joker
You are also running a little over your XMP values. Your ram is running at 1339.2. Try adjusting your ram ratio down in the BIOS. I don't have a Gigabyte MB. Maybe Joker can walk you through it.
Oh yeah then kick the dog.