Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Tue 18/09/2012 12:07:39 GMT your computer crashed crash dump file: C:\Windows\Minidump\091812-15069-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x1 (0x774718FA, 0x0, 0xFFFF, 0xFFFFF880079B6CA0) Error: APC_INDEX_MISMATCH 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 there has been a mismatch in the APC state index. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Tue 18/09/2012 10:32:12 GMT your computer crashed crash dump file: C:\Windows\Minidump\091812-15678-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x4E (0x8D, 0x3982D, 0x510010, 0xFFFFF680000193AB) 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 Tue 18/09/2012 10:28:24 GMT your computer crashed crash dump file: C:\Windows\Minidump\091812-16660-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0xA (0x70C03010080, 0x2, 0x1, 0xFFFFF80002C7A9E6) 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 Tue 18/09/2012 10:20:59 GMT your computer crashed crash dump file: C:\Windows\Minidump\091812-15646-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0xD1 (0x68, 0xB, 0x0, 0xFFFFF880053944C6) 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 access 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 another driver which cannot be identified at this time. On Tue 18/09/2012 06:33:44 GMT your computer crashed crash dump file: C:\Windows\Minidump\091812-15256-01.dmp This was probably caused by the following module: watchdog.sys (watchdog+0x122F) Bugcheck code: 0x119 (0x7000000, 0xFFFFFA80054A6010, 0xFFFFFA8005F3D010, 0xFFFFFA8004D3C010) 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 Tue 18/09/2012 06:29:20 GMT your computer crashed crash dump file: C:\Windows\Minidump\091812-15288-01.dmp This was probably caused by the following module: watchdog.sys (watchdog+0x122F) Bugcheck code: 0x119 (0x7000000, 0xFFFFFA8005483010, 0xFFFFFA8005CA1010, 0xFFFFFA8003C31180) 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 Mon 17/09/2012 19:40:07 GMT your computer crashed crash dump file: C:\Windows\Minidump\091712-16832-01.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88) Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88002FD9E08, 0xFFFFF88002FD9660, 0xFFFFF80002C90074) Error: NTFS_FILE_SYSTEM file path: C:\Windows\system32\drivers\ntfs.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT File System Driver Bug check description: This indicates a problem occurred in the NTFS file system. 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 Mon 17/09/2012 19:32:06 GMT your computer crashed crash dump file: C:\Windows\Minidump\091712-15693-02.dmp This was probably caused by the following module: win32k.sys (win32k+0x1F4514) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000264514, 0xFFFFF880074C4D30, 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 Mon 17/09/2012 18:17:26 GMT your computer crashed crash dump file: C:\Windows\Minidump\091712-15069-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002CCD11B, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 17/09/2012 18:06:05 GMT your computer crashed crash dump file: C:\Windows\Minidump\091712-15880-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x4A (0x74BE2E09, 0x2, 0x0, 0xFFFFF88006D62CA0) 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 which cannot be identified at this time. On Mon 17/09/2012 10:31:55 GMT your computer crashed crash dump file: C:\Windows\Minidump\091712-15678-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0xC9744) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002CD6744, 0xFFFFF88003124618, 0xFFFFF88003123E70) 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 Mon 17/09/2012 10:27:10 GMT your computer crashed crash dump file: C:\Windows\Minidump\091712-17082-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002CD611B, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 17/09/2012 07:37:22 GMT your computer crashed crash dump file: C:\Windows\Minidump\091712-16130-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C9011B, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 17/09/2012 07:34:36 GMT your computer crashed crash dump file: C:\Windows\Minidump\091712-16161-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CD7E9B, 0xFFFFF88006AF2B30, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 16/09/2012 20:13:07 GMT your computer crashed crash dump file: C:\Windows\Minidump\091612-14913-01.dmp This was probably caused by the following module: watchdog.sys (watchdog+0x122F) Bugcheck code: 0x119 (0x7000000, 0xFFFFFA8005447010, 0xFFFFFA800449C010, 0xFFFFFA8003C5CAC0) 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.