Solved Memory RAM advice

[graphomet]

Hi Forum.

I'd like to add some more memory to my PC, I got my PC upgraded 3 years ago, and the Tech guy left in my PC my old RAM and I spotted the new ones called Mushkin silverline. So My main question are ram sticks compatible with other brands, or is it better to have the same brand used? for example I saw my Mushkin silverline are the budget price ones, but If I can go for the Mushkin redline, which is considered super duper, would it cause issues having a more advanced memory stick as opposed to the ones with less performance?

Thank you.

 

[Boozad]

It's always best to run RAM in kits, I certainly wouldn't pair new with your old RAM. What are your system specs and the exact specs of the new RAM? We wouldn't be able to advise on compatibility before we knew all of that.

 

[graphomet]

Hi, Here are some of my pc specks... I know they are old.

Its been like 2 years now Im getting the BSOD.. its been one day since Im taking each memory out and seeing if it crashes, so i can see which ram stick is faulty.

I have installed on my PC 2 of each of these RAM sticks. maybe they are conflicting with each other and its causing this problem Im assuming.

Also what would be the best solution if I am to buy new ram sticks. I use Adobe products, for video editing and design. Ill be getting a new machine done up by the end of the year. So whats the best temporally low cost ram just to be safe for now. I can spend up to $300 for now.

 

[Boozad]

Right, first of all can you fill in your system specs by following the link in my signature, that's what's needed. Secondly I wouldn't be running that RAM together, while it may not be the cause of the BSODs it's certainly could be causing issues.

Fill in your specs as above first, then post up your BSOD logs following http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

To test your RAM follow the instructions below.

Download and run MemTest86+ to test your RAM. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Note

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

 

[graphomet]

I actually laughed for a sec, when you said post your BSOD! I know them off by heart now. These are the messages I get when my PC crashes.

PFN List Corrupt
Bad pool header in non page area
IRQL_NOT_LESS_EQUAL
PAGE_FAULT_IN_NONPAGED_AREA

These are the ones I remember occurring once a day.

 

[AddRAM]

Please post a link to your motherboard, we need to know what you have so we can advise you.

 

[GokAy]

The joke is on you

You are supposed to run the diagnostic tool provided in http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html and attach what is being asked. Read the instructions. Posting that message like that won't help anyone.

 

[graphomet]

Here are the specks, Ill do the BSOD instruction now.

 

[graphomet]

dm log collector.

Here is the zip file. I did the dm log collector.

 

[GokAy]

If you ask me, you should remove the old RAMs, then load BIOS defaults and check whether RAM settings are correct (adjust if not). Then test for a while (until you get BSODs or feel confident they are alright).
And only then, add your old RAMs into the mix. If BSOD, then make sure you run them at the slower timings (whichever set is slower) or add some voltage (may not work). At the end it is possible they won't work together.

 

[graphomet]

Ill remove the old rams, and leave the 2 new ones in. The old rams are close to the processor, so when I take them out of the slots, should I also place the new ones in their position or it doesn't matter having ram sticks further away from the possessor?

 

[GokAy]

You should consult your motherboard manual for slot selection.

 

[Boozad]

One last time:

Right, first of all can you fill in your system specs by following the link in my signature

I'm not going to be jumping backwards and forwards and sifting through screenshots to keep finding your components, that's what the system specs area is there for as it follows your every post and we can find the information in one click.

Now, all of your dumps (including 0x3B, 0x50, 0x24, 0xA and 0x4E) are pointing towards memory corruption so it's imperative to remove the old RAM, configure the two sticks of new RAM according to the instructions in your motherboard manual as already pointed out and run MemTest86+ as posted in post #4

 

[Layback Bear]

These good folks trying to help need your help.

Here are two Tutorials that will help you post your (My System Specs) as they should be.
By Brink:
http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

By Kari:
http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html

Please read and comply to Boozad's request for System Specs.

 

[graphomet]

Hi forum.

I have filled out my system specs. I hope its sufficient info about my PC system.

Today I removed the old Ram sticks, and placed the two new ones in their position. Im following up on how the system goes. Hoping it was the old Rams causing the BSOD.

 

[Boozad]

Thank you for updating your specs. Have you run MemTest86+ as advised in post #4?

 

[graphomet]

Hi Boozad.

This time Ill put in all 4 ram sticks, unfortunately even now with the 2 new ram sticks I got a BSOD again. This time I got a new error: Reference by pointer.

Ive never seen this error message before.

So Ill insert all 4 RAM sticks and try the MemTest86+

 

[Boozad]

Leave the old RAM out. There's a problem somewhere and putting the old RAM back in isn't helping identify what the problem is. Run the tool linked in the BSOD Posting Instructions again and upload the new lots so I can see the latest dump file.

 

[GokAy]

Load defaults in BIOS (first menu or exit menu), old settings can be interfering. Then check if Auto timings are correct.

 

[graphomet]

Here is the new crash Zip.

I'm now starting to think it could be my graphics card, causing the issue.