Sudden blackouts Windows 101803
-
@gjacobse Will be doing this as well, thanks Gene
-
The experience we have had was due to Dell Services and other programs running on startup. I have removed them using autoruns from Sysinternals.
-
@dbeato said in Sudden blackouts Windows 101803:
The experience we have had was due to Dell Services and other programs running on startup. I have removed them using autoruns from Sysinternals.
We've got VERY little of that, totally clean internal build.
-
@scottalanmiller said in Sudden blackouts Windows 101803:
@dbeato said in Sudden blackouts Windows 101803:
The experience we have had was due to Dell Services and other programs running on startup. I have removed them using autoruns from Sysinternals.
We've got VERY little of that, totally clean internal build.
okay, so are you using a Golden Image correct?
-
@scottalanmiller said in Sudden blackouts Windows 101803:
We've got VERY little of that, totally clean internal build.
@dbeato said in Sudden blackouts Windows 101803:
okay, so are you using a Golden Image correct?
The former does mot mean the latter. Though it does mean the latter is at least possible. But it is highly unlikely. Using imaging takes more resources, that mostly is not worth it.
-
@dbeato said in Sudden blackouts Windows 101803:
@scottalanmiller said in Sudden blackouts Windows 101803:
@dbeato said in Sudden blackouts Windows 101803:
The experience we have had was due to Dell Services and other programs running on startup. I have removed them using autoruns from Sysinternals.
We've got VERY little of that, totally clean internal build.
okay, so are you using a Golden Image correct?
Just the Windows install media.
-
@jaredbusch said in Sudden blackouts Windows 101803:
@scottalanmiller said in Sudden blackouts Windows 101803:
We've got VERY little of that, totally clean internal build.
@dbeato said in Sudden blackouts Windows 101803:
okay, so are you using a Golden Image correct?
The former does mot mean the latter. Though it does mean the latter is at least possible. But it is highly unlikely. Using imaging takes more resources, that mostly is not worth it.
Correct, it's a small environment and this is the first of new machines. We'd be making a golden image for about eight people. Which could make sense, but as we are planning to move to Windows Home, instead of Pro, it makes even less sense going forward.
-
Tried this, but it didn't work...
Timeout Detection and Recovery is a Windows feature that can detect when the video adapter hardware or a driver on your computer has taken longer than expected to complete an operation. When this occurs, Windows attempts to recover and reset the graphics hardware. If the GPU is unable to recover and reset the graphics hardware in the time permitted (two seconds), your system may become unresponsive, and display the error message “Display driver stopped responding and has recovered.”
Giving it 8 seconds instead of the default two as recommended by Microsoft to fix some issues
-
@scottalanmiller said in Sudden blackouts Windows 101803:
@dbeato said in Sudden blackouts Windows 101803:
@scottalanmiller said in Sudden blackouts Windows 101803:
@dbeato said in Sudden blackouts Windows 101803:
The experience we have had was due to Dell Services and other programs running on startup. I have removed them using autoruns from Sysinternals.
We've got VERY little of that, totally clean internal build.
okay, so are you using a Golden Image correct?
Just the Windows install media.
So you just reinstall Windows which is fine. Which we do, but the issue happened to companies that just had the standard image (OEM) from Dell and the Dell Support Services were there.
-
@jaredbusch said in Sudden blackouts Windows 101803:
@scottalanmiller said in Sudden blackouts Windows 101803:
We've got VERY little of that, totally clean internal build.
@dbeato said in Sudden blackouts Windows 101803:
okay, so are you using a Golden Image correct?
The former does mot mean the latter. Though it does mean the latter is at least possible. But it is highly unlikely. Using imaging takes more resources, that mostly is not worth it.
Yeah, you are correct. Small customers rarely would want to do imaging for us, so we reinstall most of the time to have a clean OS.
-
Errors still keep happening, started trying with older drivers to see which one finally works and resolves the issue.
We have the event logging now:
Event ID 4101
display driver amdkmdap stopped responding and has successfully recoveredSo it is some driver issue.
-
Here is what Reliability Monitor says..
-
And digging in...
-
@EddieJennings found a BIOS update to apply. Trying that...
-
@scottalanmiller We are testing an updated driver + the TDR registry fix before trying the upgrade on the BIOS
-
Cumulative 1803 update suddenly available for it. Giving that a shot now.
-
Before the update, we ran Furmark for 30 minutes to stress test the gpu and try to trigger the error but the gpu ran perfectly without a single error.
-
@scottalanmiller triggered the error again, so updates didn't help
.Ran a webgl benchmark in chrome on one monitor while surfing on the other. Watching CPUZ, temp was reaching 60C when the errors where logged.
-
@romo said in Sudden blackouts Windows 101803:
@scottalanmiller triggered the error again, so updates didn't help
.Ran a webgl benchmark in chrome on one monitor while surfing on the other. Watching CPUZ, temp was reaching 60C when the errors where logged.
Now that's getting pretty warm.
-
@EddieJennings is going to play with it shortly. His local Microcenter just opened 12 minutes ago. He's going to pick up thermal grease, go in, and reseat everything, regrease the CPU, do the BIOS update, and we'll test again. If that doesn't work, this afternoon he's going to pop in an NVidia card to see if we can bypass the problem that way.
