-------------------------------------------------------------------------------- System Information (local) -------------------------------------------------------------------------------- computer name: LOUISA-TOSH windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel(R) Core(TM) i3 CPU M 330 @ 2.13GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 4149825536 total VM: 2147352576, free: 1927835648 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Fri 04/10/2013 19:57:16 GMT your computer crashed crash dump file: C:\Windows\Minidump\100413-18439-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80) Bugcheck code: 0x50 (0xFFFFF820127BABE0, 0x0, 0xFFFFF8000320A9BC, 0x5) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Fri 04/10/2013 19:57:16 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: 9489361drv.sys (9489361drv+0x2F4F1) Bugcheck code: 0x50 (0xFFFFF820127BABE0, 0x0, 0xFFFFF8000320A9BC, 0x5) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\DRIVERS\9489361drv.sys 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. 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: 9489361drv.sys . Google query: 9489361drv.sys PAGE_FAULT_IN_NONPAGED_AREA On Fri 04/10/2013 08:32:19 GMT your computer crashed crash dump file: C:\Windows\Minidump\100413-20685-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80) Bugcheck code: 0x1A (0x41790, 0xFFFFFA80000047A0, 0xFFFF, 0x0) 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 that cannot be identified at this time. On Thu 03/10/2013 21:33:04 GMT your computer crashed crash dump file: C:\Windows\Minidump\100413-21294-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80) Bugcheck code: 0x1A (0x41790, 0xFFFFFA80000047D0, 0xFFFF, 0x0) 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 that cannot be identified at this time. On Tue 01/10/2013 18:09:19 GMT your computer crashed crash dump file: C:\Windows\Minidump\100113-18782-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80) Bugcheck code: 0x1A (0x41790, 0xFFFFFA80000047D0, 0xFFFF, 0x0) 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 that cannot be identified at this time. On Tue 01/10/2013 15:07:01 GMT your computer crashed crash dump file: C:\Windows\Minidump\100113-18626-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80) Bugcheck code: 0x19 (0x3, 0xFFFFF8A00AD0DB40, 0xFFFFF8200AD0DB40, 0xFFFFF8A00AD0DB40) Error: BAD_POOL_HEADER 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 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 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. On Tue 01/10/2013 14:36:03 GMT your computer crashed crash dump file: C:\Windows\Minidump\100113-17674-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80) Bugcheck code: 0x19 (0x3, 0xFFFFF8A00CC625F0, 0xFFFFF8200CC625F0, 0xFFFFF8A00CC625F0) Error: BAD_POOL_HEADER 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 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 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. On Mon 30/09/2013 14:56:39 GMT your computer crashed crash dump file: C:\Windows\Minidump\093013-21481-01.dmp This was probably caused by the following module: fltmgr.sys (fltmgr+0x6C3B) Bugcheck code: 0x19 (0x3, 0xFFFFFA8003ADD8F0, 0xFFFFFA0003ADD8F0, 0xFFFFFA8003ADD8F0) Error: BAD_POOL_HEADER file path: C:\Windows\system32\drivers\fltmgr.sys product: Système d’exploitation Microsoft® Windows® company: Microsoft Corporation description: Gestionnaire de filtres de système de fichiers Microsoft 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 memory 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 may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 8 crash dumps have been found and analyzed. 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: 9489361drv.sys 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.