Jump to content

HELP! BSOD After Windows Logo

Go to solution Solved by dragoon20005,

well if safe mode also fails

 

it means the OS is really broken

 

time to re install the OS

 

but first backup the data on the OS disk using another PC

Did not know where to place this so sorry if in the wrong place.

 

Hey,

Today my PC has started to Blue Screen after it gets past the windows start up logo and keeps restarting and doing the same thing.

I have tried booting into Safe Mode and it does the exact same thing. I don't know what is the matter and don't know what to do.

Should I reinstall windows? Is it a hardware issue? Or can it be sorted out straight away?

I will try and get a picture of the BSOD.

My hardware is:
i5 3570k OCed to 4GHz. (I set back to default 3.4GHz but still same)
Gigabyte Z77-D3H
GTX 780
4GB x 2 RAM
Boot drive: 240GB SSD
Normal drives: 460GB SSD, 1TB HDD, 500GB HDD

if you need anything else please ask.

 

0fKJipn.jpg

Link to comment
https://linustechtips.com/topic/200814-help-bsod-after-windows-logo/
Share on other sites

Link to post
Share on other sites

BCCode: 50     0x00000050

Cause

The BCCode 50 usually occurs after the installation of faulty hardware or in the event of failure of installed
hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Resolving the Problem

Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see
if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run
hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's
manual for your computer.

Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so,
contact the manufacturer of the system service about a possible update. If the error occurs during system
startup, restart your computer, and press F8 at the character-mode menu that displays the operating system
choices. At the resulting Windows Advanced Options menu, choose theLast Known Good Configuration
option. This option is most effective when only one driver or service is added at a time.

Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it
does, contact the manufacturer of the program about a possible update.

Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must
restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for
problems between the SCSI controller and the disk.

Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the
device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.

BCCode: 50      0x00000050  <-- read this
http://www.faultwire.com/solutions-fatal_error/PAGE-FAULT-IN-NONPAGED-AREA-0x00000050-*1095.html?order=votes

 

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

 

I would start by checking your Windows Event Viewer, specifically under Application and System, check to see if any changes coincide with your BSOD's. If nothing jumps out at you run MemTest86 to screen any RAM issue's. If there aren't any I would revert back to a previous Windows state and chock it up to something that was installed/changed that you couldn't pin down....if that STILL doesn't work it'll take a considerable amount of digging around.

 

Not sure on the validity of the NTFS corruption they mention, but running Crystal Disk Info never hurt anyone. ***Just make sure not to run CHKDSK/Defrag on the SSD's.***

 

Also may be worth running SFC, directions: http://support.microsoft.com/kb/929833

LanSyndicate Build | i5-6600k | ASRock OC Formula | G.Skill 3600MHz | Samsung 850 Evo | MSI R9-290X 8GB Alphacool Block | Enthoo Pro M | XTR Pro 750w | Custom Loop |

Daily | 5960X | X99 Sabertooth | G.Skill 3000MHz | 750 NVMe | 850 Evo | x2 WD Se 2TB | x2 Seagate 3TB | Sapphire R9-290X 8GB | Enthoo Primo | EVGA 1000G2 | Custom Loop |

Game Box | 4690K | Z97i-Plus | G.Skill 2400MHz | x2 840 Evo | GTX 970 shorty | Corsair 250D modded with H105 | EVGA 650w B2 |

 

Link to post
Share on other sites

BCCode: 50     0x00000050

Cause

The BCCode 50 usually occurs after the installation of faulty hardware or in the event of failure of installed

hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Resolving the Problem

Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see

if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run

hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's

manual for your computer.

Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so,

contact the manufacturer of the system service about a possible update. If the error occurs during system

startup, restart your computer, and press F8 at the character-mode menu that displays the operating system

choices. At the resulting Windows Advanced Options menu, choose theLast Known Good Configuration

option. This option is most effective when only one driver or service is added at a time.

Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it

does, contact the manufacturer of the program about a possible update.

Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must

restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for

problems between the SCSI controller and the disk.

Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the

device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.

BCCode: 50      0x00000050  <-- read this

http://www.faultwire.com/solutions-fatal_error/PAGE-FAULT-IN-NONPAGED-AREA-0x00000050-*1095.html?order=votes

 

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

 

I would start by checking your Windows Event Viewer, specifically under Application and System, check to see if any changes coincide with your BSOD's. If nothing jumps out at you run MemTest86 to screen any RAM issue's. If there aren't any I would revert back to a previous Windows state and chock it up to something that was installed/changed that you couldn't pin down....if that STILL doesn't work it'll take a considerable amount of digging around.

 

Also may be worth running SFC, directions: http://support.microsoft.com/kb/929833

 

Only new bit which was added is Windows Officer 365, no new hardware no nothing.

 

I shall run Memtest, do you know how long I should try it for? An hour? etc

 

If not, I shall check the files and then would you say, possibly reinstalling Windows?

Link to post
Share on other sites

well if safe mode also fails

 

it means the OS is really broken

 

time to re install the OS

 

but first backup the data on the OS disk using another PC

Budget? Uses? Currency? Location? Operating System? Peripherals? Monitor? Use PCPartPicker wherever possible. 

Quote whom you're replying to, and set option to follow your topics. Or Else we can't see your reply.

 

Link to post
Share on other sites

well if safe mode also fails

 

it means the OS is really broken

 

time to re install the OS

 

but first backup the data on the OS disk using another PC

 

So reinstall the OS? I don't really have much I want to safe off it, apart from one or two douments which I need.

 

The last thing I installed with Microsoft Officer 365 from my university, I don't think that could have damaged anything :P

Link to post
Share on other sites

So reinstall the OS? I don't really have much I want to safe off it, apart from one or two douments which I need.

 

The last thing I installed with Microsoft Officer 365 from my university, I don't think that could have damaged anything :P

we dont know for sure what cause the BSOD and you OS cant even go to safemode without crashing

 

i will save the headache and reinstall the OS

Budget? Uses? Currency? Location? Operating System? Peripherals? Monitor? Use PCPartPicker wherever possible. 

Quote whom you're replying to, and set option to follow your topics. Or Else we can't see your reply.

 

Link to post
Share on other sites

we dont know for sure what cause the BSOD and you OS cant even go to safemode without crashing

 

i will save the headache and reinstall the OS

 

Okay wil ldo.

 

If you want to access your data, download Ubuntu or Linux mint live disc.

Regarding your Bluescreen, you could fix it, but it is easier to re install your OS.

 

Hope I have Ubuntu on a disk. SO this would allow me to enter my C drive and get whatever documents I want?

Link to post
Share on other sites

So reinstall the OS? I don't really have much I want to safe off it, apart from one or two douments which I need.

 

The last thing I installed with Microsoft Officer 365 from my university, I don't think that could have damaged anything :P

You would be surprised how much Microsoft can screw up Windows updates :unsure: If you JUST installed Office 365 it should have come with 4-10 updates (can't remember how many I had to sit through). I would say revert back to a previous Windows version that wasn't throwing BSOD's, run all the diagnostics, then try re-installing Office 365.

 

As for the MemTest I would let it run for at least an hour, 2-6 if you want to be really thorough. If RAM was bad I've almost always had it throw errors in the first 15min of testing.

LanSyndicate Build | i5-6600k | ASRock OC Formula | G.Skill 3600MHz | Samsung 850 Evo | MSI R9-290X 8GB Alphacool Block | Enthoo Pro M | XTR Pro 750w | Custom Loop |

Daily | 5960X | X99 Sabertooth | G.Skill 3000MHz | 750 NVMe | 850 Evo | x2 WD Se 2TB | x2 Seagate 3TB | Sapphire R9-290X 8GB | Enthoo Primo | EVGA 1000G2 | Custom Loop |

Game Box | 4690K | Z97i-Plus | G.Skill 2400MHz | x2 840 Evo | GTX 970 shorty | Corsair 250D modded with H105 | EVGA 650w B2 |

 

Link to post
Share on other sites

You would be surprised how much Microsoft can screw up Windows updates :unsure: If you JUST installed Office 365 it should have come with 4-10 updates (can't remember how many I had to sit through). I would say revert back to a previous Windows version that wasn't throwing BSOD's, run all the diagnostics, then try re-installing Office 365.

 

As for the MemTest I would let it run for at least an hour, 2-6 if you want to be really thorough. If RAM was bad I've almost always had it throw errors in the first 15min of testing.

 

Yeah, I do remember doing updates after I insalled it.

 

I did the F8 and do "last best start up" thingy, and that didn't work either, so I guess my Windows is fucked?

 

I will devo still do the Memtest, always good to make sure.

Link to post
Share on other sites

  • 3 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×