Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer.

On Thu 2/9/2012 6:24:34 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\020812-27175-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF88004807648) Error: DRIVER_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 a kernel-mode driver attempted to acc ess 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 the Windows kernel. Possibly this problem is caused by a nother driver which cannot be identified at this time. On Thu 2/9/2012 6:16:49 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\020812-24850-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0xD1 (0xFFFFF8804FD37151, 0x2, 0x0, 0xFFFFF88004408EC4) Error: DRIVER_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 a kernel-mode driver attempted to acc ess 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 the Windows kernel. Possibly this problem is caused by a nother driver which cannot be identified at this time. On Thu 2/9/2012 3:43:40 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\020812-23290-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0xC4 (0x91, 0x0, 0xFFFFF880009F6040, 0x0) Error: DRIVER_VERIFIER_DETECTED_VIOLATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft Windows Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpa ndKernelStackAndCallout. 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 a nother driver which cannot be identified at this time. On Thu 2/9/2012 2:27:20 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\020812-24148-01.dmp

This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x95D8) Bugcheck code: 0xD1 (0xFFFFF87F8FC8E62D, 0x2, 0x1, 0xFFFFF880048095D8) 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 acc ess 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 m ay be incorrect. Possibly this problem is caused by another driver on your syste m which cannot be identified at this time. On Thu 2/9/2012 1:49:34 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\020812-23618-01.dmp This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x8F88) Bugcheck code: 0xD1 (0xFFFFFFFF8B483049, 0x2, 0x1, 0xFFFFF88004808F88) 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 acc ess 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 m ay be incorrect. Possibly this problem is caused by another driver on your syste m which cannot be identified at this time. On Tue 2/7/2012 9:38:19 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\020712-26520-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x349E6E) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002D99E6E, 0xFFFFF880031 91808, 0xFFFFF88003191060) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 system thread generated an exceptio n which the error handler did not catch. 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 a nother driver which cannot be identified at this time. On Tue 2/7/2012 9:36:43 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\020712-24195-01.dmp This was probably caused by the following module: win32k.sys (win32k+0xC3FEF) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000E3FEF, 0xFFFFF880042F10C0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 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 m ay be incorrect. Possibly this problem is caused by another driver on your syste m which cannot be identified at this time. On Mon 2/6/2012 10:24:57 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\020612-26161-01.dmp This was probably caused by the following module: usbport.sys (USBPORT+0x12AED) Bugcheck code: 0x19 (0x3, 0xFFFFF80002C128E0, 0xFFFFF80002C128FF, 0xFFFFF80002C1 28E0) Error: BAD_POOL_HEADER 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 a pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often mem ory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in a standard Microsoft module. Your system configuration m ay be incorrect. Possibly this problem is caused by another driver on your syste m which cannot be identified at this time. On Mon 2/6/2012 10:47:58 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\020612-25740-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0xC4 (0x91, 0x0, 0xFFFFFA800A80F9B0, 0x0) Error: DRIVER_VERIFIER_DETECTED_VIOLATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft Windows Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpa ndKernelStackAndCallout. 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 a nother driver which cannot be identified at this time. On Sat 2/4/2012 7:07:19 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\020412-33680-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x4B16CC) Bugcheck code: 0x124 (0x0, 0xFFFFFA80079596F8, 0x0, 0x0) Error: WHEA_UNCORRECTABLE_ERROR file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft Windows Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Har

dware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by a nother driver which cannot be identified at this time. On Sat 2/4/2012 10:41:20 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\020412-25272-01.dmp This was probably caused by the following module: atikmdag.sys (atikmdag+0x102B2 0) Bugcheck code: 0xD1 (0xFFFFFFFFC00348FA, 0x9, 0x1, 0xFFFFF88004978B20) 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 acc ess 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 er ror. It is suggested you look for an update for the following driver: atikmdag.s ys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.). Google query: atikmdag.sys Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_ EQUAL

On Fri 2/3/2012 3:43:23 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\020212-24850-01.dmp This was probably caused by the following module: hal.dll (hal+0x7B7F) Bugcheck code: 0xD1 (0xFFFFF87F87E637F0, 0x9, 0x8, 0xFFFFF87F87E637F0) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\hal.dll product: Microsoft Windows Operating System company: Microsoft Corporation description: Hardware Abstraction Layer DLL Bug check description: This indicates that a kernel-mode driver attempted to acc ess 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 m ay be incorrect. Possibly this problem is caused by another driver on your syste m which cannot be identified at this time. On Wed 2/1/2012 3:05:13 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\013112-35630-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0xD1 (0x30B0A7C, 0x9, 0x0, 0xFFFFF8800495A6BE) Error: DRIVER_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 a kernel-mode driver attempted to acc ess 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 the Windows kernel. Possibly this problem is caused by a nother driver which cannot be identified at this time. On Wed 2/1/2012 3:01:52 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\013112-35303-01.dmp This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20D45) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004820D45, 0xFFFFF880029 D86A8, 0xFFFFF880029D7F00) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 system thread generated an exceptio n which the error handler did not catch. 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 m ay be incorrect. Possibly this problem is caused by another driver on your syste m which cannot be identified at this time. On Wed 2/1/2012 2:38:02 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\013112-35849-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0xA (0xFFFFF704401A6194, 0x0, 0x1, 0xFFFFF80002B068B4) 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 dr iver 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 a nother driver which cannot be identified at this time. The following dump files were found but could not be read. These files may be co rrupt: C:\Windows\Minidump\020212-27783-01.dmp

-------------------------------------------------------------------------------Conclusion -------------------------------------------------------------------------------On your computer a total of 25 crash dumps have been found. Only 24 could be ana lyzed. Only 15 are included in this report. 2 third party drivers have been iden tified to be causing system crashes on your computer. It is strongly suggested t hat 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.) If no updates for these drivers are available, try searching with Google names of these drivers in combination the errors that have been reported se drivers and include the brand and model name of your computer as well query. This often yields interesting results from discussions from users e been experiencing similar problems. on the for the in the who hav

Read the topic general suggestions for troubleshooting system crashes for more i nformation. Note that it's not always possible to state with certainty whether a reported dr iver 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 produ cts that these drivers belong to and regularly visit Windows update or enable au tomatic updates for Windows. In case a piece of malfunctioning hardware is causi ng 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.