Hi Friends!
I am sorry I kept you wating for my post for such a long time. Well, I just moved to IT city of India (it is not its' official tag, but people call it though) & was busy adapting to the new environment.
Lets come to the topic of todays learning: Blue Screen Of Death. Lets get started.
All Windows users would have faced this screen at least once in their life time. Correct??
To begin with and to write on this topic, I made an extensive search on the net about- what this problem is; where/how could you log this error & possible solutions(including a link to Microsoft KBHotfix).
As this is the first part of the series, let's try to understand what causes this error?
Windows(even linux, FYI) OS runs in two modes:
slave/user/unprivileged mode and the master/kernel/privileged.
Now, the inquisitive human mind asks, "what are they? Right?".
To put it in simple terms to answer this question, let us understand it as to perform a specialised task, the user-mode(code) makes a system call into supervisor mode and here the trusted code of the OS will perform the necessary task and return the result to the user space.
Stop errors(general term for BSOD) are invariably caused by kernel portal components exceptions for eg. hardware, third-party drivers or anti-virus services.
The screen turns blue because there is some exceptions occured in the kernel (either through device driver error or the service error), and when Windows detects some error in the Kernel, it will try to abort the processes, lest something more dangerous occur. Hence we get a blue screen and typically it is followed by a system restart.
Brien had presented the anatomy of this error. You could read it link here.
Hope this gives a clear idea of what causes the error, the next post will be on Saving a memory dump and the solution to this nemesis.
Catch you in the second part of this blog.
Till then,
Have a safe computing!
I am sorry I kept you wating for my post for such a long time. Well, I just moved to IT city of India (it is not its' official tag, but people call it though) & was busy adapting to the new environment.
Lets come to the topic of todays learning: Blue Screen Of Death. Lets get started.
All Windows users would have faced this screen at least once in their life time. Correct??
To begin with and to write on this topic, I made an extensive search on the net about- what this problem is; where/how could you log this error & possible solutions(including a link to Microsoft KBHotfix).
As this is the first part of the series, let's try to understand what causes this error?
Windows(even linux, FYI) OS runs in two modes:
slave/user/unprivileged mode and the master/kernel/privileged.
Now, the inquisitive human mind asks, "what are they? Right?".
To put it in simple terms to answer this question, let us understand it as to perform a specialised task, the user-mode(code) makes a system call into supervisor mode and here the trusted code of the OS will perform the necessary task and return the result to the user space.
Stop errors(general term for BSOD) are invariably caused by kernel portal components exceptions for eg. hardware, third-party drivers or anti-virus services.
The screen turns blue because there is some exceptions occured in the kernel (either through device driver error or the service error), and when Windows detects some error in the Kernel, it will try to abort the processes, lest something more dangerous occur. Hence we get a blue screen and typically it is followed by a system restart.
Brien had presented the anatomy of this error. You could read it link here.
Hope this gives a clear idea of what causes the error, the next post will be on Saving a memory dump and the solution to this nemesis.
Catch you in the second part of this blog.
Till then,
Have a safe computing!
No comments:
Post a Comment