Solved Really need help, PC no longer working.

[paulpicks21]

Firstly I am not 100% sure this is the correct section to post this so if not then my apologies.


Ok so I used the PC for several hours Friday night, not doing much just chatting on Skype and general surfing.
I shut it down normally and went to bed.

The next day I get up and switch it on, it goes past the post and as soon as windows try's to start it came up with an error - 0xc0000225 and says 'Windows failed to load because the system registry file is missing or corrupt'

I restart it a few times, same issue.

Safe mode won't work nor last known good configuration point.

So I put my windows 7 CD in and attempt to do a repair install at first it didn't work, so I ran it a couple more times and it appeared to do something as the next time it booted it came up with a new error - 0xc0000098

PC still won't boot into windows so I run the repair a few more times but it just say's that it is unable to automatically repair now.

I tried system restore using the CD but that had no effect.

Now to the bit that worries me the most, when in the repair install section if I press 'load drivers' I can then view 'computer', the only drive connected is my M4 and it is showing some strange things.

C: is system reserved 70.2MB free of 99.9
D: is Local disk 26.2GB of 59.5GB (which should be my C: drive)
X: is boot 28.7MB of 31.1MB


I really don't have any idea why its gone wrong and I have no idea how to fix it.

I would much prefer not to have to do a clean install if its avoidable so any help would be great.

Thanks

Paul.

 

[Kaktussoft]

Now to the bit that worries me the most, when in the repair install section if I press 'load drivers' I can then view 'computer', the only drive connected is my M4 and it is showing some strange things.

C: is system reserved 70.2MB free of 99.9
D: is Local disk 26.2GB of 59.5GB (which should be my C: drive)
X: is boot 28.7MB of 31.1MB

X is a ramdisk with your current " recovery environment" .
D is your C-drive in wondows. No problem at all.
System reserved is also normal.

 

[Kaktussoft]

Firstly I am not 100% sure this is the correct section to post this so if not then my apologies.


Ok so I used the PC for several hours Friday night, not doing much just chatting on Skype and general surfing.
I shut it down normally and went to bed.

The next day I get up and switch it on, it goes past the post and as soon as windows try's to start it came up with an error - 0xc0000225 and says 'Windows failed to load because the system registry file is missing or corrupt'

I restart it a few times, same issue.

Safe mode won't work nor last known good configuration point.

So I put my windows 7 CD in and attempt to do a repair install at first it didn't work, so I ran it a couple more times and it appeared to do something as the next time it booted it came up with a new error - 0xc0000098

PC still won't boot into windows so I run the repair a few more times but it just say's that it is unable to automatically repair now.

I tried system restore using the CD but that had no effect.

Now to the bit that worries me the most, when in the repair install section if I press 'load drivers' I can then view 'computer', the only drive connected is my M4 and it is showing some strange things.

C: is system reserved 70.2MB free of 99.9
D: is Local disk 26.2GB of 59.5GB (which should be my C: drive)
X: is boot 28.7MB of 31.1MB


I really don't have any idea why its gone wrong and I have no idea how to fix it.

I would much prefer not to have to do a clean install if its avoidable so any help would be great.

Thanks

Paul.

win7 doesn't have a repair install option at all!! So what are you talking about??

And only has an option to upgrdate install, which is actually mostly the same. But that can only be performed from within windows!! So what did you do and how did that finish? I think you made things worse

 

[Kaktussoft]

First thing to do is check your disk for errors from within "recovery environment"

chkdsk/f C:
chkdsk/f D:

any errors?

 

[Kaktussoft]

So I put my windows 7 CD in and attempt to do a repair install at first it didn't work, so I ran it a couple more times and it appeared to do something as the next time it booted it came up with a new error - 0xc0000098

Did you try startup repair 3 times with boots in between? Can you post your bootmenu (bcd) here?

just copy C:\boot\bcd to an usb-stick and transfer to working pc. so the file from "system reserved" partition!

 

[paulpicks21]

Sorry yes, my mistake I typed the wrong thing.

I meant start up repair.


I will try what you said.

 

[Anak]

Hi Paul,

If possible, I would like you to show a snip of how your Disk Management is laid out.

Type/copy/paste devmgmt.msc into either the Start/Search box or the Run box (preferred)

When Computer Management opens, go to Storage, open it, and click on Disk Management.

From there you should be able to to take the snip.

If you have any external HDD's try to show them also.

 

[Kaktussoft]

first thing to do is "system restore" to a date prior to problems

 

[paulpicks21]

Ok the bcd -


Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {2eb6f770-f04a-11e0-b905-ab4871cd5c8b}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {2eb6f76e-f04a-11e0-b905-ab4871cd5c8b}
device ramdisk=[D:]\Recovery\2eb6f76e-f04a-11e0-b905-ab4871cd5c8b\Winre.wim,{2eb6f76f-f04a-11e0-b905-ab4871cd5c8b}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[D:]\Recovery\2eb6f76e-f04a-11e0-b905-ab4871cd5c8b\Winre.wim,{2eb6f76f-f04a-11e0-b905-ab4871cd5c8b}
systemroot \windows
nx OptIn
winpe Yes

Windows Boot Loader
-------------------
identifier {default}
device partition=D:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
osdevice partition=D:
systemroot \Windows
resumeobject {2eb6f770-f04a-11e0-b905-ab4871cd5c8b}
nx OptIn

Resume from Hibernate
---------------------
identifier {2eb6f770-f04a-11e0-b905-ab4871cd5c8b}
device partition=D:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=D:
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {2eb6f76f-f04a-11e0-b905-ab4871cd5c8b}
description Ramdisk Options
ramdisksdidevice partition=D:
ramdisksdipath \Recovery\2eb6f76e-f04a-11e0-b905-ab4871cd5c8b\boot.sdi

 

[paulpicks21]

As I said before, system restore made no difference and the pc still fails to boot.


And Anak I cannot get into windows, that is the problem.


Cheers

Paul

 

[Anak]

As I said before, system restore made no difference and the pc still fails to boot.


And Anak I cannot get into windows, that is the problem.


Cheers

Paul

I missed it,

It seems odd that after you shutdown normally, and then have this problem when you go to start up the next day.

Almost seems like a hardware problem. Bad Ram could cause a machine to a hard/no start condition.

I would try removing, and then re-setting the ram sticks, just pull them out, and put them right back in where they came out of.

Has the inside of the case ever been cleaned?

 

[paulpicks21]

As I said before, system restore made no difference and the pc still fails to boot.


And Anak I cannot get into windows, that is the problem.


Cheers

Paul

I missed it,

It seems odd that after you shutdown normally, and then have this problem when you go to start up the next day.

Almost seems like a hardware problem. Bad Ram could cause a machine to a hard/no start condition.

I would try removing, and then re-setting the ram sticks, just pull them out, and put them right back in where they came out of.

Has the inside of the case ever been cleaned?

I did remove both sticks yesterday and tried it with just 1 in at a time to see if the ram was bad. Still the same problem.

Its clean inside.

Thanks

Paul.

 

[paulpicks21]

I have marked this as solved now.

I had no option but to go ahead and reinstall windows in the end.

It is now working 100% fine.


I still don't know what caused the issue which is very annoying but at least my PC works again.



Thanks to all that replied.


Paul.

 

[Kaktussoft]

Nothing wrong with bcd so far as I can see. Still error 0xc0000098 ? even after 3 startup repairs with reboots in between? If so, rebuild the bcd

bcdedit /export C:\BCD_Backup
c:
cd boot
attrib bcd -s -h -r
ren c:\boot\bcd bcd.old
bootrec /RebuildBcd

After that the old bcd is in c:\BCD_BACKUP and in c:\boot\bcd.old as well
You can always go back to old situation by doing:
bcdedit/import c:\BCD_BACKUP

Does system boot after doing the bootrec/rebuildbcd command?

 

[paulpicks21]

Thanks for your reply, but please read my last post above yours.


Regards

Paul.

 

[Anak]

I have marked this as solved now.

I had no option but to go ahead and reinstall windows in the end.

It is now working 100% fine.

I still don't know what caused the issue which is very annoying but at least my PC works again.

Thanks to all that replied.

Paul.

Your welcome!

I was going to reply when I saw you had already re-installed.

The only other situations that I could think of would be, that overnite you may have had a momentary power outage, and the surge when the power came back up may have caused a problem with the SSD's, but with the machine shut down for the night, and your maybe having it connected to a UPS that would be rare to impossible. Although, a startup surge is within the realm of possibility. Bad Capacitors, PSU?


And, I have noticed in this Crashes and Debugging forum that sometimes when the OP has multiple Drives (mixed or not) that the helper will ask the OP to disconnect all but the one that has the original boot, and OS on it to avoid any conflicts with startup.

If memory serves correctly, there have been instances on startup where the main drive will loop back to another drive that has an image of the original, and become confused.

Read post #17 here in the VIP Forum, and whs's reply in #18: Very strange story - I am baffled

 

[paulpicks21]

Thanks for taking the time to help me try and figure out why it happened Anak.

It is a bit of a puzzler!

It was completely shut down for the whole time in between working and not working so I don't think a power surge could have caused an issue.

One of the things I did pretty much straight away was to remove my spinner HDD so I only had the operating system ssd connected.

It was saying some drivers were missing every time I tried to boot, but why they were suddenly missing is a mystery to me.

I don't think I will ever get to the bottom of it, I just hope it was a freak occurrence and never happens again.


Cheers

Paul.

 

[Anak]

Some more thoughts....

How did your memory upgrade go last week?
Are you doing any serious over-clocking? Once problems arise its best to back them down.

Here is some interesting reading about SSD's that I've come across.
The owner of the site Zsolt Kerekes has been involved with SSD's for over 21years.

Of particular interest:
Bad block management in flash SSDs - article StorageSearch.com
Data Integrity Challenges in flash SSD Design
Why Consumers Can Expect More Flaky Flash SSDs!
SSDs vs HDDs? - not exactly says StorageSearch.com
What happens in SSDs when the power goes down suddenly? - reliability architecture article
The SSD Reliability Papers - StorageSearch.com
Storage reliability articles - StorageSearch.com

If you have any previous clones or images of your system, it might be possible to install the latest one before this problem, just to see if you can pick up anything from Event Viewer or even .dmp files.

If you search for instability problems for your two SSD's, you come up with some results, but since they are so new on the consumer market not a lot of answers.

 

[Anak]

Now to the bit that worries me the most, when in the repair install section if I press 'load drivers' I can then view 'computer', the only drive connected is my M4 and it is showing some strange things

Paul, not saying this is related, but I saw this, and wondered if you did too.
http://www.sevenforums.com/news/206828-attention-crucial-m4-ssd-owners.html

 

[paulpicks21]

Some more thoughts....

How did your memory upgrade go last week?
Are you doing any serious over-clocking? Once problems arise its best to back them down.

Here is some interesting reading about SSD's that I've come across.
The owner of the site Zsolt Kerekes has been involved with SSD's for over 21years.

Of particular interest:
Bad block management in flash SSDs - article StorageSearch.com
Data Integrity Challenges in flash SSD Design
Why Consumers Can Expect More Flaky Flash SSDs!
SSDs vs HDDs? - not exactly says StorageSearch.com
What happens in SSDs when the power goes down suddenly? - reliability architecture article
The SSD Reliability Papers - StorageSearch.com
Storage reliability articles - StorageSearch.com

If you have any previous clones or images of your system, it might be possible to install the latest one before this problem, just to see if you can pick up anything from Event Viewer or even .dmp files.

If you search for instability problems for your two SSD's, you come up with some results, but since they are so new on the consumer market not a lot of answers.

Sorry I should have replied to you sooner seeing as you were kind enough to post again.

I didn't do the memory upgrade in the end.

Yes I did have the CPU overclocked at the time and I reverted it back to stock settings before I did the reinstall. It is still stock now.

I only have the M4 SSD in the PC, I put the F60 into my other PC before Christmas. (I will update my system specs in a minute).

In reply to your post regarding the M4 Firmware, I am still yet to update it, however mine has only done a couple of 100hrs so far so nowhere near the 5000 that they state the issue will begin.

I can confirm the PC is still running perfectly since the reinstall so that's good news.

Once again thanks for your help


Paul.