BCCode: d1

Funny, it is pointing to your wireless adapter drivers. Please uninstall them and install a fresh copy.

Code:

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_062110-24273-01.zip\062110-24273-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0325c000 PsLoadedModuleList = 0xfffff800`03499e50
Debug session time: Mon Jun 21 17:55:59.135 2010 (UTC - 4:00)
System Uptime: 0 days 0:12:15.259
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.......
Unable to load image \SystemRoot\system32\DRIVERS\Darusb_win7x.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Darusb_win7x.sys
*** ERROR: Module load completed but symbols could not be loaded for Darusb_win7x.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88006e53bd6, fffff8800b8929c8, fffff8800b892230}

Probably caused by : Darusb_win7x.sys ( Darusb_win7x+2bd6 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88006e53bd6, The address that the exception occurred at
Arg3: fffff8800b8929c8, Exception Record Address
Arg4: fffff8800b892230, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
Darusb_win7x+2bd6
fffff880`06e53bd6 8981f00b0000    mov     dword ptr [rcx+0BF0h],eax

EXCEPTION_RECORD:  fffff8800b8929c8 -- (.exr 0xfffff8800b8929c8)
ExceptionAddress: fffff88006e53bd6 (Darusb_win7x+0x0000000000002bd6)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000bf0
Attempt to write to address 0000000000000bf0

CONTEXT:  fffff8800b892230 -- (.cxr 0xfffff8800b892230)
rax=0000000000001000 rbx=fffffa800a802050 rcx=0000000000000000
rdx=0000000000001000 rsi=fffffa800af0db60 rdi=fffffa800a79db00
rip=fffff88006e53bd6 rsp=fffff8800b892c00 rbp=fffff800034715a0
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffffa800a831198 r12=fffffa800a79db00 r13=0000000000000001
r14=fffff8800b892ce8 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
Darusb_win7x+0x2bd6:
fffff880`06e53bd6 8981f00b0000    mov     dword ptr [rcx+0BF0h],eax ds:002b:00000000`00000bf0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000bf0

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800035040e0
 0000000000000bf0 

FOLLOWUP_IP: 
Darusb_win7x+2bd6
fffff880`06e53bd6 8981f00b0000    mov     dword ptr [rcx+0BF0h],eax

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 0000000100000000 to fffff88006e53bd6

STACK_TEXT:  
fffff880`0b892c00 00000001`00000000 : fffff800`034715a0 fffffa80`0a802050 fffff880`06e53de1 00000000`00000000 : Darusb_win7x+0x2bd6
fffff880`0b892c08 fffff800`034715a0 : fffffa80`0a802050 fffff880`06e53de1 00000000`00000000 00000000`00001000 : 0x1`00000000
fffff880`0b892c10 fffffa80`0a802050 : fffff880`06e53de1 00000000`00000000 00000000`00001000 fffff780`00000008 : nt!ExWorkerQueue
fffff880`0b892c18 fffff880`06e53de1 : 00000000`00000000 00000000`00001000 fffff780`00000008 00000000`00000000 : 0xfffffa80`0a802050
fffff880`0b892c20 00000000`00000000 : 00000000`00001000 fffff780`00000008 00000000`00000000 fffff800`03446e80 : Darusb_win7x+0x2de1


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Darusb_win7x+2bd6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Darusb_win7x

IMAGE_NAME:  Darusb_win7x.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b19e77d

STACK_COMMAND:  .cxr 0xfffff8800b892230 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_Darusb_win7x+2bd6

BUCKET_ID:  X64_0x7E_Darusb_win7x+2bd6

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

If BSODs continue, please enable driver verifier: Using Driver Verifier to identify issues with Drivers

shihong5858 said:

so is it means it is caused by the wireless adapter again?

That's what the dmp points to. That doesn't necessarily mean it's correct, but it's accurate enough to merit prompt attention.

Yes, you are right, the bugcheck indicate the same problem, D-link device (Darusb_win7x.sys)
Is your device only cerified for Window vista?? I personally recommend you to use internal wifi card rather than an USB device, I think they are more likely to reliable and compatible with window 7
here is the bugcheck:

Code:

BugCheck C1, {fffff9800596afd0, fffff9800596aff4, 7f402c, 24}
Unable to load image \SystemRoot\system32\DRIVERS\Darusb_win7x.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Darusb_win7x.sys
*** ERROR: Module load completed but symbols could not be loaded for Darusb_win7x.sys
Probably caused by : Darusb_win7x.sys ( Darusb_win7x+bf31 )
Followup: MachineOwner
---------

Tuan

Can you un-install the driver, remove the usb and keep driver verifier running to see what else can be wrong?

Ummm...I still see sptd.sys in the loaded driver, have you uninstall Deamon tool and run the sptd uninstaller for testing: DuplexSecure - Downloads
I'm sorry if this sounds funny to you, but I was in your situation, I got BSODs, the dump file indicated enthernet driver (updated, problem keep chasing), and bummm...after uninstall Deamon tool--->> no more at least until today

Try to do it again as well

Tuan