Sign in with
Sign up | Sign in
Your question
Solved

Upgrading Memory on ASUS P7P55D-E Pro

Tags:
  • Memory
  • DDR3
  • Kingston
Last response: in Memory
Share
April 15, 2014 8:12:42 PM

My 10 year old son uses this system for his gaming and it currently has 4 gig memory.

The existing memory is Kingston KVR1333D3N9K2/4G kit. I ordered the Kingston KHX1333C9D3B1K2/8G which is 2 sticks of 4G RAM.

When I put the new memory in the BIOS will recognize the RAM but it won't boot past the Windows Splash screen and it goes to a Blue Screen.

I tried resetting the CMOS and swapped the memory out and tried different configurations using only on of the new modules in each slot but I can't get it to load windows.

I'm thinking this memory should work but I'm at a loss.

The CPU is an i3-550. Running WIn 7 Home Premium 64 Bit.

I'd appreciate any help I can get.

More about : upgrading memory asus p7p55d pro

Best solution

a c 2199 } Memory
April 15, 2014 8:32:13 PM

Try with 1 stick in slot 1 and see if it boots, if so then add the second stick in slot 3, ensure DRAM voltage shows correctly in BIOS
Share
April 15, 2014 9:08:47 PM

Wow tradesman, thanks for the quick response. I already tried 1 new stick in slot 1 and then tried 1 in slot 3 and got the same error.

But I just ran through the same thing again as you asked - put 1 new stick in slot 1 and it ran all the way up to the Windows Starting Screen then went to blue screen. On recycle I entered BIOS and checked in Bios Information and that showed Memory Usable Size of 4088MB.

Then I went into AI Tweaker Tab and it showed the DRAM Voltage set to [AUTO] and it showed a voltage reading that went between 1.553V and 1.559V.

Also, just wanted to say the BIOS was reset to all default settings when I originally tried the new sticks this afternoon.

Again, I really do appreciate the help.
m
0
l
Related resources
April 15, 2014 9:16:40 PM

I repeated the above test with each of the two new sticks and got the same result with the second one.

An FYI - I updated the BIOS to the most recent before I traded out the memory for the first time.
m
0
l
a c 2199 } Memory
April 15, 2014 9:20:17 PM

Do you have the latest BIOS, if not try that, if you do then would go back to a single stick in slot 1 and set up manually
m
0
l
April 16, 2014 2:20:27 PM

I have the lastest BIOS. I've built all my computers for the past 25 years but when it comes to the details of setting this kind of stuff manually I'm at a loss and could use a little guidance.

Is there any indication of what could be the problem? Memory is recognized in BIOS but Windows blue screens. Does that mean anything? Is there a starting point?

Sorry but when it comes to this kind of detail I'm quite the noob.
m
0
l
a c 2199 } Memory
April 16, 2014 3:15:14 PM

Go into BIOS manually set DRAM freq to 1333, then the base timings to 9-9-9-27 and the DRAM Voltage to 1.5, also look for Command rate or command timing and ensure it's at 2T or 2N
m
0
l
April 16, 2014 6:08:48 PM

Went into BIOS and manually set the DRAM to 1333, set the timings to 9-9-9-27 and the DRAM V to 1.5 - also set the timing to 2N. Blue screen at "Windows Starting" splash screen.

Repeated the whole process with the second new stick in slot 1. Same thing.

This is a bit frustrating. What happened to the days when all you were concerned about was the size of the memory stick? lol
m
0
l
a b } Memory
April 17, 2014 9:33:36 AM

Hello, I'm Jewel with Kingston Technical Support. The symptoms you are experiencing are exactly what we tend to see when Single Rank 4GB modules are installed in systems that do not support it. The BIOS sees that the memory is there but the memory is used for more than a minor degree like when Windows starts the system crashes. It is very likely that the 4GB HyperX memory modules you purchased are Single Rank usgin 4Gbit DRAM instead of the previously common 2Gbit DRAM as we have moved over to that configuration mostly due to part availability. Some older motherboards are not able to fully communicate with the larger capacity DRAM chips. If your motherboard supports 8GB modules than that would not be the issue, if it does not than that is the problem. If you see a "1R" on the Kingston memory label that would indicate it is Single Rank, if that is not present than we can verify that by referencing other information on the module. Knowing which motherboard is in question would be very helpful in figuring out the exact issue. For further assistance, please call us at 1-800-435-0640 (USA and Canada only) M - F 6am - 6pm PT and I or another available Technician will assist you. Please be sure to have the part in question on hand when you call.

Thank you for selecting Kingston as your upgrade partner.
m
0
l
a c 2199 } Memory
April 17, 2014 3:18:20 PM

kingstonhq said:
Hello, I'm Jewel with Kingston Technical Support. The symptoms you are experiencing are exactly what we tend to see when Single Rank 4GB modules are installed in systems that do not support it. The BIOS sees that the memory is there but the memory is used for more than a minor degree like when Windows starts the system crashes. It is very likely that the 4GB HyperX memory modules you purchased are Single Rank usgin 4Gbit DRAM instead of the previously common 2Gbit DRAM as we have moved over to that configuration mostly due to part availability. Some older motherboards are not able to fully communicate with the larger capacity DRAM chips. If your motherboard supports 8GB modules than that would not be the issue, if it does not than that is the problem. If you see a "1R" on the Kingston memory label that would indicate it is Single Rank, if that is not present than we can verify that by referencing other information on the module. Knowing which motherboard is in question would be very helpful in figuring out the exact issue. For further assistance, please call us at 1-800-435-0640 (USA and Canada only) M - F 6am - 6pm PT and I or another available Technician will assist you. Please be sure to have the part in question on hand when you call.

Thank you for selecting Kingston as your upgrade partner.

________________________________

In title of thread: mobo is the ASUS P7P55D-E Pro
m
0
l
April 17, 2014 3:44:40 PM

Jewel,

Thanks for the reply. I went ahead and called your Technical Support Number and opened up a case number - #130748.

I was asked to run memtest on each of the sticks. I'm going to do it later on tonight.

Tradesman is it ok for me to keep posting any tests/results I go through with Kingston customer support so I can get feedback by the community here and also a record if we are successful and someone else runs into the same issues?
m
0
l
a c 2199 } Memory
April 17, 2014 5:31:18 PM

Sure, hopefully there will be good info that will someone in the future
m
0
l
April 17, 2014 7:34:05 PM

Put new stick #1 into Channel A1 and set BIOS to default. Setup boot from Memtest86 disk and the test ran for a few seconds then froze at test #1 - 14%. Tried multiple times to reboot, reset stick, etc. Went into BIOS and manually set DRAM to 1333, set timings to 9-9-9-27. Boot to memtest disk and test freezes at same spot - test 1 @ 14%.

Tried above with new stick #2 in Channel A1. Same result.

Then tried new stick #1 in Channel A2. Same result.
m
0
l
April 17, 2014 7:41:49 PM

kingstonhq,

I don't see a 1R on the label of the memory. How can we identify if it is a single rank? I tried to explain your post to the technician on the phone today but it seemed he wasn't interested in pursuing that line of thinking. However, it seems you are identifying my problem as one which you've seen before with the same symptoms. With the memory test running for only a few seconds I am more inclined to say it seems to mirror the exact symptom of the windows splash screen starting up and then freezing.

My other question is this - if my problem is indeed the one you've identified with the 1R issue, is there a work around with this memory or a case of me returning the memory sticks and getting something else?

Thanks,

Ken
m
0
l
a c 2199 } Memory
April 17, 2014 7:49:33 PM

Dropped them a line to check back :) 
m
0
l
April 17, 2014 8:01:14 PM

Thanks Tradesman. I've been coming to tomshardware for so many years as my go to place for recommendations whenever I decided to either upgrade or build a new system. This is the first time I've come to the forums for technical help and I just wanted to thank you for taking the time to help me with this issue.
m
0
l
a c 2199 } Memory
April 17, 2014 8:24:44 PM

Can you boot into safe mode?
m
0
l
April 17, 2014 9:05:21 PM

No it won't boot into safe mode. I tried that the other day - it starts loading files then goes to blue screen.
m
0
l
a c 2199 } Memory
April 17, 2014 9:16:23 PM

Could try reloading Win
m
0
l
April 19, 2014 6:40:32 AM

Last night I burned a copy of Knoppix and booted up with the one new stick in. It loaded and ran for a few minutes before it locked up. I ran it a few times and it froze each time. I put the old memory back in and ran the Knoppix disk again just to make sure it wasn't something happening with Knoppix and the computer ran for a while like that. I'm thinking Jewel is dead on with an incompatibility issue with this memory and my gear. I'll wait to hear back if there's a fix or I have to return the memory.
m
0
l
a c 2199 } Memory
April 19, 2014 8:14:31 AM

May well be the problem
m
0
l
a b } Memory
April 23, 2014 11:24:03 AM

Sorry for the delayed response. We should be able to verify whether the module is 1R or not based on a revision number on the label that looks like this 9912345-123.A00LF
m
0
l
!