- Thread Author
- #1
Hi,
I have been recieving multiple BSOD's since I had a fresh install of Windows 7 Ultimate 64, I used to have W7U 32 bit but a had an extreme number of BSOD's and I thought that maybe because i had 4 gb of ram and it wasnt all being used is why i had so many issue. I have been using the software "WhoCrashed" 2.10 Home Edition to figure out how to fix the BSOD's but no luck, im not that savy on how to fix these BSOD's. Im attaching My Specs and the minidumps. Who Crashed Gave me these details on the past BSOD's:
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
[FONT=Segoe UI, Arial]On Sun 11/21/2010 9:21:28 PM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]afd.sys[/FONT]
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF88003FD3775, 0xFFFFF8800800CF00, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
Dump file: C:\Windows\Minidump\112110-20156-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\drivers\afd.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Ancillary Function Driver for WinSock
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]
[FONT=Segoe UI, Arial]On Sun 11/21/2010 8:08:02 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]tcpip.sys[/FONT]
Bugcheck code: 0xD1 (0xFFFFF87F81941748, 0x2, 0x0, 0xFFFFF8800187EC70)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
Dump file: C:\Windows\Minidump\112110-21453-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\drivers\tcpip.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: TCP/IP Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]
[FONT=Segoe UI, Arial]On Sun 11/21/2010 6:46:24 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
Dump file: C:\Windows\Minidump\112110-28765-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]
Like I said im not that savy so if you could give me simple, detailed, childish if necessary explanations or fixes it would be greatly appreciated! Thanks[/FONT]
I have been recieving multiple BSOD's since I had a fresh install of Windows 7 Ultimate 64, I used to have W7U 32 bit but a had an extreme number of BSOD's and I thought that maybe because i had 4 gb of ram and it wasnt all being used is why i had so many issue. I have been using the software "WhoCrashed" 2.10 Home Edition to figure out how to fix the BSOD's but no luck, im not that savy on how to fix these BSOD's. Im attaching My Specs and the minidumps. Who Crashed Gave me these details on the past BSOD's:
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
[FONT=Segoe UI, Arial]On Sun 11/21/2010 9:21:28 PM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]afd.sys[/FONT]
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF88003FD3775, 0xFFFFF8800800CF00, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
Dump file: C:\Windows\Minidump\112110-20156-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\drivers\afd.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Ancillary Function Driver for WinSock
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]
[FONT=Segoe UI, Arial]On Sun 11/21/2010 8:08:02 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]tcpip.sys[/FONT]
Bugcheck code: 0xD1 (0xFFFFF87F81941748, 0x2, 0x0, 0xFFFFF8800187EC70)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
Dump file: C:\Windows\Minidump\112110-21453-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\drivers\tcpip.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: TCP/IP Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]
[/FONT]
[FONT=Segoe UI, Arial]On Sun 11/21/2010 6:46:24 AM your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
Dump file: C:\Windows\Minidump\112110-28765-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
[/FONT][FONT=Segoe UI, Arial]
Like I said im not that savy so if you could give me simple, detailed, childish if necessary explanations or fixes it would be greatly appreciated! Thanks[/FONT]