1 Reply Latest reply on Apr 22, 2014 10:15 AM by allan_intel

    BETA Display Driver (10.18.10.3540) Appears to Cause Reboots w/Remote Desktop

    Hannes

      I have configured a new NUC and have noticed a problem that I wanted to report and see if anyone else has encountered.

      The problem was that I observed frequest spontaneous reboots of the NUC when connected to it via Remote Desktop. I couldn't stay connected for more than about 10 minutes maximum before  the NUC would reboot. Looking in the event log I would observe the following errors each time:


      The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

       

      The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000094, 0xfffff800ca81dcfa, 0xffffd000407b1130, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 042014-6421-01.

       

      I ran a series of tests including comprehensive memory tests and these all came back fine.

       

      Since I was running a BETA Intel Display driver (10.18.10.3540) I thought that I would go back to the latest released version (10.18.10.3496) and this seems to have resolved the issue. I've run several hours now via remote desktop with no crashes.

       

      I was just curious to see if anyone reported a similiar experience.

       

      System Configuration:

      Intel NUC D54250WYB with the new chassis that accomodates the laptop HD
      BIOS 0025
      16GB Corsair Vengeance DDR3L DRAM
      256GB Crucial M500 mSATA SSD
      1TB Seagate 9.5mm 7200RPM HD
      Intel 7260 AC WiFi
      Windows 8.1 Pro Update 1 with all the latest Windows updates installed + Windows Media Center

      Only application installed so far are:

      Symantec System Recovery Desktop Edition 2013 w/SP2
      VMware Workstation 10.0.2

       

      Again, dropping back to the latest released video driver (10.18.10.3496) resolved the issue. I had initially installed the BETA because it said that it resolved an issue that it sounds like I may encounter when I connect to an AV system.