Multiple BSOD lately, display problem - atikmpag.sys

RockySC · 17 Apr 2015

Hi guys, I really hope you can help me with this issue. I have been having multiple BSOD lately and there doesn't seem to be an end in sight for me. These problems happen randomly, not when I'm playing games (I almost never use my computer for that anyway), just at any random times. I know next to nothing about the technical aspects of computers, so bare with me. I'm pretty sure it has to do with my display adapter. Almost every time before the BSOD hits my screen flashes, goes black then comes back all glitched out, then a bubble on the lower right hand corner pops up saying the display driver has stopped responding, something AMD, and then anywhere from a few seconds to a few minutes later I get the BSOD. When the screen flashes, I know it's all over.

I did try to install an update, but when I did so it installed and totally changed the format of my screen, and I couldn't get it to go back to "normal" no matter what I did. I do not have the option for screen resolution will not display 1920x1080 at all, so my screen just isn't right for what it normally is. I did a system restore and it brought me back to where I am now.

It also states atikmpag.sys on the BSOD. I have a shot of the screen if it helps at all as well. Here is a direct link to that...

https://i.imgur.com/o8Vhp5G.jpg

I have also followed the directions and went ahead and ran the utility, and attached the results to my post. Many thanks in advance for any help you may be able to offer to me. I'm going out of my mind. Thanks so much for your time.

RockySC · 17 Apr 2015

Here is a WhoCrashed report as well...

System Information (local)
computer name: BRENT-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: HP Pavilion dv7 Notebook PC, Hewlett-Packard, 165A
CPU: GenuineIntel Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 6387777536 total

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 4/17/2015 10:45:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041715-19063-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x41C7, 0x45D6, 0x45D5)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 4/17/2015 10:45:15 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x5292)
Bugcheck code: 0x119 (0x1, 0x41C7, 0x45D6, 0x45D5)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
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 the video scheduler has detected a fatal violation.
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. VIDEO_SCHEDULER_INTERNAL_ERROR

On Fri 4/17/2015 10:37:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041715-22916-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7B78)
Bugcheck code: 0x116 (0xFFFFFA800CA2F010, 0xFFFFF88001C07B78, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 attempt to reset the display driver and recover from a timeout failed.
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. VIDEO_TDR_ERROR

On Fri 4/17/2015 10:26:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041715-19656-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7B78)
Bugcheck code: 0x116 (0xFFFFFA800C0441E0, 0xFFFFF88003007B78, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 attempt to reset the display driver and recover from a timeout failed.
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. VIDEO_TDR_ERROR

On Fri 4/17/2015 10:13:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041715-23587-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7B78)
Bugcheck code: 0x116 (0xFFFFFA800B9594E0, 0xFFFFF88001C4CB78, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 attempt to reset the display driver and recover from a timeout failed.
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. VIDEO_TDR_ERROR

On Fri 4/17/2015 9:55:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041715-12714-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7B78)
Bugcheck code: 0x116 (0xFFFFFA800CC344E0, 0xFFFFF88003114B78, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 attempt to reset the display driver and recover from a timeout failed.
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. VIDEO_TDR_ERROR

On Fri 4/17/2015 7:42:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041715-22869-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7B78)
Bugcheck code: 0x116 (0xFFFFFA800C4044E0, 0xFFFFF88001C07B78, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 attempt to reset the display driver and recover from a timeout failed.
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. VIDEO_TDR_ERROR

On Wed 4/8/2015 5:07:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040815-8689-01.dmp
This was probably caused by the following module: igdpmd64.sys (igdpmd64+0xF91BA)
Bugcheck code: 0xA (0x2A80019C0720, 0x2, 0x1, 0xFFFFF80002AC5B6E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\igdpmd64.sys
product: Intel Graphics Accelerator Drivers for Windows 7(R)
company: Intel Corporation
description: Intel Graphics 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: igdpmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation IRQL_NOT_LESS_OR_EQUAL

On Sat 3/28/2015 3:19:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032715-26785-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x2A8004208C20, 0x2, 0x1, 0xFFFFF80002AC16F4)
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 Fri 3/20/2015 12:10:35 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031915-19609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x2A80013759C0, 0x2, 0x1, 0xFFFFF80002A766F4)
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.

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

igdpmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

cipley · 18 Apr 2015

Hi RockySC,

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800c0441e0, fffff88003007b78, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+7b78 )

Code:

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.

TDR Failure usually occurs when the hardware fails to recover at the time intended. There are many causes. It could be because of overheating or dust accumulating on your hardware. Check this post by H2SO4 about this error.

Code:

2: kd> lmvm atikmpag
start             end                 module name
fffff880`03000000 fffff880`03051000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Sat Oct 01 08:28:45 2011 (4E866CCD)

and your driver is...pretty outdated. It tends to give away errors.
Did you update using the official driver from the manufacturer?
AMD - Download Drivers Page

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {2a8004208c20, 2, 1, fffff80002ac16f4}

Probably caused by : memory_corruption ( nt!MiDeletePteList+1aa )

Followup: MachineOwner

Now this is where it get more interesting...it blames for memory corruption.

Code:

fffff880`20b73018  fffff880`04403d5aUnable to load image \SystemRoot\System32\Drivers\dump_iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dump_iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_iaStor.sys
 dump_iaStor+0x3d5a

that is windows driver to provide disk access during dumping process...
- You may try to update your Windows
- Try to check your RAM just to be sure: Check RAM using MemTest86+

Let it run until at least 8 passes are completed, or errors are found (whichever comes first). The longer you run it, the better.

RockySC · 19 Apr 2015

Thank you for your help.

I updated Intel and the AMD drivers and I am not getting the BSOD like I was getting just over, and over, and over again.

However I do have a new problem. When I put my computer in sleep mode, the screen will not come back on and I have to force shutdown and then restart. Here is a thread where others who update AMD have the same problem...

Does anyone still get the AMD 7xxx bug where your monitor doesn't wake up from sleep? - AnandTech Forums

I do not see any solution however. Would any of you guys be able to help me on this weird one?

Is it possible to downgrade to 13.12? I think the problems started after that.

cipley · 19 Apr 2015

Looks like you have KB2670838 update.
I suggest to uninstall them. This update is known to cause crashes on computers / laptops that use Hybrid graphics in Windows 7.

See if it helps.

Code:

Domain:                    WORKGROUP
Logon Server:              \\BRENT-PC
Hotfix(s):                 250 Hotfix(s) Installed.
                           [01]: KB2849697
                           [02]: KB2849696
                           [03]: KB2841134
                           [04]: KB2670838
                           [05]: KB2830477

Golden · 20 Apr 2015

I'd urge caution before uninstalling that update - its a prerequisite for installing IE10 and IE11. Best to see if the updated drivers fix the issue.

Run a new DM log Collector for the new BSOD you referred to, and upload the ZIP file here.

RockySC · 20 Apr 2015

Already attempted removing it, no problems it seems so far. We shall see.

I am now not getting as many BSOD (or any since this started really), my resolution is fine, and I can also put my computer in sleep and wake it up as normal.

I have attached the new report. Thanks!

RockySC · 20 Apr 2015

Also, here is my new WhoCrashed report as well...

System Information (local)
computer name: BRENT-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: HP Pavilion dv7 Notebook PC, Hewlett-Packard, 165A
CPU: GenuineIntel Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 6387777536 total

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 4/17/2015 11:35:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041715-15849-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0xA (0x2A80050F09EA, 0x2, 0x0, 0xFFFFF80001ECD8D7)
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 Fri 4/17/2015 11:35:17 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: 0xA (0x2A80050F09EA, 0x2, 0x0, 0xFFFFF80001ECD8D7)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Fri 4/17/2015 10:45:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041715-19063-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x1, 0x41C7, 0x45D6, 0x45D5)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 4/17/2015 10:37:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041715-22916-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7B78)
Bugcheck code: 0x116 (0xFFFFFA800CA2F010, 0xFFFFF88001C07B78, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 attempt to reset the display driver and recover from a timeout failed.
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. VIDEO_TDR_ERROR

On Fri 4/17/2015 10:26:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041715-19656-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7B78)
Bugcheck code: 0x116 (0xFFFFFA800C0441E0, 0xFFFFF88003007B78, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 attempt to reset the display driver and recover from a timeout failed.
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. VIDEO_TDR_ERROR

On Fri 4/17/2015 10:13:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041715-23587-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7B78)
Bugcheck code: 0x116 (0xFFFFFA800B9594E0, 0xFFFFF88001C4CB78, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 attempt to reset the display driver and recover from a timeout failed.
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. VIDEO_TDR_ERROR

On Fri 4/17/2015 9:55:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041715-12714-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7B78)
Bugcheck code: 0x116 (0xFFFFFA800CC344E0, 0xFFFFF88003114B78, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 attempt to reset the display driver and recover from a timeout failed.
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. VIDEO_TDR_ERROR

On Fri 4/17/2015 7:42:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041715-22869-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7B78)
Bugcheck code: 0x116 (0xFFFFFA800C4044E0, 0xFFFFF88001C07B78, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 attempt to reset the display driver and recover from a timeout failed.
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. VIDEO_TDR_ERROR

On Wed 4/8/2015 5:07:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040815-8689-01.dmp
This was probably caused by the following module: igdpmd64.sys (igdpmd64+0xF91BA)
Bugcheck code: 0xA (0x2A80019C0720, 0x2, 0x1, 0xFFFFF80002AC5B6E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\igdpmd64.sys
product: Intel Graphics Accelerator Drivers for Windows 7(R)
company: Intel Corporation
description: Intel Graphics 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: igdpmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation IRQL_NOT_LESS_OR_EQUAL

On Sat 3/28/2015 3:19:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032715-26785-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x2A8004208C20, 0x2, 0x1, 0xFFFFF80002AC16F4)
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.