Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

BSOD - atikmpag.sys was named in most of WhoCrashed report - Help plea


  • Please log in to reply

#1
Tungsten72

Tungsten72

    Member

  • Member
  • PipPip
  • 65 posts
Hello, have been having a lot of BSOD's while gaming. Updated drivers for AMD Catalyst Video Card (XFX Radeon HD 6770) a few days ago & BSOD's have happened with more frequency, almost daily. Tonight tried to do some google searches. Found a recommendation on another site for WhoCrashed, downloaded that free version & got this report. Please let me know what other info you might need.

System Information (local)
--------------------------------------------------------------------------------

computer name: *******
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Aspire M3410, Acer
CPU: AuthenticAMD AMD Athlon™ II X4 645 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4286328832 total
VM: 2147352576, free: 1920376832




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 1/26/2014 3:41:57 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012514-20514-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0xA20C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800425220C, 0xFFFFF88003824CA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_SERVICE_EXCEPTION



On Sun 1/26/2014 3:41:57 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0xA20C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800425220C, 0xFFFFF88003824CA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_SERVICE_EXCEPTION



On Fri 1/24/2014 4:33:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012314-22214-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFA800A6E70B0, 0x0, 0xFFFFF800033F6123, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 1/22/2014 9:47:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012214-50871-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x36880)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF800032DA512)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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. IRQL_NOT_LESS_OR_EQUAL



On Wed 1/22/2014 1:01:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-24102-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF88005609637)
Bugcheck code: 0xD1 (0x4C4, 0x2, 0x0, 0xFFFFF88005609637)
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 Sun 1/19/2014 11:14:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011914-20373-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x6879)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88000C62879, 0xFFFFF8800A557880, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sun 11/3/2013 9:41:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110313-18766-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x5EE3)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x130009, 0xFFFFFA8005E72980)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 Sat 11/2/2013 12:09:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110113-19609-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x28546)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800516F546, 0xFFFFF88009D720A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Fri 11/1/2013 12:30:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\103113-17425-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D27D)
Bugcheck code: 0xFE (0x6, 0xFFFFFA8007333300, 0x48766544, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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 10/31/2013 2:10:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\103013-19780-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF88004A1B61E)
Bugcheck code: 0x50 (0xFFFFF8A00FBD31E0, 0x1, 0xFFFFF88004A1B61E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

16 crash dumps have been found and analyzed. Only 10 are included in this report. 5 third party drivers have 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.)
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
atipmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)
bckd.sys (K9 Web Protection Driver, Blue Coat Systems, Inc.)
atihdw76.sys (AMD High Definition Audio Function Driver, Advanced Micro Devices)

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.
  • 0

Advertisements


#2
KingdomSeeker

KingdomSeeker

    Member

  • Member
  • PipPip
  • 80 posts
Please go to the website of your video card manufacturer and download the drivers from there. If the install doesn't solve the issue then go to devise manager in the control panel and uninstall them and reboot. Windows should find the updated drivers and install them. Please let us know if this works. Thank you and good luck.
  • 0

#3
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Another suggestion is to uninstall the Catalyst suite and just install the device driver itself. The suite has been shown to cause issues many times and the uninstall of it usually takes care of the BSOD that is referenced.
  • 0

#4
Tungsten72

Tungsten72

    Member

  • Topic Starter
  • Member
  • PipPip
  • 65 posts
Hello, thanks for your replies. rshaffer61, I don't know how to uninstall only the Catalyst. Could you give instructions on how to do this? Thank you.

Another BSOD today here is the WhoCrashed report:

On Mon 1/27/2014 12:02:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012614-20295-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800032725B7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 1/27/2014 12:02:59 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngRestoreFloatingPointState+0xDC98)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800032725B7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.





ALSO, I just happened to have Speccy installed on this computer. Decided to check some temps cuz I've been reading that might cause BSOD... (Speccy is updated) So here are the temps...



Operating System
Windows 7 Home Premium 64-bit SP1
CPU
AMD Athlon II X4 645 69 °F
Propus 45nm Technology
RAM
4.00GB Dual-Channel DDR3 @ 664MHz (9-9-9-24)
Motherboard
Acer Aspire M3410 (CPU 1) 97 °F
Graphics
ASUS VS247 (1920x1080@60Hz)
1024MB ATI AMD Radeon HD 6700 Series (XFX Pine Group) 106 °F
Storage
931GB Western Digital WDC WD10EADX-22TDHB0 SCSI Disk Device (RAID)
Optical Drives
HL-DT-ST DVDRAM GH60N SCSI CdRom Device
Audio
Realtek High Definition Audio
On Mon 1/27/2014 12:02:59 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngRestoreFloatingPointState+0xDC98)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800032725B7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.

Edited by Tungsten72, 26 January 2014 - 06:45 PM.

  • 0

#5
Tungsten72

Tungsten72

    Member

  • Topic Starter
  • Member
  • PipPip
  • 65 posts
I forgot to also mention I have done a ScanDisk check. The day I first posted here.



KingdomSeeker: That is where I got the drivers that I updated a few days ago. From their website. Are you saying to go there again & reinstall?
  • 0

#6
Tungsten72

Tungsten72

    Member

  • Topic Starter
  • Member
  • PipPip
  • 65 posts
According to AMD's website I have the latest Driver available: Driver Version 13.251.0.0 Driver Date: 12/6/13.
  • 0

#7
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Did you install just the driver or the whole Catalyst suite?
Most people will download and install the complete suite.
Your video does show a elevated temperature also.
  • 0

#8
Tungsten72

Tungsten72

    Member

  • Topic Starter
  • Member
  • PipPip
  • 65 posts
Well I suppose you are right I got the whole thing, here's the exact page I downloaded from: After answering questions from drop down menu's like OP system... AMD driver Series... Windows7 64 bit... etc it leads me to this page:

http://support.amd.c...ktop?os=Windows 7 - 64

I don't know where to get video card driver only & not the whole suite.

Edited by Tungsten72, 26 January 2014 - 07:14 PM.

  • 0

#9
Tungsten72

Tungsten72

    Member

  • Topic Starter
  • Member
  • PipPip
  • 65 posts
The link I provided in the above post is not exactly the page I see. Don't know why it won't go to the exact page. But basically it give me only the one option from that list you see... the 3rd one down that's 208mb


Catalyst Software Suite 208 MB 13.12 12/18/2013 Download
Description:

Package contains the following graphics drivers and dependent/required software for the products specified in the current version's official release notes for the 64 bit version of Windows Vista:
Display Driver ver. 13.251
OpenCL™ Driver ver. 10.0.1348.5
Catalyst Control Center ver. 2013.1206.1602.28764
Languages:
Czech, Danish, German, Greek, US English, Spanish, Finnish, French, Hungarian, Italian, Japanese, Korean, Dutch, Norwegian, Polish, Portuguese, Russian, Swedish, Thai, Turkish, Chinese (Traditional), Chinese (Simplified)
  • 0

#10
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Within that suite is the driver. Once you have the driver then just update through the Device Manager and have it go to where the driver is to install it. I imagine it is a zip file so if you unzip it to the desktop everything will be in that folder.
  • 0

Advertisements


#11
Tungsten72

Tungsten72

    Member

  • Topic Starter
  • Member
  • PipPip
  • 65 posts
Device Manager says there are no updates for the driver at this time.

Are you saying uninstall AMD Catalyst & then upon rebooting go into device manager & install driver from there? What if it gives me the Suite again?

Edited by Tungsten72, 26 January 2014 - 08:17 PM.

  • 0

#12
Tungsten72

Tungsten72

    Member

  • Topic Starter
  • Member
  • PipPip
  • 65 posts
I opened up the case to vacuum & make sure everything was seated firmly. Took another look at Speccy afterward & strangely its running hotter now:

Operating System
Windows 7 Home Premium 64-bit SP1
CPU
AMD Athlon II X4 645 92 °F
Propus 45nm Technology
RAM
4.00GB Dual-Channel DDR3 @ 665MHz (9-9-9-24)
Motherboard
Acer Aspire M3410 (CPU 1) 115 °F
Graphics
ASUS VS247 (1920x1080@60Hz)
1024MB ATI AMD Radeon HD 6700 Series (XFX Pine Group) 110 °F
Storage
931GB Western Digital WDC WD10EADX-22TDHB0 SCSI Disk Device (RAID)
Optical Drives
HL-DT-ST DVDRAM GH60N SCSI CdRom Device
Audio
Realtek High Definition Audio
  • 0

#13
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
You would need to uninstall the complete suite first. Then reboot and install only the driver.
  • 0

#14
KingdomSeeker

KingdomSeeker

    Member

  • Member
  • PipPip
  • 80 posts
I'm also thinking you should probably blow out the dust that may be causing the overgeating with an air can or even a vacuum cleaner that can blow air.
  • 0

#15
Tungsten72

Tungsten72

    Member

  • Topic Starter
  • Member
  • PipPip
  • 65 posts
KingdomSeeker, I did the canned air & vacuum. The heat sink on the CPU was caked with dust, but it looks good now. But temps still running high. Here's the latest. I'll uninstall that Catalyst tomorrow & reinstall the driver only & see how that goes.

Worth noting... the video card & power supply were installed in July. If you want to take a gander at that convo here is the link (user name Jen147 is my geeks to go account, Tungsten72 is my son's) http://www.geekstogo...card-confusion/

Thank you for your time.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP