• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

MAJOR memory problem

kcbass

Golden Member
I'm running a gigabyte GA-7VRXP motherboard with a 512 PC2700 64x4 2.5 latency memory module. I am trying to add a second module which is identical to the first. When I installed it into the second memory slot, I received a windows blue screen error which stated that my BIOS was not ACPI compatible, and would not allow me to log into windows. My BIOS version is AMI BIOS GA-7VRXP F12, which is the latest for my motherboard. When I tried the second memory module by itself, twenty percent of the time, the system freezes halfway through BIOS bootup, and never gets to the windows 2000 load screen. The other eighty percent of the time, the BIOS gives me the bad memory beep...wo what's the deal? Do I need to RMA this module? Is there anything I should try that I haven't yet? I can't try the meory in another machine because I don't have one
 
Definately try the RAM test. And I know this might sounds stupid but make sure you reseat it nice and good and check for any damage to the module that you could see physically. Also try switching it to a different mem bank. That can sometimes help.
 
I'm not overclocked, and now I've checked the RAM physically, AND I've tried every bank. Where do I find this memtest? Can I find it on download.com? Also, can I use the memtest since I can't even get through the BIOS with the memory?
 
The part that bothers me most is the fact that the BIOS even begins to boot up some of the time...I've RMA'd memory before that wouldn't even get the BIOS to beep, it was so far gone, and when the company receives it, it tests as ok. I'm concerned that my motherboard won't accept this combination of RAM, but it's compatible up to 3 gigs at 2700...
 
If you can get through the BIOS routine with both modules installed you can use memtest86 - it runs from a DOS boot floppy.
Otherwise don't know how you can use this unless you can put the memory in a friends comp & get it to boot, but here's where you can download memtest86 .
 
Originally posted by: cobo
Don't know how you can use this unless you can put the memory in a friends comp & get it to boot, but here's where you can download <a class=ftalternatingbarlinklarge href="http://www.memtest86.com/" target=blank>memtest86</A> .

Memtest has its own loader and it takes very little memory, so if even a small part of the lower address RAM is good, it will likely still load. There's both a floppy and CD-ROM (ISO) boot version. This sounds like bad RAM to me though.

-cap
 
Yeah...that's pretty much what I had figured from the start, I just wanted to be sure. Unfortunately, I can only get halfway through the BIOS boot, so the system never has the chance to search for a boot record from either the floppy or the cdrom...
 

this may sound a little off the wall, but have you tried seating then removing your memory several times? I have an abit kr7a-133R board that when new, refused to post 95% of the time no matter which stick (3) of crucial 512mbDDR I used or which socket I was in (4 sockets). The other 5% of the time I would lockup after posting.

After searching through several mb forums I found someone who had had a similar problem. The solution was to forcefully seat and remove a module from each socket 10 to 15 times. After doing this the system happily posts and boots with 1.5GB in three sockets. Wierd since the socket contacts were gold plated as was the memory...😕
 
I'd give it up for dead.

If you REALLY want to find out, try a different computer, if you know someone else who's computer you can plug it into. I'd simply call and RMA it though, myself. I'm assuming this is generic RAM, right?
 
I did RMA it, and they called me to let me know it worked just fine. What we determined was that the motherboard was not compatible with the brand of chips on the memory stick. They shipped me a different brand of equivalent memory, and everything works just fine. Thanks for the help
 
Back
Top