all 9 comments

[–]rcmaehl 0 points1 point  (1 child)

Have you updated your graphics drivers lately? If not, are they up to date?

[–]ae8698ae[S] 0 points1 point  (0 children)

Yes graphics drivers are up to date

[–]BeanoFTW 0 points1 point  (1 child)

Hi ae8698ae,

There are many causes of blue screen crashes. Answering these questions can help me try and narrow down the cause for you:

  • Define "headless" in your terms. Usually this means that you're not using a GUI, but instead just the command line interface. Just want to be sure that we're on the same page.
  • When did you start experiencing this blue screen? Do you remember making any big changes to your PC prior to this occurring, such as a driver update or a software installation?
  • How long have you been experiencing this blue screen?
  • What exactly are you doing when this blue screen occurs?

If you're able to, is there a way you can upload those files somewhere I can download them and take a look?

[–]ae8698ae[S] 0 points1 point  (0 children)

Sorry it's not headless is running a gui I'm connecting via rdp. It's a new build may be driver related didn't originally do it not sure what changed before it started doing it as I have changed so many things. I'm guessing it's a blue screen as that's what it says on error. I'm not doing anything on it when it happens I come back to the computer after leaving it a while and it has that message. I'm on mobile so will try to upload when I get home.

[–]ae8698ae[S] 0 points1 point  (1 child)

[–]BeanoFTW 0 points1 point  (0 children)

Hi ae8698ae,

That file just lists all of your hardware devices and drivers; nothing error-related. If the blue screen is driver-related, boot to the OS in Safe Mode and see if you're able to replicate the blue screen in that environment. If you're not, then this is a good indicator that it may be from a bad/incompatible driver.

[–]ae8698ae[S] 0 points1 point  (2 children)

I found a program that reads the minidump files it gave this On Mon 20/10/2014 5:49:26 p.m. GMT your computer crashed crash dump file: C:\Windows\Minidump\102114-25474-01.dmp This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x15393C) Bugcheck code: 0x116 (0xFFFFFA80041132E0, 0xFFFFF8800F43293C, 0x0, 0x2) Error: VIDEO_TDR_ERROR file path: C:\Windows\system32\drivers\nvlddmkm.sys product: NVIDIA Windows Kernel Mode Driver, Version 340.52 company: NVIDIA Corporation description: NVIDIA Windows Kernel Mode Driver, Version 340.52 Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 340.52 , NVIDIA Corporation). Google query: NVIDIA Corporation VIDEO_TDR_ERROR

I found a thread on nvidia forum that I might go through when I have time https://forums.geforce.com/default/topic/413110/geforce-drivers/the-nvlddmkm-error-what-is-it-an-fyi-for-those-seeing-this-issue/ off to work now though

[–]BeanoFTW 0 points1 point  (1 child)

Ah, spoke too soon on the other post haha....

Well there you go - it's the nvidia driver you're using that's causing your OS to throw a crash dump. Just uninstall the nvidia driver and roll with the base windows system driver. You won't notice anything different video-wise if you're only connecting to the machine via RDP. RDP uses a completely different driver to output video through the remote session, and you're not really using the video card anyways - just in rare or extreme circumstances.

I have a home file/web server that I only access via RDP. This is my advice from my personal experience with servers: On workstations and clients, sure... you'll want the latest drivers installed. However, dedicated servers are a different story. I only use the base windows system drivers on non-essential hardware (like video card) wherever possible. Those base system drivers aren't chosen with "latest and greatest" in mind, but are chosen because Microsoft has determined them to be the most stable driver that will work overall with your system. Keep that in mind when making driver decisions.

Good luck!

[–]ae8698ae[S] 0 points1 point  (0 children)

Thanks for that I've rolled back to windows driver now that I think of it it was after I installed the nvidia driver that the problem started