Product: Microsoft® Windows® Operating Systemīug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed. This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x5D390)īugcheck code: 0x116 (0xFFFFFA8012B101A0, 0xFFFFF88004B06D90, 0x0, 0x2)įile path: C:\Windows\system32\drivers\dxgkrnl.sys On Sat 4:52:16 PM your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\062219-29031-01.dmp Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps. For best results, configure your system to write out complete or automatic crash dumps. This system is not configured for complete or automatic crash dumps. Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z87-PROĬPU: GenuineIntel Intel(R) Core(TM) i7-4770K CPU 3.50GHz Intel8664, level: 6Ĭrash dumps are enabled on your computer. Windows version: Windows 7 Service Pack 1, 6.1, build: 7601 and since these errors stopped abruptly so long ago, maybe it was fixed then? These might have nothing to do with the current problem. There's nothing at all from the current string of problems. WhoCrashed found no logs to analyze since last June, long before the current issues developed. It's hit-or-miss if it offers that option pressing F8 during Post usually only brings up a prompt to choose a drive to boot from, rather than the Safe Mode page. My only known fix is to press the reset button on the case, and boot into Safe Mode, if it gives me that option. Windows says the driver is up-to-date, and cannot resolve this issue.
Windows says it cannot load the drivers for this component (code 31). Under the System Devices list, the only driver error indicated is for something called the "AMDA00 Interface", made by ASUSTek Computer Inc.
PC will boot successfully into any Safe Mode if told to, and has not yet suffered any similar errors or failures while in this mode. Rarely, the keyboard fails to activate during Post, making it impossible to select Safe Mode instead of the default Normal boot. This eventually became the persistent default behavior. Monitors would eventually go to sleep, indicating they are not receiving any data. If the system successfully boots in normal mode (now a very rare occurrence), this is still the inevitable fate.Īs trouble progressed, black screen would begin to occur immediately following the login screen, with no progress past that point. The first few times, the screens would randomly turn black after approximately 5 to 60 minutes of runtime.
0 kommentar(er)
