P8Z68-V PRO resets itself (any opinions from P8P67 owners?)

[evilspoons]

EDIT: PROBLEM IS SOLVED! See post below (#10).

OK, so I have:

- P8Z68-V PRO
- Core i7 2600k
- 2 x 4 GB RAM kit, G.Skill Ripjaws X F3-12800CL9D-8GBXL
- Scythe Mugen 2 Rev. B cooler
- LG CH10LS20 Blu-Ray/DVD drive
- Some old 320 GB Seagate hard drive for a test install of Windows 7 64-bit

I've removed all other hardware from my PC, I'm running on the Intel integrated graphics (Normally I have a BFG GTX 285, 2 hard drives). I originally had Corsair Vengance RAM but I couldn't get the system to boot properly with both sticks of that installed. The Ripjaws appear to be better, I am typing this from the screwy computer right now. RAM is set up using XMP profile settings.

The computer will appear to function normally for an indeterminate amount of time then just reset. There is no BSOD - I have Windows set to not automatically restart on one.

I ran the Intel Burn Tool for 5 cycles at maximum RAM utilization, no problem. I ran OCCT once and it reset, I ran it again and it was fine. Memtest86+ passed two cycles or more.

There are approximately six billion settings available in the EFI for this system and I'm not sure if any of them are causing this issue. The mainboard came with BIOS 0221 or something, it's not on the website. I switched to the newest version, 8801 - there is no changelog available yet.

Any thoughts? Anyone with a P8P67 with similar issues? (The boards are practically identical...).

 

[bankster55]

there is a way to configure Win 7 to do a crash dump - do it and look
also, have you looked in event viewer - all sections?
set all Intel ports to hotswap except optical port?
set spread spectrum to enabled?
disabled PLL Overvoltage?
turned off Marvel and JMIcron
used a regular DVD and unplugged the BRD?
take mobo out of case and run?
Full cmos reset? (battery out - PSU unplugged)
Dont sleep or hibernate anything?
Unplug ALL USB?
Disable in this profile all USB roots and hubs in dev man?
Checked for loose connections - ram seating? CPU socket bent pins?
Tried your Vidcard?
Flakey wall power?

I could put 100 of these here.
The sad thing is there is a humungous learning curve on the P67 mobos
However first reports say the Z68 solves most P67 probs, including USB and sleep, so I am thinking its siomething on your end, not the mobo
So, as always, I recommend trying the TPU switch and rebooting twice to windows to see is system can find its own best settings.

 

[evilspoons]

there is a way to configure Win 7 to do a crash dump - do it and look
also, have you looked in event viewer - all sections?

Nothing there, just the events from when the computer begins to boot up again. It literally just resets - Windows has no time to show a BSOD or do a crash dump.

set all Intel ports to hotswap except optical port?

I'm not sure what you mean...?

set spread spectrum to enabled?

It's enabled by default, turning it off didn't make any difference.

disabled PLL Overvoltage?

I've switched it off, but the TPU seems to turn it back on (unless I am crazy).

turned off Marvel and JMIcron

They are off, I have no need for them at the moment.

used a regular DVD and unplugged the BRD?

I had to buy the BRD because I don't have any IDE ports now (no sense wasting money buying another DVD drive). The resets happen with the BRD unplugged as far as I can remember.

take mobo out of case and run?

I may have to do this... it took like 45 minutes to get the dang thing in because of the huge CPU cooler though.

Full cmos reset? (battery out - PSU unplugged)

Done it five or six times... ugh.

Dont sleep or hibernate anything?

Totally unrelated to the sleep timers, since I've had it reset within 30 seconds of windows starting... unless it's a CPU sleep state issue I have no knowledge of.

Unplug ALL USB?
Disable in this profile all USB roots and hubs in dev man?

Can't, no PS/2 ports on this mainboard - there would be nowhere to plug in my keyboard or mouse, haha.

Checked for loose connections - ram seating? CPU socket bent pins?

Haven't taken the CPU off since it took me 90 minutes to get the cooler on properly (ugh). RAM has been in and out several times, checked it each time.

Tried your Vidcard?

Card is now installed, still reset a couple times.

Flakey wall power?

Previous PC on same power outlets worked fine, I'm also plugged into a double-conversion UPS.

I will continue to try the suggestions I haven't already covered... has anyone else had this issue specifically?

 

[bankster55]

now see, this is the way everyone should respond to a help request answer ea - one by one
>you I like!
But your kinda prob is the kind I hate - not one thing obviously wrong
I feel your pain

fwiw hot swap WITH CACHE DUMP is not enabled by Intel chipsets (safely remove is only on the marvel), kinda crazy because AHCI is Intel spec
So ASUS added it to the bios, but its default disabled in the bios SATA AHCI settings because of legacy devices

yeah, I have seen posts on other forums where enabling hot swap fixes issues and no one knows why.. This is another of those strange things going on with the ASUS P67 that seemingly have no explanation. As was said, HDD on AHCI controller means hot swap enabled by protocol.

"Hot plugging is a feature of AHCI and it's supported by the chipset, the only problem is I don't know of any way to force the hard drive to dump its cache to platters. With nVidia chipsets, you can click the "safely remove hardware" icon in the system tray, but Intel doesn't support that. I looked in system properties, and "optimize for quick removal" is also greyed out.
http://www.abxzone.com/forums/f154/hot-plugging-esata-possible-without-ahci-112301.html

And it looks like the Intel Controller does NOT support safely remove option, and ASUS added it to BIOS themselves

Quote:
why is hot swapping only working on the marvell controller?

As long as the Intel SATA controller is in AHCI mode, hot plugging will work (I do this on Intel SATA ports in Windows XP, where there’s no native AHCI support). What you don’t get with the Intel SATA AHCI drivers in Windows 7 is the Safely Remove option for the connected drives. Windows 7’s native SATA AHCI drivers do have this feature, so uninstalling Intel’s drivers should bring the option back.
http://forums.whirlpool.net.au/archive/1588905

In other words, you can unplug the HDD when running, but the cache (32-64MB on most drives now) is still not cleared, unless you enable hot swap in the bios. Possibly also when shutting down or hibernating. At least thats the only possible explanation for the setting, and would explain some issues. And would explain why going back to IDE or Win 7 AHCI drivers seems to work. Windows def does not like unfinished business - any time you shut down Win 7 and something has not been saved it freaks out. And this is strictly an Intel AHCI/driver problem. Since SSD's are basically all cache, may also be involved with them.
----------------------------
It's disabled by default because some older optical drives have an issue with it enabled. Its one of those problems where we're going to get some issues whichever way we set it (though we'll make a switch based upon demand as needed). In any case, we're looking at some ways around this if possible. I'm glad we have what we've got in place, as some other vendor boards have no such option and the only current recourse on those boards is to use IDE mode if you have the associated SSDs.

S3 should and does work on most systems, so not a chipset problem per se (unless PLL OV is enabled). The MIVE board needs S3 fixed on the 2133 memory ratio and we are currently looking into this.

Other than that, I believe there is a problem with some of the Intel RST drivers and also Sanforce SSDs needing "hot plug" enabled on their respective ports in the BIOS. Both can interfere with S3 and cause OS freezes etc.

The TPU ON switch on the mobo makes all its own settings, disabling PLL Overvoltage is something to try separately

Could also be a CPU heat shutoff. You could run realtemp and just leave it on

Seems to me just dropping out with no warning/BSOD after passing burn test indicates some sort of intermittent connection. Could try working PSU-mobo connectors around by hand with things running to see if you can make it happen. Guess you dont have another PSU to try? Even an el cheapo?

Flakey ram? Run memtest 86+ overnight, or prime95 for several hours

Intel graphics adapter may be jumping to external slot?
In APM advanced tab see if power on by PCIe enabled
Have to get internal an external graphics bios setting co-ordinated

I am also a bit concerned with a gigantic heatsink in this troubled situation. You could try just making it tight enough for contact. Check all around to make sure its not touching anything. Also some mobo shut down if the 3 or 4 pin mobo CPU fan connector is contact sloppy

 

[Thor86]

You did not mention what power supply unit in use.

Also make sure your board standoffs and add on cards are not shorting something.

 

[evilspoons]

You did not mention what power supply unit in use.

Also make sure your board standoffs and add on cards are not shorting something.

Power supply was a 550 watt Enermax (EG651P-VE(24P)).

I bought a Corsair HX750W - it was on sale and I wanted the modular cabling and something a little newer since my old Enermax didn't even have PCIe or SATA power connectors.

I woke my computer up from hibernation. About 15 seconds later it reset again. GAH!

 

[Scabies]

hate to necro, but we seem to be having the same problem. have had it crash during the windows experience index, WoW, EVE, Windows 7 SP1 update (that was fun)... all sorts of random things. I've tried letting the board optimize an overclock, tried resetting everything to default, then default minus extras (marvell controller, USB3, etc)... I get the feeling that it has to do with something within Z68, since the chipset heatsink is the only thing that gets hot. The GPU doesnt crash during Furmark (Sapphire 6950 Vapor-X, tops out at 72*c and ~43% fanspeed), so I would feel safe saying its not the PSU, and memtest86 passes. But yeah I can testify the logless crash exists. Just snaps off and back on (oh and enjoy your 1TB RAID-1 verification).

 

[Patrese]

I had zero issues with my AsRock Z68 Extreme 4 so far, but there are some reports of random crashes and reboots related to the USB 3.0 drivers. Given you've tried nearly every trick on the book plus a bit of extras, I'd give it a try.

 

[dbrons]

Just want to chime in to say my new system, very similar, is working perfectly.
Could that old hd be causing trouble?

But the only time I had real problems it was an extra stand-off, or screw or something wedged under the board

Dave

 

[evilspoons]

Update!

A couple weeks ago the techs at the place I bought the board from were finally able to reproduce the problem after I explained it to them in great detail.

They then gave me a new board and I rebuilt the computer. Everything works perfectly now with the same operating system install, same hard drive, blah blah. It was the board itself that was defective.

Note that my original board came with BIOS 0221 or something on it (not even on their website). The new one came with 0501.

After determining everything worked, I reinstalled the giant Scythe cooler with MX-4 thermal interface goo instead of the crap that came in the Scythe box. The ah heck now idles at 29 degrees C in a 25 degree C room. Not bad!!

 

[pristine]

Hello All,

I have the same problem and totally devastated!

I have built a new PC with the following sepcs:

i7-2600k (NO Overclocking)
P8Z68 V PRO (because of the critical errors, I updated to 0501 version, but still no luck)
GSKILL RIPJAWS F3-12800CL9D-4GBXL ;they are 2x2GB sitting in DIMM A2,B2 as per mb instruction
stock air cooler
Sapphire HD4690 1GB
PSU 1000W

now the problem is i get reboots in widnows 7 and even in the bios environment.
I noticed that the motherboard automatically sets DDR3 RAM voltages to 1.64V.
In GSKILL website, it mentiones TESTED AT 1.5V
What should I do? Should I set it to 1.5V manually? (I did, but it has reboot once, since)

Also, in the win environment, everytime the system reboots, it logs CRITICAL ERROR as following :

Microsoft-Windows-Kernel-Power
EventID 41

I did MEMTEST, no error. I did some other test, no problem.

I ran prime95, I noticed very high temperatures at 90C (82C in the evening actually) when running its most cpu intensive torture test.
other than that, the system is usually 38C in idle and 40~45C when doing most daily stuff.

Somewhere i read that cpu might not get the required voltage, so I picked up some sensor info from asus probe:

The voltages are:
in IDLE mode:
V Core: 0.832V, +12:12.384V, +5V:5.22V, +3.3V: 3.376V
Also the ASUS TuboV EVO says;
BCLK freq: 100.3MHZ, CPU Voltage:1.6V, DDR Voltage:1.5V, VCCIO: 1.05V, CPU PLL: 1.80V, PCH:1.05V, all the others are 0.5V


In Prime 95 torture test mode:
V Core: 1.248V, +12:12.384V, +5V:5.22V, +3.3V: 3.36V
Also the ASUS TuboV EVO says;
BCLK freq: 100.3MHZ, CPU Voltage:1.65V, DDR Voltage:1.5V, VCCIO: 1.05V, CPU PLL: 1.80V, PCH:1.05V, all the others are 0.5V

Please help.

Thank you.

 

[bankster55]

You cant use stock cooler and run torture tests
Buy a nice cheap Coolermaster 212+
Have you set XMP profile for mem in bios?
Have you tried mem O.K. button?

 

[pristine]

You cant use stock cooler and run torture tests
Buy a nice cheap Coolermaster 212+
Have you set XMP profile for mem in bios?
Have you tried mem O.K. button?

Hi again,

Thanks for the reply.

actually, I ran the torture test in my poorly ventilated room at noon and while it hit 91C I stopped it. I ran the test in the late afternoon and it stabilized around 82C.

I used to believe that the stock cooler would be nice for normal use for some time until I get a corsair H70.
Now, if the reboot problems are because of the air cooler I will change it, but I doubt it.

As for the XMP profile, NO, I did not know about it! I will set it in the next run. ( I have come home right now)

As for the MEM OK, I have pushed it several times during the past days.
Is it supposed to adjust the memory settings?

Were the voltage numbers correct for this system?
Is it wise to lower the memory voltage to 1.5V (as marked by GSKIL as 1.5V tested)?

It is interesting that I get reboots even in BIOS.

Thank you.

 

[Kenmitch]

I used to believe that the stock cooler would be nice for normal use for some time until I get a corsair H70.

Were the voltage numbers correct for this system? Is it wise to lower the memory voltage to 1.5V (as marked by GSKIL as 1.5V tested)?

I used to believe that the stock cooler would be nice for normal use for some time until I get a corsair H70.

Welcome to the forum

Best Buy has the H50 on sale for $39.99 currently. Won't be as good but for the price

Gskill makes some nice ram....But sometimes you may need to bump the ram voltage a little bit. If it's rated for 1.50v's then maybe try around 1.55v or so. It's possible your MB doesn't like your ram. If you think it's your ram then you could try downclocking it to see if it helps or not. If rated at 1600 drop it down to 1333 and try it out.

 

[bankster55]

Hi again,

Thanks for the reply.

actually, I ran the torture test in my poorly ventilated room at noon and while it hit 91C I stopped it. I ran the test in the late afternoon and it stabilized around 82C.

I used to believe that the stock cooler would be nice for normal use for some time until I get a corsair H70.
Now, if the reboot problems are because of the air cooler I will change it, but I doubt it.

As for the XMP profile, NO, I did not know about it! I will set it in the next run. ( I have come home right now)

As for the MEM OK, I have pushed it several times during the past days.
Is it supposed to adjust the memory settings?

Were the voltage numbers correct for this system?
Is it wise to lower the memory voltage to 1.5V (as marked by GSKIL as 1.5V tested)?

It is interesting that I get reboots even in BIOS.

Thank you.

First of all the P67 Z68 chipset intro is one of the most problem laced ever. You really gotta do your homework on these. Most random reboots are related to sleep hibernate probs, USB devices that are not compatible, or SSD drives that have issues with the chipset SATA drivers or bios recognition. You do have a more interesting prob as to the bios reboots. The mobo WILL double post normally if you dont set certain things, but a RANDOM reboot while in the bios is a new one on me.

You have to read the info in the manual on the mem O.K. button and how it works

These mobo all have TPU EPU switches. By either flipping the TPU switch on mobo so that its LED comes on, or by picking the Turbo square window in EZ page the mobo itself will give a stable overclock.This setting has an artificial intelligence that makes a very good reiable overclock, usually ~4.35Ghz. May take coupla full boots to take. This way you dont have to set anything

The GSkill is supposed to be 1600 RAM @1.5V You are expected to pay extra for the better graded chips they use to obtain this low voltage. FWIW any RAM over 1333 is a waste on the SB with mem controller on die, and any higher speed RAM may be more trouble than its worth. I buy Supertalent 4GB sticks 1333 1.5V with micron chips @ superbiiz. ($32 ea) I buy from SupBiiz because I can pick any one of six dram vendors.

You could look in the Win 7 event viewer in the various categories and might get a clue whats involved

What max CPU shutoff temp do you have in bios?

You might get more answers if you start your own thread - this one says solved

 

[pristine]

What max CPU shutoff temp do you have in bios?

You might get more answers if you start your own thread - this one says solved

Hi again,

Thank you for your reply.

In bios, I get higher tempretures than windows (idle). In bios I get around 60~65C with higher fan rpm.

In windows, asus probe reports of cpu:38C and fan 1125rpm.

Note: my room temprature is around 27C is suppose.

today I set the profiles in bios to X.M.P and it automatically set my ram modules to 1.5V.

I have not encountered any reboot yet. But the problem is I don't know where it comes from, or i could simulate the situation and check the system.
I have disconnected and connected usb hubs and usb devices. still no reboot.

Now I am waiting for a reboot. If I knew that mobo is deffected I was more relaxed! but now, I am waiting!

* EDIT: If a reboot happen again, I will start a new thread.