Resolved RAM not totally recognized.

I thought I would Post this recent problem as it may help others.
I purchased Vista Business OS with Word Professional 2007 thrown in and installed them to a HD in my Comp.

After getting everything setup and running (SP1 & SP2) I had an "Unknown Device" show up in Device Manager.
Vista kept looking for Drivers for this "device" and after a lot of blood and tears, I've fixed it.
I also noted that my RAM (2Gigs) was only showing 1Gig in System display.
This had me puzzled, so I swapped cables back to my Windows XP HDD, and checked RAM and it was 1Gig as well.
I then did a "PeteC" - I pulled the RAM and cleaned all contacts and slots and re-installed the RAM (2x512Mb & 1x1Gb) and fired up and there is my 2Gigs again.
I went into BIOS and disabled "MIDIPORT" as Vista had suggested I get drivers from the manufacturer for this "Unknown Device ".
I saved and Booted and all is sweet - no question marks in Device Manager and all my RAM is working.
I swapped back the cables for the Vista HDD and it's all go again.
So far so good with Vista - I thought that I would give this OS a go as I was almost ready to condemn it from all users comments.
As I say - so far so good - time will tell. I hope I haven't bored you with this Post, but it might help to remember to remove and clean RAM contacts now and then. cheers Neil.

 

I never have used anything but a clean pencil eraser to clean contacts in my 30 years with the phone company. Just one or two rubs and not from one end to the other, but up and down. This is the way that Bell Labs has run many test and this proved to be the best thing to do.

 

A pencil eraser has also been my greatest [secret] tool when it comes to RAM. A good rub down clears most of the problems.

 

Thanks for the input guys as I regularly clean/blow out the comps, dirty connections in the RAM wasn't my first thought. Best way to do it is with the eraser as you both explained. Cheers Neil.

 

have your tried running memtest?
I would also suggest re-seating the RAM

 

Neil fixed the issue himself JD, he was only posting his experience for information to others.

@Neil, I know there was no issue to resolve but perhaps you should mark this thread as such anyway.

 

Wilco, wildfire. Neil.