Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- On Sun 20/01/2013 16:45:47 GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012013-24039-02.dmp
- This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1457)
- Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
- Error: UNEXPECTED_KERNEL_MODE_TRAP
- file path: C:\Windows\system32\drivers\dxgkrnl.sys
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: DirectX Graphics Kernel
- Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
- 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 20/01/2013 16:45:47 GMT your computer crashed
- crash dump file: C:\Windows\memory.dmp
- This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1457)
- Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
- Error: UNEXPECTED_KERNEL_MODE_TRAP
- file path: C:\Windows\system32\drivers\dxgkrnl.sys
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: DirectX Graphics Kernel
- Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
- 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 20/01/2013 16:02:19 GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012013-23836-01.dmp
- This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x16BB1)
- Bugcheck code: 0x50 (0xFFFFFFFFADBEBC38, 0x0, 0xFFFFFFFF92FD5BB1, 0x2)
- 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.
- On Sun 20/01/2013 15:50:09 GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012013-24367-01.dmp
- This was probably caused by the following module: atikmdag.sys (atikmdag+0x76320)
- Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9267D320, 0xFFFFFFFF998BF5F8, 0x0)
- Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
- 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 program generated an exception 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.
- 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. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
- On Sun 20/01/2013 15:26:48 GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012013-25053-01.dmp
- This was probably caused by the following module: atikmdag.sys (atikmdag+0xE100C)
- Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9270100C, 0xFFFFFFFF8FF9A990, 0x0)
- Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
- 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 program generated an exception 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.
- 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. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
- On Sun 20/01/2013 11:50:10 GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012013-24039-01.dmp
- This was probably caused by the following module: atikmdag.sys (atikmdag+0x4938DE)
- Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF92AA48DE, 0xFFFFFFFF9C1399C0, 0x0)
- Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
- 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 program generated an exception 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.
- 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. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
- On Sun 20/01/2013 11:43:16 GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012013-25630-01.dmp
- This was probably caused by the following module: win32k.sys (win32k+0xCB374)
- Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9758B374, 0xFFFFFFFF8D5C2C24, 0x0)
- Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
- 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 a kernel-mode program generated an exception 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 may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
- On Sun 20/01/2013 10:26:54 GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012013-24772-01.dmp
- This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x1E918)
- Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF92F20918, 0xFFFFFFFF8E2ADAE1, 0x0)
- Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
- file path: C:\Windows\system32\drivers\dxgkrnl.sys
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: DirectX Graphics Kernel
- Bug check description: This indicates that a kernel-mode program generated an exception 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 may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
- On Sun 20/01/2013 09:36:04 GMT your computer crashed
- crash dump file: C:\Windows\Minidump\012013-30201-01.dmp
- This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
- Bugcheck code: 0x1A (0x8886, 0xFFFFFFFF849AEDF8, 0xFFFFFFFF849B5014, 0x200)
- Error: MEMORY_MANAGEMENT
- file path: C:\Windows\system32\ntkrnlpa.exe
- product: Microsoft® Windows® Operating System
- company: Microsoft Corporation
- description: NT Kernel & System
- Bug check description: This indicates that a severe memory management error occurred.
- This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
- The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement