An Overclock too Far - or Memory undervolted ?

Soldato
Joined
20 Aug 2006
Posts
9,779
strange one here please ....

have had PC at 3.5 gig (Q6600) at high vcore - but stable - for last week or so (normally have my PC at 3.3 - but did some cable management dropped the temps a bit and managed to push up to 3.5)

I also found that I could get my memory down to 780 CAS4 at only 1.9V

I thought it was stable, memtest in dos was fine for 30-40 mins (Yes I know I should have tested for longer) - and was small prime stable for > 3 hours.

I haven't had any crashes - or errors in usage over last week (gaming, internet browsing etc)

yet I booted the other day to find one of my 3 drives couldn't be accessed at all (a long chkdsk fixed it to some extent) and one of my other 3 drives had some files at 0kb ...

the odd thing is the files that have become 0kb (some were as big as 20gb originally) - I haven't accessed recently

I thought it could be a HDD failing, but 2 at same time seems odd.

I can only think of 2 things ?

(1) overclocked too high and its ended up with duff data being written to wrong place onHDD thus corrupting some files ?

(2) I undervolted the memory, I thought 1.9V seemed low (as I had had it on 2.1V) - but everything seemed ok. I do have 4 sticks of RAM though so perhaps only in some circumstances the 2nd bank was being used which weren't stable ?

just don't want to loose any more data :( any ideas please ?

not had this problem before with overclocking. What would corrupt files that haven't been accessed ?

I';ve thought the other possibility was PC was accidently turned off at wall while it was in S3 sleep the other day ... could thave have caused problems ?

cheers, Mark.
 
Last edited:
I did have a thought

after the power was removed when it was in S3 sleep ...

I took the computer apart and moved the HDDs ... now its possible after moving they weren't plugged into the same SATA ports ...

now if the drive order changed - and windows was writing to the disks after S3 sleep is it possible it tried to write some data to wrong drives thus corrupting the allocation tables ?
 
Back
Top Bottom