bankajac Posted February 13, 2012 Share Posted February 13, 2012 Used whocrashed.exe to get this: Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Mon 2/13/2012 5:20:50 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\021312-83788-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 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 which cannot be identified at this time. On Mon 2/13/2012 5:20:50 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0) Error: MEMORY_MANAGEMENT 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 Mon 2/13/2012 4:18:47 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\021312-83335-01.dmp This was probably caused by the following module: win32k.sys (win32k+0xC64E0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001A64E0, 0xFFFFF8800611F090, 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 Tue 2/7/2012 2:44:22 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\020712-81822-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x19 (0x3, 0xFFFFFA80058BC9D0, 0xFFFFFA80058BC9D0, 0xFFFFF80002C5CAB0) 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 which cannot be identified at this time. On Mon 2/6/2012 3:12:33 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\020612-63664-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x50 (0xFFFFF900C1DE5A68, 0x0, 0xFFFFF80002BAF5F7, 0x0) 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 which cannot be identified at this time. On Wed 1/25/2012 7:44:57 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\012512-74708-01.dmp This was probably caused by the following module: win32k.sys (win32k+0xC64E0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001164E0, 0xFFFFF880077F4D40, 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 Thu 1/19/2012 9:53:29 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\011912-85691-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x109 (0xA3A039D8980155C2, 0x0, 0x4B19CD86F81A0705, 0x101) Error: CRITICAL_STRUCTURE_CORRUPTION 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 kernel has detected critical kernel code or data corruption. 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 1/14/2012 7:51:25 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\011412-70652-01.dmp This was probably caused by the following module: fltmgr.sys (fltmgr+0x4CB3) Bugcheck code: 0xA (0xFFFFFA8023E01050, 0x2, 0x1, 0xFFFFF80002987FE6) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\fltmgr.sys product: Microsoft? Windows? Operating System company: Microsoft Corporation description: Microsoft Filesystem Filter Manager 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 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 Wed 1/11/2012 3:27:37 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\011112-65770-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFF8A00DB41010) Error: BAD_POOL_CALLER 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 current thread is making a bad pool request. 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 Thu 1/5/2012 4:13:36 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\010512-67002-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x50 (0xFFFFF98006400800, 0x0, 0xFFFFF80002BC5687, 0x0) 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 which cannot be identified at this time. On Fri 12/30/2011 4:53:33 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\123011-69342-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x19 (0x20, 0xFFFFF8A00C4C37E0, 0xFFFFF8A00C4C3BF0, 0x541033D) 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 which cannot be identified at this time. Not much help but can someone with skill in reading these things help me out. I am attaching the minidumps. Thanks in advance. 011412-70652-01.zip Link to comment Share on other sites More sharing options...
nate.wages Posted February 13, 2012 Share Posted February 13, 2012 I would start off by running "sfc /scannow" in a command prompt, to verify that none of the offending files are corrupt. I had an issue recently where win32k.sys had become corrupt because of a bad sector on the hdd. It caused windows to become nearly unresponsive whenever flash or java (I forget which) was loaded. Link to comment Share on other sites More sharing options...
Recommended Posts