Problems with 2600K/Asus P8P67 Pro Build

[wcladley]

Hello,

I am a first time builder, having some issues with my first build. I am trying to determine if the problems are related to the P8P67 Pro, or if I have simply done something wrong: Specs are as follows:

Intel Core i7 2600K (stock clocks)
P8P67 Pro
2GB PNY Ram (waiting on 16GB of Ripjaws (F3-10666CL9D-8GBRL,1333 MHz) to arrive but wanted to test the system with some spare DDR3)
64GB Crucial SSD (boot drive)
640GB WD Black Caviar HDD
Corsair TX850w PSU
AMD Radeon 6850
Windows 7 Pro 64-Bit

Since using the system, I have had three instances of the computer crashing. Once during web surfing, once during program installation, and once during a game (so, at a variety of load levels). When this happens, the HDD activity light on the case (CM Storm Scout) remains lit and the mouse, keyboard, and screen become unresponsive. I have checked the temps (via SpeedFan, Asus Utilities, and HWMonitor, and all return a CPU idle of around 29C and 40C under load (GPU holds at around 37C, mobo at 28C). Windows Memory Diagnostics have also returned no issues. I did not run MemTest86+ as it does not fully support Sandy Bridge.

Here are some odd (to me anyway) circumstances that have surrounded this activity:

1. The issue cropped up after I upgraded the bios to 1003 from the factory installed version (0402 I think).
2. When I turn the computer on, it seems to "rev" once (lights come on, fans spin) and then shuts down before coming on in full a few seconds later.
3. There is a large discrepancy between cpu temps in BIOS and those within Windows (46C to 48C in BIOS vs. the numbers listed above). As the CPU fan only spins at about 1000 RPMs most of the time and I cannot detect significant heat from the case, I am fairly confident that I do not have an overheating issue.
4. A large green light on the board next to "CLRTC" is lit constantly.

I believe I may be experiencing a RAM compatibility issue or just simply not have enough of it, as half of the system RAM seems to be in use according to Task Manager. Any advice from those more experienced at this than myself would be helpful. I thought I did my homework on PC building but is likely that I have overlooked something simple/obvious.

Thanks,

Wcladley

 

[mlc]

don't overcomplicate things...

If the issue began occurring after you flashed to a new bios.. then it's pretty certain to be an issue relating to the bios upgrade....
1) the bios is bad, in which case try flashing back to the original bios to see if the problem goes away
2) the bios is ok, but the settings are different... in which case try running with Optimal Settings to see if it stabilized, then tweak from there

I would try clearing the cmos (pull battery, set jumper, etc.) and then post into your bios and set it to run at optimal settings.. and boot into windows.. If that's stable . .then go back into bios and apply your settings...

some manufacturers instruct you to post using the optimal settings after an update.. prior to going in and changing things..

 

[ahurtt]

What prompted you to update the BIOS?

What are the specs on the PNY RAM you're temporarily using now? Is the RAM on the approved memory maker list for the motherboard? Is it 1.5V or 1.65V memory?

 

[wcladley]

I updated the BIOS simply out of curiosity and the fact that 1003 seemed to offer some new features. This was a definite error in retrospect. Specs on the memory are: 667 MHz (odd because it was meant to be 1333 MHz), 1.5 volt, turns out that is was not on the approved list. I tried clearing the CMOS (with removing the battery) and reset the board to optimal defaults. I suppose I will just wait until I receive the approved memory and go from there.

 

[BoomerD]

IF you can't resolve the problems, here's some tips from ASUS...and when all else fails, it tells you how to revert back to the previous BIOS:

http://vip.asus.com/forum/view.aspx...&model=Maximus+Formula&page=1&SLanguage=en-us

 

[ahurtt]

Let us know how it goes by reverting your BIOS. If that doesn't work, just wait for your permanent DDR 3 RAM to arrive and give us an update on your success or failure with that. Are you sure the PNY memory you're using temporarily is DDR3 and not DDR2?

 

[00Aron]

I built my 2600k on a P8P67 Pro last week myself and may be able to shed some light on the subject(s).

1) I am using the 1053 beta version of bios and so far have not had any problems. This with overclocking to 4.5ghz @ 1.275 volts (only changes I made in BIOS was to set CPU voltage to manual and setting the turbo OC for all cores to 45). I flashed to 1053 before doing anything else to this build, so I cannot comment on the factory bios or 1003 versions.

2) This restarting problem is a known problem on several Asus boards from what I've read. I managed to completely resolve this issue (at least for the last 4 days) by doing a CMOS clear. The procedure for this is simply:
- Shutdown computer
- Unplug power cord
- Open case and move CLRTC jumper cap from pins 1-2 (default) to 2-3. Keep cap on pins 2-3 for 5 to 10 seconds then move cap back to pins 1-2.
- Plug computer in again and boot into BIOS to re-enter any changes you made. (This process can be found in the P8P67 Pro motherboard user manual, along with a lot of other information you should take a look at, including the answer to your Green LED question)

As I said, this process has worked for me and for others to remedy the "cold-boot" multiple boot problems. This jumper cap is located right next to the green light you mentioned, which takes me to

4) (out of order, I know) This light simply indicates power to the board... either the computer is on... in a sleep mode... or off but plugged in. It is normal to be lit if it is plugged in.

3) Mine also indicates higher temps in BIOS than in HWMonitor or Real Temp (which are both within 1 degree of each other). I sit around 43 or 44C idle according to BIOS... but only 26-28C idle in Windows.

Other thoughts...
- Ensure all your chipset drivers are up-to-date (CD that came with the motherboard) as well as other devices (graphics card, etc...)
- Disable the Marvell Storage controller if you don't have any devices connected through it (removes the "No hard drives found!" message when booting and also cuts down on boot time... can be found in the "Advanced" -> "Onboard Devices Configuration" menu). I would recommend you plug your SATA drives into either the 4x Blue SATA connectors if it's a 3gb/s drive or the 2x Gray SATA connectors if you have 6gb/s drives. The 2x Navy Blue SATA connectors are the Marvell controller connectors.
- 2gb memory is the minimum recommended amount for Win7 64bit and I know you said you have more coming, but could very well just be a memory problem. Run CPU-Z and check that it is showing your memory with all the correct stats / timings. Watch your motherboard during a boot process. There should be 4 red LEDs that light and turn off during the POST. If any of them stay lit, it indicates a problem has been found in that area (CPU, Memory, VGA or Boot Device).

 

[wcladley]

Well, I received and installed the new supported memory a few days ago. Things have been stable since that point. No more cold boot issues, and no crashes to speak of thus far. I have tested the system with a few resource-intensive games and 3DMark11. This level of stability has been maintained for around 72 hours. Because of this, I have not reverted to the previous BIOS, and do not intend to if further usage is problem free. Thanks for the suggestions and assistance. I'll provide an update if something else crops up.