1866 Dominator Plat - Pre-memory PCH initialization has started - Asus Z9pe=D8 ws

[marchitect]

Corsair Support.

I’ve been trying to troubleshoot an issue now for 3+ weeks. I’m thinking my issue may be RAM related and I’m hoping you can help.

System:

Asus – Z9PE-D8 WS

Processors: Intel – Xeon 2687w (2x)

Memory: Dominator Platinum, 8x8(64GB) 1866, 14900, 9,10,9,27

Coolers: Corsair H100i (2x)

Windows 7 64 Ultimate.

SSD’s: Samsung 840 Pro 256GB for OS, another 840 Pro for Users, Profile

Power Supply: EVGA NEX1500

The error that keeps coming up is ASUS Q-Code 22. "Pre-memory PCH initialization has started".

I’ve had 3 different motherboards through RMA process. In addition, I’ve not only reset the CMOS, but I’ve tried installing a new CMOS chip from ASUS. And this error comes up every time. I'm using the latest BIOS, 3302

The system seems to run fine, but I have not yet really tested the system. It runs very basic things fine like email and internet browsing. I have yet to install my core programs and use the system for its intended purpose because I’m trying to resolve the 22 error first. I don’t want to get to a critical point and have some memory related error killing my work.

I’ve seen other forums discuss this "Pre-memory PCH initialization has started" issue and the reason I’m concerned is that on other forums people with this error can’t even boot their system. I’m able to boot the system every time, but I’m concerned I may be sitting on a time bomb since others find this error with terrible circumstances.

BIOS Settings: I have tried setting everything to AUTO. I have tried manually setting the timings to factory settings: 9,10,9,27. I have also tried manually setting the voltage to factory settings: 1.5V. This board’s BIOS doesn’t have a specific X.M.P. setting, but setting to AUTO is supposed to enable XMP is available. I haven’t tried alternate timings or voltages yet. I was hoping to get some suggestions from this forum.

In addition, I have also manually adjusted the voltage to 1.55 and 1.56 volts. I have also tried different timings, changing the 27 from 22 up to 31 with no change in results.

[peanutz94]

I'm confused? I found your post in a competitors forums googling, and you list a two sets of their memory. What is the actual memory you are trying to use and how many kits?

You stated 2 sets of their memory , which could be the issue in itself.

http://www.G.Skilll.us/forum/showthread.php?p=70282#post70282

 

You also have to change the memory frequency manually, not by changing BCLK. Page 4-21 in your MB manual shows how to choose memory speed If left on AUTO it will only run at 1333mhz. So you need to change your AIoverclock setting from auto to manual, then go into the memory configuration settings found on that page to choose the correct frequency under "DDR Speed".

 

If you still get the same MB error code the it's probably best to test the memory .

I know this is a very long process in your case , but i would test each module individually with memtest86+ (there is a link on the left side) Let each stick run for a minimum of 3 passes or until you find an error.

 

But this will also depend on what memory you are really running... If you have tried the competitor memory and still get the same code as the Dominators then you don't have memory problems. Since you have already RMA'd the board it may be one of your CPU's or you just don't have your BIOS configured correctly.

[marchitect]

I'm confused? I found your post in a competitors forums googling, and you list a two sets of their memory. What is the actual memory you are trying to use and how many kits?

You stated 2 sets of their memory , which could be the issue in itself.

http://www.G.Skilll.us/forum/showthread.php?p=70282#post70282

 

You also have to change the memory frequency manually, not by changing BCLK. Page 4-21 in your MB manual shows how to choose memory speed If left on AUTO it will only run at 1333mhz. So you need to change your AIoverclock setting from auto to manual, then go into the memory configuration settings found on that page to choose the correct frequency under "DDR Speed".

 

If you still get the same MB error code the it's probably best to test the memory .

I know this is a very long process in your case , but i would test each module individually with memtest86+ (there is a link on the left side) Let each stick run for a minimum of 3 passes or until you find an error.

 

But this will also depend on what memory you are really running... If you have tried the competitor memory and still get the same code as the Dominators then you don't have memory problems. Since you have already RMA'd the board it may be one of your CPU's or you just don't have your BIOS configured correctly.

 

In an effort to try to solve this issue, I have even tried the G.Skill memory you saw in a different post. This was done to try to rule out the RAM being faulty. And since the MB has been RMA'd I don't think it's the MB. In each case I have 2 sets of 32GB. One 32gb kit for each processor. I don't know of anyone buying a single 64GB kit for this motherboard. That doesn't seem necessary for this board.

 

In my testing I thought that the RAM was the problem. Now I think it is still memory/ram related but has to do with the timings/voltages that the MB and processors want.

 

I currently have the Dominator RAM set to manual and DDR speed "Forced" to 1600. Setting it to "Force" 1866 only results with a no-post. This is consistent with the MB from many different users.

 

I'm not sure how to test the CPU for errors and because I'm able to get some of the highest Cinebench scores I've seen (25.20) consistently, I don't think it's the CPU's.

 

I think, like you said, it's probably a BIOS setting somewhere.

[marchitect]

I talked to ASUS support today about my pre-memory initialization error (code 22). The first question they asked was: "Are you using buffered or un-buffered memory"?

I didn't know the answer. I told support I was using Dominator Platinum 32GB kits. He looked up the ram on his computer and immediately said, "There's your problem."

Asus Support said that the Dominator Platinum is 'buffered' ram and the Z9PE-D8 WS doesn't work well with buffered ram.

He said I should try the Dominator GT memory which is on the Corsair website as being tested with the Z9PE-D8 WS motherboard.

I did some research and couldn't verify if the Dominator Platinum as buffered or un-buffered. Can someone please verify this.

I'm wondering what the difference is between Dominator Platinum and Dominator GT. I thought the GT was the same thing as Platinum, just an older version.

 

My questions:

Has the Dominator GT 32GB (4x8) 1866 memory been tested on the Z9PE-D8 WS motherboard? - Asus thinks so, but it's not on Corsair's website.

 

Is the Dominator Platinum buffered or un-buffered?

 

What's the difference between Dominator Platinum and GT?

 

Thanks so much.

 

In an effort to try to solve this issue, I have even tried the G.Skill memory you saw in a different post. This was done to try to rule out the RAM being faulty. And since the MB has been RMA'd I don't think it's the MB. In each case I have 2 sets of 32GB. One 32gb kit for each processor. I don't know of anyone buying a single 64GB kit for this motherboard. That doesn't seem necessary for this board.

 

In my testing I thought that the RAM was the problem. Now I think it is still memory/ram related but has to do with the timings/voltages that the MB and processors want.

 

I currently have the Dominator RAM set to manual and DDR speed "Forced" to 1600. Setting it to "Force" 1866 only results with a no-post. This is consistent with the MB from many different users.

 

I'm not sure how to test the CPU for errors and because I'm able to get some of the highest Cinebench scores I've seen (25.20) consistently, I don't think it's the CPU's.

 

I think, like you said, it's probably a BIOS setting somewhere.

[RAM GUY]

All of our DDR3 memory is unbuffered and non-ECC. I have no idea how he got the information he told you but it is wrong.

 

Dominator GT is no different than Dominator Platinum spec-wise so if Dominator GT works @ X Frequency, so will Dominator Platinums. The only difference is the heatsink used, and that Dominator Platinum has many more kits available for different speed and capacity needs.

[peanutz94]

I'm not sure how to test the CPU for errors and because I'm able to get some of the highest Cinebench scores I've seen (25.20) consistently, I don't think it's the CPU's.

Check out Intel CPU diagnostic tool!

https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=19792

[marchitect]

 

My questions:

Has the Dominator GT 32GB (4x8) 1866 memory been tested on the Z9PE-D8 WS motherboard? - Asus thinks so, but it's not on Corsair's website.

 

Thanks so much.

 

Can you verify if any of the 1866 (4x8) Dominator Platinum or GT memory have been tested with the Asus Z9PE-D8 WS motherboard?

[peanutz94]

If it doesn't show on the website, then no , it wouldn't have been tested.

 

But if ASUS says THEY tested it and it's fine that would be no different. As long as it appears in one of the two or you get ASUS to verify that. But considering the advice you already got from them i would ask for a supervisor or someone above the basic techs.

[marchitect]

If it doesn't show on the website, then no , it wouldn't have been tested.

 

But if ASUS says THEY tested it and it's fine that would be no different. As long as it appears in one of the two or you get ASUS to verify that. But considering the advice you already got from them i would ask for a supervisor or someone above the basic techs.

 

I got an email from ASUS support. It shows a spread sheet matrix apparently from Corsair showing all the ram that has been tested on the Z9PE-D8 WS motherboard. But the spreadsheet doesn't specifically say it's for the Asus Z9 board, the support guy just said it was and then emailed it to me.

It seemed like he was pulling info from a different Corsair source than I have access to.

That's why I wanted Corsair to conform if they have tested more memory chipsets than currently show on the website.