I had this issue with vista also, currently running windows 7 build 7600. Bought a WD MyworldbookII NAS, if i try to transfer large files to it via networked drive i get a bsod. if i use a ftp method everything works fine, Keep in mind its totally random and not dependent on file name or file size(I found something in the vista forums about file name), also i cant duplicate the error with the same file. sometimes it does it sometimes it doesn't, totally random. i have the latest firmware for the nas as well as the latest driver for my intell wifi link 5300AGN driver version 13.0.0.107. i have read some issue with broadcomm drivers ....but seeing as i only use a wireless connection i didn't believe it was related, but i do have a broadcomm netlink gigabit ethernet connection using driver version 11.22.0.2. I have attached the minidump. hopefully someone has a fix for this.
Hi and welcome
This crash was probably caused by your wifi driver. It crashed the hardware abstraction layer and the system puked and died. Your system has serval old drivers and I would update them all.
I would also run a system file check by typing cmd in search>right click and run as admin
SFC /SCANNOW
Let us know the results
Ken J+
secdrv.SYS fffff880`027d1000 fffff880`027dc000 0x0000b000 0x4508052e 9/13/2006 8:18:38 AM
rimmpx64.sys fffff880`04de3000 fffff880`04df7000 0x00014000 0x45fdfeee 3/18/2007 10:09:34 PM
rimspx64.sys fffff880`03a71000 fffff880`03a88000 0x00017000 0x46a886a0 7/26/2007 6:33:52 AM
rixdpx64.sys fffff880`04e43000 fffff880`04e9a000 0x00057000 0x46a9ccde 7/27/2007 5:45:50 AM
ALSysIO64.sys fffff880`02987000 fffff880`0298e000 0x00007000 0x494c2047 12/19/2008 5:29:27 PM
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\112009-21855-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*
Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList = 0xfffff800`02c8ae50
Debug session time: Fri Nov 20 07:36:32.976 2009 (GMT-5)
System Uptime: 0 days 0:25:59.724
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff80002a06477}
Unable to load image \SystemRoot\system32\DRIVERS\netw5v64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a06477, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf50e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
hal!HalpDmaNextContiguousPiece+103
fffff800`02a06477 448b08 mov r9d,dword ptr [rax]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88002f19010 -- (.trap 0xfffff88002f19010)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000bd0
rdx=0000000000000bd0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a06477 rsp=fffff88002f191a8 rbp=0000000000000000
r8=0000000000000578 r9=0000000000000000 r10=00000000000fffff
r11=fffffa8008809430 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe nc
hal!HalpDmaNextContiguousPiece+0x103:
fffff800`02a06477 448b08 mov r9d,dword ptr [rax] ds:0001:00000000`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002abe469 to fffff80002abef00
STACK_TEXT:
fffff880`02f18ec8 fffff800`02abe469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f18ed0 fffff800`02abd0e0 : fffffa80`08144a48 fffffa80`085edd10 00000000`00000001 fffff880`048feea0 : nt!KiBugCheckDispatch+0x69
fffff880`02f19010 fffff800`02a06477 : fffffa80`07343240 fffffa80`08147430 fffff800`02a06524 fffffa80`085edd10 : nt!KiPageFault+0x260
fffff880`02f191a8 fffff800`02a06524 : fffffa80`085edd10 fffffa80`08809430 fffffa80`08809270 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103
fffff880`02f191c0 fffff800`02a094fb : fffffa80`085edd10 fffffa80`08809430 fffffa80`07343240 00000000`00000050 : hal!HalpDmaMapScatterTransfer+0x34
fffff880`02f19210 fffff800`02a09472 : fffffa80`085edd10 fffffa80`085edd08 00000000`00000578 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff880`02f192a0 fffff800`02a0894f : 00000000`00000000 fffff800`02a05fb9 00000000`00000000 00000000`00000003 : hal!IoMapTransfer+0x8e
fffff880`02f192e0 fffff800`02a08afd : fffffa80`0846f050 fffffa80`08809430 00000000`00000001 fffffa80`00000000 : hal!HalpAllocateAdapterCallback+0xc7
fffff880`02f19380 fffff800`02a09156 : fffffa80`08809430 00000000`00000500 fffffa80`08809400 00000000`00000006 : hal!IoFreeAdapterChannel+0x109
fffff880`02f193b0 fffff800`02a0871f : fffffa80`07f01880 00000000`000005fc fffffa80`08809430 fffffa80`073084f0 : hal!HalAllocateAdapterChannel+0x11a
fffff880`02f193f0 fffff880`0162f7c0 : fffffa80`06e6ea40 fffffa80`088090a0 00000000`000000d0 fffff880`04ad4f27 : hal!HalBuildScatterGatherList+0x2f3
fffff880`02f19460 fffff880`0488db7d : fffffa80`0846f1a0 fffff880`04ad4b20 fffffa80`07d41a70 fffff780`00000014 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff880`02f19500 fffffa80`0846f1a0 : fffff880`04ad4b20 fffffa80`07d41a70 fffff780`00000014 00000000`00000000 : netw5v64+0x5b7d
fffff880`02f19508 fffff880`04ad4b20 : fffffa80`07d41a70 fffff780`00000014 00000000`00000000 000005fc`00000100 : 0xfffffa80`0846f1a0
fffff880`02f19510 fffffa80`07d41a70 : fffff780`00000014 00000000`00000000 000005fc`00000100 00000000`00000000 : netw5v64+0x24cb20
fffff880`02f19518 fffff780`00000014 : 00000000`00000000 000005fc`00000100 00000000`00000000 fffff880`04895fb9 : 0xfffffa80`07d41a70
fffff880`02f19520 00000000`00000000 : 000005fc`00000100 00000000`00000000 fffff880`04895fb9 fffff880`04b54f80 : 0xfffff780`00000014
STACK_COMMAND: kb
FOLLOWUP_IP:
netw5v64+5b7d
fffff880`0488db7d ?? ???
SYMBOL_STACK_INDEX: c
SYMBOL_NAME: netw5v64+5b7d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: netw5v64
IMAGE_NAME: netw5v64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49cbab84
FAILURE_BUCKET_ID: X64_0xA_netw5v64+5b7d
BUCKET_ID: X64_0xA_netw5v64+5b7d
Followup: MachineOwner
Hope this helps
Ken J+
---------
