windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: AuthenticAMD AMD Athlon(tm) II X2 250 Processor AMD586, level: 16 2 logical processors, active mask: 3 RAM: 4292988928 total VM: 2147352576, free: 1985552384 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Sat 15/09/2012 20:50:13 GMT your computer crashed crash dump file: C:\Windows\Minidump\091512-15834-01.dmp This was probably caused by the following module: atikmdag.sys (atikmdag+0xC695) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880048FB695, 0xFFFFF880021D3A08, 0xFFFFF880021D3260) Error: SYSTEM_THREAD_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 system thread 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: atikmdag.sys Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M On Sat 15/09/2012 20:50:13 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: atikmdag.sys (atikmdag+0xC695) Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF880048FB695, 0xFFFFF880021D3A08, 0xFFFFF880021D3260) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 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 bug check indicates that a system thread generated an exception that the error handler did not catch. 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: atikmdag.sys Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED On Sat 15/09/2012 19:22:59 GMT your computer crashed crash dump file: C:\Windows\Minidump\091512-15132-01.dmp This was probably caused by the following module: win32k.sys (win32k+0xEDC8A) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600011DC8A, 0xFFFFF880021CA120, 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 may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sat 15/09/2012 18:32:16 GMT your computer crashed crash dump file: C:\Windows\Minidump\091512-15256-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x4E (0x8D, 0xB3559, 0x510010, 0xFFFFF6800001ABA3) Error: PFN_LIST_CORRUPT 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 the page frame number (PFN) list is corrupted. 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 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 which cannot be identified at this time. On Sat 15/09/2012 18:01:34 GMT your computer crashed crash dump file: C:\Windows\Minidump\091512-15054-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x1A (0x8884, 0xFFFFFA800326A450, 0xFFFFFA80032611B0, 0x504) Error: MEMORY_MANAGEMENT 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 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 which cannot be identified at this time. On Sat 15/09/2012 16:44:27 GMT your computer crashed crash dump file: C:\Windows\Minidump\091512-21013-02.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x3B7, 0x5D00000077E) Error: MEMORY_MANAGEMENT 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 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 which cannot be identified at this time. On Sat 15/09/2012 16:30:38 GMT your computer crashed crash dump file: C:\Windows\Minidump\091512-14944-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x1ABDD3) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002BABDD3, 0xFFFFF88002FEF938, 0xFFFFF88002FEF190) 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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 15/09/2012 00:39:25 GMT your computer crashed crash dump file: C:\Windows\Minidump\091512-14976-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002AFD51E) 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 which cannot be identified at this time. On Fri 14/09/2012 20:25:15 GMT your computer crashed crash dump file: C:\Windows\Minidump\091412-15927-01.dmp This was probably caused by the following module: watchdog.sys (watchdog+0x122F) Bugcheck code: 0x119 (0x7000000, 0xFFFFFA800547B010, 0xFFFFFA8003DAA720, 0xFFFFFA8004D698C0) 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 which cannot be identified at this time. On Fri 14/09/2012 19:29:32 GMT your computer crashed crash dump file: C:\Windows\Minidump\091412-15958-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFF9, 0x2, 0x0, 0xFFFFF80002ADF531) 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 which cannot be identified at this time. On Fri 14/09/2012 17:02:01 GMT your computer crashed crash dump file: C:\Windows\Minidump\091412-17238-01.dmp This was probably caused by the following module: watchdog.sys (watchdog+0x122F) Bugcheck code: 0x119 (0x7000000, 0xFFFFFA8005412010, 0xFFFFFA80044DC010, 0xFFFFFA8003EB1D90) 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 which cannot be identified at this time. On Fri 14/09/2012 11:53:01 GMT your computer crashed crash dump file: C:\Windows\Minidump\091412-15444-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x4E (0x2, 0x50E65, 0x12FFFF, 0x10) Error: PFN_LIST_CORRUPT 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 the page frame number (PFN) list is corrupted. 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 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 which cannot be identified at this time. On Thu 13/09/2012 19:39:19 GMT your computer crashed crash dump file: C:\Windows\Minidump\091312-18283-01.dmp This was probably caused by the following module: watchdog.sys (watchdog+0x122F) Bugcheck code: 0x119 (0x7000000, 0xFFFFFA80054C5410, 0xFFFFFA80063C7AF0, 0xFFFFFA8005F02AA0) 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 which cannot be identified at this time. On Thu 13/09/2012 17:57:12 GMT your computer crashed crash dump file: C:\Windows\Minidump\091312-15381-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x4E (0x8D, 0x17665, 0x510010, 0xFFFFF6FC8060FA2B) Error: PFN_LIST_CORRUPT 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 the page frame number (PFN) list is corrupted. 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 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 which cannot be identified at this time. On Thu 13/09/2012 17:03:26 GMT your computer crashed crash dump file: C:\Windows\Minidump\091312-16302-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x1A (0x8885, 0xFFFFFA8000A0C3B0, 0xFFFFFA8000A0C230, 0x504) Error: MEMORY_MANAGEMENT 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 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 which cannot be identified at this time. The following dump files were found but could not be read. These files may be corrupt: C:\Windows\Minidump\091512-16489-01.dmp C:\Windows\Minidump\091512-20997-01.dmp -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- On your computer a total of 36 crash dumps have been found. Only 34 could be 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: atikmdag.sys (ATI Radeon Kernel Mode 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.