>>>>In my case the BSOD, I think, is caused by memory but not necessarily faulty memory chip (I used the utility you recommended and it found no fault). What I see before the BSOD "fires" is my screens go haywire; they start jumping around, size changes, go On and Off. This goes on for about 5-15 seconds and then very quiet :).
>>>
>>>A video problem like that could have several causes:
>>>
>>>1. Bad cable connections if you're using more than 1 monitor. Try to avoid "converters" in cables e.g. DVI to VGA. Try to use digital over analog connections e.g. HDMI better than DVI better than VGA
>>>
>>>2. Bad video driver. Try using the latest from Windows Update or your computer manufacturer (Dell, HP etc.) or chipset maker (nVidia, AMD)
>>>
>>>3. Bad video adapter hardware. All adapters have a controller; if you have a so-called "discrete" adapter it will also have its own video RAM rather than using some of the main system RAM. Either a controller or video RAM failure can cause symptoms like you're seeing.
>>>
>>>4. There is a small chance a secondary monitor (if you're using more than 1) could cause problems like this. If you can try a different secondary monitor, do so. If not, try running with just 1 monitor for a while - longer than it would normally take to generate a BSOD - to see if that makes a difference. If the BSODs go away, it could be the secondary monitor, or software/drivers that support multi-monitor operation.
>>
>>All good suggestions. Interesting that when I had BSOD with Aventail VPN it was ONLY when I am at work where I have two monitors. But the BSOD with VS2012 happened only when I was at home where I don't have second monitor (just the one on the notebook). I will have to carefully go through all other items and check. And I am not that savvy on IT issues so it will be a challenge. Thank you very much!
>>
>>P.S. The computer I am using is 3.5 years old. Maybe time to buy a new one.
>
>A disgusting reality is that backwards compatibility between a computer and operating system can be a problem. Often, computer manufacturers and Microsoft will work together when a new version of an OS is about to be released. Can you check and see if your computer and OS are compatible? It may be listed somewhere.
>
>I remember the words of George Goley IV, “One computer in 500 will not work with FoxPro regardless of what you do”! Extend that to any computer issue. Well, all I can do is wish you luck and hope you resolve the issue.
>
>I find it helps to record each thing I do when I am attempting to resolve a problem, and write down the result. I end up with a short document that is easy to review and keeps track of what has occured. On the top of a piece of paper I define the title of what the issue is. Then I create two columns – the left side for what I have attempted and the right side for the result. It is interesting how I will later experience a new issue and remember that sheet of paper with the results, etc. By double checking the paper I often find a result that resolves something I already experienced.

I have been using this computer since release of Windows 7 (more than 3 years). So it must be compatible. But I agree that your suggestion to make written notes of all steps is very helpful. I will adapt it. Thank you.