Blue screen of death

[Ne007]

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]

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

[Mels_Smileys45]

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]

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]

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

[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 .....

[multi]

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]

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]

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]

Yeah BSOD with XP is mostly a hardware issue.

[MorphineInduced]

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]

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]

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]

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]

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!

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.

[Nogoodpunk42]

that isnt a BSOD though thats just an error message

[multi]

:error

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


the blue screen you get 'right when windows is booting up' is a 'STOP message'
the one you get when you are in windows..usualy from running some program is windows taking a dump
(of the memory variety)
both are BSOD error screens but of a slightly different nature

if you can post up some info on them, then you/some kind soul can do a search for similar errors that have been posted and get a rough idea what is playing up

Pc problem..... (http://showthread.php?t=35948&highlight=%22stop+message%22)
i need help!!! (http://showthread.php?t=18927&highlight=bsod)

i am not saying i will know what the problem is once you post the error
but it would be more likely to get the original question answered if you did

[YWD67]

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....

Fine speech, but you offer no answer just a anti-MS XP speech, while Mel has, an I agree that the problem
maybe be a hardware problem that XP is detecting.

Next time you make a disagreeing post MorphineInduced, try and do so with out the 'PRICK" attitude next time please.
Just a thought. (ASS BAG)

[The Hunter]

I dont think insults are needed, and further I have been running xp here with no problems for quite a while, this install for about 1 1/2 years with no problems. Yes I do use my pc a lot, and I would personally suspect a hardware problem, as the quality of the pc has no bearing on a piece of hardware shitting the bed. It can and does happen.

[Ne007]

I wasn't able to repair windows, as it gave me the blue screen error:

Stop: 0x00000050 (0xFFFFFFCA, 0X00000001, 0xF7CA69A8, 0x00000000)

[Theinfamousone]

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.

I am running a dual core 64 bit Athlon with 2 gigs of Corsair RAM and an ASUS SLI A8N Premium and a brand new 300 gig Maxtor DIamond 16 MB buffer hard drive and I get the BSOD all the time with fresh installs of XP Pro!

[vixenk]

http://support.microsoft.com/?kbid=329293

Microsoft's database comes in handy. ;)

My recommendation... boot into safe mode if you can, uninstall your video card drivers, restart, and then see if the problem continues on Window's default drivers. If that doesn't work, follow the steps outlined in the link posted above.

[que-em]

I am running a dual core 64 bit Athlon with 2 gigs of Corsair RAM and an ASUS SLI A8N Premium and a brand new 300 gig Maxtor DIamond 16 MB buffer hard drive and I get the BSOD all the time with fresh installs of XP Pro!


you can put me in that category also. amd 3800 x2, asus a8n sli premium, 2 gigs corsair. blue screen if not every night every 2 or 3 days. i did a memtest with one of them linux distro and the memory passed. only thing i can figure is XP isn't putting the video card in check. xp might be might be one of microsoft best produced os but it damn sure isn't perfect. the f**ked up thing is i had the same problem with my old computer.

[kokanezub]

just reinstall windows

[Ne007]

just reinstall windows


0x00000050 is a memory issue. reinstalling windows will do no good for that.

What I did was swap out the graphics card, because it can be an issue with the graphics memory. That did no good.

THEN I swapped out the ram and found one stick of ram was bad. My computer now runs perfectly with no data loss...although I am running on 512mb of ram for the moment.

[axlman]

Get yourself a copy of MemTest86, I'd run that on the current working stick just to check it out anyway.

http://www.memtest86.com/#download0

Also, QuickTech Pro is a nice little PC Daig program that will test your hardware

[multi]

Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA - This message occurs when you install a faulty or incompatible device driver or a driver for a system service. Uninstall the newly installed device or service, obtain the correct driver for your version of Windows.




0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online Win XP Resource Kit (http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/prmd_stp_ccgm.asp) article, or see Windows 2000 Professional Resource Kit, p. 1548.)
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card). Use the General Troubleshooting of STOP Messages (http://aumha.org/win5/kbestop.php#general) checklist above.


You receive a Stop 0x00000050 error on a Blue Screen (http://support.microsoft.com/?kbid=894278&sd=RMVP) {KB 894278} Win 2000, Win XP, Server 2003 (with concurrent 1003/System entry in Event Viewer: possible Rootkit spyware infestation)
Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors (http://support.microsoft.com/?kbid=183169&sd=RMVP) {KB 183169} Win NT, Win 2000, Win XP
During setup (http://support.microsoft.com/?kbid=171003&sd=RMVP) {KB 171003} Win NT, Win 2000, Win XP
Easy CD Creator 5.0 Does Not Function In Windows XP (http://support.microsoft.com/?kbid=310628&sd=RMVP) {KB 310628} Win XP
How to Use Driver Verifier to Troubleshoot Windows Drivers (http://support.microsoft.com/?kbid=244617&sd=RMVP) {KB 244617} Win 2000, Win XP, Server 2003
STOP Error When You Start Windows After You Connect a Scanner (http://support.microsoft.com/?kbid=310869&sd=RMVP) {KB 310869} Win XP
Stop 0x1E in PROTCLS.SYS When You Undock a Toshiba Tecra 8100 (http://support.microsoft.com/?kbid=284154&sd=RMVP) {KB 284154} Win XP
STOP 0x4E, STOP 0x1A, STOP 0x50, and STOP 0xA Errors Occur When You Try to Start the Computer (http://support.microsoft.com/?kbid=271955&sd=RMVP) {KB 271955} Win NT 4.0 (corrupt physical RAM)
“STOP 0x00000050” Error Message in Stac97.sys After You Upgrade Your Panasonic Toughbook to Win XP Service Pack 1 (http://support.microsoft.com/?kbid=329832&sd=RMVP) {KB 329832} Win XP SP1memtest is a good idea

[Ne007]

Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems.



I do believe this was the information that helped me solve the problem.
Thanks.

[MorphineInduced]

Fine speech, but you offer no answer just a anti-MS XP speech, while Mel has, an I agree that the problem
maybe be a hardware problem that XP is detecting.

Next time you make a disagreeing post MorphineInduced, try and do so with out the 'PRICK" attitude next time please.
Just a thought. (ASS BAG)


Let me guess you are one of the many moderators from in here and he went and cried to you so you come and show up .... My speech isnt a anti -MS speech , I clearly stated that its not in all cases that Blue Screens appear from crappy hardware ...... I think that was plainly obvious since there has been others in here that have had it occur and they run top notch shit ..... Its amazing how you can come in here and then leave on my profile a comment about not being a prick when yet you turn around and call me a ass bag .... Is it that you are trying to tempt me into making you just another one on my list with some of the other moderators that I have made look like jackasses because of the crap the pull in these forums ...... Its quite amazing how I can look on my Reputation list and see Jorge and Crazy Horse giving me a pat on the back and yet ... The real Prick here , which is you .... who has nothing better to do but come around and talk shit ......

I dont know how many times anyone could tell anyone of you that it isnt necessarly a hardware problem everytime you get a blue screen yet I will see you all around preaching how great there OS is .... even linux is flawed and yet your friend there sounds just like some of the linux users in there own forums ..... So lets say ya Mel was correct about it being Hardware defects .... but then he turns around commenting like he did ...... So then this guy that was asking for help takes it that it is now always gonna mean that its hardware defects and not a problem with the OS ..... so how would that help the guy , when that piece of information is wrong ...... Ya look at what problem would occur from that ........ maybe try and think a little bit more before you come around talking shit .....

[multi]

So then this guy that was asking for help takes it that it is now always gonna mean that its hardware defects and not a problem with the OS
no ....he will post the error code next time :icon_comp

rather than being a memory problem it may well of been a driver issue
he didnt exactly say..

curious minds need to know .. :icon_cycl

anyway..glad its all sorted Ne0 !

[Ne007]

After I took out the bad ram, my computer works fine...IT WASN'T WINDOWS!

Gosh...someone put a closed sign on this.

[YWD67]

Let me guess you are one of the many moderators from in here and he went and cried to you so you come and show up .... My speech isnt a anti -MS speech , I clearly stated that its not in all cases that Blue Screens appear from crappy hardware ...... I think that was plainly obvious since there has been others in here that have had it occur and they run top notch shit ..... Its amazing how you can come in here and then leave on my profile a comment about not being a prick when yet you turn around and call me a ass bag .... Is it that you are trying to tempt me into making you just another one on my list with some of the other moderators that I have made look like jackasses because of the crap the pull in these forums ...... Its quite amazing how I can look on my Reputation list and see Jorge and Crazy Horse giving me a pat on the back and yet ... The real Prick here , which is you .... who has nothing better to do but come around and talk shit ......

I dont know how many times anyone could tell anyone of you that it isnt necessarly a hardware problem everytime you get a blue screen yet I will see you all around preaching how great there OS is .... even linux is flawed and yet your friend there sounds just like some of the linux users in there own forums ..... So lets say ya Mel was correct about it being Hardware defects .... but then he turns around commenting like he did ...... So then this guy that was asking for help takes it that it is now always gonna mean that its hardware defects and not a problem with the OS ..... so how would that help the guy , when that piece of information is wrong ...... Ya look at what problem would occur from that ........ maybe try and think a little bit more before you come around talking shit .....

Let's see here now.
1: I am not a Mod.
2. I said I had a simular problem and it was hardware connected not it had to be the problem
3. In the end it had nothing to do with the OS
4. You had an arrogant attititude on the first post and still have one now.

You are 0 and 4 now so get a clue. If you think dispensing correct information entails having an arrgant attitude and trying to make a jackass out of everyone who disagrees with you is going to make people listen to you guess what?
Your wrong and still are a prick ass bag.

[The Hunter]

Closed.....................

[The Hunter]

http://www.google.com/custom?q=is+a+hardware+problem+the+usual+cause+of+ the+blue+screen+of+death&sa=Google+Search&cof=GIMP%3Ared%3BT%3Ablack%3BLW%3A150%3BBIMG%3Agra y%3BALC%3Ared%3BL%3Ahttp%3A%2F%2Fhome.eastlink.ca% 2Fimages%2Felcslogo.gif%3BGFNT%3Agray%3BLC%3Ablue% 3BLH%3A45%3BBGC%3Awhite%3BAH%3Aleft%3BVLC%3Apurple %3BS%3Ahttp%3A%2F%2Fhome.eastlink.ca%3BGALT%3Agree n%3BAWFID%3A4ba87f8562bc4600%3B