dual core hotfix?

[cheesegrater]

I would update the BIOS if you haven't done so already. There were some RAID issues with the older eVGA BIOS releases. Your BIOS settings will be reset, so you will have to set them up again.

[NicksFXHouse]

I agree with Cheeze... make sure the BIOS is indeed the latest release and make sure after you flash a BIOS, you power down, unplug the tower, open the tower, clear the CMOS manualy, power back up... go into the BIOS and before you do anything else.. go to the exit screen and select 'load setup defaults' then hit F-10 to save/exit and reboot... set the BIOS up from there.


That error is very specific and I hope is not a harware failure however that one is usually is.

[yf]

"crash" "crash"

when I boot it doday i got a note "windows recoverd from a serios error, and the more info was...hard disc

I'm in the midle of doing the oo defrag passes and a baloon popt up saying "problem with your raid" and some nombers, It whent away to fast to write it down after thet it "hung" i forced the shut down.

agree with Cheeze... make sure the BIOS is indeed the latest release and make sure after you flash a BIOS, you power down, unplug the tower, open the tower, clear the CMOS manualy, power back up... go into the BIOS and before you do anything else.. go to the exit screen and select 'load setup defaults' then hit F-10 to save/exit and reboot... set the BIOS up from there.

saturday midnight some of the links in the website did not work! I was only abble to flash it from with in windows using the nvidia control panal.

so the raid drivers I used the original floopy.

What sould I do now????????????????????

[yf]

the chipset and ntune is the ladest

[NicksFXHouse]

I thought you were installing FSX when this happened.. I am a bit confused. I would not have gone any further after seeing an error like that.

Anyway, it sounds like you either have a corrupt RAID array or one of the drives in the array is defective.

Run CHKDSK /R from the WindowsXP RECOVERY CONSOLE. Boot into the Windows Setup disk and hit R to enter the recovery console. Log into the system as Administrator (unless you have no password then just hit enter)

At the prompt, type CHKDSK /R and allow it to complete. That CHKDSK run ONLY recovers files from corrupt areas of the disk (if possible) and then marks the file allocation table so Windows will never put a file on that spot on the hard disk again. If the problem continues, there is more that one bad spot.

See if it reports finding a problem.

After you run CHKDSK /R from the RECOVERY CONSOLE, you should still verify the disk with the DOS utilitys from the manufacture of the hard drive. CHKDSK does not repair the disk, only the manufactures utility disk has that ability if it is even possible.

You are most likely going that have to start over because once a RAID-0 array is corrupt, there is very little chance of fixing it and know for sure it is fixed. In the event of starting over I would delete the array and have the manufactures DOS utilities disk run on each drive to see if one turns up a defect on the disk. It is also possible you have a defective SATA cable or connector.

[yf]

yah, its both true, I got the blue screen
i got a recover massage, I got the system hung at the point of  the second space defragment at the FSX files.

[NicksFXHouse]

[quote]yah, its both true, I got the blue screen
i got a recover massage, I got the system hung at the point of

[cheesegrater]

This is what I would do...

Update your BIOS, and then set up RAID using the newest drivers. A lot of people had RAID trouble on the 680i chipset. There is a giant thread about it on the eVGA message boards.

http://www.evga.com/community/messagebo ... hichpage=1

Here you can get new BIOS and RAID drivers here.

http://www.evga.com/support/drivers/

Also, use the newest chipset, and audio drivers.

[yf]

may I at least ghost  the array, and whan i finish truble shooting i will ghost it back?

I flash the bios, it saying "no updait"
reconfiguerd the array and I was able to boot again

[NicksFXHouse]

This is what I would do...

Update your BIOS, and then set up RAID. A lot of people had RAID trouble on the 680i chipset. There is a giant thread about it on the eVGA message boards.

http://www.evga.com/community/messagebo ... hichpage=1

Here you can get new BIOS and RAID drivers here.

http://www.evga.com/Support/Drivers/def ... p?switch=2

http://www.evga.com/Support/Drivers/def ... p?switch=2

Also, use the newest chipset, and audio drivers.

DFI stopped their first production run of the Nv680i and ate quite a few motherboards because of stability issues with the chipset. I understand they have another run going now after changes from Nvidia and the design of the board.


If that is true then yf could very well be dealing with a controller issue specific to the motherboard however I would still run those drives through a complete scan to confirm them.



and no yf, I would not do a ghost of anything. Why would you want to save corrupted files to be put back on a partition. You will never know what files are corrupted and what are not. Partition imaging is ONLY done once you have a fully stable install and it has proven itself in combat. After the system has run for a period of time without issues, THEN make a ghost backup.

Doing it now would be like saving a virus and puting back on the drive later.

[yf]

Here you can get new BIOS and RAID drivers here.

http://www.evga.com/Support/Drivers/def ... p?switch=2

http://www.evga.com/Support/Drivers/def ... p?switch=2

none of the links is current.

I download it from here
http://www.evga.com/Support/Drivers/def ... p?switch=2

put it on the floopy hit f6 and windows did not see the files it is looking for...

[yf]

I'm on the phone with evga I will tell you result in a moment...

[yf]

EVGA Tech support saying

It

[NicksFXHouse]

[quote]EVGA Tech support saying

It

[yf]

Well. first I down clock my memory to 800MHz and voltage to 2.100 and I ran the space defrag 3 times, with reboots between each run, all no problem, now I'm did the complete name and it finish in 20 minutes.. I restart and I, doing it again, if I will see any problem one more time, I will think then, to return this will cost restock fee as I