![]() ![]() I would try each one longer, until a crash occurs even if it takes a day. However, framerates were consistently lower across the board and I was getting stuttering left and right. Is this a common problem and does anyone have any idea how to fix it? Note that every crash occurred while playing Overwatch, and that no two blue screens share the exact same problem. Possibly this problem is caused by another driver on your system that cannot be identified at this time. Your system configuration may be incorrect. The crash took place in a standard Microsoft module. This was probably caused by the following module: msahci.sys (0xFFFFF88000E34B54)īugcheck code: 0xD1 (0xFFFFFFFF8B481275, 0xB, 0x0, 0xFFFFF88000E34B54)įile path: C:\Windows\system32\drivers\msahci.sysīug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This afternoon I reinstalled the drivers again, but seemingly to no avail.Ĭrash dump file: C:\Windows\Minidump\022817-16910-01.dmp Google query: Advanced Micro Devices, Inc. ![]() It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.). This was probably caused by the following module: atikmdag.sys (atikmdag+0x10B42EE)īugcheck code: 0x3B (0xC000001D, 0xFFFFF8800FED22EE, 0xFFFFF88007F54830, 0x0)įile path: C:\Windows\system32\drivers\atikmdag.sysĭescription: ATI Radeon Kernel Mode Driverīug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.Ī third party driver was identified as the probable root cause of this system error. However, only a few minutes after I reinstalled the drivers, I got another blue screen. Possibly this problem is caused by another driver that cannot be identified at this time.Īt first, I assumed it was a driver issue and simply reinstalled my drivers. The crash took place in the Windows kernel. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. Product: Microsoft® Windows® Operating Systemīug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)īugcheck code: 0xA (0x48, 0x2, 0x0, 0xFFFFF80002ECCC79)įile path: C:\Windows\system32\ntoskrnl.exe ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |