SSD + overclocking a bad mix

Associate
Joined
20 May 2006
Posts
1,029
Location
London
Since getting an Agility 3 60GB I have had many BSOD's.
Have updated firmware to 2.09.
My Q9550 on a P5Q-E was 100% stable at 3.4GHz 400 x 8.5 FSB strap 400.
I ran 24/7 @ 3.83GHz 445 x 8.5, FSB strap 333 but would BSOD with Hal.dll +ntoskml.exe error on reboot after program/windows update.
[previous C:\ RMA'ed due to bad sectors]

The higher setting has proved to be v unstable BSOD at least once a day.
Today on advise in OCZ forum I cleared CMOS by removing battery. Reset BIOS settings manually.
PC would not boot on higher setting, would not pass post until I changed FSB strap to 400MHz. Crashes within 5 minutes of running BOINC + F@H yet passed intel burn test for 26 mins on max settings:confused:

Q Is this just another problem with the OCZ SSD/sandforce controller or are ssd's in general sensitive to overclocking?

It is connected via a Startech controller card in PCIE 2.0 slot. This has a Marvel controller & I know the the P67 mobo have had an issue & OCZ says use MSAHCI driver not intel/marvel, I'm on MSAHCI.

Should I reinstall Windows or rma this SSD & get another brand/give up on SSD for my P45 mobo?

Thanks
 
Thanks for the replies.
The wasted hours trying to get this to work:mad:
Stable @ 3.4GHz at present but to sacrifice nearly 400MHz for this ssd seems too much.
 
Hey P....

Don't want to rain on your parade, but I'm running two OCZ's (60GB Vertex 2E's) in Raid 0 on a Asus RE3 with WinXP Pro........no issues whatsoever. Never needed to update firmware etc.

Is there anyway to check the drive for errors or imminent failure?
 
Are your bios profiles exactly the same except for the oc?

I was getting bsod with my new Crucial M4 and it was driving me nuts. Turned out I had contoller as IDE in the bios when I installed windows and I'd changed it to AHCI after the install. Windows didn't like it at all. Changed it back to IDE in the bios, used regedit to change the windows setting to AHCI and then changed the bios. Worked fine since. Anyway, sorry to butt in.
 
Last edited:
I can't claim to fully understand these things but from my limited knowledge I can't see how an SSD would be affecting your overclock. Never heard of such an issue before either, the only thing out of the ordinary would be that you are connecting through a PCI-E card. Dunno why that would cause a problem but perhaps trying plugging it into the mobo.

Could just be the SSD being faulty, heard lots of things about these Agility 3's dunno if it was all cleared up?
 
Hi Loudbob - both crystal disk infor & this
SSDLife.png


Was 11 years the other day. NB I have the Agility 3 only errors are the firmware 2.02, 2.06, 2.08[withdrawn!] & 2.09 which will no doubt be replaced before too long & the sandforce controller:eek:
 
At the start I made sure I was on AHCI with only th ssd connected. Followed the OCZ setup guide.
Will try it on mobo sata port tomorrow to eliminate the card as a problem.

Pretty sure its the ssd that is duff, I'm one of the unlucky ones as a lot are running just fine. Doubt they will get repeat business from me. However I think Sandforce should take a lot of the blame as they have caused problems for Corsair as well.
 
No, I wouldn't blame SSD. Yet.
Try to:
0) Go to skick Q9550 value (2.83)
1) download Ubuntu, any of the latest versions, and burn DVD/CD
2) physically unplug your SSD
3) overclock your system to max you want (3.8 ?)
4) boot from that burnt DVD/CD
5) pick MemTest from BootMenu, wait for 2-3 full cycles
6) See if BSOD appears

P.S.
I hope you've got SATA Spread Spectrum (as other spreads too) disabled in your BIOS.
 
Last edited:
Thanks for your help, guys,

Run Memtest 4.10 OK
In the wee small hours it suddenly dawned on me that before I was aware there was a firmware issue with the ssd I had upgraded the bios:o
Reverted to the old one, I think, & hey presto! Have booted into windows at old high settings passed intel burn test & have been running BOINC for nearly 1 hr. Fingers crossed.

I should have had a secretary keeping track of what I had done.
 
RMA the SSD mate, had 2 Agility 3s even after a wipe and FW update still bluescreened on a stock rig. The system works fine with a 2E 90Gb.
 
Thanks Toxic:)

Had a BSOD after reboot today wuth the usual hal.dll + ntoskml.exe error, was hoping these would go away with the new SSD as old hdd had been rma'ed with bad sectors.
Have put PCIE back to 103MHz & upped NB volts to 1.42 from 1.4. Desktop seems a bit more responsive with BOINC running.
Will see what happens after next weeks Win updates.
I think the SSD is working ok as no crash during use for 4 days.
 
Back
Top Bottom