Sorry to start another BSOD thread, but I'm really at a loss about my BSOD problem, which seem to be increasing in frequency lately. Here is an analysis usin the WhoCrashed software
System Information (local)
--------------------------------------------------------------------------------
computer name: XXX-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™2 Duo CPU P8700 @ 2.53GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4222504960 total
VM: 2147352576, free: 1986191360
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 27/03/2011 10:07:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032711-36644-01.dmp
This was probably caused by the following module: netw5s64.sys (NETw5s64+0x1188D)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x210007, 0xFFFFFA8005B46A00)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\netw5s64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
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.
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: netw5s64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: netw5s64.sys Intel Corporation BAD_POOL_CALLER
On Sun 27/03/2011 10:07:03 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netw5s64.sys (NETw5s64+0x1F7E65)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x210007, 0xFFFFFA8005B46A00)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\netw5s64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
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.
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: netw5s64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: netw5s64.sys Intel Corporation BAD_POOL_CALLER
On Sun 27/03/2011 3:29:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032711-39983-01.dmp
This was probably caused by the following module: afd.sys (afd+0x25FA)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88003AB05FA, 0xFFFFF8800CD7DC30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 23/03/2011 3:13:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032311-38157-01.dmp
This was probably caused by the following module: afd.sys (afd+0x25FA)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88003AD25FA, 0xFFFFF8800C1F4C30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 23/03/2011 12:45:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032311-39281-01.dmp
This was probably caused by the following module: afd.sys (afd+0x25FA)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88003A395FA, 0xFFFFF8800A6B79E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 23/03/2011 8:20:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032311-38251-01.dmp
This was probably caused by the following module: afd.sys (afd+0x25FA)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88003AD65FA, 0xFFFFF8800C37AC30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 21/03/2011 6:28:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032111-21138-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x19 (0x22, 0x10000, 0x0, 0x0)
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 14/03/2011 8:24:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031411-25864-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x18002200, 0xFFFFFA80070B453C)
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 03/03/2011 1:04:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030311-24913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x210000, 0xFFFFFA8003FE7010)
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 Sat 12/02/2011 2:27:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021211-24788-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x4, 0xFFFFF8800A845924)
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 Fri 11/02/2011 1:54:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021111-22713-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA8196F390A8, 0x2, 0x0, 0xFFFFF800031464D8)
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 Sun 06/02/2011 9:20:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020611-20623-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x3E00F, 0xFFFFFA8008B41A00)
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 Wed 02/02/2011 1:02:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020211-22011-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800784CB30, 0xFFFFFA800784CE10, 0xFFFFF800033985D0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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/01/2011 3:39:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011611-24632-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x4060003, 0xFFFFFA8004425AB0)
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 Mon 03/01/2011 10:56:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010311-32105-01.dmp
This was probably caused by the following module: netw5v64.sys (netw5v64+0x1B81F4)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800665A1F4, 0xFFFFF8800CBAB930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\netw5v64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link 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.
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: netw5v64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: netw5v64.sys Intel Corporation SYSTEM_SERVICE_EXCEPTION
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
29 crash dumps have been found and analyzed. Only 15 are included in this report. 4 third party drivers have 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:
netw5v64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation)
netw5s64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation)
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.
Sign In
Create Account
