BSOD on virtual server 2016
-
Doesn't BlueScreenView work with Server 2016?
-
@dustinb3403 said in BSOD on virtual server 2016:
Doesn't BlueScreenView work with Server 2016?
yes, it does. Thanks for the link. Cool feature is that it lets you right click the dump and launch a google search. That said, in my case, it doesn't indicate which driver caused it since it was ntoskrnl.exe that crashed.
-
@mike-davis said in BSOD on virtual server 2016:
@dustinb3403 said in BSOD on virtual server 2016:
Doesn't BlueScreenView work with Server 2016?
yes, it does. Thanks for the link. Cool feature is that it lets you right click the dump and launch a google search. That said, in my case, it doesn't indicate which driver caused it since it was ntoskrnl.exe that crashed.
I was actually just having issues with the same thing on a user system. In our cases (two) one was an Antivirus issue, and the other was a USB driver issue.
-
The clients had an issue with one of the two Xerox drivers because of an issue with Webroot and the Windows 10 creators update. An update from Webroot fixed the problem.
-
Does Windows Debugger give more info than that? Should also tell you what driver caused the crash
-
@mike-davis said in BSOD on virtual server 2016:
The clients had an issue with one of the two Xerox drivers because of an issue with Webroot and the Windows 10 creators update. An update from Webroot fixed the problem.
Drag, a Blue Screen from that incompatibility.
-
@jackcpickup said in BSOD on virtual server 2016:
Does Windows Debugger give more info than that? Should also tell you what driver caused the crash
Bluescreenview tells you that as well. It supports Windows 10 so server 2016 is supported (Same kernel).
-
For a second I was terrified that the capitalization was wrong and that MS made a new version of Virtual Server 2005!
Pheww
-
@scottalanmiller said in BSOD on virtual server 2016:
For a second I was terrified that the capitalization was wrong and that MS made a new version of Virtual Server 2005!
oh, I wanted to be clear it's a VM since most BSODs are caused by drivers and VMs don't have all the third party drivers that physical boxes do.
-
@mike-davis said in BSOD on virtual server 2016:
@scottalanmiller said in BSOD on virtual server 2016:
For a second I was terrified that the capitalization was wrong and that MS made a new version of Virtual Server 2005!
oh, I wanted to be clear it's a VM since most BSODs are caused by drivers and VMs don't have all the third party drivers that physical boxes do.
But this one does, specifically the printer drivers
-
By the way what Xerox drivers do you get? Are using the PCL6 global drivers, do you use those? 90% of my printers are Xerox.
-
@dbeato said in BSOD on virtual server 2016:
By the way what Xerox drivers do you get? Are using the PCL6
I am using the PCL 6. Not sure if it was the global driver. In the process of that driver not rolling, I also installed the PS, PCL5, and XPS. I have since removed the extra drivers and the old drivers from the Konica that the copier replaced.
-
@mike-davis said in BSOD on virtual server 2016:
@dbeato said in BSOD on virtual server 2016:
By the way what Xerox drivers do you get? Are using the PCL6I am using the PCL 6. Not sure if it was the global driver. In the process of that driver not rolling, I also installed the PS, PCL5, and XPS. I have since removed the extra drivers and the old drivers from the Konica that the copier replaced.
Okay, I have the following on my server with Server 2012 R2
-
Have you tried removing any faulty drivers from safe mode?
-
@darek-hamann said in BSOD on virtual server 2016:
Have you tried removing any faulty drivers from safe mode?
I don't know what the faulty drivers are. I removed the printer drivers I don't need through print management and haven't had a blue screen yet, but only time will tell.
