Sign in with
Sign up | Sign in
Your question
Solved

Memory Management Error and DRAM bios message

Last response: in Memory
Share
November 22, 2013 12:20:30 PM

Hi, new here but pretty familiar with computers. However, last night was the first time I transfered a whole computer to a new case, and I think I may have damaged something.

Here are my specs:

AMD Phenom/Athlon? II
8GB DDR3 1333Mhz Dual Channel (one stock 4GB stick and one Kingston ValueRAM)
2GB GTX 760 EVGA brand Video card (this is newly installed, however I have run this card in my system before without incident, except for overheating which is why it was removed till I got the new case)
750W Corsair power supply, also new, also previousl installed and then removed for the same reason as the GTX 760

Last night, after painstakingly remember my Intro to Computer Tech class, I installed all the parts in my new case and started the computer. However, once windows started to boot it eventually froze, and I had to restart the computer. Same problem with Ubuntu ( I have a dual boot system), but then it also gave me an error along the lines of "DRAM error, reducing (size? speed?)" which I tried to read as best as able.
I had the this problem with a completely different system before, when I had a mix of incompatible RAM. Switching the ram to the right kind for all slots fixed the issue, but since this is the same mobo and ram and almost everything else, I'm not sure where the trouble is.
I have not yet run memtest, but I will do that as soon as I am home. But I'm also wondering: could this be a mobo or CPU issue? When installing the mobo I was a bit rough with the ram slots (few places to get grip on that thing), and I initially forgot about how to hook up the F Panel correctly. Could I have damaged these parts?
Also just to note, my bios no longer does the long boot. It does quick boot, which I set to long boot. Could that be indicative of some kind of setting changes? Perhaps from being out of power for too long or something?

Thanks in advance for ANY help you guys can provide me.
a c 131 } Memory
November 22, 2013 12:39:25 PM

I would try the ram sticks separately, and reseat the ram, if you never pulled them, put them back in after the move, one of them may have wiggled loose, or gotten dust in the slot, or on a contact. This is most likely a mismatched ram issue. Try raising dram voltage to 1.55v and see if that helps if both sticks seem to boot by themselves.
m
0
l
November 22, 2013 12:39:34 PM

Check Device manager to ensure there are any problems
m
0
l
Related resources
November 22, 2013 12:42:40 PM

Well, it gives me a BSOD if it boots up. And after its failed boot enough, it doesn't start---or at least, my monitor doesn't say anything.

After I had this issue initially, I re-seeded the ram and it booted up, then I got the memory management BSOD for the first time.

RAM is solid, never removed it but I may be damaged the connectors, its hard to tell, they looked just fine.
m
0
l
November 22, 2013 12:44:45 PM

Supahos said:
I would try the ram sticks separately, and reseat the ram, if you never pulled them, put them back in after the move, one of them may have wiggled loose, or gotten dust in the slot, or on a contact. This is most likely a mismatched ram issue. Try raising dram voltage to 1.55v and see if that helps if both sticks seem to boot by themselves.


Its the same RAM as before, although yes they mismatched. Could this suddenly be a problem? I'm thinking I damaged something given that everything was fine till I moved it to the new case.

I will check that as well to see if it helps though. I think though that my motherboard says it has a max of 1.5v for memory. I will look in the BIOS later.
m
0
l
November 22, 2013 12:44:56 PM

Have you touched the pins directly with your fingers?
If you have, you may have damaged the component with your static electricity
m
0
l
a c 131 } Memory
November 22, 2013 12:45:30 PM

Try each stick by itself, if they both work, we can try to get some settings that work with them now... If you have any used compressed air to blow out the Dram slots, and use something like a makeup sponge, or if you don't have one (that was a Trademan suggestion) try a soft tshirt on the contacts of the memory, make sure the shirt is 100% cotton so it won't carry static.
m
0
l
November 22, 2013 12:49:01 PM

Supahos said:
Try each stick by itself, if they both work, we can try to get some settings that work with them now... If you have any used compressed air to blow out the Dram slots, and use something like a makeup sponge, or if you don't have one (that was a Trademan suggestion) try a soft tshirt on the contacts of the memory, make sure the shirt is 100% cotton so it won't carry static.


Ok, I'll try them seperately.

If one of them is bad, I just bought a new kit and having it shipped here priority, by tomorrow I will have it.

So if it turns out to be bad mem that will be easy...it sounds like a RAM issue though, correct?
m
0
l
a c 131 } Memory
November 22, 2013 12:51:46 PM

Yes that would be my guess, however all ram issues can have 2 common and 1 other cause (bad stick, bad slot, possible bad memory controller on cpu/motherboard) I would see if one of the sticks will work stable, and just use it till the new kit arrives since you have one coming.
m
0
l
a b } Memory
November 22, 2013 12:53:26 PM

what works great for cleaning the contact on the ram is a pencil eraser.
m
0
l
November 22, 2013 12:54:42 PM

Supahos said:
Yes that would be my guess, however all ram issues can have 2 common and 1 other cause (bad stick, bad slot, possible bad memory controller on cpu/motherboard) I would see if one of the sticks will work stable, and just use it till the new kit arrives since you have one coming.


Ok, would it be better to run a mem test first, then see if any errors are returned?

I think that Ubuntu has a memory tester that I can load from GRUB before even loading the OS. I will try that, record it, then try each stick, and see what the results are.

I'll report back after doing these.
m
0
l
a c 131 } Memory
November 22, 2013 12:55:33 PM

aldan said:
what works great for cleaning the contact on the ram is a pencil eraser.


Unless you rub too hard and take out one of the contacts, or get eraser parts on the pcb, or use a dirty eraser and put graphite from a pencil on the memory.
m
0
l
a b } Memory
November 22, 2013 1:38:26 PM

you are right,should have said new eraser.
m
0
l
November 23, 2013 12:57:44 AM

Ok, long story short, it seems to be fixed now.

Basicaly, I ran memtest...no errors. I attempted to launch with the sticks individually in different slots. Same error. Also, i was getting another error---CMOS low battery and what not. Quick google turned up some results, and eventually i realized that i had removed and discarded the jumper for the CMOS (silly me, thought it was just a stupid green piece of plastic in my way). Found it, replaced it, restarted, windows crash. No RAM errors on bootup though, but still memory management error in Windows.

But, Ubuntu runs perfectly fine. No trouble. So, restarted, safe mode in windows, did system restore (thank god for system restore), rebooted. Solved

Now works 100% as far as I can tell, no errors and date and time are correct. Still testing it, I will check back in a day or so to let you know.


Thanks again for your help guys, especially Supahos. Really appreciate the help!
m
0
l

Best solution

a c 131 } Memory
November 25, 2013 8:52:42 AM

Glad to hear you got up and running, I think what likely happened is that jumper missing made a system file in windows become corrupt, once you fixed the issue Linux was able to run, but windows still had a corrupt file from the memory failures. you fixed that and everything should be okay going forward.

If you think you have it all figured out feel free to close the thread.
Share
November 27, 2013 6:41:20 AM

That sounds like the problem. I have been up and running since with almost no trouble; had a hiccup with my computer not completely booting up once but that was the last thing and it happened on that same day. Since, I seem to be good. Thanks again for your help!
m
0
l
!