- Joined
- Feb 19, 2004
- Location
- England Lancashire.
Hey all
The OC'ing of my new CPU a Barton 2600+ goes well and the CPU is standing up to the test no problems
However I fear my Elixir 2700 DDR is not
Twice this happened as follows.
I stepped up the FSB two points from 185MHz to 187MHz and I lost my SATA maxtor drive
1st time it happened, I did the oc restarted my machine from bios booted ok, until I got to desktop and clicked, 'my computer' and saw that my SATA drive wasn't even there anymore, it had disappeared from the listing
So I put the OC back to 185 and things were fine.
Later I tried it again, this time the same thing happened as before, only when I put it back to 185MHz FSB and restarted again, the system did a file check on the SATA drive, and when I finally did get to desktop, I found out that 2 really large dir's on that drive had been turned to just, 'filename.file' with no clear file extention that windows could read.
Even the contents of the dir's in question read, '0mb' but inside, 'my computer' the space that they had used when they were fine, was still missing.
So, I was missing two correct names for 2 dir's, and the space they took up with what was inside them originaly.
Finally I had to keep my oc on the FSB at 185MHz and delete-re partition the SATA drive.
The drive is back up and running fine now and it is working as normal.
I am going to put this down to the ram not coping with the 186 and above oc.
I think it just corrupted the 2 dirs on that disk for whatever reason, I cant even remember now if I had them two dir's open or not after the 1st boot into the desktop running 186MHz oc on the FSB.
Anyways whatever it was, the SATA drive sure didn't like it.
Thinking about it though, it happened right after I upped the FSB 2 points, and both occasions, so it has to be the ram.
Anyone any ideas, anyone thinking I am right about the ram?
007
The OC'ing of my new CPU a Barton 2600+ goes well and the CPU is standing up to the test no problems
However I fear my Elixir 2700 DDR is not
Twice this happened as follows.
I stepped up the FSB two points from 185MHz to 187MHz and I lost my SATA maxtor drive
1st time it happened, I did the oc restarted my machine from bios booted ok, until I got to desktop and clicked, 'my computer' and saw that my SATA drive wasn't even there anymore, it had disappeared from the listing
So I put the OC back to 185 and things were fine.
Later I tried it again, this time the same thing happened as before, only when I put it back to 185MHz FSB and restarted again, the system did a file check on the SATA drive, and when I finally did get to desktop, I found out that 2 really large dir's on that drive had been turned to just, 'filename.file' with no clear file extention that windows could read.
Even the contents of the dir's in question read, '0mb' but inside, 'my computer' the space that they had used when they were fine, was still missing.
So, I was missing two correct names for 2 dir's, and the space they took up with what was inside them originaly.
Finally I had to keep my oc on the FSB at 185MHz and delete-re partition the SATA drive.
The drive is back up and running fine now and it is working as normal.
I am going to put this down to the ram not coping with the 186 and above oc.
I think it just corrupted the 2 dirs on that disk for whatever reason, I cant even remember now if I had them two dir's open or not after the 1st boot into the desktop running 186MHz oc on the FSB.
Anyways whatever it was, the SATA drive sure didn't like it.
Thinking about it though, it happened right after I upped the FSB 2 points, and both occasions, so it has to be the ram.
Anyone any ideas, anyone thinking I am right about the ram?
007