Windows 10 (64 bit) doesn't detect new memory installed

[roseypeach]

I offered to install memory in a friends computer, he has the HP Omni All in one desktop model 120-1333w. There was no issue, the memory popped right in, and the machine started up as expected. It seemed to be a bit faster however Windows didn't detect the upgrade. I checked his version of Windows and decided it was due to the OS being 32 bit, so I upgraded his Windows 10 to 64 bit but it still doesn't recognize the memory I installed.

The machine is running even better, the 64 bit version of Windows 10 helped quite a bit but the new memory is still 'unreported' by Windows.

I'm stumped. Does anyone have any ideas what else I can try? I've never encountered this problem before. I know the memory is appropriate (I double checked/triple checked the specifications) the memory fits perfectly but the machine only 'sees' the old module.

 

[Cycloid Torus]

Consider trying http://www.dell.com/support/home/us/en/19/product-support/product/inspiron-17r-5720/diagnose

Many reasons could be 'overlooked' - especially if new RAM is not the same as the old RAM (some memory slots define timing of RAM for all slots.

Read over the information about upgrading RAM and adding RAM in the user's manual (very likely you can download from DELL support.

 

[roseypeach]

That is information for my computer, the one I am working on is a HP Omni 120-1333w All in one desktop pc. There is no user support for his system on the HP website and the memory upgrade information is very limited. It's an older model that isn't supported anymore.

 

[Cycloid Torus]

Oh, this system......https://support.hp.com/lv-en/product/hp-omni-120-1300-desktop-pc-series/5296555/manuals

I have had some success determining what is compatible by going to Crucial and/or Kingston websites.

 

[roseypeach]

Actually I did, the Crucial scan pointed this particular SODIMM out that I purchased through Amazon Prime. That's why I was dumbfounded as to why Windows didn't detect it.

The packing information for this model shows these shipped with either Memory - SODIMM, 4GB PC3-10600 CL9 or PC3-12800 as the appropriate memory for his system. He has the Omni 120-1333w All in one desktop. I cannot find 200 pin DDR3 PC3 10600 CL9 so I ran Speccy and discovered he has this memory installed: Micron 4GB PC3-12800 DDR3 1600MHz unbuffered non-ECC MT16KTF51264HZ-1G6M1 204 pin.

That means the FAQ (https://support.hp.com/lt-en/document/c03319083) on the Omni 120-1333w has a major typo. This memory I just linked for you is 204 pin (Speccy identified that specific module) but the FAQ on the model says it takes 200 pin and nothing higher than 10600.

I purchased and installed a Timetec Hynix IC 4GB DDR3 1600MHz PC3-12800 Non ECC Unbuffered 1.35V CL11 1Rx8 Single Rank 204 Pin. Yet Windows 10 (64 bit) will not recognize it. I am stumped.

Please let me know if there is anything I'm overlooking or haven't thought of, I could use all the help I can get on this.

Thanks a bunch

 

[Cycloid Torus]

Mobo maker is actual AOC - a monitor maker - typos seem more likely.

Micron 4GB PC3-12800 DDR3 1600MHz unbuffered non-ECC MT16KTF51264HZ-1G6M1 204 pin is a 1.5v part - so you may be overvolting the Timetec Hynix IC 4GB DDR3 1600MHz PC3-12800 Non ECC Unbuffered 1.35V CL11 1Rx8 Single Rank 204 Pin which is a 1.35v part.

If both 1.5v then might work.

ps I have made this happen myself - a couple of times.

 

[Cycloid Torus]

According to a post by a Crucial guru, 1.35v should work at 1.5v, but there may be other issues...

"
Re: mixing 1.5v and 1.35v memory


Hi Ron,



Thanks for contacting us today. If both are being recommended for your system then you could use either with no issues. 1.35v is dual volt memory. It will run at 1.5v if necessary or when mixed with 1.5v memory. The advantage to 1.35v is it does use less power. We typically recommend on using 1.35v because it can be used at either voltage. Please let me know if you have any other questions or concerns.


YogiH, Crucial Moderator, US"

 

[roseypeach]

Thanks so much for that! I guess I will go with the Micron part and see if that resolves the issue.

REP+++++ (y)