how to resolve blue screen problem?
-
Friday, June 24, 2011 6:27 PMplease suggest me how to fix blue screen error in server?
Thanks& Regards, SelPri | India | +91-9986655633 Future Looks Bright...
All Replies
-
Friday, June 24, 2011 7:20 PM
It depends on what the BSOD error is? When the computer blue screens, you should see an error code. The error could be related to bad memory, storage, etc...
Visit: anITKB.com, an IT Knowledge Base. -
Friday, June 24, 2011 9:25 PMOk thanks.. Normally what are all the steps i need to do?
Thanks& Regards, SelPri | India | +91-9986655633 Future Looks Bright... -
Friday, June 24, 2011 9:53 PM
Hello,
you have to use a debugger like Windbg.
To read dump files: http://support.microsoft.com/kb/315263
Please use Microsoft Skydrive to upload dump files (c:\windows\minidumps). Once done, post a link here.
You can also contact Microsoft CSS.
Based on my experience, most of BSODs were caused by:
- drivers that have not been updated
- malware programs
- bad RAM
- problems with disks and their cables
- problems with processors
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.Microsoft Student Partner 2010 / 2011
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows 7, Configuring
Microsoft Certified IT Professional: Enterprise Administrator -
Friday, June 24, 2011 10:30 PMthkx
Thanks& Regards, SelPri | India | +91-9986655633 Future Looks Bright... -
Sunday, June 26, 2011 9:49 AM
The first thing you can do in troubleshooting blue screens is enable a complete memory dump and turn off automatic reboot. This is done under the system properties in Startup and Recovery. It's best to do this right after you install Windows, before you start getting any BSODs. Sometimes the blue screen will show the name of the driver that is causing the problem. If nothing else, you can look up the STOP code and see what the problem is.
The most important info to record from the blue screen is the technical info, it will look something like this:
*** STOP: 0x000000EB (0x00000032, 0x00002345, 0xABCDEF00, 0x00000000)
The first number after the STOP is the bug check code. In this case it translates to DIRTY_MAPPED_PAGES_CONGESTION. (I just picked that one at random, I've never actually seen that on a live system). The 4 numbers after that are the bug check parameters, which are explained in the debugger help file. For example, in this case the first number would mean the total number of dirty pages.
If the info on the blue screen isn't enough to pinpoint the problem, you will need to install the Microsoft debugging tools. This can be downloaded from:
http://www.microsoft.com/ddk/debugging/default.aspAlso see this Kb article http://support.microsoft.com/kb/315263
http://www.pcstats.com/articleview.cfm?articleID=1647
http://www.virmansec.com/blogs/skhairuddin- Marked As Answer by Tim QuanModerator Monday, June 27, 2011 2:44 AM

