Greetings!

AS a University Student my PCs arnt the greatest. However my desktop isnt the worst. I have an IBM Thincenter 8810-e96 and its a nice system. I recently loaded it up with 4.5GB DDR2 Ram. a huge boost from the 2gb it had. (2gb + 1gb+1gb+512mb) now when it boots i get the message

Extended Ram Failed at Offset 22

a few MONTHS ago i got the message and reseated the ram and it went away. but *censored* back again and not sure whats wrong as i have had Memtest test the ram and it passed in 2 different machines. Perhaps Its not compatible or something? system boots fine into windows 7 HP

Any ideas?I'd say you will have to remove 1 stick and run it for a while and see if the problem comes back. If the problem comes back, remove a different stick and put the prior removed stick back in. Eventually you should get to a point where the problem is gone. Also just a FYI, you probably already know this, but with mixed memory sizes your only able to get single-channel memory mode if the system supports dual channel. I'd start by removing the 512MB stick and see how it runs on 4GB. And if problem comes back place the 512MB stick back in and remove a 1GB stick and bring it to 3.5GB and see what happens. Another thing to CONSIDER is that you might have a bummed memory slot. I had this before where memtest is fine because the connection is made, but the INTERMITTENT connection breaks for even a fraction of a second and then the system crashes or acts up. I have had to populate 3 of 4 slots before and avoid use of a bummed memory slot such as slots 0, 2, and 3 stuffed with RAM and slot 1 left empty because the prior owner of the system damaged the memory slot by rocking the ram stick out vs using the eject wings  as well as another board that I got for free that was failing memcheck at boot and it looked like someone gouged the board with a screw driver and sliced through 2 traces between the memory slots so that only slots 0 and 1 were good and 2 and 3 were unable to be used, so as long as no memory was stuffed into slots 2 and 3 the system would run completely fine. I ended up scraping the mask off the board around these traces and added a strand of wire soldered to bridge the broken traces and get the other 2 slots back.  Quote from: DaveLembke on May 25, 2015, 09:03:58 AM

I'd say you will have to remove 1 stick and run it for a while and see if the problem comes back. If the problem comes back, remove a different stick and put the prior removed stick back in. Eventually you should get to a point where the problem is gone. Also just a FYI, you probably already know this, but with mixed memory sizes your only able to get single-channel memory mode if the system supports dual channel. I'd start by removing the 512MB stick and see how it runs on 4GB. And if problem comes back place the 512MB stick back in and remove a 1GB stick and bring it to 3.5GB and see what happens. Another thing to consider is that you might have a bummed memory slot. I had this before where memtest is fine because the connection is made, but the intermittent connection breaks for even a fraction of a second and then the system crashes or acts up. I have had to populate 3 of 4 slots before and avoid use of a bummed memory slot such as slots 0, 2, and 3 stuffed with RAM and slot 1 left empty because the prior owner of the system damaged the memory slot by rocking the ram stick out vs using the eject wings  as well as another board that I got for free that was failing memcheck at boot and it looked like someone gouged the board with a screw driver and sliced through 2 traces between the memory slots so that only slots 0 and 1 were good and 2 and 3 were unable to be used, so as long as no memory was stuffed into slots 2 and 3 the system would run completely fine. I ended up scraping the mask off the board around these traces and added a strand of wire soldered to bridge the broken traces and get the other 2 slots back.