8GB of RAM causing BSoD

I have 4 2GB sticks of DDR2 800 RAM. I noticed that I have been getting a lot of BSoDs after installing them. I never got a BSoD on this computer before except for one time, but it was something that I had caused and it was completely hardware unrelated. Anyway, it seems to only happen when I am in a game. It doesn't matter how resource heavy the game is. I have gotten a BSoD in Warhammer Online, The Sims 2, Spore, and StepMania. I haven't really bothered to check any other games, but four should be enough to prove that it's not a buggy game that is causing the BSoDs. Also, the error message is different every time.

I ran the program Memtest86 three times and not once did it come up with an error. I did some Googling and found that increasing the RAM voltage to about 2.2V could be the solution, but I don't want to do that. I am extremely paranoid when it comes to frying electronics, and increasing the voltage is something I am really uneasy about. Before I do anything, I wanted to make sure this was a possible and relatively safe solution. Also, if there is anything else that might be able to help, please let me know.

Few things you can do:

- Try setting all memory timings to the slowest setting possible in the BIOS (or just leave them at AUTO if you don't know what you're doing )

- Since you have 2 memory modules, try them 1 by 1 (aka remove 1 - MAKE SURE YOUR PC IS DISCONNECTED FROM ANY POWER SOURCE WHEN YOU REMOVER THE MODULES). Try to game with 1 module, and then switch them. Try to see if if maybe one module is causing the problems...

- Overvolt the modules, like you said. Overvolting can't really damage your modules, because most memory can take 2.5volt easy. The only problem is HEAT. Make sure you keep them below 70~80 degrees Celcius. If the modules have metal heat spreaders on them, then this shouldn't be a real problem.

Also, check in your BIOS if the memory voltage is STABLE and doesn't go up and town too much (more then +10% variation).

Also, is your pc connected to a GROUNDED plug connection in the wall? Random static can also create memory errors...

The timings are on Auto. I have no idea how to overclock memory so I have never messed with them.

I have four sticks actually. But the sticks themselves are not the problem. I ran Memtest86 three times and there were no errors.

How exactly do I increase the voltage? I went into the BIOS and the setting was grayed out. Is there something special I must do, or is it just the limitations of my motherboard?

The voltage seems to be stable, so I don't think that is the problem.

My PC is connected to ground. I wouldn't be using it if it wasn't.


Anyway, I took out 2 of the 4 sticks to see if going back down to 4GB would fix the problem. So far Warhammer has not given me a BSoD, but I've gone a full day without crashing before so it is still too soon to tell.

You do use a 64 OS, right?

With 32 OS, the 4 last GB of ram won't give you anything (The OS cannot use it from what I know). It may be that when your computer is trying to attach memory to those last 4 GB, a BSoD occurs, though I don't really know.

Edit: Wow, lol, you shouldn't get BSoD-ed by StepMania though.

Yes I have a 64-bit OS.

Yeah, getting a BSoD in StepMania was really the last straw for me.


Edit: Well, I played Warhammer all day today and not once did I crash. I guess I will just have to settle for 4GB of RAM until 64-bit technology gets all the bugs worked out of it.

it would help if you provide information on what kind of BSOD you get. also make sure your motherboard supports over 8gigs of ram and if any recent bios for the motherboard came out.

Well, I think I found a possible solution, though I can't confirm it because I don't bother to get 8 GB ram on a x32 OS:

make boot.ini writeable (able to change it)
open boot.ini in notepad or some text editor, you'll get up something like this:

Code:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows Vista Home Edition" /noexecute=optin /fastdetect /usepmtimer

Whatever written does not really matter, but just change the last line by adding in /PAE in it (Physical Address Extension) so it's like this:

Code:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows Vista Home Edition" /noexecute=optin /fastdetect /usepmtimer /PAE

(Uh, please do not blame me if the computer blows up. It won't do it, most likely, but meh)

Is your CPU overclocked? Having more modules of RAM can make an OC unstable

Did the problem start when you installed the 8GB of RAM? Or was it before?

8GB is more than enough for even the most intensive personal computer needs; I'd say that if the problem happened separately from you installing the RAM, it has nothing to do with your RAM.

What's the stop error message? :f6: could be a number of things going on.. I never started getting BSODs with MS till my drivers started screwing up & then the BSODs started getting more frequent, then found out my RAM was failing..

Well, I think I found a possible solution, though I can't confirm it because I don't bother to get 8 GB ram on a x32 OS:

Whatever written does not really matter, but just change the last line by adding in /PAE in it (Physical Address Extension) so it's like this:

Non Server Windows Systems do support the pae but it does not work as expected. It does nothing as windows imposes a limit of 4gb maximum ram so you buy the 64bit version (stupid microsoft marketing)

Also the OP is using a 64bit OS, there is no PAE there

Non Server Windows Systems do support the pae but it does not work as expected. It does nothing as windows imposes a limit of 4gb maximum ram so you buy the 64bit version (stupid microsoft marketing)

Also the OP is using a 64bit OS, there is no PAE there

Oh, I thought PAE was available in x64 as well. (And, it does in fact do something on x32. )

Does your motherboard support 8GB of RAM?

Oh, I thought PAE was available in x64 as well. (And, it does in fact do something on x32. )

Sure it does something on windows 2003 advanced server datacenter edition but not on xp or vista
(In fact it does something but nothing useful - you can't have 4gig ram with it enabled)

Non Server Windows Systems do support the pae but it does not work as expected. It does nothing as windows imposes a limit of 4gb maximum ram so you buy the 64bit version (stupid microsoft marketing)

Seriously, read up on 32 bit.
32 bit can't handle more than 4gb. It's just a limitation of 32bit.
It's not defined by Windows.

Anyway, I need some more information on those BSOD's

Sure it does something on windows 2003 advanced server datacenter edition but not on xp or vista
(In fact it does something but nothing useful - you can't have 4gig ram with it enabled)

For people unable to get exactly 4 GB RAM (like, they get 3496 or something), aren't they able to drag it up to 4 GB?

One fact though, is that my comp starts applications faster, and it loads faster as well, from what I've seen.

Edit: While addressing heavy programs requiring a lot of RAM.

Seriously, read up on 32 bit.
32 bit can't handle more than 4gb. It's just a limitation of 32bit.
It's not defined by Windows.

Google PAE (Physical Adress Extension) plawks. Server 2003 Datacenter Edition can handle 128gig on 32bit (and that's a marketing restriction again) 256gig should be possible. Linux can too (but I hear it's a little buggy)
Why do you feel the need to correct people when you have no idea what they are talking about?

For people unable to get exactly 4 GB RAM (like, they get 3496 or something), aren't they able to drag it up to 4 GB?

In theory they could but it's locked down - so no.