Blue Screen (not BSOD) when using mouse in Windows Server 2012
-
Direct on the box and/or RDP. Same either way.
-
And:
It's Server 2012 Essentials and this happens at the console (local k/b, video, mouse) even after uninstall of remote software (teamviewer and screenconnect), as well as uninstall of SolarWinds MSP (LogicNow RMM) monitoring, AV, and web filter.
-
What is the server used for? I'm assuming that at least PowerShell works so that it is still usable in the meantime?
-
I guess that it is possible that the GPU is failing.
-
Might be worth virtualizing just because it needs to be done anyway and it might fix this problem along with it. Worth a try, anyway.
-
Try turning the resolution way down. 800x600 or something like that.
-
It's their only server (very small business) so it's the DC/DNS/DHCP and application/file server. It's a pretty basic box but this is happening even when the place is closed so I don't think it's a performance issue. The box wouldn't likely be hearty enough to go VM and isn't very up-gradable.
Unfortunately because it's their applications server, their main app they use requires a right click to get into the settings to interact with several of it's features, so this is causing a significant impact. PS won't work with that app.
Could be the GPU, but it's only certain things that trigger the problem. Almost all right clicks (if not all) don't work and most left clicks work but not all.
-
@CCWTech said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:
It's their only server (very small business) so it's the DC/DNS/DHCP and application/file server. It's a pretty basic box but this is happening even when the place is closed so I don't think it's a performance issue.
I wouldn't think so. If it was it wouldn't be at that point or in that predictable of a way and it's not the kind of error you expect with a performance issue.
-
@CCWTech said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:
The box wouldn't likely be hearty enough to go VM and isn't very up-gradable.
Doesn't require anything extra. If there isn't enough power to go VM, there isn't enough power now. It would be completely taxed if virtualization was an issue.
-
@CCWTech said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:
Could be the GPU, but it's only certain things that trigger the problem. Almost all right clicks (if not all) don't work and most left clicks work but not all.
That actually suggests GPU. GPUs failing like this will often fail on certain system calls, which would only happen from certain applications or actions.
-
@CCWTech said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:
Unfortunately because it's their applications server, their main app they use requires a right click to get into the settings to interact with several of it's features, so this is causing a significant impact. PS won't work with that app.
Well that sucks. Definitely one of the many downsides to legacy app design.
-
@scottalanmiller said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:
@CCWTech said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:
Could be the GPU, but it's only certain things that trigger the problem. Almost all right clicks (if not all) don't work and most left clicks work but not all.
That actually suggests GPU. GPUs failing like this will often fail on certain system calls, which would only happen from certain applications or actions.
It's going to take some convincing to get DELL to replace the system board. Would a different video card be a good test or if the onboard GPU is a problem would it most likely still have an issue because it's still a device on the server?
-
@CCWTech said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:
@scottalanmiller said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:
@CCWTech said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:
Could be the GPU, but it's only certain things that trigger the problem. Almost all right clicks (if not all) don't work and most left clicks work but not all.
That actually suggests GPU. GPUs failing like this will often fail on certain system calls, which would only happen from certain applications or actions.
It's going to take some convincing to get DELL to replace the system board. Would a different video card be a good test or if the onboard GPU is a problem would it most likely still have an issue because it's still a device on the server?
A different GPU would work fine for a test.
-
@scottalanmiller Legacy is right. This is an DB application that still uses delphi and is a flat file database.
-
If you were virtualized, you could just move this workload to a PC to show that it is a hardware or hardware/driver problem and throw it in Dell's lap.
-
@scottalanmiller Ok, I'll try a different GPU and see what happens.
-
@CCWTech said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:
@scottalanmiller Legacy is right. This is an DB application that still uses delphi and is a flat file database.
Bwhahahaha. Below the home line, for sure. Not that Delphi itself is "so" bad, it's just... old.
-
Bringing over from the other discussion from @CCWTech :
Thanks for the suggestions. The box is pretty basic and it would be tough to go to hyper-v right now. It's their only server. (Very small business).
I've tried several different resolutions with no success.
They should have never purchased it in the first place given the software that they run. However it's a brand new box that they paid way to much money for, (their old IT company sold this to them) and we are looking at getting them something better. (What they have can't be upgraded to where they need to be.)
They are trying to decide. I just don't wanna be the guy that tells them because I can't figure out the issue with right click they need a new server. I'm trying to convince them of that on it's own merits, if that makes sense.
-
@scottalanmiller Yeah, I do VM on almost all new servers I set up.
-
@mlnews said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:
Bringing over from the other discussion from @CCWTech :
They should have never purchased it in the first place given the software that they run. However it's a brand new box that they paid way to much money for, (their old IT company sold this to them) and we are looking at getting them something better. (What they have can't be upgraded to where they need to be.)
They are trying to decide. I just don't wanna be the guy that tells them because I can't figure out the issue with right click they need a new server. I'm trying to convince them of that on it's own merits, if that makes sense.
This might not be the best course of action. Right now is a good time to tell them that their previous people violated some super basic best practices and trying to fix a fundamentally broken system might not make any sense. Not virtualized - not a business, just a hobby. Who knows what else is wrong, beyond this hardware issue. Explain to them that they are investing a lot into trying to fix something that should not be a problem at all and even if you can fix the driver issue, it's still not a properly built system. Investing into the old system is just throwing money at existing technical debt, that's bad business.
Identify what is wrong and show how investing in the future is likely dramatically better than investing into past mistakes.
