Blue screen of doom and restart loop. ;o;

Zylos · December 09, 2009, 03:32:31 PM

I'm in a computer lab right now, because my own computer has a serious problem.

Last night, I was in the middle of playing a game when everything suddenly froze up. It waited a few seconds and then did an automatic restart because of a system failure. It came to the windows loading screen, loaded up, and then the infamous blue screen of death flashed on my monitor for a split second before restarting the computer again because of system failure. "Well fuck, that's not good..." I said to myself. So I tried restarting in safe mood, but no sooner than it loaded up the files that it too did an automatic restart, not even flashing the blue screen at me. Needless to say, it's impossible to use my computer at the moment, which pretty much screws me over.

The last time this happened to me was last January on my parents computer, in which my brother had to take it over to Geek Squad and remove about 100+ viruses from the hard drive (go figure, my parents didn't trust anything but Norton) and my mother ended up frying the external hard drive with all of the data because she used the wrong power cable for it. I, however, don't even have time to take my computer anywhere, next week is finals week and I friggin' need my computer... not to mention I don't have the money to get this thing fixed.

Anyone able to help? I'm kinda desperate here.

Roph · December 09, 2009, 07:58:52 PM

Have you tried only once to get into safe mode? If so I would keep trying, and then disable automatic restarts on bluescreens.

To do that, right click my computer -> properties -> advanced -> startup and recovery settings -> system failure -> untick automatic restart. Then you'll be able to read the BSOD and get the error code and file name (if any).

Though if you're able to get into safe mode I'd recommend doing a system restore =o

Irock · December 09, 2009, 10:20:13 PM

Try to take a photo of the BSoD before it restarts.

Mr_Wiggles · December 10, 2009, 06:11:51 AM

well blue screens are caused by a few things, perhaps some info on what you where doing the time of the crash? idk, power outage, updating hardware, installing of some sort?
other wise i agree and that a system restore may need to be done, that is if you can get into safe mode....
and what os are your working with?
but maybe youd like to read up on this when you get back into this copmuter lab...
http://www.webnewswire.com/node/486924

Rukishou · December 10, 2009, 02:42:01 PM

I got the blues (

) just yesterday (haven't slept since then so I guess you could say "earlier today" if you wanted to - but why would you want to say that?) for the first time on my newly-repaired laptop. Hooray...

Zylos · December 10, 2009, 03:49:24 PM

Quote from: Roph on December 09, 2009, 07:58:52 PM
Have you tried only once to get into safe mode? If so I would keep trying, and then disable automatic restarts on bluescreens.

To do that, right click my computer -> properties -> advanced -> startup and recovery settings -> system failure -> untick automatic restart. Then you'll be able to read the BSOD and get the error code and file name (if any).

Though if you're able to get into safe mode I'd recommend doing a system restore =o

I've tried multiple times to get into safe mode to no avail. It will load up the files, then freeze for a second after loading and do an auto-restart again. I'd take a photo if I had a camera, but don't have one again. Is there at least some way to disable them from one of the start up or boot menus, or perhaps slow the screen down long enough to write it down?

Irock · December 10, 2009, 07:16:09 PM

http://www.technibble.com/how-to-disable-automatic-restart-for-bsod-if-you-are-unable-to-get-into-windows/

Try this out.

Zylos · December 10, 2009, 10:59:44 PM

Okay, managed to disable the automatic restart and get the code.

***STOP: 0x0000007E (0xC0000005, 0x857CDE7A, 0xF78E67B8, 0xF78E64B4)

tSwitch · December 10, 2009, 11:18:58 PM

are you sure it's not 0x0000007F?
I can't find an 0x0000007E code.

Zylos · December 10, 2009, 11:22:20 PM

It's definitely 0x0000007E. I'm positive.

EvilM00s · December 11, 2009, 04:53:02 AM

Are there any filenames associated with the error? If so, they should show up just under the code in the message box.

Crankeye · December 31, 2009, 10:32:35 AM

For god sakes I hope you got it fixed by now.

You need to run a chkdsk on the drive and it should be fix no problem.

1. Get your windows cd an put it in your computer. When it prompts you hit "R" to start the recovery console. Follow the directions till you get to a prompt.
2. Type in the prompt:

Code Select

chkdsk /f /r c: