My Memtest86 (v4.20) results

RAM stands for "Random Access Memory". All memory since computer came about have been called RAM.

Check out this link.
Random-access memory - Wikipedia, the free encyclopedia

DeaconFrost said:

That's very possible, even likely. Bad memory is definitely one thing that can cause a BSoD.

I'm very happy to see this post. Btw, does it matter what type of BSoD it is? Memory_Management is probably the most showing BSoD I've been experiencing. But also a few others. Still, I think It's pretty random what kind of BSoD my computer spits out, It would still be memory.

Gave you a reputation for your kindness news!

In order to properly help figure out what's wrong with your RAM you need to provide "full" systems specs. Specifically the motherboards's make and model, the RAM's manufacturer and model number of the RAM.

The reason for this is that certain RAM requires certain voltages that the board my not be "automatically" providing. Therefore this may require setting manually setting the RAM's specs.

Example my Corsair Dominator TR3X6G1600C8D 1600MHz RAM requires a voltage of 1.65volts. If I let my Gigabyte GA-X58A-UD5 motherboard set it "Automatically" it will set the RAM (to 1.5volts) below it's required voltage of 1.65volts.... and it will most likely fail memtest.

My two cents.

FredeGail said:

Still, I think It's pretty random what kind of BSoD my computer spits out, It would still be memory.

Thank you for the Rep! To answer your question, in my experience, random, changing BSoDs have been a clue that memory may be bad. If I am troubleshooting a system with the same BSoD, I can usually figure that out. If they keep changing, my very next step is to run Memtest. Then, if I see failures, I move on the the testing each stick and each slot process.

DeaconFrost said:

FredeGail said:

Still, I think It's pretty random what kind of BSoD my computer spits out, It would still be memory.

Thank you for the Rep! To answer your question, in my experience, random, changing BSoDs have been a clue that memory may be bad. If I am troubleshooting a system with the same BSoD, I can usually figure that out. If they keep changing, my very next step is to run Memtest. Then, if I see failures, I move on the the testing each stick and each slot process.

Yeah, MemTests is totally the best place to start off troubleshooting BSoD's.

If I get those new RAM, and my slots are aight. You think I'm going to be fine? The rest of my hardware is cool.

Considering the amount of errors you saw in Memtest, and the Kingston memory being compatible, I would think you'd be good to go.

DeaconFrost said:

Considering the amount of errors you saw in Memtest, and the Kingston memory being compatible, I would think you'd be good to go.

Awesome, totally awesome! I'll celebrate this with something

Britton30 said:

sygnus21 said:

In order to properly help figure out what's wrong with your RAM you need to provide "full" systems specs. Specifically the motherboards's make and model, the RAM's manufacturer and model number of the RAM.

The reason for this is that certain RAM requires certain voltages that the board my not be "automatically" providing. Therefore this may require setting manually setting the RAM's specs.

Example my Corsair Dominator TR3X6G1600C8D 1600MHz RAM requires a voltage of 1.65volts. If I let my Gigabyte GA-X58A-UD5 motherboard set it "Automatically" it will set the RAM (to 1.5volts) below it's required voltage of 1.65volts.... and it will most likely fail memtest.

My two cents.

Hi FredeGail, I;m weighing it to subsribe to this very interesting post.
In my new build I also got a few BSOD's, sometimes not if I changed the RAM aroun. I am using 4 sticks of GSkill RAM. As sygnus21 says, check your voltage setting, it turned out all my RAM sticks were goo but needed a voltage tweak.

Hey mate!
Thanks for your really interesting post. I think I have that stuff covered, my older brother last weak took a look at that. The first picture you're seeing here is a little information about the RAM I'm using taking from my MemTest before I had the errors.
1.
=================

2.
=================

3.
==================


You might take a look if I need to change something.