Im sitting there working away on the computer I just rebuilt not long ago,

Decided to use Libre Spreadsheet to create a table for my PCR500s midi key values, etc...

Never opened it before on this computer after reloading everything.

Went to close out and the computer got real slow-Sonar was open in the background.

I finally got it to close the documents and Sonar and rebooted.

When it finally came up, I made it back into X1 and then it gave me a BSOD.  Couldnt catch what it said cause it was fast.

After coming back up the second time it went into self recovery back to factory.

After doing the initial setup like it does on a new computer it wouldnt log into windows and froze up solid.

Killed it, brought it back up, did a restart and back into recovery it went trying to do a repair.  The message it last had was that "This might take an hour while repairing file" or something to that effect.

Only time will tell if it will come back. 

All them new HDD and now this-Wonderful  

Yikes, that's bad. Fingers crossed that it comes back ok.

Well, that sucks.  Good luck.  

Thanks Guys,

Looking like its the new OS HDD having probs.

Researching it now.   

Error Code 2000-0142

Found a couple threads on attempting to fix that has worked for some.  Just hope I dont have to play the warranty replace game on a new drive   UGHHH

It is COMFORTING after getting back in long enough to see all my projects on the Proj HDD and the Backups on the Backup HDD  were all there and fine    

Currently trying to run a System Image done right after rebuild-Worked good

And trying to do a bootrec.exe. /fxmbr and possibly rebuild if needed of MBR.

Fingers are crossed,  if not the receipt and the box the HDD came in are out and ready  

Currently trying to run a System Image done right after rebuild-Worked good

I assume you are not saving the image to the questionable disc or using Windows System Image. If I had a running system in this situation, the first thing I would do is xcopy any data from the drive onto a backup. A disc image of a questionable system may not restore a good system. Unless you have an imaging program that can extract individual files from the image, your image may not save your data in a usable form.

slartabartfast

Currently trying to run a System Image done right after rebuild-Worked good

I assume you are not saving the image to the questionable disc or using Windows System Image. If I had a running system in this situation, the first thing I would do is xcopy any data from the drive onto a backup. A disc image of a questionable system may not restore a good system. Unless you have an imaging program that can extract individual files from the image, your image may not save your data in a usable form.

No Slart,  Not burning a copy, just reloading so I can try some of the fixes others have done that have worked for them.


I would never be at ease thinking this drive will make it for anything reliable even being new.


I did get it loaded and running.
On the chkdsk/r run it found two bad sectors and loaded a report/file or something.  Havent looked closely at it yet and really arent sure how to at this point LOL   Im learning as I go.


Anyway


chkdsk ran OK
chkdsk/r had them 2 sectors identified
bootrec.exe /fixmbr - I get it is not recognized as an internal or external command, operable program or batch file

So I think I will try a few more things and stop wasting my time farting with it,  box it up and swap it out on the warranty  

Unless you have any good ideas on it?  Im not a comp tech by any means