Bleeping Computer -
Likely a bad video card
I processed the five (5) dumps found in the Sysnative zipped folder.
I experienced symbol errors on several of the dumps. Basically, each Microsoft driver is looked up at a Microsoft symbol site and some of your Windows drivers are not recognizable to the Microsoft symbol site. Some reasons this can happen -
- the driver is corrupted and the file characteristics have changed
- there is a problem with the Microsoft symbol site
- a new version of the Microsoft driver was released; you updated it via Windows Updates, but the new driver has not yet been placed on the symbol server.
All of that is good to know (I guess), but what it comes down to is that I was unable to accurately process most of your dumps due to bad symbols.
The bugcheck and probable causes from your 5 dumps -
BugCheck 100000EA, {ffffb00aef0cb1c0, 0, 0, 0} Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45 ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 133, {1, 1e00, fffff80611d73358, 0} Probably caused by : condrv.sys ( condrv!CdpCreateProcess+14f ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 100000EA, {ffffac843b48e300, 0, 0, 0} Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45 ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 100000EA, {ffff9085fcf4a540, 0, 0, 0} Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45 ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` BugCheck 100000EA, {ffff828ad52a4040, 0, 0, 0} Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45 ) ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
0xea - This is the bugcheck that you described as "thread stuck in driver". Here is additional information on it -- indicates that a thread in a device driver is endlessly spinning. The likely cause - A device driver is spinning in an infinite loop, most likely waiting for hardware to become idle. This usually indicates problem with the hardware itself, or with the device driver programming the hardware incorrectly. Frequently, this is the result of a bad video card or a bad display driver.
0x133 - DPC Watchdog Violation - indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above. The value of Parameter 1 indicates whether a single DPC exceeded a timeout, or whether the system cumulatively spent an extended period of time at IRQL DISPATCH_LEVEL or above.
Usually in Windows, the word "WATCHDOG" refers in some manner to video.
The probable causes -
- dxgkrnl.sys - Microsoft DirectX Graphics kernel driver
- condrv.sys - simply listed as a "console driver"
The driver download site for your Dell system - https://www.dell.com/support/home/us/en/04/product-support/product/precision-17-7730-laptop/drivers
Also, each dump named your ATI video drivers -
atikmdag.sys Mon Jun 18 09:29:42 2018 (5B27DDF6) atikmpag.sys Mon Jun 18 09:01:46 2018 (5B27D76A)
I don't see these particular drivers at the Dell driver site, so go to ATI to update them. I'm positive that they have newer drivers than those two June 2018 drivers that you have in your system -
First, however, it is extremely important for you to create a Windows system restore point so that you can easily un-do the driver updates if you need to -
After the restore point is created, then go ahead and update the ATI drivers.
That is it for now.
Regards. . .
jcgriff2
0 comments:
Post a Comment