Printable View
I had run a SFC and it encountered corrupted files on my system, that where all corrected... But then, just after, i had run SFC again and he still finds corrupted files that he says it have corrected....:shrug:
And this keep appening no matter how much times i run SFC...
Anyone have a clue?
Could be real, but also could be a false alert.Quote:
Originally Posted by M@G!C
How can this be real ?
If the files get corrupted when getting copied from the disc to your HDD.
Yes i know but im using Windows Vista and SFC doesn´t ask for the disk, it just correct the files.Quote:
Originally Posted by BenchZowner
I think there must be original system files anywhere in the windows folder, that SFC uses this way it doesn´t need the disk.
Reboot at stock fsb 1333 and run sfc again to see if it's a false alert.
Ok. i will do that, when i get home. :up:Quote:
Originally Posted by MateoTTR
I´m at work right now....
This also makes me wonder how system files can possibly get corrupted after a long period of time:Quote:
Originally Posted by BenchZowner
Basically you install your system, you run SFC at first boot and make sure everything is fine. Then how the hell can system files become corrupted a week after, when all those sytem dlls are read-only and should never be written back to disk?
See my point? To corrupt a file you have to write to disk.
All this corruption stuff is very confusing IMHO.
thats true...Quote:
Originally Posted by MateoTTR
the only thing that comes to my mind right away is that maybe data packages get corrupted and the hdd controller then writes them to the wrong sectors on the hdd? so then he basically writes some jibberish into a part of the file, overwriting the original data and hence corrupting it.
I would understand that the registry gets corrupt though, being a kind of database stored in a file that is frequently updated.
GRRRRRRRRRRRR ......:mad: I´m getting pissed with this board....
I was running on 1400QDR and 1800 memory for five days and everything was just fine, no BSOD or any FREEZE at all...
Today i reverted for 1333QDR and 1333 memory to run the SFC to see if the corrupt files apear... and guess what..... gave me BSOD 3 times when i was in windows...
I have run SFC and again same thing he always says he finds corrupted files and that have corrected them again and again...
I just can´t understand what´s going on....
Just 2 words:
CRAPPY BOARD:mad:
Try to understand this guys, maybe something...:eek:
Ok back up without corruption.
1st I went out today & got another 2 new harddrives, installed vista 64 + SP1 all software & games noproblems at all.
2nd Still using same timings ect, no difference at all.
3rd I tried to install new IBM Hitachi Deskstar drives again & corruption all over, nothing but problems. Back to Seagate...
Do I smell hardware problems? Yes Sir 100%
It has nothing to do with my bios settings! All points at different types of drives, trust me.
How can it install on 1 set of drives & not on another?:shrug:
I have had the problems with WD, Seagate, Samsung and IBM drives, both using onboard SATA and Raid, and using a Highpoint SATA Raid card!Quote:
Originally Posted by TheHardCase
So basically if you dont own Maxtor, you screwed? lol
I had no problems with my 7200.9 so far...
I have had corruption with Maxtor drives as well slim, so nope :p:
The issue has nothing to do with the HDDs themselves.
is this corruption problem a matter of luck on getting the motherboard?
Quote:
Originally Posted by GAR
Quote:
Originally Posted by BenchZowner
Yeah I understand.
Cant wait for saturday to torture this board... like I said, is here in my hands already but the challenge will be this saturday night.
-----TO EVERYBODY w/ AIR COOLING-----
What heatsinks are you using for your S2E???
ThermalRight Ultra-120 Extreme currently.
Swiftech MCX159-CU and ThermalRight HR-05 for NB/SB ( not all the time ) [ stock heatsinks are good enough, provided you have a fan over the NB cooler ]
Up SPP voltage to 1.35V and MCP to 1.55V at stock settings (probably good for most setups), cured our data corruption problems with 14 different drives. Now if only that worked at 1600 Sync, we might be getting somewhere. With the VTT tables being borked when clocking up, it is hard to cure that problem with voltages. ;)Quote:
Originally Posted by saaya
and from my previous postQuote:
Up SPP voltage to 1.35V and MCP to 1.55V at stock settings (probably good for most setups), cured our data corruption problems with 14 different drives.
By the way does sfc /scannow take in to account microsoft updates?Quote:
So due to these problems I setup Raid again, but this time I set the stripe block to 128K. In addition I upped MCP(southbridge) from 1.50v to 1.55v.
RLM
OK fellas, ive been running for 2 weeks without ANY issues on my eVGA at 475fsb, i dont wanna jinks myself LOL, everytime i post my stable settings, the next day i get a failure or some sort, anyway here it goes.........
Voltages used are as follows in the bios for other people with similar setup to help you out with 475fsb............Following settings is what i use, my computer sometimes stays on for days, i have played crysis for over 2 hours to test, played team fortress 2 for hours, every game i have thrown at it, handles with no problems, passes prime95 for hours, blend and small....good luck
FSB = 475x8, all spread spectrums disabled, cpu features disabled, P1/P2 enables.
cpu = 1.4250 in windows 1.39idle, 1.33 load
memory = 1.900
fsb = 1.400
spp = 1.500
mcp = 1.600
http://img146.imageshack.us/img146/2581/38ghzjn8.jpg
Thanks for sharing GAR:up:
RLM
Great job GAR on that Q9450, is that about the highest FSB you can get for 24/7 use? Just curious because I've got an Q9550 C1 with similar results (but on my old Blitz Extreme) not on my current S2E. Also can you clarify your VCORE for me please (what do you actually set the VCORE to in BIOS), thanks very much!
I had corruption "problems" on my old nForce4 board.
Solution was extremly simple: Do not install nforce mobo/ide/sata drivers.
It is not the board, or the harddrives - it is the DRIVERS.
How PC work. Read from HDD -> load to RAM -> "process with" CPU -> back to RAM -> write to HDD.
If there is a HDD error - it will corrupt everything. If CPU is unstable - you will notice.
However if its RAM it can be a "bit random". But again - after a few hours of burn-in bench... you will notice.
More likly error occures in the drivers. Silent killer that waits to be triggered.
Why in drivers? There can be many reasons: badly written code, code that reads wrong values, mobo sends wrong values to driver etc etc.
For any data to be corrupted it must first be processed. It can't just "happen" by it self. Why OS? It is accessed each second, on each boot.
And the only place this ACTUALY can happen - in drivers. Anyone tried to look "inside"?:
# SMBus Driver (v4.62) WHQL
# SataRAID Driver (v9.99.09) WHQL
# SataIDE Driver (v9.99.09) WHQL
# RAIDTOOL Application (v9.99.09) "Sedona"
That is whole banch of software just to access the HDD's?
PS: not all hdd's are the same. I bet if you install SCSI disc's you wont get any error.
if its the drivers then why does the corruption only take place after altering the default FSB of the cpu to overclocked levels? im no expert but if it really was that simple then everyone in this thread would be posting their immense overclocking results without corruption instead of asking other users if there are any fixes available or newer bioses to correct the problem.
Maybe, but again who really tested without drivers? I know it worked for me on all previous nForce boards. It just for me it looks like people are trying to adjust their systems so that drivers can "work". I suggest to drop nvidia mobo drivers and let windows do the disc work by it self.Quote:
Originally Posted by andymg350
Amen brotherQuote:
Originally Posted by andymg350
This board is driving me crazy awesome on most accounts except where it really matters...