New
#1
Many BSODs, relating to memory and drivers
Most of the errors say it's "likely not a hardware problem," but they never identify a driver. I've reinstalled Windows like 3 times in the past year, and I still get constant crashes, so I think it is the hardware causing the problem. I've run Memtest86 overnight once or twice and with multiple passes and every time it says all's good..any other suggestions?
Thanks. Here is a log from using WhoCrashed, and I've also attached the response from using the program in the BSOD guidelines.
Code:System Information (local) -------------------------------------------------------------------------------- computer name: windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 8580947968 total VM: 2147352576, free: 1932845056 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Tue 7/10/2012 4:14:18 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\071012-32276-01.dmp This was probably caused by the following module: tcpip.sys (tcpip+0x5E3AA) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\tcpip.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: TCP/IP 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 which cannot be identified at this time. On Tue 7/10/2012 12:35:51 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\071012-29780-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x109 (0xA3A039D8A236453C, 0xB3B7465EF4B31492, 0xFFFFF80002EB2F58, 0x1) 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 Sun 7/8/2012 8:37:53 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\070812-28158-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) Bugcheck code: 0x50 (0xFFFFF6800045A4F8, 0x0, 0xFFFFF80002E88B62, 0x2) 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 7/4/2012 3:07:53 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\070412-38204-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) Bugcheck code: 0x1A (0x411, 0xFFFFF6FC50129EE0, 0x8770000202F40882, 0xFFFFF8A0047F8209) 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 Tue 7/3/2012 4:36:58 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\070312-25584-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003156B50, 0xFFFFF8800BCB8B30, 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 7/1/2012 7:58:28 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\070112-47252-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) Bugcheck code: 0x1A (0x41790, 0xFFFFFA80036CE910, 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 which cannot be identified at this time. On Wed 6/27/2012 10:24:33 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\062712-37674-01.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8) Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007536D28, 0xFFFFF88007536590, 0xFFFFF80002CB8171) 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 Tue 6/26/2012 8:32:57 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\062612-29359-01.dmp This was probably caused by the following module: win32k.sys (win32k+0xCB4A5) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600017B4A5, 0xFFFFF88008298120, 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 Wed 6/20/2012 4:04:15 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\062012-26566-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x96FC0) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002CECFC0, 0xFFFFF880093F6F48, 0xFFFFF880093F67B0) 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 6/18/2012 8:56:04 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\061812-38828-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x14B1F, 0x15D17C09) 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 6/11/2012 4:23:01 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\061112-34788-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) Bugcheck code: 0x1A (0x41790, 0xFFFFFA80037EF0C0, 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 which cannot be identified at this time. On Wed 5/30/2012 10:38:57 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\053012-25662-01.dmp This was probably caused by the following module: fastfat.sys (fastfat+0x1D82) Bugcheck code: 0x23 (0xE00E6, 0xFFFFF880031FC4D8, 0xFFFFF880031FBD40, 0xFFFFF88001096B51) Error: FAT_FILE_SYSTEM file path: C:\Windows\system32\drivers\fastfat.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Fast FAT File System Driver Bug check description: This indicates that a problem occurred in the FAT 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 Sun 5/27/2012 2:04:00 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\052712-20607-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CDA144, 0xFFFFF8800AEDD920, 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 Sat 5/26/2012 9:44:12 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\052712-19188-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) Bugcheck code: 0x109 (0xA3A039D89C74D7D1, 0xB3B7465EEEF2A703, 0xFFFFF80002C1AB10, 0x1) 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 5/26/2012 7:42:09 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\052612-145658-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70040) Bugcheck code: 0x109 (0xA3A039D89F4D453D, 0xB3B7465EF1CA1733, 0xFFFFF80002CD6E3A, 0x1) 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. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 15 crash dumps have been found and analyzed. 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.
Quote