Quantcast
Viewing all articles
Browse latest Browse all 6058

Solved: Constant BSODs for any 3d application!

Hey everybody I have been suffering from constant BSODs from the same two files which always happens during gameplay of any games (it happens for some games faster than others). I know it is a driver problem as a computer shop tested ALL the hardware in my pc and everything came back ok. I have tried everything to get rid of this BSOD and have attached the info from the Crash Dump below. I have already tried updating Windows 7, updating Bios, checked temps in pc (idle it sits around 40 and under load its anywhere from 60-70), uninstalling drivers using DDU and reinstalling, reverted to previous versions of the driver/betas, I have done the trick with copying the file to the desktop and expanding it myself through cmd... all to no avail. If anyone needs more info please let me know and I will provide as best as possible. At this point I'm about ready to say to heck with AMD and go Nvidia. The report from the Crash Dump is always the same, and it is always the same two files being reported: Atikmdag.sys and Dxgmms1.sys.



Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 23/01/2014 5:09:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012314-14227-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x5B3D)
Bugcheck code: 0xD1 (0x3F8018, 0x2, 0x1, 0xFFFFF8800517CB3D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 23/01/2014 5:09:22 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x4D9E1)
Bugcheck code: 0xD1 (0x3F8018, 0x2, 0x1, 0xFFFFF8800517CB3D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL








Conclusion





2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Viewing all articles
Browse latest Browse all 6058

Trending Articles