Newly Built System locking up - CPU Vcore experiencing MASSIVE fluctuations (33%)

[MarkC9]

Hey guys,
I'm currently attempting to fix a locking issue with my newly built computer.

First and foremost I will describe the problem:
- Once every 12-72 hours my computer will lock up, displaying a frozen frame of whatever was last on the monitor.
- The lockups occur randomly; sometimes when nothing is running at all but the OS.
- All functionality is gone.
- Fans, CPU, GPU, and mobo are all still powered.
- Anything in a USB slot can still receive power. However anything new plugged into USB cannot.
- I've unplugged the DVI from the video card and plugged it back in a few minutes later, only to see the same frozen frame of my desktop (in this case, Breaking Bad in full screen).
- The only resolution is to hold down the power and restart, then all is fine for 1/2 a day to 3 days.
- On top of this, my direct replacement warranty expires in 4 days. :doh:


My specs are as follows:
ASUS P8Z68 V-Pro (MOBO)
Intel i7-2600k (CPU)
Zotac GTX 580 (VGA)
NZXT HALE90 1000W (PSU)
G.Skill 8GB 1600mhz Sniper (RAM)
ASUS PCE N-13 (LAN)
Intel 510 120gb (SSD/BOOT)
Samsung 1TB HE103SJ (HDD)
Cooler Master Hyper 212 (COOL)


Potential culprit 1
- I'm getting an odd voltage reading using my NZXT 1000W PSU. Massive fluctuations. Using Speedfan and HW monitor, the "Vcore" voltages are flying about everywhere. My ASUS board features an "EZ overclock" button in this BIOS so I thought this might be it, but set back to stock the problem still persists.

Overclocked to 4.5ghz:
http://img339.imageshack.us/img339/6217/voltagessketch.png
http://img406.imageshack.us/img406/4834/vcore2.png

Stock at 3.5ghz
http://img263.imageshack.us/img263/4613/speefanvcorenooc.png
http://img171.imageshack.us/img171/4250/vcorenooc.png

I should comment, in the ASUS UEFI (BIOS) window, it doesn't show the voltages fluctuating by more than a couple %. I'm not sure how that fits into the picture here. I do however feel this is the likely culprit to my freezing issue.



Potential culprit 2
The Intel SSD, since SSDs in general simply aren't that reliable (even Intel has close to 10% RMA in first year). It does figure out pretty nicely. I can't physically do anything because I'm not longer connected to a drive containing an OS, letting alone drivers for anything connected. The last image could be stored in RAM, hence why I can still see the last frame when unplug my DVI and plugging it back in. Not sure how it would explain the USB fiasco though.


Potential culprit 3
My video card (Zotac NVIDIA GTX 580). Even though I unplugged the DVI and plugged it back in, only to receive a signal, it could be that the card had that stored in it's RAM. There is nothing that points me in this direction however through testing, is it does above with the CPU/PSU.


Potential culprit 4
My RAM, simply because many people report that locking up is commonly a RAM problem. However I do not quite understand how to use MemTest x64. Is there a simpler program I can use for the same result, preferably through the OS? That or maybe a link on how I can get it to boot off a thumb drive. Thanks in advance.


So there we have it, I know it's a lot to read but I figured I'd be thorough as to not waste anyone's time with back and forths needed to attain info. I am open to suggestions on how to solve this problem as I really am not that savvy when it comes to building or repairing computers. I'm stumped and in dire need to solve this within 4 days, so I can return any faulty parts for direct exchange.

Thank you so much for your time if you have made it this far.
:band:
I appreciate any and all help!

 

[Blain]

The Intel SSD, since SSDs in general simply aren't that reliable (even Intel has close to 10% RMA in first year).

Name that tune! Please link us up with those statistics.

 

[zi0n.]

When was this built? Was it OC'd the whole time?

 

[MarkC9]

Name that tune! Please link us up with those statistics.

Are your other 21,000 posts this helpful? If you'd like to see the statistics, drive yourself down to Toronto, hit up the Canada Computers in North York, and ask them to show you a list of SSD return rates by brand on their extended warranty plans.

 

[MarkC9]

When was this built? Was it OC'd the whole time?

It was built about 2 weeks ago. It's wasn't OC'd at first, then was, then wasn't, and now is again. It has locked up. during all those stages. I found out my RAM was running at 1.65V instead of it's 1.5V standard as per it's label. Could that have been the culprit?

 

[zi0n.]

If it was more than 2 weeks I would say.. because I was having a similar problem but I built mine around february and it was OC'd the whole time and all I needed was to add more voltage to the cpu & memory, no more lockups!

 

[T_Yamamoto]

Hey, OP dont talk trash about Blain like that
he is a great guy
youre just being a jerk

 

[MarkC9]

Guy A: Reads out of his own free will paragraph after paragraph of someone explaining a problem and asking for help, yet decides to pinpoint 3-4 words in brackets that are rather irrelevant in assisting to find a solution for this problem (point of thread), makes a witty remark about his obvious suspicions with the OPs accuracy of statement, and offers no help or solution to the problem despite having 21,000 posts and 12+ years experience on these boards.

Guy B: Tells Guy A his post is of no help, relevance, and explains (with the same level of respect given by Guy A) where this statistic comes from.

Yet in your world, Guy B is the jerk. Nice logic, friend. 😵 :thumbsup:

 

[T_Yamamoto]

oh to me it sounded sorta...jerkyish

 

[Neutralman]

Mark may I ask which company built the computer? Or was it all newegg built yourself.

 

[Blain]

* These forums are made up of people interested in all things PC.
* You made a statement which took me by surprise.
* Assuming you didn't make the numbers up out of thin air, I simply asked you for a source for such statistics.
* Having never heard of anything near those failure rates, I would like to read more.

 

[mfenn]

Mark, you've got to remember the all important rule #10. That is, don't ask for help if you're thin-skinned.

Anyway, let's go down your scenarios:
1. A fluctuating Vcore in and of itself is not a problem and is in fact completely normal. The CPU's power saving techniques work by reducing voltage. However, that's not to say that the mobo doesn't let the voltage drop too low. Try going into the BIOS and turning off all power-saving features like EIST, SpeedStep, C states, etc.
2. While you could very well be experiencing data corruption from a drive going bad, your symptoms aren't really indicative of that to me. You can try doing a fresh install on an HDD though.
3. That is completely normal. As you've surmised, the GPU outputs the last image that it was told to display.
4. Memtest86+ is pretty simple to use. Just download the ISO, burn it to a disk, and boot off of it. It will tell you if there are any errors.

Based on your symptoms and the fact that the system was overclocked with elevated voltages, I'm betting that the Vcore is dropping to low. This is either because you have a bad part to begin with or that the overclock damaged it. Other possible culprits are PSU, memory, and SSD.

 

[MarkC9]

Neutralman: Built part by part from various sources


Blain: You simply asked me for a source for that information. I simply asked for assistance with my problem. Why, when you have put in no effort to assist me with my problem, would I give a crap to hunt down statistics for you? Let alone ones that my retailer showed me on their in-store computer. It's not like you are a noob, 21,000 posts later and you had nothing to contribute in helping me with this problem? I'm sure you do have an interest in that SSD stat, but let's be honest: You used your PhD in Jerkology to aid this interest: "Name that tune!", and you even took the effort to bold it. Really? I'm no fool, I can read that intent like a book :ninja:. Why someone would enter a thread specifically meant to address a computer issue and instead offer no help and query them about 1 little statement is beyond me, and should be beyond a member with 21,000 posts and 12 years board experience.
Next time stay on topic, query them during or after you have assisted them, and you'll get a proper reply most likely.


mfenn: Meh. IMO it's obvious what happened here: Advanced user sees a statement he believes is inaccurate and decides to ignore the entire purpose of the thread just to call out the OP. In this case, this statement was 4 words placed in brackets amongst a post of hundreds of words. In this case as well, the OP was smart enough to see what was happening here and instead of playing along unknowingly, is now calling out this user for putting his own crap (interests, trolling, whatever it is) over the OP's.

Thank you for the proper reply though 😀
1) I will reset everything to bone dry stock (aside from DRAM) and then make sure all the voltages match. Checking today, the DRAM was at 1.65V stock when it's supposed to be 1.5V; could that have caused these issues?
2) I think I will be cloning my OS onto an HDD if this problem can't be fixed through your first suggestion, combined with switching the DRAM voltage.
3) Ah okay; so does this mean the video card is out of the question then? Since it still posts what it receives seemingly.
4) Yeah I was using the wrong installer, gonna run it today. Thanks!

 

[bryanl]

Replace one major component at a time, until the problem changes, starting with the usual suspects: memory, video, and drives.

Hard drives are usually trustworthy if they pass their factory diagnostics; I don't know about SSDs.

Video, provided power is sufficient, is more likely to have an issue with its software driver problem than its hardware.

Memory is often defective if it has a higher than normal voltage rating, consists of unidentifiable chips, is covered with a futuristic sci-fi style heat spreader, or has a name associated with adventure. I would hate for my memory to possess any of those negative characteristics, let alone all of them. Several hours of testing, even 12 hours, can be needed to find defects, and some diagnostics are so badly designed they'll never find any.

 

[Puppies04]

Hi markc9, I know you are stressed because your system is broken but remember the number one rule of anandtech forums...

Don't even think about claiming anyone other than OCZ have problems with their SSD's, infact just to be safe you can add a signature claiming your undying loyalty to everything non-ocz. 😀

Ok now onto your problem, first off i would suggest running memtest overnight (8 hours should be about right) if you can run it that long without any faults you should be in the clear. Memtest needs to be run at startup outside the windows environment. Download the program and burn it to a disc then boot from it.

Mfenns advice is as usual spot on, do this

1. A fluctuating Vcore in and of itself is not a problem and is in fact completely normal. The CPU's power saving techniques work by reducing voltage. However, that's not to say that the mobo doesn't let the voltage drop too low. Try going into the BIOS and turning off all power-saving features like EIST, SpeedStep, C states, etc.

I would also suggest re-installing your OS onto your SSD and if the problem doesn't go away try taking the SSD out and installing windows onto your HDD.

At that point you have ruled out problems with your ram,mobo power delivery and ssd.

I know that is going to take you a little while to complete but until you start eliminating potental problems nobody is going to be able to help you.

 

[Puppies04]

Also you don't mention if your RAM is overclocked.... if it is set it back to standard. Although if it passes memtest while overclocked it should be fine.

 

[mfenn]

Thank you for the proper reply though 😀
1) I will reset everything to bone dry stock (aside from DRAM) and then make sure all the voltages match. Checking today, the DRAM was at 1.65V stock when it's supposed to be 1.5V; could that have caused these issues?

Which exact kit do you have (model number)? Most Sniper memory is 1.5V, but some is 1.6V. Make sure that you have the timings properly set per the specs.

3) Ah okay; so does this mean the video card is out of the question then? Since it still posts what it receives seemingly.

Yes and no. The video card itself being defective is unlikely to give the symptoms you are experiencing. However, it is possible that the GPU is pulling too much power. If your PSU is marginally defective, that could be enough to push its output voltages too low. You're in luck though, you have a Z68 board. Just pull the GPU entirely and use the IGP to eliminate that as a possible cause.