Blue Screen (not BSOD) when using mouse in Windows Server 2012
-
@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.
-
@CCWTech said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:
@scottalanmiller Yeah, I do VM on almost all new servers I set up.
Almost? Need to make that "all".
-
@scottalanmiller LOL... Yeah I was getting that you are a huge VM fan from the other posts. Just curious, are you a Hyper-V or a VMware fan?
-
@CCWTech said in Blue Screen (not BSOD) when using mouse in Windows Server 2012:
@scottalanmiller LOL... Yeah I was getting that you are a huge VM fan from the other posts. Just curious, are you a Hyper-V or a VMware fan?
I try very hard to be a fan of best practices, but not vendors
Hyper-V, VMware, KVM and Xen areal excellent and the right choice at different times. VMware I find rarely appropriate in the SMB space simply because the cost makes it effectively impossible to make business sense because SMBs often have totaly budgets smaller than VMware licensing would be. Same reason that I often find Windows not to make sense, not that it isn't excellent, but because SMBs lack the budgets to be able to get the value out of it.For the SMB, Hyper-V is really the most appropriate most of the time. XenServer can be great too, but Hyper-V more often than not.
-
-
Thanks!
-
What hardware is maxed on out the current system? In what directions are you taxed?
