[DomeD-]

Ok here we go again. I tried to post this before but apparently it didnt work haha.

Ok I have an all-in-one machine here that isnt booting to windows. It is getting an error code BSOD of Critical_Process_Died everytime I turn it on. I have tried to Recover the machine but it is saying that I need recovery media for some reason. Windows 8 shouldnt need recovery media. I also tried to restore it but to no avail it doesnt even start the process just tells me it failed to start. The recovery partition for this machine is only 300 MB's so I assume there is a problem because Windows 8 couldnt possibly fit into that small recovery partition. I tried using Acronis but it isnt compatible with Windows 8 or 8.1 because it hasnt been updated in forever. Acronis 11 btw. I have any information that is needed to help fix this issue please just rely with what info you need and I can obtain it for you. I have every tool possible if nessassary so feel free to ask me to open the machine or anything you can think of that might be the problem. Keep in mind it is an All-In-One so I would rather not open it beacuse its a pain lololol. Please feel free to ask any questions you may have and thank you for any input from anyone :].

Regards,
DomeD-

 

[atminside]

Have you tried booting to a Win8/8.1 DVD/USB and selecting the repair options?

 

[Vagrant Storm]

My guess is memory trouble...possibly hard drive trouble, but I'd try to run a memory test first.

Though what is an "All-in-one" machine? I guess I am not familiar with that term

 

[DomeD-]

Quote:

Originally Posted by atminside

Have you tried booting to a Win8/8.1 DVD/USB and selecting the repair options?

Yes sir. I have tried all the repair options to no avail. The machine says start up repair could not repair anything (along those lines)

 

[DomeD-]

Quote:

Originally Posted by Vagrant Storm

My guess is memory trouble...possibly hard drive trouble, but I'd try to run a memory test first.

Though what is an "All-in-one" machine? I guess I am not familiar with that term

The machine has pasted thorough hardware tests. All hardware inside the computer is sound and working.

 

[atminside]

Quote:

Originally Posted by DomeD-

Yes sir. I have tried all the repair options to no avail. The machine says start up repair could not repair anything (along those lines)

Boot to Memtest86+, run a few loops and let us know what it says.

Also try a chkdsk /f /r on the system drive.

 

[Vagrant Storm]

Quote:

Originally Posted by atminside

Quote:

Originally Posted by DomeD-

Yes sir. I have tried all the repair options to no avail. The machine says start up repair could not repair anything (along those lines)

Boot to Memtest86+, run a few loops and let us know what it says.

Also try a chkdsk /f /r on the system drive.

This is what I meant by memory test. The POST that runs doesn't do any of what memtest will do.

And I'd boot from the install disk and select the admin console and run the chkdsk /f /r there.

 

[DomeD-]

Quote:

Originally Posted by atminside

Boot to Memtest86+, run a few loops and let us know what it says.

Also try a chkdsk /f /r on the system drive.

Okie Dokie! I will try that chkdsk cmd and get back to you. The diagnostic programs I used for testing the units hardware are as followed.
Memory Tests:
Eurosoft QA+: Walking Bit Left and Right Tests Passed, Inverse Walking Left and Right Passed, Checkboard Passed, Bit Stuck Left and Right Passed, MicroTechnology Passed.

HDD: Same EuroSoft QA+: ButterflySeek Passed, Random Read passed, Linear Read Passed, S.M.A.R.T. Status Passed, Extended Tests on all and Passed.

Ran the following scans in a bootable Windows Envernment. Kaspersky 0 Infections. Panda 0, Webroot 0, Spydoc 0.
Clean no infections found. Im running that chkdsk as soon as I finish this post.

 

[DomeD-]

Quote:

Originally Posted by Vagrant Storm

This is what I meant by memory test. The POST that runs doesn't do any of what memtest will do.

And I'd boot from the install disk and select the admin console and run the chkdsk /f /r there.

Thanks for the input my friend! I do not have the discs :/ If I did this would be really easy to fix since I am aloud to restore the entire unit if needed.

 

[DomeD-]

ok ok bare with me as Im not the best with CMD prompts. I go into advanced repair options and I open the cmd prompt it says

x:\windows\system32 I type the cmd and it says the fiel type is NTFS. Cannot lock current drive. Windows cannot run checkdisk on this volume because it is write protected. Do i have to do this cmd in diskpart inside the partition?

 

[Vagrant Storm]

Quote:

Originally Posted by DomeD-

ok ok bare with me as Im not the best with CMD prompts. I go into advanced repair options and I open the cmd prompt it says

x:\windows\system32 I type the cmd and it says the fiel type is NTFS. Cannot lock current drive. Windows cannot run checkdisk on this volume because it is write protected. Do i have to do this cmd in diskpart inside the partition?

add a /x to the command

...actually...you don't need the /f in there if you use /x. I am not sure if it will throw an error if you use both or not though.

here...useful knowledge

 

[atminside]

You have to point to the system drive, which isn't X, before running.

 

[DomeD-]

Quote:

Originally Posted by atminside

You have to point to the system drive, which isn't X, before running.

If you could explain how to do this I would be very thankful!!!!!!!!!

 

[atminside]

Quote:

Originally Posted by DomeD-

If you could explain how to do this I would be very thankful!!!!!!!!!

http://technet.microsoft.com/en-us/magazine/ee872425.aspx
Explains pointing to drives and what the /f and /r modifiers do.

http://support.microsoft.com/kb/300415
Explains usage of diskpart.
Use this to find what letter your system drive is mounted to in the recovery console. It usually isn't C:/

 

[Vagrant Storm]

The full command would be chkdisk C: /r /x

replace the "C" with whatever drive letter you have as your system drive. It is most likely C unless you've purposely changed it.

 

[atminside]

Quote:

Originally Posted by Vagrant Storm

The full command would be chkdisk C: /r /x

replace the "C" with whatever drive letter you have as your system drive. It is most likely C unless you've purposely changed it.

Not when you boot to a recovery disc to run command prompt. It loads the recovery disc as C.

 

[Vagrant Storm]

Quote:

Originally Posted by atminside

Quote:

Originally Posted by Vagrant Storm

The full command would be chkdisk C: /r /x

replace the "C" with whatever drive letter you have as your system drive. It is most likely C unless you've purposely changed it.

Not when you boot to a recovery disc to run command prompt. It loads the recovery disc as C.

He didn't have any disks, though.

 

[atminside]

Quote:

Originally Posted by Vagrant Storm

He didn't have any disks, though.

Download the ISO that matches your OS from Microsoft.
You can also do chkdsk from the recovery boot of the HDD, which he has been in once already.