BSOD: How to fix?

This topic is locked from further discussion.

#1 Posted by BluRayHiDef (10837 posts) -

#2 Edited by Arthas045 (5045 posts) -

Could try going into safe mode and trying a restore from a few days ago.

I wonder what you changed error states driver problem.

F8 while booting will take you to safe mode.

Also google the error and that will give you an idea.

#3 Posted by BluRayHiDef (10837 posts) -

Could try going into safe mode and trying a restore from a few days ago.

I wonder what you changed error states driver problem.

F8 while booting will take you to safe mode.

It must be due to an automatic Windows update, because I haven't manually updated anything in a while. In fact, I haven't even been using my PC much in the last two weeks because of my PS4.

#4 Edited by Arthas045 (5045 posts) -

If you google that 0x0000 etc error it will give you a clearer answer.

#5 Edited by zaku101 (4315 posts) -

Update your graphic card drivers, get the latest beta drivers.

#6 Edited by Arthas045 (5045 posts) -
#7 Posted by GummiRaccoon (13593 posts) -

Format the drive.

Install linux.

#8 Posted by ShimmerMan (4426 posts) -

Make sure all the hardware in the PC is seated correctly in its place. Sometimes a sound card/ram/GPU etc can become slightly loose and this can cause BSOD.

#9 Posted by the_bi99man (11022 posts) -

In my experience, if a BSOD doesn't fix itself with a simple restart, then your HDD is fried, and there is no fixing it. Get a new HDD, and take your busted one to a local computer shop, where they can hopefully recover most of your files.

I should be noted, however, that I'm no tech, and I'm sure there are other causes for these errors. I just haven't personally seen any. Every time I've got a BSOD, it's meant a fried hard drive.

#10 Posted by kaleb_mulhall (7 posts) -

Well, Honestly There are alot of fixes for this... I'll name a couple... Have you cleared the BIOS? Take out astick of ram... Reinstall windows... (could of corrupted) The hard-drive could be on the way out... These are just off top of my head man... try some things! :-)

#11 Posted by 04dcarraher (18860 posts) -

Download blue screen view and run it it will tell you more info of what service and dll was at fault

#12 Posted by GummiRaccoon (13593 posts) -

open command prompt as admin type sfc /scannow

and

open command prompt as admin type chkdsk /R

#13 Posted by PredatorRules (7004 posts) -

I hate Blue and Red screens of death, sometimes I think to boot install XP with service pack 3

#15 Posted by MlauTheDaft (2963 posts) -

Could you elaborate? A power state failure... Would you happen to use a Haswell CPU along with an old PSU?

#16 Posted by PernicioEnigma (5271 posts) -

Format the drive.

Install linux.

Why on earth would he do that?

#17 Posted by kraken2109 (12936 posts) -

memtest

#18 Posted by GummiRaccoon (13593 posts) -

@PernicioEnigma: Because a kernel panic in linux doesn't bring your entire computer to its knees.

#19 Edited by JigglyWiggly_ (23352 posts) -

@GummiRaccoon said:

@PernicioEnigma: Because a kernel panic in linux doesn't bring your entire computer to its knees.

wat

what else are you going to do before a reboot run a stack trace?

#20 Posted by GummiRaccoon (13593 posts) -

@GummiRaccoon said:

@PernicioEnigma: Because a kernel panic in linux doesn't bring your entire computer to its knees.

wat

what else are you going to do before a reboot run a stack trace?

You've never recovered from a kernel panic without rebooting?

#21 Edited by JigglyWiggly_ (23352 posts) -

@JigglyWiggly_ said:

@GummiRaccoon said:

@PernicioEnigma: Because a kernel panic in linux doesn't bring your entire computer to its knees.

wat

what else are you going to do before a reboot run a stack trace?

You've never recovered from a kernel panic without rebooting?

no