News:

Tekforums.net - The improved home of Tekforums! :D

Main Menu

New build BSOD

Started by Binary Shadow, January 27, 2011, 23:36:14 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Binary Shadow

Got my new build running windows 7 pro 64bit, running with no page file at all as it has 8Gb RAM, had 2 blue screens IRQL NOT LESS OR EQUAL

Since then i have enabled the page file to try and get some data about the cause, the BSOD hasnt been seen since.

What do people reckon? dodgy RAM? fault driver?

bit odd it hasnt happened since the page file was turned back on.

Clock'd 0Ne

Sounds like dodgy RAM to me, turning the page file off shouldn't cause those issues unless you are running some program that doesn't particularly appreciate not having a page file.

Turning the page file on probably means you've hardly touched your physical memory, therefore it hasn't tried to address a dodgy area of RAM.

In any case I would memory test the RAM just to be sure it is eliminated as problem.

Binary Shadow

I'll fit an optical drive at the weekend and run memtest then

bear

How does a quad work with the RAM ? does it use  4x2 Gb, if so that could be the reason ?

Binary Shadow

I dont know lol

I set the BIOS to use the memory in 'Ganged mode' if that makes any difference, it also defaulted to 1300mhz speed on the ram but i changed that up to 1600 (the RAM is sold as 1600mhz so thought it would be fine).

Binary Shadow

a quick google seems to suggest that currently all the cores see the RAM as a bucket of memory

If i switch to unganged it should assign each core its own stick of ram

Clock'd 0Ne

It's been ages since I've fiddled with anything like this but the RAM might need lower timings to run at 1600Mhz, you should check it over carefully.

I would have thought this 'ganged mode' is the default/most sensible option? I don't see why anyone would want to split the memory by core rather than pooled, except maybe for specialist applications.

Binary Shadow

Un ganged is the default, looks like the ganged is a phenom feature

I left all the timings at the defaults, would have thought that would be relaxed enough

Shaun

First thing I would look at is if the Ram is getting enough volts to run at 1600.

chaotic_uk

#9
some amd mobo's will not run ram at full speed if all 4 slots are full , had this on my last mobo which would only run at 800mhz in stead of 1066 . as far as i know it is no different with ddr3 ram on some boards , anything over 1333mhz is classed as overclocked from what i have read on ddr3 mobo's

Binary Shadow

#10

IMG_0703 by Adam Woodford, on Flickr


IMG_0704 by Adam Woodford, on Flickr

Now set in unganged mode

This is the memory in use: http://www.ebuyer.com/product/234975

chaotic_uk

try setting it to the next one down so it runs 1333mhz and test it

Binary Shadow

I have manually set the timings to the SPD values, changed to unganged mode and turned the page file off, still at 1600mhz.

Running ok so far.