Windows Blue Screen of Death (BSOD)
The Windows Blue Screen of Death or BSOD as we techies call it can be the bane of our existance. I have spent long and frustrating hours trying to troubleshoot these messages. Initally i was like many who just shrugged their shoulders and put it down to faulty hardware or Windows biting the bullet. While this can be the case these messages are actually helpful in diagnosing the root of the problem.
The trick is knowing how to decipher the obsure combinations of numbers and letters that appear on the blue screen…see below
You will note that there are 2 “errors” here and they will help us to work out what the problem is. Now here is my secret weapon a website that has an excellent repository of information on these TROUBLESHOOTING
WINDOWS STOP MESSAGES
If you head on over to the site you will see a good explanation of what the messages mean as well as a huge list of them with explanations and hints.Using the search feature there I entered the fault PAGE_FAULT_IN_NONPAGED_AREA.
The search turned up….
0×00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online MSDN article.)
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 checklist above.
- You receive a Stop 0×00000050 error on a Blue Screen {KB 894278} Win 2000, Win XP, Server 2003 (with concurrent 1003/System entry in Event Viewer: possible Rootkit spyware infestation)
- Possible Resolutions to STOP 0×0A, 0×01E, and 0×50 Errors {KB 183169} Win NT, Win 2000, Win XP
- During setup {KB 171003} Win NT, Win 2000, Win XP
- Easy CD Creator 5.0 Does Not Function In Windows XP {KB 310628} Win XP
- How to Use Driver Verifier to Troubleshoot Windows Drivers {KB 244617} Win 2000, Win XP, Server 2003
- STOP Error When You Start Windows After You Connect a Scanner {KB 310869} Win XP
- Stop 0×1E in PROTCLS.SYS When You Undock a Toshiba Tecra 8100 {KB 284154} Win XP
- STOP 0×4E, STOP 0×1A, STOP 0×50, and STOP 0xA Errors Occur When You Try to Start the Computer {KB 271955} Win NT 4.0 (corrupt physical RAM)
- “STOP 0×00000050” Error Message in Stac97.sys After You Upgrade Your Panasonic Toughbook to Win XP Service Pack 1 {KB 329832} Win XP SP1
The above is the information we need to help us start to troubleshoot this error. While this is a lot of information with some time and a little patience and experience it is possible that this BSOD can be resolved without drastic measures.
Unfortunatley its not always possible to fix these and in the end a reformat and or hardware upgrade are the only options left, but should be considered a last resort. Of course your friendly PC tech will be glad to help if you get in over your head. But it is always nice to know what you are dealing with even if you cant reslove it yourself.