New build unstable at stock, please help to troubleshoot

Quick reply as getting ready for qualifying (will check in later):

From your latest post i would rule out the PSU.

With regard to your Win 7 issue - have you checked the files 'MD5 checksum' to see that it's downloaded correctly? It could be that it's simply a corrupt d/l.

It's certainly looking like it is the SSD - and if I would steer the retailer towards this thread if you do end up rma'ing the drive.
 
Ok, more info and very interesting, thankfully my TV has picture in picture, so can fiddle on pc as well as watch qualifying.

So, a new install done on the SSD all smooth so far, no crashes. BUT I still have the boot issue, where from cold, the SSD is not recognised, on the first POST, but after hitting rset it works fine. It would then figure that the SSD does not show up in the bios if I enter at first opportunity. I did not have this issue with the HDD.

it gets interesting when I move the SSD to a 3gb sata port, no problems.

So theres something up with the SSD and the 6gb sata ports. Which 6gb port and which cable makes no odds...... From the machine being off, in AHCI mode only (works in IDE mode), the SSD is not recognised in a 6gb channel, but is after restart, hope that makes sense.

So we are making progress, but I will admit, I dont know where to go from here.... And mobo is B3 stepping for the record
 
Last edited:
Ports are in interesting development...

I have one eye on qualifying so bear with me if you've tried this.

Try looking for 'Delay For HDD' or similar in the BIOS and increase the time.
 
Will do, having done a quick google, this issue doesnt seem uncommon with AHCI and OCZ drives, I found reference to an Asus mobo with issues. Yet if it works with the HDD, im trying to figure out where the issue is, I guess I still have to assume SSD.
 
Now, I dont want to proclaim I can run before I can walk.... But Plec, I think you hit the nail on the head, and I could owe you a beer.

I fiddled with a couple of ambiguous settings in the bios, one being staggered HDD spinup, the other being something about timeout. The latter meant the splashscreen displayed for a painfully long time, lesson learned. The staggered spin up however, seems to have done the trick! If this stands the test of time that is one really annoying problem solved.

Now I need to add back in the HDD and pray that doesnt add instability, and otherwise see if I am generally stable.
 
Im now copying over all music and photos from external drive, everything stable so far.

I can only assume if I remain stable that updating the firmware on the SSD was key
 
Im now copying over all music and photos from external drive, everything stable so far.

Excellent - here's hoping you've cracked it.

I can only assume if I remain stable that updating the firmware on the SSD was key

It's not just the SDD's that inevitably need the firmware updating on these latest MBs - H67/P67.

I've had to update both Samsung F3 and WD Green drivers to get them recognised on different flavoured P67 MBs for friends. And none of the boards would recognise my old Maxtors (no great loss).
 
Thanks Plec, all holding up ok.

I would have persued an RMA and bought a new drive before considering a delayed HDD spinup. I googled about it, and the result talks of power loss to a drive when many drives are started at the same time. Yet I struggled with just one drive. What's your take on it?
 
Last edited:
What's your take on it?

Personally I still think you have a problem as, you’ve rightly pointed out yourself, you usually only have to set the ‘HDD Delay’ when the MB is having problems engaging numerous conventional drives during post (or a slow spin up). It may be that it will function fine from now on, with the delay, but it does rather fly-in-the-face of the appeal of an SSD.

My gut feels that it’s the drive at fault but there’s still a chance it could be the Sata controller on the MB.

However, either 'maybe' a flash, firmware or driver update away from being corrected (i stress maybe.) - as past similar SSD problems have been solved with updates (but usually with the firmware update).

Will do, having done a quick google, this issue doesnt seem uncommon with AHCI and OCZ drives, I found reference to an Asus mobo with issues.

And with the results of your above search these 'updates' may be sooner rather than later as it appears not to be an isolated incident. It depends whether you’re prepared to wait a little longer for a possible fix or force the issue with an rma.

Corsair, for instance, have requested SSDs be rma’ed with a similar problems to yours (just googled their forums) – link.

If I was in your position I would contact OCZ and ask for their take on the situation – bulleting all the steps you’ve taken to get this drive active. It maybe that they have a similar ethos to that of Corsair and will swap the drive on the evidence you provide.

I would also consider informing the retailer, you bought the drive from, just so you keep that channel of communication open in case OCZ suggest you return it directly to the retailer (if they advise you to return it all.).
 
Last edited:
Useful info, thanks.

It's the staggered spin up option I have enabled, no specific HDD delay. So in practice it takes no longer to boot. I'm still in Windows within 10-12 secs of hitting the power button, so that doesn't bother me.

Previously if I left the machine on overnight, I would wake to find a BSOD but all ok so far.
 
So in practice it takes no longer to boot. I'm still in Windows within 10-12 secs of hitting the power button, so that doesn't bother me.

Sounds like a solution with no compromises - in which case I would observe for now with the hope/thinking that it's fixed. (I thought you may have been waiting 20+ seconds (just for BIOS) due to a combination of 'hdd delay' and dsiabling 'quick post' etc...)

Previously if I left the machine on overnight, I would wake to find a BSOD but all ok so far.

Looks promising all round - you've hopefully found the right combination of updates/tweaks.

Keep me posted - i hope it's all one way for you now.
 
Last edited:
Bad news BSOD tonight. Turned machine on, left it to see if it was stable, as previously had issues with BSODs when idle, and same thing tonight, after an hour or so at a guess.

BSOD said it had shut down the pc to prevent damage etc etc, and then reference STOP and then I guess some address of the fault in question. Now Im really frustrated, and somewhat back to square 1.1. Plec, any thoughts?

Is there anyway to troubleshoot the BSOD? Else Im back to installing the OS on the HDD and seeing if thats stable for prolonged period of time.
 
Another BSOD tonight and im losing my rag. Ive just ordered another set of ram, same spec, and a different cpu cooler, as my current one is tough to fit, and blocks the nearest dimm slot. Thinking about it, the issue could quite frankly be anything. When the new kit comes, I am going to rebuild the machine and see what happens. Swap the modular psu lead, change the psu socket the lead goes into.

If that fails I dont know where to go, I srriously doubt my Corsair psu is bad, so im leaning towards mobo or sdd.... God this is annoying, and getting expensive.
 
Sorry MrM missied your last update - and have just got back in.

Will read through thread again and pay particular attention to your last 2 replies and get back later tonight or tomorrow morning.

But i'm inclined to agree with you - in that it's still wide open as to what is the fault - but like you i would be staring hard at the MB/SSD.
 
Last edited:
My original Scythe heatsink did the job fine, but it was a pita to fit. If I am going to potentially be fiddling with ram, then it's easier if I replace it with something with easier access. Ive gone for a Noctua with the 9mm fans.

Last couple of BSODS referenced memory, and ram is cheap, so I thought hell, no loss at adding another 4gb anyway. If I still have problems then it's a tough call. I'm struggling to grasp why the issue could be the Sdd, as surely it can't be that complicated to go wrong, vs the mobo.
 
Noctua cooler and more ram arrived this morning. Followed by a removal of all components and re-installation. Have to say the Noctua NH-U9B SE2 is a great bit of kit. V ery easy to install, far more so than my Previous Scythe, its more noisy though, and 3pin mobo header mean I cant control the speed via bios, which is a minor niggle. However, access to ram is much better. Ive thrown caution to the wind and running 2gb in each slot, firmly pushed in to see what happens. Ive reseated cpu, changed psu cables so hoping if they were one of the annoying causes, I wil have ironed it out. Now just have to be patient and see if a BSOD rears its head.
 
Yeah, so my machine has been on 24/7 since I added the ram and changed the HS and not had a single BSOD, error or anything bad of note, so I am more confident than ever that the issue is solved, though still unable to pinpoint where the problem lay. Have to say the machine is pretty quick now with 8gb of ram and the ssd running in AHCI without issue.

Thanks for following up Plec.

For anyone else reading this, I strongly recommend heatsinks that attach via tightening screws on to a backplate, opposed to clip on, or click and twist locking mechanisms.The Noctua heatsink is machined to perfection, and installion a breeze.
 
Thanks for following up Plec.

Pleasure – I’m pleased to read that you finally seem to have cracked it (that’s probably just introduced multiple BSODs and frazzled the PSU.)

...though still unable to pinpoint where the problem lay.

It may have been a combination of factors – more compatible memory, firmware upgrade, staggered spin etc... so finding the source maybe impossible now (certainly not practical or even recommended for sanity reasons)

For anyone else reading this, I strongly recommend heatsinks that attach via tightening screws on to a backplate, opposed to clip on, or click and twist locking mechanisms.The Noctua heatsink is machined to perfection, and installion a breeze.

Very easy to install, far more so than my Previous Scythe

There is also the outside chance that it was the Scythe causing the problem – if it had the pathetic push pin method of attachment? The insane amount of force sometimes required to get pushpins to grip the MB can cause some MBs to warp considerably. This can then compromise the dimm slots closest to the socket and in turn cause intermittent stability issues.

But who cares - as long as it's stable run with it...
 
Back
Top Bottom