[jogibso1]

This has happened every day in the last 2 weeks for me. That can't be good. No major changes as far as I know. Googling tells me it is a video plugin error, but I am not sure how true that is.

The only CONSISTENT thing I have noticed is that this happens every time the computer is placed into sleep mode. It happens occasionally other times too, at least daily, but definitely happens if I go into sleep mode.

I've changed my setting so that it never sleeps, not screen saver, etc. But I still come back to the machine with the notification that "windows has recovered from an unexpected shutdown".

I'd love to figure out what it is!

I have a Dell XPS 8500, 8GB RAM, Intel Core i5-3450 CPU @ 3.1 GHz. Windows 7 64 but

I can send it to the blue screen with a simple directive to hibernate/sleep, so I am glad to gather any info I need to....just need to know what folks would like to see. Thanks for the help!
Josh

Edited by jogibso1, 28 September 2013 - 04:58 PM.

[Advertisements]

Hi Josh,

It seems there are a number of things that may cause it.

Here is a link from MS with several things to try.

http://answers.micro...AllReplies#tabs

[Dave46]

Hi Josh,

It seems there are a number of things that may cause it.

Here is a link from MS with several things to try.

http://answers.micro...AllReplies#tabs

[rshaffer61]

Just to add some help for everyone.

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads







Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program

[jogibso1]

Hi Just saw this. Will get right on it.

In the meantime, here is the crash report from Windows once it restarts:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 4a
BCP1: 00000000736E2E09
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF88008A7EB60
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\093013-29811-01.dmp
C:\Users\Josh Desktop\AppData\Local\Temp\WER-52431-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft....88&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

[jogibso1]

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

computer name: JOSHDESKTOP-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™ i5-3450 CPU @ 3.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8551428096 total
VM: 2147352576, free: 1899122688




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 10/1/2013 1:32:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\093013-29811-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x736E2E09, 0x2, 0x0, 0xFFFFF88008A7EB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 10/1/2013 1:32:05 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4A (0x736E2E09, 0x2, 0x0, 0xFFFFF88008A7EB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/28/2013 3:00:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092813-22666-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73A22E09, 0x2, 0x0, 0xFFFFF88007C64B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/28/2013 7:12:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092813-21231-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x750D2E09, 0x2, 0x0, 0xFFFFF8800867BB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 9/27/2013 3:17:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-22635-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73932E09, 0x2, 0x0, 0xFFFFF88008A7EB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/26/2013 8:12:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-47720-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73B42E09, 0x2, 0x0, 0xFFFFF880088B2B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/26/2013 7:42:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-19125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73EF2E09, 0x2, 0x0, 0xFFFFF88007CFCB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/26/2013 4:24:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-24523-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x74892E09, 0x2, 0x0, 0xFFFFF880088F2B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/26/2013 11:21:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-19624-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73E52E09, 0x2, 0x0, 0xFFFFF88007C9AB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/26/2013 1:51:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092513-49249-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x736E2E09, 0x2, 0x0, 0xFFFFF88008A9AB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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 9/23/2013 1:26:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092313-19390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x74102E09, 0x2, 0x0, 0xFFFFF8800868EB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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 9/23/2013 11:11:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092313-24476-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73C42E09, 0x2, 0x0, 0xFFFFF88008858B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 9/22/2013 8:15:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092213-18782-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73B52E09, 0x2, 0x0, 0xFFFFF88007EB9B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 9/22/2013 4:15:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092213-31418-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73E42E09, 0x2, 0x0, 0xFFFFF88008664B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/21/2013 2:02:04 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092013-35349-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73EB2E09, 0x2, 0x0, 0xFFFFF88007D4AB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




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

20 crash dumps have been found and analyzed. Only 15 are included in this report. 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:

atikmpag.sys (AMD multi-vendor Miniport 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.

[rshaffer61]

WHEW!!!!!!! OK first question is what AV, Spyware, malware software do you have installed?

[jogibso1]

I very recently uninstalled AVG, as I was advised by reading others in this forum. I guess I haven't replaced it: I tried to activate Windows Dfefender, cant tell if it worked.

I have Zone Alarm as my firewall

[rshaffer61]

OK you need to update this driver.

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

[jogibso1]

Trying my best to get it to update and can't. Says its up to date. Any pointers?

Edited by jogibso1, 30 September 2013 - 08:42 PM.
profanity

[rshaffer61]

Try this:

Download DriverMax and have it scan your system. It will open their website with all the out of date drivers you can update. With the free version you can update only 2 drivers per day so if you have a lot of them it will take a few days to get everything updated. I have been using it for about 4 months now and like it better then any other utility out there for keeping my drivers up to date.
If you want you can post screenshots of all the drivers in the list that need to be updated and I will suggest in what order to get them.

[jogibso1]

This is very helpful thank you so much. Here is a screenshot...I presume I want to tackle the first one first? (Sorry, I think I doubled up a couple of the screencaps)

[rshaffer61]

Start with the first two AMD Radeon and the AMD High Definition.
Download and install those two. The hard thing is you will be only able to do two at a time every day since this is the free version. I use this to keep my drivers up to date and have had hardly any issues with it for the past 2 years now.

[jogibso1]

I went ahead and updated those two, and it seems to have taken care of it. I will get the rest too just to be sure. Thanks so much for this!!

[rshaffer61]

OK then work in order and if anything goes wrong let me know. Once you have everything updated then let me know if everything is working correctly. I will wait for your updates.

[jogibso1]

well, I thought I was done but came bacl home today to a blue screen error. I have only updated those two drivers so far, but plan to do two more tonight. Could you let me know if you think any of those others from the list above would take priority?

here is the crash report again:


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

computer name: JOSHDESKTOP-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™ i5-3450 CPU @ 3.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8551428096 total
VM: 2147352576, free: 1921499136




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 10/2/2013 7:33:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100213-50029-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x74A12E09, 0x2, 0x0, 0xFFFFF880088A1B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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 10/2/2013 7:33:09 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4A (0x74A12E09, 0x2, 0x0, 0xFFFFF880088A1B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 10/1/2013 1:32:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\093013-29811-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x736E2E09, 0x2, 0x0, 0xFFFFF88008A7EB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/28/2013 3:00:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092813-22666-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73A22E09, 0x2, 0x0, 0xFFFFF88007C64B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 9/28/2013 7:12:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092813-21231-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x750D2E09, 0x2, 0x0, 0xFFFFF8800867BB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 9/27/2013 3:17:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-22635-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73932E09, 0x2, 0x0, 0xFFFFF88008A7EB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/26/2013 8:12:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-47720-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73B42E09, 0x2, 0x0, 0xFFFFF880088B2B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/26/2013 7:42:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-19125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73EF2E09, 0x2, 0x0, 0xFFFFF88007CFCB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/26/2013 4:24:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-24523-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x74892E09, 0x2, 0x0, 0xFFFFF880088F2B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/26/2013 11:21:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092613-19624-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73E52E09, 0x2, 0x0, 0xFFFFF88007C9AB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 9/26/2013 1:51:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092513-49249-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x736E2E09, 0x2, 0x0, 0xFFFFF88008A9AB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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 9/23/2013 1:26:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092313-19390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x74102E09, 0x2, 0x0, 0xFFFFF8800868EB60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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 9/23/2013 11:11:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092313-24476-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73C42E09, 0x2, 0x0, 0xFFFFF88008858B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 9/22/2013 8:15:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092213-18782-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73B52E09, 0x2, 0x0, 0xFFFFF88007EB9B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 9/22/2013 4:15:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092213-31418-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x4A (0x73E42E09, 0x2, 0x0, 0xFFFFF88008664B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




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

21 crash dumps have been found and analyzed. Only 15 are included in this report. 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:

atikmpag.sys (AMD multi-vendor Miniport 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.