I’ve had 3 CLOCK_WATCHDOG_TIMEOUT bsods today while playing around in a material, two of these have been when a material is loading after pressing ‘apply’ when changes have been made, the third was after I dropped a material onto the landscape, I believe this was a previously unused material so shaders needed to be compiled but it didn’t get that far before crashing.
I can’t recreate this problem in older engine versions.
My spec:
i7 4790K (overclocked but the third time this happened it was back to stock clocks)
Nvidia GTX970 (factory overclock) 358.91 drivers.
32gb RAM (stock speeds of 1600mhz)
Windows 10 with all latest updates
this system seems stable in every stress test I throw at it and have never had a problem until the 4.11 preview which leads me to Think it might be an engine bug… I could be wrong though!!
In most cases, the engine itself cannot cause a BSOD. It might be triggering Windows driver processes which are causing the BSoD. To that end, I would try to get the December 1st Nvidia driver (359.06) and see if you get any different results. We are currently tracking a possible issue with the latest Dec 21st driver (361.43) on 970 cards, and I don’t want to trade one problem with another for you.
We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.