The Corsair User Forums  

Go Back   The Corsair User Forums > Corsair Product Discussion > Solid State Drives (SSD)

Reply
 
Thread Tools Search this Thread Rating: Thread Rating: 6 votes, 5.00 average. Display Modes
  #1  
Old 04-27-2012, 01:30 PM
Baasha Baasha is offline
Registered User
Baasha's PC Specs
 
Join Date: Dec 2011
Location: USA
Posts: 44
POST ID # = 574996
Baasha Reputation: 10
Angry Corsair Force GT 120GB "Error Occurred" - BSOD --> MS Office DEATH!

I bought a pair of Corsair Force GT 120GB SSDs and set them up as a RAID-0 array for my main (OS) drive late last year.

I've been having problems with these drives intermittently with the message of "Error Occurred" in RED during boot for which I had to go into IRST and reset the drive to "Normal" after which the drive seemed okay.

In fact, last month, the boot sector was corrupted (BCD file in the "Boot" folder) and so I had to do a "repair" install and my system from then on had a "Windows 7 (recovered)" tag in the msconfig.exe window under OS.

Things worked okay but yesterday, when I turned on my computer in the morning, it booted into Windows okay but within a minute caused a BSOD (0xF4) and then I saw the dreaded "Error Occurred" message again. Once again, I used IRST to "clear" the error and reset the disk to "Normal". Upon reboot, the computer automatically ran CHKDSK (I didn't assign it to run) and it found the following (saved in a .log file on the C: drive):

Quote:

Checking file system on C:
The type of the file system is NTFS.
Volume label is ForceGT_RAID-0.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0xe96e2 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0x69ee is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 27118.
206848 file records processed.

File verification completed.
207 large file records processed.

0 bad file records processed.

2 EA records processed.

44 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
271884 index entries processed.

Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file TMP000~1 (2147) into directory file 78926.
Recovering orphaned file TMP0000000F29A89661250FB2D6 (2147) into directory file 78926.
4 unindexed files scanned.

Recovering orphaned file VBE (137853) into directory file 572.
CHKDSK is recovering remaining unindexed files.
2 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...
206848 file SDs/SIDs processed.

Cleaning up 282 unused index entries from index $SII of file 0x9.
Cleaning up 282 unused index entries from index $SDH of file 0x9.
Cleaning up 282 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 27118.
32520 data files processed.

CHKDSK is verifying Usn Journal...
The USN Journal entry at offset 0x5165a998 and length 0x19759600 crosses
the page boundary.
The USN Journal entry at offset 0x5165b000 and length 0xeb851eb8 crosses
the page boundary.
The USN Journal entry at offset 0x5165c000 and length 0x3de056b crosses
the page boundary.
The USN Journal entry at offset 0x5165d000 and length 0x1000005 crosses
the page boundary.
The USN Journal entry length 0x634 at offset 0x5165e000 in file
0xe6c6 is not aligned.
Repairing Usn Journal file record segment.
36435784 USN bytes processed.

Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

234434559 KB total disk space.
115402252 KB in 172165 files.
92920 KB in 32521 indexes.
0 KB in bad sectors.
318851 KB in use by the system.
65536 KB occupied by the log file.
118620536 KB available on disk.

4096 bytes in each allocation unit.
58608639 total allocation units on disk.
29655134 allocation units available on disk.

Internal Info:
00 28 03 00 91 1f 03 00 b1 c4 05 00 00 00 00 00 .(..............
3b 05 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ;...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
After the CHKDSK, it booted to desktop fine and I wanted to start my work (using MS Office). When I opened Excel, I got a popup immediately with a Red "X" saying something along the lines of "Excel needs to shut down". I was like WTF so I clicked "Okay" and it shut down. I tried other MS Office programs and they too immediately gave me the popup and crashed right away.

I was using MS Office Professional Plus 2010 btw.

So, thinking that MS Office was somehow borked, I uninstalled it, ran CC-Cleaner and cleared any extraneous info related to the install and restarted the computer.

I then tried to reinstall MS Office and that's when things went REALLY BAD!

Every time I tried installing MS Office, it would go about 75% of the way and then say "Microsoft Office 2010 Professional Plus encountered an error during setup." I had to exit the install and it never completed. I have tried about 10 times so far to no avail. MS Office just refuses to install!

I have searched online for hours for a solution and NONE of them work. The reason I am posting this here is because all of this started with the SSD giving me that BSOD and "error". As you can see in the CHKDSK log, some files were "deleted" and some sectors were corrupt so I'm wondering if that caused MS Office to die a miserable death!

I am so frustrated because MS Office is vital to my work and I am handicapped without it. I have spent WAY TOO MUCH time on trying to fix this issue and it has lead no where. I bought these Corsair SSDs thinking they would IMPROVE overall performance and instead I've had numerous BSODs, "recoveries", and other issues with errors because of them. I have so many programs and data on my system that reinstalling Windows is really a last resort and would take an inordinate amount of time that I simply don't have. I have the latest Firmware for the SSDs and the latest BIOS update for my motherboard so it has nothing to do with those things.

Unfortunately, although I created some restore points, I turned System Restore off thinking I could still use the restore points once I turn it back on! It turns out that once you turn System Restore (Protection) "off", it automatically deletes all the restore points!

Can someone who is savvy with computers PLEASE HELP ME? I really need to reinstall Office 2010 and then everything will be okay. All other programs are working fine even though Windows has a "recovered" tag on it.

PLEASE HELP!

Last edited by Baasha; 04-27-2012 at 01:36 PM.
Reply With Quote


  #2  
Old 04-28-2012, 08:07 AM
Toasted Toasted is offline
Registered User
 
Join Date: Apr 2011
Posts: 19,337
POST ID # = 575173
Toasted Toasted Reputation: 108
Default

Try this and click Method 4
http://support.microsoft.com/kb/290301/

Even though you uninstalled it, Check if there are any remaining files left behind. Try to reinstall Office 2010.

If that failed
Download Windows Installer CleanUp utility and remove the Office 2010 entries, Then try and reinstall.
http://majorgeeks.com/download.php?det=4459
Reply With Quote


Reply

Tags
bsod, corsair, force gt, ssd

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 04:47 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2018, vBulletin Solutions, Inc.