Studio 15, Win7 x64, and Intel 5300 cause BSOD under high network load

System:

Dell Studio 1555 w/ Bios A07
Windows 7 Professional x64
Intel 5300 Wireless card
4 GB RAM
Intel C2D P8600 2.40GHz CPU

Problem:

Under high network load over a wireless connection using the Dell Studio 1555 and the Intel 5300 card I occasionally get a BSOD. This occurs every 1-3 days, and is unpredictable, but happens more frequently the more connections are opened and the faster the transfer speeds are.

Steps taken:

I have tried many different driver versions. I have tried the Dell driver for Vista v 12.4, and I have also tried v12.x and v13.000.107 from Intel's site. Most recently I've installed the driver Dell just released on the driver download page for Win7 x64 and the Studio 1555, which appears to be a modified Intel driver from May, v12.4.1.11

I have tried changing wireless security from WEP, WPA and WPA2, all cause BSOD.
I have tried channel width band at 2.4GHz and Auto
I have tried changing roaming aggressiveness from lowest to highest and in-between, to no avail
I have tried throughput enhancement on Enabled and Disabled
I have tried Transmit power at Lowest to Highest, no fix there either
I have disabled "Allow the computer to turn off this device to conserve power"
I have in battery options tried maximum through minimum power usage on both battery and plugged in settings.

Solution?

None found so far. I've seen this problem posted in other locations on the internet and so far have seen no solution.

Any solutions, ideas, of feedback would be wonderful...

Here is the debug of the most recent BSOD from Dell's newest x64 Win7 driver from their support dl site:


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 1097, 4060001, fffffa800b103500}

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
GetPointerFromAddress: unable to read from fffff80002f0f0e0
Probably caused by : netw5v64.sys ( netw5v64+6009 )

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

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000004060001, Memory contents of the pool block
Arg4: fffffa800b103500, Address of the block of pool being deallocated

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


POOL_ADDRESS:  fffffa800b103500 

FREED_POOL_TAG:  Int2

BUGCHECK_STR:  0xc2_7_Int2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002e0a60e to fffff80002cd8f00

STACK_TEXT:  
fffff880`02f1b5c8 fffff800`02e0a60e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`04060001 : nt!KeBugCheckEx
fffff880`02f1b5d0 fffff880`016f3695 : fffffa80`0b47bd10 fffff880`02f1b810 00000000`00000000 fffffa80`0b47bd10 : nt!ExFreePool+0xccb
fffff880`02f1b680 fffff880`04869009 : fffffa80`0bef1e20 fffffa80`0a91d4f8 fffffa80`0a91d56f fffff880`00000030 : ndis!NdisFreeMemory+0x15
fffff880`02f1b6b0 fffffa80`0bef1e20 : fffffa80`0a91d4f8 fffffa80`0a91d56f fffff880`00000030 fffff880`02f1b720 : netw5v64+0x6009
fffff880`02f1b6b8 fffffa80`0a91d4f8 : fffffa80`0a91d56f fffff880`00000030 fffff880`02f1b720 fffffa80`0b47bd10 : 0xfffffa80`0bef1e20
fffff880`02f1b6c0 fffffa80`0a91d56f : fffff880`00000030 fffff880`02f1b720 fffffa80`0b47bd10 00000000`000000e8 : 0xfffffa80`0a91d4f8
fffff880`02f1b6c8 fffff880`00000030 : fffff880`02f1b720 fffffa80`0b47bd10 00000000`000000e8 fffffa80`0b103500 : 0xfffffa80`0a91d56f
fffff880`02f1b6d0 fffff880`02f1b720 : fffffa80`0b47bd10 00000000`000000e8 fffffa80`0b103500 fffffa80`0b37ae80 : 0xfffff880`00000030
fffff880`02f1b6d8 fffffa80`0b47bd10 : 00000000`000000e8 fffffa80`0b103500 fffffa80`0b37ae80 fffffa80`04140010 : 0xfffff880`02f1b720
fffff880`02f1b6e0 00000000`000000e8 : fffffa80`0b103500 fffffa80`0b37ae80 fffffa80`04140010 00000000`00000000 : 0xfffffa80`0b47bd10
fffff880`02f1b6e8 fffffa80`0b103500 : fffffa80`0b37ae80 fffffa80`04140010 00000000`00000000 fffffa80`0b47bd10 : 0xe8
fffff880`02f1b6f0 fffffa80`0b37ae80 : fffffa80`04140010 00000000`00000000 fffffa80`0b47bd10 fffffa80`04140010 : 0xfffffa80`0b103500
fffff880`02f1b6f8 fffffa80`04140010 : 00000000`00000000 fffffa80`0b47bd10 fffffa80`04140010 fffff880`04a1642c : 0xfffffa80`0b37ae80
fffff880`02f1b700 00000000`00000000 : fffffa80`0b47bd10 fffffa80`04140010 fffff880`04a1642c fffffa80`00000048 : 0xfffffa80`04140010


STACK_COMMAND:  kb

FOLLOWUP_IP: 
netw5v64+6009
fffff880`04869009 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  netw5v64+6009

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: netw5v64

IMAGE_NAME:  netw5v64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a0c3e06

FAILURE_BUCKET_ID:  X64_0xc2_7_Int2_netw5v64+6009

BUCKET_ID:  X64_0xc2_7_Int2_netw5v64+6009

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

1: kd> lmvm netw5v64
start             end                 module name
fffff880`04863000 fffff880`04d9e000   netw5v64 T (no symbols)           
    Loaded symbol image file: netw5v64.sys
    Image path: \SystemRoot\system32\DRIVERS\netw5v64.sys
    Image name: netw5v64.sys
    Timestamp:        Thu May 14 08:51:34 2009 (4A0C3E06)
    CheckSum:         0053085F
    ImageSize:        0053B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Responses(4)

C

carpenn

2 Posts

1

November 25th, 2009 15:00

Still no word of a fix for this issue? here is another crash dump...

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

Loading Dump File [C:\Windows\Minidump\112509-22448-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: symsrv*symsrv.dll*f:\localsymbols*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.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c1c000 PsLoadedModuleList = 0xfffff800`02e59e50
Debug session time: Wed Nov 25 15:27:32.058 2009 (GMT-8)
System Uptime: 0 days 0:54:34.900
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, fffff800031fb477}

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
---------

0: 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: fffff800031fb477, address which referenced memory

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

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec40e0
0000000000000000

CURRENT_IRQL: 2

FAULTING_IP:
hal!HalpDmaNextContiguousPiece+103
fffff800`031fb477 448b08          mov     r9d,dword ptr [rax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: uTorrent.exe

TRAP_FRAME: fffff8800acf0e40 -- (.trap 0xfffff8800acf0e40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000ff0
rdx=0000000000000ff0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031fb477 rsp=fffff8800acf0fd8 rbp=0000000000000000
r8=000000000000058c r9=0000000000000000 r10=00000000000fffff
r11=fffffa80055406b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe nc
hal!HalpDmaNextContiguousPiece+0x103:
fffff800`031fb477 448b08          mov     r9d,dword ptr [rax] ds:0001:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002c8d469 to fffff80002c8df00

STACK_TEXT:
fffff880`0acf0cf8 fffff800`02c8d469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0acf0d00 fffff800`02c8c0e0 : 00000000`00002000 fffffa80`0a34a9f0 00000000`00000001 fffff880`048f0060 : nt!KiBugCheckDispatch+0x69
fffff880`0acf0e40 fffff800`031fb477 : fffffa80`0a947f40 fffffa80`0ad3d010 fffff800`031fb524 fffffa80`0a34a9f0 : nt!KiPageFault+0x260
fffff880`0acf0fd8 fffff800`031fb524 : fffffa80`0a34a9f0 fffffa80`055406b0 fffffa80`04527100 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103
fffff880`0acf0ff0 fffff800`031fe4fb : fffffa80`0a34a9f0 fffffa80`055406b0 fffffa80`0a947f40 fffffa80`04a7bfd8 : hal!HalpDmaMapScatterTransfer+0x34
fffff880`0acf1040 fffff800`031fe472 : fffffa80`0a34a9f0 fffffa80`0a34a9e8 00000000`0000058c 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff880`0acf10d0 fffff800`031fd94f : fffffa80`05540550 fffff800`031fb01e 00000000`00000001 00000000`00000003 : hal!IoMapTransfer+0x8e
fffff880`0acf1110 fffff800`031fdafd : fffffa80`04f75050 fffffa80`055406b0 00000000`00000001 fffffa80`00000000 : hal!HalpAllocateAdapterCallback+0xc7
fffff880`0acf11b0 fffff800`031fe156 : fffffa80`055406b0 00000000`00000000 fffffa80`05540600 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffff880`0acf11e0 fffff800`031fd71f : fffffa80`0426e5c0 00000000`00000050 fffffa80`055406b0 fffffa80`062bc020 : hal!HalAllocateAdapterChannel+0x11a
fffff880`0acf1220 fffff880`014b87c0 : fffffa80`043a8210 fffffa80`05540320 00000000`000000a0 fffff880`04ac6537 : hal!HalBuildScatterGatherList+0x2f3
fffff880`0acf1290 fffff880`0487eb7d : fffffa80`04f751a0 fffff880`04ac6130 fffffa80`042c0790 fffff780`00000014 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff880`0acf1330 fffffa80`04f751a0 : fffff880`04ac6130 fffffa80`042c0790 fffff780`00000014 00000000`00000000 : netw5v64+0x5b7d
fffff880`0acf1338 fffff880`04ac6130 : fffffa80`042c0790 fffff780`00000014 00000000`00000000 00000050`00000100 : 0xfffffa80`04f751a0
fffff880`0acf1340 fffffa80`042c0790 : fffff780`00000014 00000000`00000000 00000050`00000100 00000000`00000000 : netw5v64+0x24d130
fffff880`0acf1348 fffff780`00000014 : 00000000`00000000 00000050`00000100 00000000`00000000 fffff880`04886fb9 : 0xfffffa80`042c0790
fffff880`0acf1350 00000000`00000000 : 00000050`00000100 00000000`00000000 fffff880`04886fb9 fffff880`04b465e0 : 0xfffff780`00000014

STACK_COMMAND: kb

FOLLOWUP_IP:
netw5v64+5b7d
fffff880`0487eb7d ??              ???

SYMBOL_STACK_INDEX: c

SYMBOL_NAME: netw5v64+5b7d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: netw5v64

IMAGE_NAME: netw5v64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a0c3e06

FAILURE_BUCKET_ID: X64_0xA_netw5v64+5b7d

BUCKET_ID: X64_0xA_netw5v64+5b7d

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

hwam

147 Posts

0

January 16th, 2010 11:00

Same problem with my Studio 1557. BSOD pointing to my Intel wifi 5300 agn. I'm using the latest driver 13.0.0.107. Do you have a solution yet?

Grt.

G

gmd024

36 Posts

0

January 16th, 2010 14:00

carpenn - I replied to your post earlier mentioning a utility that may help find your problem - I got an email from a moderator saying my reply was inappropriate and was deleted - I've no idea why - someone must be having a bad day

I wasen't sure if you saw the earlier post before it was deleted to get the link for the bluescreenview - it may point to the cause of your issue - here it is again - http://www.nirsoft.net/utils/blue_screen_view.html

BlueScreemView helped me solve an issue recently -- hope it helps for you also

camerasforeyes

1 Message

0

January 30th, 2010 21:00

Same problem here with my studio 1557, sometimes points to hal.dll and other times to the intel driver for my 5300. Not cool, with this and overheating issues this laptop is turning into a expensive dud.

View All

No Events found!

Networking, Internet, & Bluetooth

Studio 15, Win7 x64, and Intel 5300 cause BSOD under high network load