This may or may not be a familiar sight to you. The infamous blue screen has plagued and enraged people all over the world. It occurs when the system encounters a serious issue and causes the whole system to crash, leaving this lovely friendly blue screen which to most people may as well be written in Chinese.
Blue screens can occur for a number of different reasons; Often when new software has been added, or when the system memory is overcome by a faulty/redundant address that it cannot write to. I have, in the past been absolutely aggravated to insanity trying to fix these troublesome errors!! More often than not with a very serious case it can result in reformatting the computer, but this can be hit and miss and it sometimes doesn't solve the issue.
Finding solution can be tricky. It is easier to remove problematic programs that may have been recently installed, or revert back to settings that worked before the issue occurred. If you know what to look for there are some clues in the data the blue screen throws up. At the bottom will be a list of the memory addresses where the error occurred and with which extension it had the problem with.
If your blue screen is happening all the time and not letting you even access the computer because it constantly keeps shutting down, then try operating with reduced driver or "safe mode" this can be useful in determining which programs may be causing the problem.
The blue screen error may also point to faulty or corrupted system memory. The physical memory sometimes through malicious software or physical fault, will not operate in the proper way and indeed throws up our friend the BSOD. Of-course purchasing new memory should be a last resort after trying first tweaks, software, and process of elimination.
The Common nv4_disp.dll Error
This particular error nv4_disp.dll has come up for a lot of people. I found a fix for this after a long arduous session of searching and trying different techniques out. For me this error was linked to my Nvidia graphics card and device drivers (running on windows XP). I found the solution to this problem a couple of years ago and now maybe someone else will find it useful.
On my computer this error would occur when a game would be loaded up but subsequently crash (usually in a game.)
To stop my computer crashing I found a work around by changing the hardware acceleration. in windows XP control panel>display>Troubleshoot. Then selecting hardware acceleration "none". This allows the computer to run smoothly when graphical intensive applications are not needed. When you wish to play a game try selecting the hardware acceleration back to full, then when your finished back again to none. This should give you the best chance of a stable workaround and all I can say is it worked for me after long hours of swearing and getting really annoyed.
