S.O.S computer blue screening on start up!!

Aziebol

Honorable
May 21, 2013
88
0
10,640
Computer starts up and goes to a blue screen that says error detected windows has been shut down to prevent damage.... Then it restarts and I have the option to try and repair it and when that finishes it says no problems were detected.....I have done the followings steps

I have taken out each of the GPUs and tested them separately as well as each RAM module.

Please if you have any ideas I really would appreciate the help!

Just in case it matters my specs are

Amd Fx 8350
MoBo Asus m5a99fx r2.0
2x EVGA GTX 660 signature 2 ftw edition.
8gb Corsair vengeance
 
Solution



if you just type in sfc into the cmd prompt, it should give you the following output:


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\(myuser)>sfc

Microsoft (R) Windows (R) Resource Checker Version 6.0
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

Scans the integrity of all protected system files and replaces incorrect version
s with
correct Microsoft versions.

SFC [/SCANNOW] [/VERIFYONLY] [/SCANFILE=<file>] [/VERIFYFILE=<file>]
[/OFFWINDIR=<offline windows directory> /OFFBOOTDIR=<offline boot directory>
]

/SCANNOW Scans integrity of all protected system...
hmm, can you get the BSOD codes when it happens? That will help narrow down the issue. If you swapped cases there shouldnt be an issue with the processor per se. But check and make sure there is no stress on the video card(s) and whatever heatsink you have on the processor is firmly in place and isnt moving around. Does the computer boot completely into Windows or w/e OS you are using?
 
You can also try to boot to a rescue CD to access some of the logs if you cannot get into the system.

http://www.ultimatebootcd.com/ is one of my favorites for checking out problems, but there are others.

IF you are able to get into the repair screen, you may try going to the command prompt (should be one of the options under advanced) and running:

chkdsk c: /f /r
sfc /scannow /offbootdir=c:\ /offwindir=c:\windows


There may be a problem running those where it is stated that a repair is already in progress. If that is the case you will probably need to use the repair disk I mentioned above to edit the registry to get it let you run the repairs.

Other possible issues are that you could have a bad hard disk. You can check this by seeing if it appears in your bios. If not you may need to reconnect some of the cables in your case and check for any of them to be loose.

 


The only code I see is one that say stop and then 0x00000050 then in parentheses a few much longer ones similar to that. Yeah it boots up normally does the loading windows thing then goes to a screen asking if. I want to repair something or start normally and if I try the repair one it says nothing could be repaired and if I choose start normally it goes to. The blue screen saying error has been detected windows has been shut down to prevent damage to your computer. Then at the bottom it says collecting data for crash dump and initializing disk for crash dump.
 


I am able to open a command prompt window. What should I do from there?
 


The problem is that don't you need to be able to access your computer to be able to figure that out because I am unable to do that.
 



Sorry I am dumb the BSOD code is
STOP Error 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
 



http://answers.microsoft.com/en-us/windows/forum/windows_7-system/blue-screen-bccode50/3786319c-7a40-41dc-bbdc-c74ce1181b82


Ive had this code pop on me quite often for installing bad drivers or even ISO mounting software that didnt install properly.

You may be able to get into the machine in safe mode and remove them.

If you cannot get into safe mode, then once you have that command prompt up (when booted to the repair partition) try typing the sfc /scannow /offbootdir=c:\ /offwindir=c:\windows

That will go through and repair the windows OS files which should allow you to get into safemode.
If not, its time to start slowly pulling off hardware from the machine one at a time to troubleshoot who the problem child is.
 

It's telling me that the thing you said to type into the command prompt isn't correct.

 



if you just type in sfc into the cmd prompt, it should give you the following output:


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\(myuser)>sfc

Microsoft (R) Windows (R) Resource Checker Version 6.0
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

Scans the integrity of all protected system files and replaces incorrect version
s with
correct Microsoft versions.

SFC [/SCANNOW] [/VERIFYONLY] [/SCANFILE=<file>] [/VERIFYFILE=<file>]
[/OFFWINDIR=<offline windows directory> /OFFBOOTDIR=<offline boot directory>
]

/SCANNOW Scans integrity of all protected system files and repairs files
with
problems when possible.
/VERIFYONLY Scans integrity of all protected system files. No repair operati
on is
performed.
/SCANFILE Scans integrity of the referenced file, repairs file if problems
are
identified. Specify full path <file>
/VERIFYFILE Verifies the integrity of the file with full path <file>. No re
pair
operation is performed.
/OFFBOOTDIR For offline repair specify the location of the offline boot dire
ctory
/OFFWINDIR For offline repair specify the location of the offline windows d
irectory

e.g.

sfc /SCANNOW
sfc /VERIFYFILE=c:\windows\system32\kernel32.dll
sfc /SCANFILE=d:\windows\system32\kernel32.dll /OFFBOOTDIR=d:\ /OFFWINDI
R=d:\windows
sfc /VERIFYONLY


youll want to take the sfc /scannow command and add the /OFFBOOTDIR=d:\ /OFFWINDI
R=d:\windows

but the d:\ is going to be what ever drive letter your hard drive is that holds the windows folder. Typically it is your C:\ drive but it could be something else.

A way to find it would be to use cd c: then type dir to list out the folders, if no windows folder is listed then move to the next letter cd d: then type dir. and so on til you find the windows folder.



IF no windows folder is found, then the drive may be dead and youll need to replace it... but since BSOD 50 is typically a bad driver, i would assume that youll come across it.
 
Solution