Yet another BSOD problem!

[Wolfman86]

I have been doing a lot of reading on here and you guys appear to have the best diagnostic knowledge when it comes to BSODs!

I recently just built this system (specs below) and have been getting random BSOD crashes. I have every possible up-to-date driver for my hardware installed, but yet, I still crash.

I have done everything possible to eliminate hardware failure by running Memtest86+ v4.10 for 9 hours/10 passes with no errors, ran Western Digital's hard drive diagnostic tool on both drives with no errors or bad sectors and reinstalled Windows 7. You name it, I have probably done it as far as trying to find failing hardware.

Anyways, I'll let the pros have a look at the crash dumps that were from earlier today. Any help is much appreciated!

Searching updates...1/12
close​

 

[ttran]

Hi and Welcome to SF

This can be device driver issue. One of the minidump blame afd.sys, which is a NIC driver issue.
first I would suggest updating your nic driver.
Utorrent was the process at the time of BSODs. I would think of this as networking driver issue (Ethernet controller...). Please update them.

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.631\063010-16848-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02855000 PsLoadedModuleList = 0xfffff800`02a92e50
Debug session time: Thu Jul  1 09:55:48.519 2010 (UTC + 7:00)
System Uptime: 0 days 0:38:10.205
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88005f21830, 0, fffff80002bb1fd1, 0}


Could not read faulting driver name
Probably caused by : [COLOR=Red]afd.sys [/COLOR]( afd!AfdIssueDeviceControl+bb )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88005f21830, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002bb1fd1, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002afd0e0
 fffff88005f21830 

FAULTING_IP: 
nt!IoBuildDeviceIoControlRequest+1b1
fffff800`02bb1fd1 488b842490000000 mov     rax,qword ptr [rsp+90h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  [COLOR=Blue]uTorrent.exe[/COLOR]

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88005f19610 -- (.trap 0xfffff88005f19610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8003e57a0f rbx=0000000000000000 rcx=fffffa8003e57c40
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002bb1fd1 rsp=fffff88005f197a0 rbp=fffffa800791ebf0
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8003d26810
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!IoBuildDeviceIoControlRequest+0x1b1:
fffff800`02bb1fd1 488b842490000000 mov     rax,qword ptr [rsp+90h] ss:0018:fffff880`05f19830=0000000000000000
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002945e54 to fffff800028c5600

STACK_TEXT:  
fffff880`05f194a8 fffff800`02945e54 : 00000000`00000050 fffff880`05f21830 00000000`00000000 fffff880`05f19610 : nt!KeBugCheckEx
fffff880`05f194b0 fffff800`028c36ee : 00000000`00000000 fffffa80`03e57ae0 00000000`00000000 fffff880`05f19ca0 : nt! ?? ::FNODOBFM::`string'+0x42877
fffff880`05f19610 fffff800`02bb1fd1 : fffffa80`07065450 00000000`00000000 fffffa80`0791ebf0 fffff880`02f63180 : nt!KiPageFault+0x16e
fffff880`05f197a0 fffff880`01862bcb : 00000000`00000000 fffffa80`04c14890 00000000`00000000 fffff800`02bce260 : nt!IoBuildDeviceIoControlRequest+0x1b1
fffff880`05f19810 fffff880`01862cfa : fffffa80`07b73630 fffff880`05f19ca0 fffffa80`04024c60 00000038`ec646641 : afd!AfdIssueDeviceControl+0xbb
fffff880`05f198b0 fffff880`01865329 : 00000000`00000000 fffffa80`04024e08 fffffa80`07b73630 fffffa80`04024c60 : afd!AfdSetEventHandler+0x2a
fffff880`05f19910 fffff880`0185e03b : 00000000`0000afd1 fffffa80`00000000 00000000`00000001 fffff880`05f19ca0 : afd!AfdTdiSetEventHandlers+0x39
fffff880`05f19940 fffff800`02be16b7 : fffffa80`00000101 fffff880`00000002 fffffa80`00000016 00000000`00000000 : afd! ?? ::NNGAKEGL::`string'+0x2dfb
fffff880`05f19a10 fffff800`02be1f16 : fffff880`05f19bf8 00000000`000002bc 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`05f19b40 fffff800`028c4853 : fffff880`05f19ca0 fffffa80`05db24a0 fffff880`05f19bf8 fffff880`05f19c00 : nt!NtDeviceIoControlFile+0x56
fffff880`05f19bb0 00000000`75882dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0065f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75882dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
afd!AfdIssueDeviceControl+bb
fffff880`01862bcb 488bf8          mov     rdi,rax

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  afd!AfdIssueDeviceControl+bb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: afd

IMAGE_NAME:  afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc184

FAILURE_BUCKET_ID:  X64_0x50_afd!AfdIssueDeviceControl+bb

BUCKET_ID:  X64_0x50_afd!AfdIssueDeviceControl+bb

Followup: MachineOwner
---------
BugCheck D1, {fffff800027db665, 2, 8, fffff800027db665}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Followup: MachineOwner
---------

Yep, look like all of your drivers are up to date. Please follow what I suggest

I would leave this for others who really good at reading dumps

Regard,

Tuan

 

[Wolfman86]

Thanks for the reply! I have the latest Realtek LAN driver to date, which is 7.021. I will try reinstalling uTorrent to see if that will help any.

Searching updates...1/12
close​

 

[ttran]

Even you have the latest Realtek Lan driver, I would still try to re-install that (remove all trace of old driver before updating new one).
I have seen this adf.sys BSODs before, that user also have trouble while accessing internet:
http://www.sevenforums.com/network-sharing/14122-afd-sys-blue-screen.html

Regard,
Tuan

 

[Wolfman86]

I don't know how to remove all traces of the old driver without windows automatically reinstalling it after uninstalling it via device manager. I reinstalled the newest Realtek LAN driver and also reinstalled latest uTorrent. I'll report in if any future blue screens.

Searching updates...1/12
close​

 

[ttran]

Do you install peerblock or anything like that in your machine?

 

[Wolfman86]

Nope. I'm only using Avast 5.0.594. Would that possibly cause the crashes?

Searching updates...1/12
close​

 

[ttran]

probably not!!! I have seen PeerBlock caused BSODs for many user who use P2P downloader such as Utorrent , just double check on you

 

[Wolfman86]

Crashed again a little bit ago.

Searching updates...1/12
close​

 

[ttran]

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION

Usual causes: System service, Device driver, graphics driver, ?memory

I still think something is wrong with the networking driver. The process running at the time of BSOD indicated to be Chrome.exe which belong to Google chrome browser. Please update all of your networking driver, as well as look up on NIC website to see if there are any hot fix for it.

memory_corruption was blamed in the dmp, I would download third party called memtestx86, burn it to CD using ISO Recorder v3 , let it run for at least 6,7 passes

BugCheck 3B, {c0000005, fffff96000087c8c, fffff88007406cb0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------
PROCESS_NAME: [COLOR=Red] chrome.exe[/COLOR]

What third party AV are you using?

Regard,
Tuan

 

[Wolfman86]

I was testing Google Chrome when it crashed on me and then just now crashed again in Firefox 3.6.6. I'm currently using Avast 5.0.594 as stated from last night.

I will run Memtest86+ v4.10 again overnight tonight and see what comes up.

 

[ttran]

Ok, this time aswSP.SYS, which is your Avast AV was blamed in the dmp. Try to uninstall it to see if BSODs goes away. It's strange because I never seen Avast causing problem....we never know for sure what third party software can do for us...
avast! Uninstall Utility (use this to uninstall Avast)
If you need an AV in the meantime, I would recommend you to use MSE instead, it's free, written by Microsoft.
http://www.microsoft.com/security_essentials
Please look at my previous post, as I said, since this BSOD occur frequently while you are online, I would doubt the networking driver to make sure they are working properly.

BugCheck 50, {fffff880068aef30, 0, fffff80002b73fd1, 0}

Unable to load image \SystemRoot\System32\Drivers\aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS

Could not read faulting driver name
Probably caused by : aswSP.SYS ( aswSP+1329c )

Followup: MachineOwner
---------