New
#1
Multiple BSODs while playing games, up to 3 times a day.
So, as a noob I have no idea what BSOD mean other than my computer is about to fail at any minute. I tried to get help from Microsoft, but they said that the best thing to do is to update my drivers. Since my drivers don't have any updates at all, I've no idea what to do. My computer is Sony Vaio, model VGN-AW41ZF/B and system is Windows 7 Home Premium.
But only today, I've gotten 2 BSODs while playing Minecraft. I tried to delete all my other games to try if it will help so that I could play at least one game without my computer crashed. I also tried to clean my computer, it was kinda dirty, and I constantly have a fan on my table that blows cold air on my computer (so that I wouldn't overheat). But no, it haven't helped at all.
Here's screenshots about what I'm talking about, a little bit outdated: Click.
I also added the latest 5 minidumps in the attachment.
I copied from WhoCrashed, because I have no idea from where else:
On Fri 2.8.2013 12:37:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080213-38485-01.dmp
This was probably caused by the following module: afd.sys (afd+0x243A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88002C8743A, 0xFFFFF880063B2A10, 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 that cannot be identified at this time.
On Fri 2.8.2013 12:37:13 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: afd.sys (afd+0x243A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88002C8743A, 0xFFFFF880063B2A10, 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 that cannot be identified at this time.
On Fri 2.8.2013 10:51:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080213-40825-01.dmp
This was probably caused by the following module: netw5s64.sys (NETw5s64+0xB94CF)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x4060015, 0xFFFFFA8004286E00)
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: Intel Corporation BAD_POOL_CALLER
On Tue 30.7.2013 11:31:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073013-43196-01.dmp
This was probably caused by the following module: afd.sys (afd+0x243A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88003CD443A, 0xFFFFF8800B468E30, 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 that cannot be identified at this time.
On Mon 29.7.2013 11:37:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072913-90277-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x4E (0x7, 0x13FB79, 0x1, 0x0)
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 that cannot be identified at this time.
On Sun 28.7.2013 15:41:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-33197-01.dmp
This was probably caused by the following module: afd.sys (afd+0x243A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88003A2843A, 0xFFFFF8800BEAFE30, 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 that cannot be identified at this time.
On Wed 24.7.2013 18:54:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072413-34523-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xC2 (0xB, 0xFFFFF8800647D574, 0x0, 0xFFFFF8800647E194)
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 that cannot be identified at this time.
On Wed 24.7.2013 10:56:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072413-33197-01.dmp
This was probably caused by the following module: afd.sys (afd+0x243A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88002C7D43A, 0xFFFFF8800926FA10, 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 that cannot be identified at this time.
On Tue 23.7.2013 17:39:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072313-36192-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xC2 (0x7, 0x109B, 0xC96A00C1, 0xFFFFF880043F0294)
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 that cannot be identified at this time.
On Tue 23.7.2013 11:33:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072313-31637-01.dmp
This was probably caused by the following module: afd.sys (0xFFFFF88003C1743A)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88003C1743A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 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.
On Mon 22.7.2013 17:34:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072213-31168-01.dmp
This was probably caused by the following module: afd.sys (0xFFFFF88002CF743A)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88002CF743A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 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.
On Fri 19.7.2013 17:24:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071913-41387-01.dmp
This was probably caused by the following module: afd.sys (afd+0x243A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88002CE843A, 0xFFFFF8800C1E2A10, 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 that cannot be identified at this time.
On Tue 28.5.2013 15:06:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052813-29998-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x210015, 0xFFFFFA800670C410)
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 that cannot be identified at this time.
On Sun 26.5.2013 10:40:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052613-42057-01.dmp
This was probably caused by the following module: afd.sys (afd+0x243A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88003E8143A, 0xFFFFF8800EFD7A10, 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 that cannot be identified at this time.
On Sun 19.5.2013 14:38:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051913-33696-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF8000301F3DA)
Bugcheck code: 0xA (0xFFFFFA8547FB1070, 0x2, 0x0, 0xFFFFF8000301F3DA)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 that cannot be identified at this time.