• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

BSOD Then Corrupted SSD?

J

Justintoxicated

[H]F Junkie
Joined
Apr 10, 2002
Messages
14,522
Woke my computer up this morning and got the BSOD.

Rebooted and checkdisk delted a bunch of files.

Anyways to figure out what those were? When it restarted I got an error about windows media player lib being corrupted.

Intel tools cand crystal disk info say the HD is fine but is my 160GB Intel SSD going bad?

Probably going to restore the whole drive from backup but I'd like to see which files chkdsk deleted first if there is a way to do that.
Thanks,
 
Justintoxicated said:
Woke my computer up this morning and got the BSOD.

Rebooted and checkdisk delted a bunch of files.

Anyways to figure out what those were? When it restarted I got an error about windows media player lib being corrupted.

Intel tools cand crystal disk info say the HD is fine but is my 160GB Intel SSD going bad?

Probably going to restore the whole drive from backup but I'd like to see which files chkdsk deleted first if there is a way to do that.
Thanks,
Click to expand...

Have you checked the system logs?
 
staticlag said:
Have you checked the system logs?
Click to expand...

Yes it kept repeating system error until I ran check disk. So I ran it it and deleted a bunch of files. I would like to know what they are any why it might have happened before restoring from WHS.

I have over 11 thousand errors that say

"The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume1."

Now I am overclocked to 3.2 ghz on this q9450 and have been for over 8 years at stock voltage with at least 90% of BSOD's over the years (seriously 8 fin years) being due to creative soundcard drivers for teh X-fi. However if anything I have a feeling that this might be more to having the drive completly full (4GB free)?

Never had a problem like this before though. I'm planing to restore asap but want to see which files were corrupted first.
 
Too many possibilities. I will just name a few and let you guess where:
  • SSD going bad
  • Cables bad
  • ICH bad or not set to AHCI
  • Drivers or Intel matrix version newer than 8.9 in use
  • Unstable OC (CPU or RAM)

Older system that was never really designed for SSD. Not saying that's whats wrong but I am saying the obvious, older system, expect issues.
 
Lost-Benji said:
Too many possibilities. I will just name a few and let you guess where:
  • SSD going bad
  • Cables bad
  • ICH bad or not set to AHCI
  • Drivers or Intel matrix version newer than 8.9 in use
  • Unstable OC (CPU or RAM)

Older system that was never really designed for SSD. Not saying that's whats wrong but I am saying the obvious, older system, expect issues.
Click to expand...

Not designed for SSD?
What about that comment on drivers newer than 8.9 . The newest drivers are bad?
Ok so lets forget the cause I guess since I will never know. System seems to be running fine now. I'm wondering if I should bother with a system restore as I believe these are hard on SSD drives, especially when the drive is full.

Is there a way to tell which files were deleted by chkdsk?
 
Last edited:
Justintoxicated said:
Yes it kept repeating system error until I ran check disk. So I ran it it and deleted a bunch of files. I would like to know what they are any why it might have happened before restoring from WHS.

I have over 11 thousand errors that say

"The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume1."

Now I am overclocked to 3.2 ghz on this q9450 and have been for over 8 years at stock voltage with at least 90% of BSOD's over the years (seriously 8 fin years) being due to creative soundcard drivers for teh X-fi. However if anything I have a feeling that this might be more to having the drive completly full (4GB free)?

Never had a problem like this before though. I'm planing to restore asap but want to see which files were corrupted first.
Click to expand...

8 years eh?
http://ark.intel.com/products/33923

Q9450 was released in Q1 08:confused:
 
This sounds like a huge mess.
I'd get rid of the OC to start, and run the intel SSD toolbox to figure out if there is any issues with the drive.
I'd back up as much data as I can, because you never know when more of its going to "disappear", from the state of the system you have now.
I would also run a memory test.

In my opinion, It seems like a terrible idea to add unpredictability to your storage by overclocking the CPU, especially when the hardware is totally sufficient before OC.
The fact that is has been BSODing off and on for years speaks very poorly of it as well.
A computer that is working properly should never BSOD, and I wouldn't ever trust any of my storage if it had a single BSOD like that.

My advice to you is get as much data out of the old system as you can, run away from all the hardware, and build something new for reliability.
Consider a new system with ECC memory, definitely no overclock, and a good power supply with a in-line battery backup.

Then consider a system (external disks, another computer, etc) as a regular backup for your important data.
For the old hardware, systematically test all of it if you're going to consider re-using it.
 
Last edited:
hotcrandel said:
This sounds like a huge mess.
I'd get rid of the OC to start, and run the intel SSD toolbox to figure out if there is any issues with the drive.
I'd back up as much data as I can, because you never know when more of its going to "disappear", from the state of the system you have now.
I would also run a memory test.

In my opinion, It seems like a terrible idea to add unpredictability to your storage by overclocking the CPU, especially when the hardware is totally sufficient before OC.
The fact that is has been BSODing off and on for years speaks very poorly of it as well.
A computer that is working properly should never BSOD, and I wouldn't ever trust any of my storage if it had a single BSOD like that.

My advice to you is get as much data out of the old system as you can, run away from all the hardware, and build something new for reliability.
Consider a new system with ECC memory, definitely no overclock, and a good power supply with a in-line battery backup.

Then consider a system (external disks, another computer, etc) as a regular backup for your important data.
For the old hardware, systematically test all of it if you're going to consider re-using it.
Click to expand...

1) system is not fast enough without being overclocked.
2) About the overclock. System has passes memtest, and a 36 hour intel CPU Burn test. It is stable. Well, other than the sound card. But theres nothing I can do for the sound card except stop using it. I don't think this has anything to do with the OC and it's just a drivers issue. CPU needs no extra voltage to maintain this stability. Any computer I have ever used can lock up or bluescreen over 8 years, this does not indicate an unstable OC it simply indicates that software is not perfect.
3) ECC Memory would be overkill what would I need that for?
4) Everything is already backed up on Windows home server. I just wanted to see what files were deleted by chkdsk so ic ould see if it was anything important before I write the entire contents from a backup to the disk. (This is one thing that will wear out an SSD faster than usual).
5) My next system will be overclocked as well.
 
Justintoxicated said:
  1. Not designed for SSD?
  2. What about that comment on drivers newer than 8.9 .
  3. The newest drivers are bad?
  4. Ok so lets forget the cause I guess since I will never know. System seems to be running fine now.
  5. I'm wondering if I should bother with a system restore as I believe these are hard on SSD drives, especially when the drive is full.
  6. Is there a way to tell which files were deleted by chkdsk?
Click to expand...
  1. ICH10R chipset, fast and great on good boards. Must be used with IM version 8.9, later versions were unstable on early ICH10R and older chipsets. These are and were designed for HDD's, SSD's were not around. DFI boards are nothing special either. The fact you are also using OC RAM screams novice, no offense.
  2. See Above
  3. See Above
  4. Cause was likely unstable system and/or OC, possibly used with sleep.
  5. System Restore should have been turned off years ago if on a SSD... By the sounds of it, your SSD might be in a poor state.
  6. File history.



Justintoxicated said:
1) system is not fast enough without being overclocked.
2) About the overclock. System has passes memtest, and a 36 hour intel CPU Burn test. It is stable. Well, other than the sound card. But theres nothing I can do for the sound card except stop using it. I don't think this has anything to do with the OC and it's just a drivers issue. CPU needs no extra voltage to maintain this stability. Any computer I have ever used can lock up or bluescreen over 8 years, this does not indicate an unstable OC it simply indicates that software is not perfect.
3) ECC Memory would be overkill what would I need that for?
4) Everything is already backed up on Windows home server. I just wanted to see what files were deleted by chkdsk so ic ould see if it was anything important before I write the entire contents from a backup to the disk. (This is one thing that will wear out an SSD faster than usual).
5) My next system will be overclocked as well.
Click to expand...

  1. Might be time to upgrade whole system or a QX9650 could have made a home in there.
  2. MemTest is NOT a guide by any means, flogging a system with 36 hours of IBT means little more than you have shortened the CPU's life. I don't know what your issues with the sound card are but there might be a warning there of an unstable PCI bus thanks to your OC. Lets breakdown your OC; Q9450 with max of 8x Mx means you should be running 400 host clock for a 1600FSB. Now add in the OCed RAM of PC2-8800 (DDR-II 1100) that will be stressing the X48 as you have all four DIMMs filled. DDR-II 800 is more than fast enough to flood a 1600FSB and no gain other than an e-penis extension. Stock voltage doesn't gain anything either and a smart man, uses a little extra for stability, especially when Sleep is used on the OS of when higher FSB's are used as cold-starting some boards can be a pain in arse. Oh, and your sig says 48 hours of IBT, dude, your figures and facts are not adding up.
  3. ECC is not support nor ever was on your platform.
  4. If it is backed up, nuke the system and see what a fresh load will give you. This time, look at your setup and the way you use a SSD. I am putting money on there being System Restore and Page File still being on the SSD along with other tweaks missed. Likelihood that you have the ICH in RAID mode as well and a lack of TRIM.
  5. Might be a suggestion to revisit OCing basics as I can see you have missed a few.

This all being said, this is a storage forum, the rest has been brought up as you wanted answers why you had a crash with corruption.
 
Lost-Benji said:
  1. ICH10R chipset, fast and great on good boards. Must be used with IM version 8.9, later versions were unstable on early ICH10R and older chipsets. These are and were designed for HDD's, SSD's were not around. DFI boards are nothing special either. The fact you are also using OC RAM screams novice, no offense.
  2. See Above
  3. See Above
  4. Cause was likely unstable system and/or OC, possibly used with sleep.
  5. System Restore should have been turned off years ago if on a SSD... By the sounds of it, your SSD might be in a poor state.
  6. File history.



  1. Might be time to upgrade whole system or a QX9650 could have made a home in there.
  2. MemTest is NOT a guide by any means, flogging a system with 36 hours of IBT means little more than you have shortened the CPU's life. I don't know what your issues with the sound card are but there might be a warning there of an unstable PCI bus thanks to your OC. Lets breakdown your OC; Q9450 with max of 8x Mx means you should be running 400 host clock for a 1600FSB. Now add in the OCed RAM of PC2-8800 (DDR-II 1100) that will be stressing the X48 as you have all four DIMMs filled. DDR-II 800 is more than fast enough to flood a 1600FSB and no gain other than an e-penis extension. Stock voltage doesn't gain anything either and a smart man, uses a little extra for stability, especially when Sleep is used on the OS of when higher FSB's are used as cold-starting some boards can be a pain in arse. Oh, and your sig says 48 hours of IBT, dude, your figures and facts are not adding up.
  3. ECC is not support nor ever was on your platform.
  4. If it is backed up, nuke the system and see what a fresh load will give you. This time, look at your setup and the way you use a SSD. I am putting money on there being System Restore and Page File still being on the SSD along with other tweaks missed. Likelihood that you have the ICH in RAID mode as well and a lack of TRIM.
  5. Might be a suggestion to revisit OCing basics as I can see you have missed a few.

This all being said, this is a storage forum, the rest has been brought up as you wanted answers why you had a crash with corruption.
Click to expand...


There was some great info in your post, up until you started insulting me and telling how you "think" I should overclock (adding extra voltage just to help with stability). The Hardlite calling the 11 year member a newb for buying overkill memory is quite amusing. I actually spent a few weeks alone adjusting adjusting GTLs for maximum stability by taking measurements directly off the board and running tests. Adding core voltage did nothing for this particular CPU other than making it run hotter, while adjusting GTLs brought the stability up. I would get an error after 24 hours of IBT but with adjjusted GTLs I would not error out for over 48 hours when I ended the run. Burn test works the CPU yes, but shortening the life any significant amount not true with the proper cooling, it also is a proof of stability as other with Q series CPUs without any overclock can fail that test.

Thanks for the tip on the drivers the board though, I'm using ICH9R with driver version 6.1.x. Been using AHCI mode and Trim for a very long time.
 
Last edited:
Justintoxicated said:
Thanks for the tip on the drivers the board though, I'm using ICH9R with driver version 6.1.x. Been using AHCI mode and Trim for a very long time.
Click to expand...
Thanks but it is clear you have a little more homework to do. On the ICH9R, the latest and stable release was 8.9. The first release to enable TRIM was in the 11.X series. Version 6.X does not or has never supported TRIM let alone full performance of a HDD let alone a SSD.

Justintoxicated said:
There was some great info in your post, up until you started insulting me and telling how you "think" I should overclock (adding extra voltage just to help with stability). The Hardlite calling the 11 year member a newb for buying overkill memory is quite amusing. I actually spent a few weeks alone adjusting adjusting GTLs for maximum stability by taking measurements directly off the board and running tests. Adding core voltage did nothing for this particular CPU other than making it run hotter, while adjusting GTLs brought the stability up. I would get an error after 24 hours of IBT but with adjjusted GTLs I would not error out for over 48 hours when I ended the run. Burn test works the CPU yes, but shortening the life any significant amount not true with the proper cooling, it also is a proof of stability as other with Q series CPUs without any overclock can fail that test.
Click to expand...
Sorry, but I see a blind ego here and not much more. Boards are the biggest impact on any generation CPU, not the CPU itself.
For the record, I have had under my belt the following CPU's with OC's:
  • 2x Q6600
  • 3x Q9450
  • 6x Q9550
  • 2x QX9650
  • 1x Q8200
  • 1x Q9770
  • Heap of E series duals
I also have a Q8400 on a X38-DS5 with an ICH9R holding my 45TB server smooth and stable and has been for over 18 months.
Take it or leave it, I don't care.


As for the comment on "Rank", get over yourself. I may not have been in [H] for as long like many others, doesn't mean I haven't been around in the game for same time, I have many years on you if you want to think of it like that. You have just made it clear to myself and others, your a tool if you have that sort of mentality or attitude.

Don't come asking rather simple and obvious questions if you don't like the answers.
 
If you overclock AND it causes BSODS and other problems AND you refuse to even consider that overclocking may be the root cause of your problems, you will never fix anything.

As for your question as to how you tell what files checkdisk deleted, I don't know the answer but I'm kinda surprised it's been ignored up to now. Somebody will probably come along shortly with the answer.

And BTW, I once had problems like you describe that was caused by overclocking. It took a year for me to see the light. Once I was convinced beyond any doubt that OC was indeed the culprit I vowed to never OC again and I haven't. But that's just me.
 
Lost-Benji said:
Thanks but it is clear you have a little more homework to do. On the ICH9R, the latest and stable release was 8.9. The first release to enable TRIM was in the 11.X series. Version 6.X does not or has never supported TRIM let alone full performance of a HDD let alone a SSD.

Sorry, but I see a blind ego here and not much more. Boards are the biggest impact on any generation CPU, not the CPU itself.
For the record, I have had under my belt the following CPU's with OC's:
  • 2x Q6600
  • 3x Q9450
  • 6x Q9550
  • 2x QX9650
  • 1x Q8200
  • 1x Q9770
  • Heap of E series duals
I also have a Q8400 on a X38-DS5 with an ICH9R holding my 45TB server smooth and stable and has been for over 18 months.
Take it or leave it, I don't care.


As for the comment on "Rank", get over yourself. I may not have been in [H] for as long like many others, doesn't mean I haven't been around in the game for same time, I have many years on you if you want to think of it like that. You have just made it clear to myself and others, your a tool if you have that sort of mentality or attitude.

Don't come asking rather simple and obvious questions if you don't like the answers.
Click to expand...

Thanks for the input but how can that be right? When I check to see if trim is enabled using fsutil it says it is enabled so how can trim NOT be working?

I did some more research and it shows that 11.x versions allow trim support when running Raid. I am not running raid, and never said I was. Trim support should work fine in win 7 + intel SSD in a non-raid setup.

Second, I do get annoyed when I come in asking a question and everyone blames everything right away on being overclocked (and have been for many years now) then continue on to insult me and call me a newb and I must not know what I am doing with overclocking because I didn't just add some more voltage for good measure... BTW the one who mentioned "Rank" first not me when calling me a newb, and now resorting to throwing insults and name calling on an internet forum really starts to show your maturity level.


Deadjasper said:
If you overclock AND it causes BSODS and other problems AND you refuse to even consider that overclocking may be the root cause of your problems, you will never fix anything.

As for your question as to how you tell what files checkdisk deleted, I don't know the answer but I'm kinda surprised it's been ignored up to now. Somebody will probably come along shortly with the answer.

And BTW, I once had problems like you describe that was caused by overclocking. It took a year for me to see the light. Once I was convinced beyond any doubt that OC was indeed the culprit I vowed to never OC again and I haven't. But that's just me.
Click to expand...

I Understand your point but also consider that BSOD is very often a software or driver issue. Yes maybe I'm starting to suddenly become less stable than the past too. However just because you get a BSOD does not mean it is because you are overclocked, and typically it would not corrupt a hard drive, although I admit long ago I had that happen before. In my case the BSODs error codes are documented online and experienced by many people with the same creative sound card. They don't happen often enough for me to be concerned (spaced out by months for the last year, and when the windows install was fresh, and creative drivers were worse it might happen once or twice a year). It is likely that the sound card heats up or may have some software or other hardware issue. I'm on the original windows 7 install from 5+ years ago. I'm working on building a new PC right now, but will need to use this one for a few more months.


Back on topic. I have restored the drive but I'm getting the same corrupted folders no matter how far back I seem to go. I'm thinking it must be an issue with the hard drive or my backup server at this point.
 
Last edited:
So I ran a comparison using beyond compare between my last backup before the corruption ( Z: ) and some older version I used to try to restore my computer from found this:

Code: 
//
// UNINSTALLED SOFTWARE PROGRAM RUN CHKDSK TO CLEAN THIS UP
//
10/3/2013 11:54:54 PM  Unable to load C:\oraclexe\app\oracle\product\10.2.0\server\database: The file or directory is corrupted and unreadable
10/3/2013 11:54:54 PM  Unable to load Z:\oraclexe\app\oracle\product\10.2.0\server\database: The file or directory is corrupted and unreadable
10/3/2013 11:56:54 PM  Unable to load C:\Program Files (x86)\Origin\sounds: The file or directory is corrupted and unreadable
10/3/2013 11:56:54 PM  Unable to load C:\Program Files (x86)\Origin\x64: The file or directory is corrupted and unreadable
10/3/2013 11:56:55 PM  Unable to load C:\Program Files (x86)\Origin\LegacyPM\lang: The file or directory is corrupted and unreadable
10/3/2013 11:56:55 PM  Unable to load Z:\Program Files (x86)\Origin\sounds: The file or directory is corrupted and unreadable
10/3/2013 11:56:55 PM  Unable to load Z:\Program Files (x86)\Origin\LegacyPM\lang: The file or directory is corrupted and unreadable
10/3/2013 11:56:55 PM  Unable to load Z:\Program Files (x86)\Origin\x64: The file or directory is corrupted and unreadable
10/3/2013 11:59:29 PM  Unable to load C:\Users\Justintoxicated\AppData\Local\Origin\Origin: The file or directory is corrupted and unreadable
10/3/2013 11:59:49 PM  Unable to load Z:\Users\Justintoxicated\AppData\Local\Origin\Origin: The file or directory is corrupted and unreadable
10/3/2013 11:59:49 PM  Unable to load C:\Users\Justintoxicated\AppData\Local\Origin\Web Cache\data7\2: The file or directory is corrupted and unreadable
10/3/2013 11:59:49 PM  Unable to load C:\Users\Justintoxicated\AppData\Local\Origin\Web Cache\data7\8: The file or directory is corrupted and unreadable
10/3/2013 11:59:50 PM  Unable to load Z:\Users\Justintoxicated\AppData\Local\Origin\Web Cache\data7\2: The file or directory is corrupted and unreadable
10/3/2013 11:59:50 PM  Unable to load Z:\Users\Justintoxicated\AppData\Local\Origin\Web Cache\data7\8: The file or directory is corrupted and unreadable
10/3/2013 11:59:51 PM  Unable to load C:\Users\Justintoxicated\AppData\Local\PunkBuster\BF3\pb: The file or directory is corrupted and unreadable
10/3/2013 11:59:51 PM  Unable to load Z:\Users\Justintoxicated\AppData\Local\PunkBuster\BF3\pb: The file or directory is corrupted and unreadable
10/4/2013 12:01:09 AM  Unable to load C:\Users\Justintoxicated\AppData\Roaming\TS3Client\logs: The file or directory is corrupted and unreadable
10/4/2013 12:01:14 AM  Unable to load Z:\Users\Justintoxicated\AppData\Roaming\TS3Client\logs: The file or directory is corrupted and unreadable
10/3/2013 11:58:38 PM  Unable to load C:\Users\Justintoxicated\AppData\Local\Temp: The file or directory is corrupted and unreadable
10/3/2013 11:58:48 PM  Unable to load C:\Users\Justintoxicated\AppData\Local\Microsoft\Media Player\Cache2521750: The file or directory is corrupted and unreadable
//
// UNABLE TO REMOVE THE FOLLOWING MIGHT CAUSE ISSUES LATER
//
10/4/2013 12:02:50 AM  Unable to load C:\Windows\SoftwareDistribution\Download: The file or directory is corrupted and unreadable
10/3/2013 11:59:54 PM  Unable to load C:\Users\Justintoxicated\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content: The file or directory is corrupted and unreadable
10/3/2013 11:59:54 PM  Unable to load C:\Users\Justintoxicated\AppData\LocalLow\Microsoft\CryptnetUrlCache\MetaData: The file or directory is corrupted and unreadable
10/3/2013 11:58:40 PM  Unable to load C:\Users\Justintoxicated\AppData\Local\ArmA 2 OA\MPMissionsCache: The file or directory is corrupted and unreadable
10/3/2013 11:58:40 PM  Unable to load Z:\Users\Justintoxicated\AppData\Local\ArmA 2 OA\MPMissionsCache: The file or directory is corrupted and unreadable
10/3/2013 11:57:58 PM  Unable to load C:\Users\All Users\Microsoft\Crypto\RSA\MachineKeys: The file or directory is corrupted and unreadable
10/3/2013 11:57:58 PM  Unable to load Z:\Users\All Users\Microsoft\Crypto\RSA\MachineKeys: The file or directory is corrupted and unreadable
10/3/2013 11:57:43 PM  Unable to load C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys: The file or directory is corrupted and unreadable
10/3/2013 11:57:44 PM  Unable to load Z:\ProgramData\Microsoft\Crypto\RSA\MachineKeys: The file or directory is corrupted and unreadable
10/3/2013 11:56:39 PM  Unable to load C:\Program Files (x86)\Dotjosh Studios\DayZ Commander: The file or directory is corrupted and unreadable
10/3/2013 11:56:39 PM  Unable to load Z:\Program Files (x86)\Dotjosh Studios\DayZ Commander: The file or directory is corrupted and unreadable
10/3/2013 11:56:10 PM  Unable to load C:\Program Files (x86)\Steam: The file or directory is corrupted and unreadable
10/3/2013 11:53:55 PM  Unable to load C:\Development\eclipse\configuration\org.eclipse.osgi\bundles\689\1: The file or directory is corrupted and unreadable
10/3/2013 11:53:55 PM  Unable to load Z:\Development\eclipse\configuration\org.eclipse.osgi\bundles\689\1: The file or directory is corrupted and unreadable

Should I be worried about any of these windows directories? I mean I will be building a new computer in a few months and re-installing everything from scratch at that time.

Oh yea, so my biggest problem is that my backups from the last 2 years are also all corrupted (no matter how far back I go there is corruption), so I went from a corrupt SSD to a corrupt backup. Thanks home server. I mean, at least the computer is usable now, it was unusable before the backup but this still sucks.. I ran a repair on the backup database and I'm thinking to try to restore one more time to see if that fixed anything, probably a great way to wear out an SSD is to keep restoring the drive 3 times a day.... So it appears the backup database is corrupt and needs to be reset, but I'll check if the repair function works fist. (No my server is not overclocked) Glad I have a reliable and trusty backup server! :mad:
 
If the data is corrupt and ALL backups are corrupt it is most likely not the fault of the backup server. But this is one of the problems of incremental backups... if your initial dataset gets corrupted, all depedent data is affected.
I also have a significantly overclocked desktop system, but all data is directly read from a fileserver and directly saved back there. So the chance of data corruptions are slim and filesystem metadata cannot be corrupted by my desktop.
 
Personally I've found that overclocking an SSD and using Acronis for a full (much less incremental) back-up image is nothing but complete failure.

I'm still using WHS1 for backups on an Asus P6T with three 250GB Crucial C300s in RAID0 via an LSI 9260-4 and have never had a problem.
 
I must have tried 12 backups but ended up going back a couple months and was able to find a working backup.

omniscence, I hear you there All my important data is mirrored on 2 other drives on this system and then stored seperatly 2 more times on my WHS server, then also stored again via nightly backups. Of course I'm sure I lost a few minor things (beer recipe, game saves) but I should be able to grab those off the backups with corruption this weekend. Then I lose some large updates I'll have to wait a few more days to download so I don't go over my internet usage :(

Hey Hippie, yea I'm not overclocking my SSD at all, and I didn't even realize they ever tried to release raid drivers for this MB that support trim. Now that I know about them having problems I will be ignoring that feature anyways, that does not sound like a good idea.
 
Lost-Benji said:
Thanks but it is clear you have a little more homework to do. On the ICH9R, the latest and stable release was 8.9. The first release to enable TRIM was in the 11.X series. Version 6.X does not or has never supported TRIM let alone full performance of a HDD let alone a SSD.
Click to expand...

ICH9R supports WAY, WAY newer than 8.9... You, like way too many on this site, seem to be making bad assumptions based on what boards were RELEASED with what OROM version. Assumptions tons of you have made for newer boards like P67, too. I've modded newer OROM versions than that in dozens and dozens of boards. Hell, I've brought ICH7 and ICH8 newer than 8.9. I see this sort of information parroted on this site so much and you are all incorrect. Where are you even sourcing this bad information? If you're talking about being officially supported by Intel, it's true that you won't get that for older chipsets, but what does that matter? When was the last time you actually contacted Intel about an issue with a motherboard built by someone else? I'm guessing the answer for every single person in here is and will always be, "Never."

Go look at the OROMs on station-drivers.com... they, for the most part, state which ICH/PCH versions they'll work with. Edit 2: link http://www.station-drivers.com/index.php/listes-constructeurs/28-intel-sata

I can help integrate these OROMs into some motherboards, though the chipset itself isn't the only limiting factor. Some older machines including several socket 775 boards from Asus, many OEM computers like Dell, etc., only support OROMs up to 64KB in size, which if I remember correctly means 8.7 is the newest version that'll work. On the other hand, Gigabyte boards were easy to do this on at least as far back as P35 chipset (if not further).
 
Last edited:
You must log in or register to reply here.
Back
Top