HD isn't recognized after reboot

[GGuyZ]

Hi everyone.

I'm currently at 175FSB on my P-D 805, with Gigabyte GA-8I945P-G-RH Motherboard. 3.5Ghz CPU, 700MHz RAM.

I've ran every possible test and it seems like I'm stable.

However, after installing sound drivers just now and rebooting my pc, my Hitachi SATA II 160GB Hard Disk wasn't recognized by the BIOS.

So I used the stock settings instead of my overclocked ones and then things came back to normal. I rebooted again and returned to my current overclock status and everything seems fine now.

But, this worries me quite a bit. What could be the cause, and is this a sign of instability?

An important note: It seems like my Motherboard doesn't have a PCI lock. Nevertheless, in worst case it's supposed to run at 35MHz. that isn't too high is it? and my system IS stable with all the testing programs.
so is there any other cause to this?

 

[GGuyZ]

Try another SATA port if you're using the Intel I/O controller (ICHx)
On some motherboards only a few SATA ports is at locked frequency.

Thank you for you reply!

I'm afraid I tried that already. I've asked in some other forum and was told that it won't help in my specific motherboard.

Also from Gigabyte's FAQ it seems that there's no PCI lock whatsoever on this board. Only dividers at fixed speeds(166,200,266).

Is the cause the 'high' PCI clock? should I underclock?

 

[GGuyZ]

I see that you've answered both of my threads, and I truly thank you for your help in both matters!

I've already exceeded my budget by WAY too much when getting this PC. I really can't afford anything else now.

Also, Unforunately we don't have an ebay kind system where I am from, so selling is a problem too.

I know this is hard to work with, but I've seen many good reviews and succesful overclocks with this board on newegg and other sites.

I just tried changing the ports physically and the problem still occurs.

Could it be because of my recent BIOS update? I've received an unreleased BIOS(version F4) from gigabyte to try solving the problem on my other thread. Maybe it just created this new problem? It didn't solve the other problem either so I don't mind rolling back to a previous BIOS.

 

[Whitman]

I'm not 100% sure this applies here, but..

I have a custom-built rig with a SATA HD. Every single time I Reset it, it comes up with BSOD. Scared the S*** out of me the first time, as I paid premium for a computer that just, you know - works. I have a theory that for some reason when I hit the Reset-button, the SATA drivers aren't loaded properly before the system starts looking for a HD, fooling the system into thinking that there IS no HD. The solution? To turn the computer off, then back on - and everything is peachy.

I hope that helps.

 

[GGuyZ]

thank you.

Yet I'm afraid this doesn't help in my case. I need to either clear the CMOS or load defaults for the PC to work. then I can go back to my previous overclocked state until the next time it happens.

I'm wondering... could it be a result of the unreleased BIOS I received from gigabyte?

 

[GGuyZ]

I can't say that for sure. I have bought this PC a week ago, and I stabilized my system a couple of days ago. During the entire overclocking period I never encountered this with version F3(last published stabled version). Yesterday I received this new unpublished F4 version from Gigabyte's support. After a few hours when I rebooted this problem occured for the first time. It has happend several more times since then.

Moreover, it screwed up my channel 0/1/2 IDE settings.
So I guess it's possible that it is the BIOS and not the absence of a PCI lock?

One thing that is good with this BIOS version is that I (sometimes) CAN use the 3x multiplier. But then windows seems to give me problems, so I guess I should just forget about that. It just gives me a little hope for the future that they might fix all of their issues.