• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

New build starts and stops, won't run

noel54

noel54

Member
Hi all,

I just built a new computer and I'm having trouble with it. It starts and stops, starts and stops, in rapid succession, then does it all over again, but won't continue to run normally.

Stats: MB ASUS P7P55D, CPU Intel i7-870, Memory 4GB Kingston HyperX DDR3, GPU GeForce 460 SE and PSU Corsair HX620.

The PSU is connected to both the 24 and 8 pin MB power connectors. The DIMMS are in slots A1 and B1. The case is an AZZA Hurrican 2000 with lots of fans, but it doesn't matter if they are off or on, it acts the same way upon start.

I've built many computers over the past 6 or 7 years, but this is the first one that has acted this way.

Can anyone help me? Do you need any more info?

Thanks, Noel
 
does it load past POST? Can you get into the BIOS ? I would start with CPU andmemory, try different banks, make sure evrything it connected properly
 
Last edited:
No, It never gets that far - it doesn't even get to where the fans keep turning - they stop almost immediately and then tries again... And no beep codes either - too quick for that before it starts over.

Noel
 
I'll pull the cooler (CoolerMaster Hyper X) and the CPU, re-paste and try that later tonight.

Thanks or the help. I'll post again after I try that and see if it helps.

Noel
 
could be a short somewhere. I would double check all connections, reseat the CPU (make sure there arent any bent pins), memory, PSU connectors. Bascially start from scratch. Try resetting CMOS. If all else fails, could be a faulty mobo or psu
 
Pull the mobo out of the case and put it on a nonconducting surface (like cardboard or whatever). Then just plug in the essentials: CPU, memory, video, power. You can use a screwdriver or key to short the power switch headers to turn it on. This isolates you from any problem with the case (power switches, shorting).
 
Thanks, mfenn, I'll give it a try - I just pulled the mobo out to check the standoffs, good timing!

Noel
 
mfenn,

I hooked up the mobo with the 2 power connectors and shorted the front panel power pins to start the machine. It did the same thing - BUT I noticed a LED light that indicated a CPU problem.

Looks like I have a bad CPU, so I'll need to do an RMA I guess.

Thanks for your help. I'll write back after I rebuild with a new CPU.

Noel
 
Although it could be the CPU itself, it is unlikely. The diagnostic LED is showing that the POST only makes it as far as the CPU check. The reason dor it failing at this point could be related to power, installation in the LGA, or some such problem (or the CPU itself).
 
Check the pin assembly carefully. I had similar symptoms with a 1366 rig. Turned out to be a bent pin. Could never get it straightened out quite right so I RMAed the mobo. Currently waiting on results but I'm guessing i'll have to pay for repairs out of pocket. Better than buying a whole new board though.
 
I know this is obvious but sometimes overlooked...do you have the power plug going into the Video card, I have forgotten this one before. Also check to make sure the CPU fan plug is actually going into the header for 'cpu fan' and not another case fan header.
 
What is the cycle time of this process? Sounds like a shorted power switch but you've isolated that. Does this board require a particular BIOS level to support your CPU?
 
betasub said:
Although it could be the CPU itself, it is unlikely. The diagnostic LED is showing that the POST only makes it as far as the CPU check. The reason dor it failing at this point could be related to power, installation in the LGA, or some such problem (or the CPU itself).
Click to expand...

I agree with beta. I'd inspect the socket first, then suspect the mobo. A bad CPU is very rare.
 
Hi all,

The problem was the CPU socket - bent pins. Never had that kind of problem before, but with the i7 socket, if you take the cover off wrong, you're going to bend pins, so I ruined the Mobo without even trying 🙁 I had no idea you could inflict so much damage with theses socket covers - so all of you out there, BEWARE of those covers!

So I bought a new mobo from Newegg (figured no sense in trying an RMA, over 30 days) and am rebuilding now. I'll tell you how it goes when I try to post later today.

Thanks for all the comments and help,

Noel
 
Hi all,

Well I got a new ASUS motherboard and re-built my machine. It runs!! Turns out I ended up with 3 or 4 bent pins on my new socket, too, just like the first one. But in any case I was able to straighten them up, and the machine booted right out of the gate!!

Thanks for all your help on this issue, folks. This is a great forum and the folks here are first class!!

Noel
 
Did you inspect the socket before you put the CPU in? If you are consistently bending pins, you are doing something fundamentally wrong. Unfortunately, it is one of those things that is nearly impossible to diagnose over the Internet.

Anyways, glad you got it working! 🙂
 
mfenn..

You are right, I have a problem with the 1156 socket cover. When you lift it, the design is such that the cover itself can bend the pins if you so much as sneeze when you remove it... If you have seen it, you know what I mean. The pins are extremely thin and fragile. Oh well, I'll try to stay away from 116s in the future 🙂

But I have a different problem with my old computer (E8400 CPU). I moved some HDDs around in the process of building the new one and now I get 2 dialog boxes when my computer boots into 7 - the first says "EAccess Violation " and has a big red X on it. The 2nd says "Cannot get any information from Group 3." With that I have either 1 or 2 HDDs (depending...) that do not make it into Windows 7 - they show up OK in the BIOS, however. So can you tell me what's going on here?

Thanks, Noel
 
eaccess violation is usually a program trying to access bad memory but that doesn t mean that is your problem here. i would try to see if a linux livecd loads up fine and if it does i would just reinstall my windows.
 
noel54 said:
mfenn..

You are right, I have a problem with the 1156 socket cover. When you lift it, the design is such that the cover itself can bend the pins if you so much as sneeze when you remove it... If you have seen it, you know what I mean. The pins are extremely thin and fragile. Oh well, I'll try to stay away from 116s in the future 🙂
Click to expand...

I've pit together plenty of LGA 1156 systems and never had this problem. Are you talking about the plastic cover that comes with the motherboard as protection, or the metal latch that locks the CPU in place?

noel54 said:
But I have a different problem with my old computer (E8400 CPU). I moved some HDDs around in the process of building the new one and now I get 2 dialog boxes when my computer boots into 7 - the first says "EAccess Violation " and has a big red X on it. The 2nd says "Cannot get any information from Group 3." With that I have either 1 or 2 HDDs (depending...) that do not make it into Windows 7 - they show up OK in the BIOS, however. So can you tell me what's going on here?

Thanks, Noel
Click to expand...

Were those disks dynamic or basic?
 
mfenn,

The plastic cover that has the warning note on it.

As for my older computer, they're basic disks. I had 3 SSDs and 3 platter HDDs in it originally. My boot disc, which does work, is a 30 GB OCZ Vertex 2 SSD, and it boots just fine. But I can't get any other hard drive (SSD or otherwise) to come up, though, even when I change SATA cables and/or connections, so I suspect something in the motherboard - although it was working fine before I removed some of the HDDs to put in my new computer. I'm trying to restart the older one, however, with some of the same HDDs I had in it before, so not sure why this problem.

Noel
 
You could also try booting a Linux live CD and seeing if the drives are visible there. That's a great way to rule out a hardware/software problem.
 
mfenn,

I have it running OK now. Seems the SATA cables were the main problem to the drives. I removed all the cables I had previously installed and strapped down and replaced them with new ones in and I have all my drives running well.

I'm leaving for a few days, but when I get home I plan to update all my drivers and buckle it all up.

Thanks for all your help,

Noel
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top