Windows 10 Fall Creators Update

[howard stern]

Have you turned off the TDR checker? For some reason I have to keep it off or I get the dreaded video card stopped responding in event viewer. Once I disable it that issue goes away and does not return.

Directions to delay or disable TDR's.
I originally set the delay but still had one once in awhile so I completely disabled it and have not had one since.

For 64 bit Windows

Select QWORD (64-bit) value.
Type TdrDelay as the Name and click Enter.
Double-click TdrDelay and add 8 for the Value data and clickOK.

Close the registry editor and then restart your computer for the changes to take affect.

This puts a delay on the tdr checker of 8 seconds thus the gpu can stop responding for 10 seconds, usually this fixes the problem, if you are still suffering from this issue (after updates or a reinstall of drivers, you know all that annoying driver stuff)
Then do this, do the same thing but instead of "TdrDelay" type "TdrLevel" enter the data value as 0 (it is set to that natively, but double check) then delete the TdrDelay,

Restart

 

[deadite_9]

No, I've never disabled the TDR check. Except for a very small handful of times over the past few years when the driver actually stopped responding, it's honestly never been an issue. Not really sure what's going on right now, or if it's even video card/driver related, but the most recent one happened while I was browsing the other night-- the screen seemed to flicker for a second and then it was back to normal. (In fact, it happened/recovered so fast that I wasn't even sure that it was a TDR until I checked the event viewer a few minutes later.)

My real problem, though, has been increased instability over the past week, even though the computer's sat idle for probably 80% of that time (the most that I've done since last weekend is install a few games on Steam, which I haven't even played yet). Thursday morning I got up and it appeared that it was just sitting idle, so I left it alone so that MBAM could do its daily scan before I shut her down to go to work. Checked back before heading out the door, and I got no response when I moved the mouse (everything was lit up and the fans were spinning, but the monitor was off and it wasn't waking back up). Wasn't 100% sure about shutting her down blind using just the keyboard, so I hit the reset switch and then checked the event viewer... apparently it had locked up and rebooted just before 4am, about an hour and a half before I got up. But if it was because of a bluescreen, it's not supposed to actually do anything but just sit there, because I have the automatic reboot option unchecked.

Yesterday morning I got up and checked it by moving the mouse, and the screen turned back on like it should. But when I went to shut it down a little later, I noticed there was no clock/date in the system tray, and hovering over the taskbar just gave me the blue spinny thing next to the cursor. No idea what happened there, but I assumed that explorer had crashed at some point. I held the power button in to shut it down, and went on to work.

Didn't bother with it at all last night, but when I powered it on this morning, I saw another entry in event viewer that said that the previous shutdown was unexpected, but it was referencing a time that was earlier than when I had held the power button in to kill it on Friday morning. So something really weird had happened overnight for the second night in a row.

After checking the event viewer, I decided to check both MBAM and Defender to make sure that they had updated. MBAM was fine, but opening up the Security Center caused it to just lock up hard. After that nothing was responding when I clicked it. Was really getting pissed by this point, so I just went ahead and hit the reset switch.

That was apparently the last straw, because it never came back up after that. It ran checkdisk as it was rebooting, and then dumped me into startup repair, which failed. Rebooting after that just gave me the spinning dots ad infinitum. Luckily I had a backup image from 12/22 that had everything installed/activated (minus my Steam games), so that got me back up and running.

The problem is, there weren't any Windows updates in the last week (apart from Defender definitions), so I have absolutely no idea what caused this PC to crash and burn so hard. It literally came from out of nowhere.

But it really doesn't matter. It was awesome having an 8-core/16-thread CPU for a few brief weeks, but X299 is dead to me. Just ordered an 8700K, along with a Maximus X Code, so I'll have new(er) and (more) expensive toys to play with by next weekend.