Windows 7 Prof. (x64) - Startup Failuire

Solved/Closed
Mike - Nov 22, 2011 at 05:57 PM
 Anonymous User - Nov 25, 2011 at 10:34 PM
Hello,

I have Windows 7 Professional 64-bit edition on my desktop. I have a startup up error that the repair tool sometimes cannot find, but sometimes it finds an error on Bugcheck 50 of the Bugcheck analysis phase. With hex parameters = 0xfffff880009aaff8, 0x0, 0xfffff8000327985b, 0x0.

I have done multiple system restores, but that has not solved the problem. Is there anything I can do to solve this without reinstalling Windows?

Thanks
Related:

10 responses

Anonymous User
Nov 24, 2011 at 07:15 PM
Reinstalling OS may be the possible option


If this reoccurs then you may need to check your RAm,change RAM slots and try


your can check your RAM using memtest86+ application. You can download it from the below link.

http://www.memtest.org/
1
I now know this:

http://msdn.microsoft.com/en-us/library/ff559023%28v=VS.85%29.aspx

But I did not change any hardware, and system restore did not work.

This makes me believe either the RAM failed, though my BiOS 'should' tell me so, or a corrupted NTFS problem.

Since I forced the shutdown last time, I think it may be the latter. However when I try to Chkdsk it, it says it is write protected, though I should be the admin. And write protected is by default disabled in BiOS
0
Anonymous User
Nov 22, 2011 at 07:53 PM
Go to

C:/windows/minidump

Upload the dump file to

https://authentification.site

and paste the link here
0
Thanks for replying,

It appears I am in X:\windows\ in cmd prompt, and C: is system reserved. And there is not an X:\windows\minidump that I find from using cd, or dir.
0

Didn't find the answer you are looking for?

Ask a question
Anonymous User
Nov 23, 2011 at 03:51 AM
//startup up error that the repair tool //

which repair tool?


So you have the startup error alone and not the actual blue screen issue

Can you run this and let me know if you find anything suspicious

https://support.kaspersky.com/downloads/utils/tdsskiller.exe
0
I do have the bluescreen error.
0x50

I cannot get Windows up and running on my C drive it seems.
0
Anonymous User
Nov 23, 2011 at 04:34 PM
So you are not able to boot into PC either in safemode or normal mode right?

Boot into recovery console and try to run chkdsk
0
I am not given the option to boot up in safe mode.
0
it won't let me run Chkdsk, it says the disk is write protected.
0
Anonymous User
Nov 23, 2011 at 08:16 PM
Use this command

chkdsk c: /r

ignore any errors and run it
0
The command ran that time. It did not find any file error, but it still stopped with code 0x50.

A strange thing I noticed is it state the total memory on the disk was around 100000 KB (100MB), but I have a 1 TB HDD. Which if this is what the system thinks now for some reason it would mean a page fault error would occur wouldn't it?
0
Reinstalling the OS worked. I must have interrupted an update or something with the force shut down. I appreciate your help. Thanks sundar.
0
Anonymous User
Nov 25, 2011 at 10:34 PM
Thanks for your feedback
0