| T O P I C R E V I E W |
| dady000 |
Posted - Dec 22 2016 : 11:12:28 AM
Hello, I have encountered a bug on Windows 7 SP1, when I installed the newest trial VAX on Visual Studio 2015 and 2017 RC. After the install I started Visual Studio and it crashed my system with BSOD that produced no dump. I attached the image of the BSOD. I have found the cause of the problem, and that is I had turned UAC completely off. After I enabled UAC it stopped crashing.
 |
| 7 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Jan 09 2017 : 11:36:16 AM
Thank you for the update, I am really pleased to hear that you are no longer seeing this problem.
I have seen very occasional reports of drivers causing similar problems over the years, but only with UAC turned off is a new variation of this rare problem. |
| dady000 |
Posted - Jan 09 2017 : 10:58:03 AM
quote:
Originally posted by feline
A couple of other thoughts, are you working locally or remotely? I am guessing locally, from the picture of the BSOD, but I wanted to double check.
Can you please also run Windows Update and see if you have any driver updates available or your system? It is possible that an older driver could somehow be a factor here.
So, I tested it and it doesn't happen on the newest Windows 10 build. I definitly didn't have all the updates installed on W7 and it is very likely it was some driver. But I still thought it was really weird for an addon to throw a BSOD with UAC off. Thanks for investigating this issue, if I will encounter this error in the future I will let you know. |
| dady000 |
Posted - Jan 09 2017 : 10:45:09 AM
quote:
Originally posted by feline
A couple of other thoughts, are you working locally or remotely? I am guessing locally, from the picture of the BSOD, but I wanted to double check.
Can you please also run Windows Update and see if you have any driver updates available or your system? It is possible that an older driver could somehow be a factor here.
Yeah working locally. I recently got an SSD and no longer have Windows 7 but windows 10 instead, I will try if the error occurs. Regarding that issue it is definitly possible it's an driver issue but because of no dump I was not interested in investigating it further. |
| feline |
Posted - Jan 02 2017 : 12:21:19 PM
A couple of other thoughts, are you working locally or remotely? I am guessing locally, from the picture of the BSOD, but I wanted to double check.
Can you please also run Windows Update and see if you have any driver updates available or your system? It is possible that an older driver could somehow be a factor here. |
| accord |
Posted - Dec 26 2016 : 09:30:23 AM
I wasn't able to reproduce the problem using VS2015 update 3 or VS2017 RC1 using Visual Assist 2118.
This is very unexpected and surprising.
Did you use the same combination of hardware and software before you installed VA without any problem? Blue screens are usually sign of hardware or driver problem.
Regarding not finding the dump. Is your dump saving configured correctly?
Here, you can see which directory does Windows save the dump on your system.
To open the dialog: open Control Panel, select System, select Advanced System settings, and finally, select the Setting button inside the "Startup and Recovery" box. |
| dady000 |
Posted - Dec 24 2016 : 6:01:45 PM
quote:
Originally posted by ChrisG
Hello dady000,
Wow. I'm sorry you are having this issue.
You say there was no dump being produced?
Does the crash happen as soon as you start Visual Studio every time? (assuming UAC is on)
Does starting either VS 2015 or 2017 cause the crash?
Does the crash happen if you downgrade to the previous build of Visual Assist from our archive?
http://www.wholetomato.com/downloads/
It crashes as soon as I open Visual Studio but when UAC is off. If UAC is on it does not crash. Yes both 2015 and 2017 crash. Yes it happens on older ones. |
| ChrisG |
Posted - Dec 22 2016 : 2:06:26 PM
Hello dady000,
Wow. I'm sorry you are having this issue.
You say there was no dump being produced?
Does the crash happen as soon as you start Visual Studio every time? (assuming UAC is on)
Does starting either VS 2015 or 2017 cause the crash?
Does the crash happen if you downgrade to the previous build of Visual Assist from our archive?
http://www.wholetomato.com/downloads/ |
