BSOD - Memory Management

[Mav451]

Recently I got this BSOD when I was benching my memory with Sisoft Sandra. I have benched my FSB at clocks that are VERY unstable (i.e. 211 with only 1.65vcore--that would immediately fail if tested in 3dmark) and i wouldn't get a bsod.

I mean, I've been running 12.5 x 200 for quite some time at 1.675Vcore, so running 202 x 12 should be VERY easy to handle.

I have only had BSODs occur on 2 occasions:

1) This one (Sisoft benching session)
2) and Doom3 @ 11.5 x 209 FSB [1.675 Vcore] >> well this is pretty obvious a Vcore issue.

Anyway, I got this bsod with these settings:

12 x 202 [1.65 Vcore]
11,3,3,2 [2.8]

(insert random #'s, etc. etc.)
The message was "Memory Management".

I've never had this bsod before. Its almost always been the IRQ_NOT_ALWAYS_OR_EQUAL >> which happened ALOT on my rev1.06 when i was trying to hit 200fsb, and that was usually a "tell" to increase vcore/loosen timings. Those were simple to understand.

But what the heck does memory management mean?

 

[Mav451]

Ok, i think I just answered my own question.

I never actually stress tested my memory at CL2. (my testing was all with my memory at 11,3,3,2.5 or 8,3,3,2.5; but never with cl2)

Apparently Doom3 didn't like it after 15min of play...i guess that answers my question lol.

Back to cas2.5 =(

 

[ryuji]

doom3 seems to crave cas2.. try using divider and see if you get any more preformance.. at cas2 load time is 1/3-1/4 the time and there is almost no hitches changing rooms

<edit>hmm... 512 megs.. doom3 likes a gig also and no dual channel goodness... i wonder if its dual channel cas2 more then cas2 by itself...</edit>

 

[Mav451]

haha dude, my performance is just fine with 512MB and cas 2.5 (in terms of "skipping" or loading--i didn't experience many slowdowns).

As you can already tell from my sig...my video card needs serious work before i even think of concerning myself with the RAM issue.