BSOD Please help me to read my dump files

Looks like verifier did it's job (you can disable it) - your broadcom wireless driver is called out as the culprit:

Code:

1: kd> k
Child-SP          RetAddr           Call Site
fffff880`02fb78f8 fffff800`02b9267b nt!KeBugCheckEx
fffff880`02fb7900 fffff800`02bbe356 nt!MmFreeSpecialPool+0x1bb
fffff880`02fb7a30 fffff880`014653cb nt!ExDeferredFreePool+0xf13
fffff880`02fb7ae0 fffff880`0147ad16 ndis!NdisFreeNetBuffer+0xfb
fffff880`02fb7b10 fffff880`02d2e201 ndis! ?? ::FNODOBFM::`string'+0x4516
fffff880`02fb7b40 fffff880`0151f5ad vwififlt!FilterSendNetBufferListsComplete+0x151
fffff880`02fb7b90 fffff880`04825997 ndis!NdisMSendNetBufferListsComplete+0x6d
fffff880`02fb7bd0 fffffa80`05383000 bcmwl664+0x24997
fffff880`02fb7bd8 fffff800`02c305a0 0xfffffa80`05383000
fffff880`02fb7be0 fffff980`03026f70 nt!ExWorkerQueue
fffff880`02fb7be8 fffff980`1157eed0 0xfffff980`03026f70
fffff880`02fb7bf0 00000000`00000000 0xfffff980`1157eed0

1: kd> lmvm bcmwl664
start             end                 module name
fffff880`04801000 fffff880`04c00000   bcmwl664 T (no symbols)           
    Loaded symbol image file: bcmwl664.sys
    Image path: \SystemRoot\system32\DRIVERS\bcmwl664.sys
    Image name: bcmwl664.sys
    Timestamp:        Thu Jun 03 15:25:17 2010 (4C08019D)
    CheckSum:         003FB521
    ImageSize:        003FF000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I love it when verifier actually works properly .

Now let's see if you get more BSODs.

If you do, disable it, and purchase a new one.

Okay, I am getting a bit confused as to whether it is your Ethernet or wireless drivers causing the BSODs.

Try disabling the Ethernet card in Device Manager, and ONLY using the wireless at work.

vietnam said:

It means to buy a new hardware wireless ? my current wireless is on mainboard.

No, but it does look like you were using an actual broadcom driver for the Dell rebranded/modified wireless onboard, which is never a good idea. I think you will be much better served using the driver you have installed now - it's older, yes, but it is also specifically designed for the Dell 1130 wireless card, whereas the actual broadcom driver for the chip itself may not be entirely.

Please help me

Now disable the Ethernet and use the Wireless instead.

I debuged my new BSOD which is come from Microsoft Security Essentials or Windows Defender ? Many thanks for your help.

Quang Anh

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\NVQuangAnh\Desktop\091410-17893-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50
Debug session time: Tue Sep 14 23:10:44.636 2010 (GMT+7)
System Uptime: 0 days 2:42:42.478
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6e0007fff20, 0, fffff80002aed4be, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDispatchFault+de )

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

1: 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: fffff6e0007fff20, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002aed4be, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d090e0
 fffff6e0007fff20 

FAULTING_IP: 
nt!MiDispatchFault+de
fffff800`02aed4be 488b1c29        mov     rbx,qword ptr [rcx+rbp]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880047bf820 -- (.trap 0xfffff880047bf820)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=c000fffe43c1fffe rbx=0000000000000000 rcx=fffff68000000000
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002aed4be rsp=fffff880047bf9b0 rbp=00000060007fff20
 r8=ffffc000fffe43c1  r9=0000000000000000 r10=0000000fffffffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiDispatchFault+0xde:
fffff800`02aed4be 488b1c29        mov     rbx,qword ptr [rcx+rbp] ds:0001:fffff6e0`007fff20=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b508c1 to fffff80002ad1740

STACK_TEXT:  
fffff880`047bf6b8 fffff800`02b508c1 : 00000000`00000050 fffff6e0`007fff20 00000000`00000000 fffff880`047bf820 : nt!KeBugCheckEx
fffff880`047bf6c0 fffff800`02acf82e : 00000000`00000000 00000000`090f270c 00000000`00401800 fffff800`02b68079 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`047bf820 fffff800`02aed4be : 00000000`00000000 00000000`092175d8 fffff880`047bfa50 fffffa80`055fae28 : nt!KiPageFault+0x16e
fffff880`047bf9b0 fffff800`02aeb743 : ffffffff`ffffffff 00000000`090f270c fffff880`009e7180 fffffa80`00000000 : nt!MiDispatchFault+0xde
fffff880`047bfac0 fffff800`02acf82e : 00000000`00000000 00000000`0001685a 00000000`0a45f101 00000000`00001000 : nt!MmAccessFault+0x343
fffff880`047bfc20 00000000`74cb702c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0277e9c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74cb702c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDispatchFault+de
fffff800`02aed4be 488b1c29        mov     rbx,qword ptr [rcx+rbp]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiDispatchFault+de

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiDispatchFault+de

BUCKET_ID:  X64_0x50_nt!MiDispatchFault+de

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