Blue screen of death

**Ne007** · April 14th, 2006, 03:15 AM

I get that blue screen right when windows is booting up...i've heard it called the blue screen of death.

Anyways...what likely caused that? A bad sector on the harddrive? I believe its a newer harddrive...can I trust it still?

and is there any way of fixing it....or recovering my files. maybe i could get another computer to recognize the drive and pull files off.

**Auggie2k** · April 14th, 2006, 03:34 AM

What's your OS? What exactly does the error say?

**Mels_Smileys45** · April 14th, 2006, 03:58 AM

What OS is the big question as Augie pointed out. Look at this thread here http://www.techspot.com/vb/topic8356.html it should be of great help or at least answer a few questions

**Nogoodpunk42** · April 14th, 2006, 06:17 AM

well I guess we can safely say it isn't Windows XP or OS X. It has to be one of the other windows. Not like I'm crazy about XP, but I've tried to get that screen with XP never happened. Ever.

**Mels_Smileys45** · April 14th, 2006, 06:28 AM

I am crazy about XP, best thing since sliced pizza. Ive never has a BSOD with it either.

**MorphineInduced** · April 14th, 2006, 06:57 AM

Xp isnt all that its cracked up to be ...... It is just as easy to get Blue Screens of Death with it then with any of its older OS's ....... ...... Thats why I gave up with WInduster , just for the simple fact that it doesnt allow me to do what I want with my computer without something like a Blue Screen wanting to pay me a visit one day .....

**multi** · April 14th, 2006, 07:01 AM

that would be the 'stop screen' (see start manual for details ?).. that part has always made me laugh

STOP Messages literally mean Windows has stopped! These appear only in the NT-based operating systems: Win NT, Win 2000, and Win XP. Most are hardware issues. STOP messages are identified by an 8-digit hexadecimal number, but also commonly written in a shorthand notation; e.g., a STOP 0x0000000A may also be written Stop 0xA. Four additional 8-digit hex numbers may appear in parentheses, usually unique to your computer and the particular situation.
http://aumha.org/win5/kbestop.php#0x0a

another common cause:

A. This error occurs when you try to put the system in standby mode. The cause is a third-party driver that doesn't comply with the Advanced Configuration and Power Interface (ACPI) standard for power management. When the system goes into standby mode, it tells all drivers that the system is changing power state. If a driver doesn't respond correctly, the system displays a blue screen. Almost any kind of driver (e.g., CD-ROM drivers, network drivers, keyboard filter drivers) can cause this problem.

The easiest way to fix it is to perform the following steps:

1. Create a hardware profile and boot into it.
2. Go to the device manager (My Computer, Manage, Device Manager), select View, Show hidden devices, and disable all suspect devices (i.e., non-Microsoft devices) for the current hardware profile. (You disable a device on the General tab of the device's property sheet.)
3. Reboot using the same hardware profile and try to reproduce the problem. If you can't, start re-enabling drivers and rebooting until the problem reappears. Then delete or update the offending driver.
4. If the problem persists, disable all unnecessary drivers, update the necessary ones, and try again.

**Mels_Smileys45** · April 14th, 2006, 10:30 AM

Originally Posted by MorphineInduced

Xp isnt all that its cracked up to be ...... It is just as easy to get Blue Screens of Death with it then with any of its older OS's ....... ...... Thats why I gave up with WInduster , just for the simple fact that it doesnt allow me to do what I want with my computer without something like a Blue Screen wanting to pay me a visit one day .....

Its caused more by a shitty PC than windows xp. Put the blame where it belongs. Ive never got the screen with my current pc and I do some heavy shit with it.

**YWD67** · April 14th, 2006, 12:46 PM

Few months back I got the blue screen and windows would shut down just after starting. The problem was my Nvidia video card had fried because the cooling fan had stopped working.
I was getting a blue message stating that windows has detected a problem and is shutting to avoid damage to the system.
Got a new video card and the blue screen went away.

**Mels_Smileys45** · April 14th, 2006, 01:12 PM

Yeah BSOD with XP is mostly a hardware issue.

**MorphineInduced** · April 14th, 2006, 03:28 PM

Thats kind of funny how you blame it on a shitty pc ...... I know my computer isnt , apparently you need to talk to more people before you make assumptions on it being someones PC or if its actually Windows ...... You seem to be one of those Windows finatics from the sounds of it .... IF Xp was so great then why is it so insecure when it comes to viruses and everything else ..... and thats just the start of all there holes ..... can you explain why when Xp came out why there had to be so many updates since they released a half way finished OS .... and do you even pay attention to the statistics of there new Vista ..... or do you just take peoples words instead of seeing them yourself .....

Thats very foolish to be going around acting the way you are , about anyone that has some background with computers would tell you that Xp gets blue screens out the ass if you do shit that they dont want you to mess with ........ I still find it amusing how you can be quick to blame someones computer instead of actually anaylzing the software that is installed on it ...... Its not to say that software is always the case but for the most part it is .....

Xp is only around for the masses for the most part and for those that dont really care if there OS works properly , I see alot of people that would rather have something that works for the most part at first or that doesnt really feel like writting in code from time to time .....

Maybe you should just do the research on OS's and about everything else before you go around blaming problems on other things that have a high chance of not being involved in ....... and maybe you should go make friends with people that have some form of haxing experience for starters .... for the most part they will tell you about all the weaknesses that any form of Windows has if you ask nicely....

Also if you have a failed part in youir computer why not look behind what is controlling those parts of your computer when it comes to running them ...... o wait the OS plays a part in that doesnt it ?........ think beyond the box friend....

**vixenk** · April 14th, 2006, 04:48 PM

Umm... yah...

All I'm going to say is if the kernel in XP was great, they wouldn't have rewritten it for Vista. And minor hardware issues, *especially* driver issues. for the most part should NOT make the kernel fall apart.

To the thread starter: it would be really helpful if you could post the error message + any error codes that accompany it. :)

**Ne007** · April 14th, 2006, 04:52 PM

I'm sorry...I've been at work for the past 13 hours....

It's windows xp professional...and I'm not sure what the screen says as it flashes quickly..something about "windows has encountered an error....if you've seen this screen before...something"

My computer was operative perfectly until I woke up this morning.

and..this isn't a shitty computer.

**multi** · April 14th, 2006, 06:23 PM

what make and model main board is it ?

the stop error message might help work out if it is the hard drive failing or not
seems to be more commonly wrong device drivers

if its really bad you could try a repair install of xp
i know i have fixed something similar like that

**vixenk** · April 14th, 2006, 07:26 PM

Originally Posted by Ne007

I'm sorry...I've been at work for the past 13 hours....

Eeks! That sucks, I know. :( Definitely go home and get some sleep before you try tackling this issue!

Originally Posted by Ne007

It's windows xp professional...and I'm not sure what the screen says as it flashes quickly..something about "windows has encountered an error....if you've seen this screen before...something"

There should be a combination of numbers/some letters on the screen as well. This is the error code I was speaking of earlier.