Reasons For ( BSOD ) Blue Screen Of Death Errors

At times you will receive an Error with a Blue Screen and a Stop error with an Associated Error Code .  In Such Situation the server keeps on rebooting and there is very little which we can do . Below are the reasons why blue screen of death Errors occur .

BSOD Errors are mainly caused because of Hardware Issues

1)  Installation of Wrong Device Drivers

2) Any hardware issue inside the Server

3) Rebooting the server while Windows updates are being applied on the Server

When a BSOD error Occurs Windows Automatically creates a minidump file which has information about the crash as to why it is crashing .

In order to troubleshoot the issue you can use the Windbg tool to read the minidump file and find out the cause of the issue .


Repair.exe Plesk Syntax

1) Goto Command prompt

2) Type Cd %plesk_cli%

3) The Path will be changed to C:\Program Files (x86)\Parallels\Plesk\bin>

4) Execute the Following Command  repair.exe  –reconfigure-web-site -web-site-name domainname

Difference Between IIS 6.0 , IIS 7.0 and IIS 8.0

IIS 7.0 and IIS 8.0 Have the Same Working Architecture , So let us discuss the Difference Between IIS 6.0 and IIS 7.0 ( IIS 8.0 )

In IIS 6.0 the www service Performs the following Tasks

a) The WWW Service manages application pools and worker processes, such as starting, stopping, and recycling worker processes.

b) The WWW Service reads configuration information from the IIS metabase and uses that information to configure and update the HTTP listener, HTTP.sys

In IIS 7.0 and 8.0 the above tasks which were performed by the www Service alone are Split into two Services www Service and Windows Process Activation Service also called as WAS .

The WWW Service is the listener adapter for the HTTP listener, HTTP.sys. As the listener adapter, the WWW Service is primarily responsible for configuring HTTP.sys, updating HTTP.sys when configuration changes, and notifying WAS when a request enters the request queue.

Windows Process Activation Service (WAS) manages application pool configuration and worker processes instead of the WWW Service. This enables you to use the same configuration and process model for HTTP and non-HTTP sites.


(adsbygoogle = window.adsbygoogle || []).push({}); //--> Feedjit Flag Counter