Filed under: Windows Repair Software
Windows Blue Screen of Death at startup (sometimes). Can you help?
January 11, 2011
7 thoughts on “Windows Blue Screen of Death at startup (sometimes). Can you help?”
Comments are closed.
Clean Registry and Optimize PC
If your pc get Blue Screen Of Death (BOSD) you have to check your pc heath, and then fix your pc directly.
Check your pc health online for the website:
http://bosd-checking.com/Blue_Screen_Of_Death
The Windows operating system constantly refers to the registry to get information about all of the components such as hardware and software which are installed on the computer. The registry tells Windows what to do and how to access the various programs, files, and processes.However, the registry can contain bad information which sends Windows off doing useless tasks or running unneeded routines. Sometimes errors occur including the blue screen of death. Other times the system slows down. Because of the sheer number of factors that can affect the registry, there’s no one size fits all approach. You can’t just go into the registry and remove the bad information because it’s nearly impossible to decipher which information is good and which information is bad. That’s a job better suited for software. I should like to commend Registry Easy http://cleanup-comuter-run-perfectly.com to you ! You can try ! Good luck!
In Microsoft Windows NT-based operating systems, the blue screen of death (displayed in 80×50 text mode as opposed to 9x/Me’s 80×25) occurs when the kernel or a driver running in kernel mode encounters an error from which it cannot recover. This is usually caused by an illegal operation being performed. The only safe action the operating system can take in this situation is to restart the computer. As a result, data may be lost, as users are not given an opportunity to save data that has not yet been saved to the hard drive.
The text on the error screen contains the code of the error along with four error-dependent values in parentheses that are there to help software engineers fix the problem that occurred. Depending on the error code, it may display the address where the problem occurred, along with the driver which is loaded at that address. Under Windows NT and 2000, the second and third sections of the screen may contain information on all loaded drivers and a stack dump, respectively. The driver information is in three columns; the first lists the base address of the driver, the second lists the driver’s creation date (as a Unix timestamp), and the third lists the name of the driver.
By default, Windows creates a memory dump file when a blue screen error occurs. Depending on the OS version, there may be several formats this can be saved in, ranging from a 64kB "minidump" to a "complete dump" which is effectively a copy of the entire contents of physical RAM. The resulting memory dump file may be debugged later, using a kernel debugger. A debugger is necessary to obtain a stack trace, and may be required to ascertain the true cause of the problem; as the information on-screen is limited and thus possibly misleading, it may hide the true source of the error.
Microsoft Windows can also be configured to send live debugging information to a kernel debugger running on a separate computer. Windows XP also allows for kernel debugging from the machine that is running the OS. If a blue screen error is encountered while a live kernel debugger is attached to the system, Windows will halt execution and cause the debugger to break in, rather than displaying the BSoD. The debugger can then be used to examine the contents of memory and determine the source of the problem.
A BSoD can also be caused by a critical boot loader error, where the operating system is unable to access the boot partition due to incorrect storage drivers, a damaged file system or similar problems. In such cases, there is no memory dump saved. Since the system is unable to boot from the hard drive in this situation, correction of the problem often requires booting from the Microsoft Windows CD. After booting to the CD, it may be possible to correct the problem by performing a repair install or by using the Recovery Console (with CHKDSK, or fixboot).
How to repair:
Insert the Windows XP installation CD (correct service pack) and follow the prompts. When it gets to where it says "format this partition", "repair an installation of Windows XP", select "R" which is repair. You might be required to provide your administrator password and other stuff, after which your copy of windows will be repaired or restored to an earlier date.
Otherwise, you’ll just have to reformat and reload your Windows. If you have any important documents you don’t want to lose, you can remove the harddisk, insert it on another computer and copy backup the files into that computer’s drive, flash disk, CD or DVD. Insert the harddrive back to the affected computer, insert the XP CD and follow prompts.
Hope this helps.
Run Linux
try a clean reinstall… or buy a legal copy! that will help!
Yeah…I had that issue a while ago. Nothing worked, but getting it cleaned out and rebooted.
Insert windows disk – boot from CD – click repair
see if that works.
do you have the error code from the blue screen? What is it saying is failing?
If its software something like a update or repair will work, if its hardware you might need to fix something.. if you can give me details of errors (either that really long number it gives or just what it reads.. or both)