Random BSoDs started yesterday

[Cyan Ryan]

So I've had this laptop since December and it's ran great, but it had two BSoDs yesterday. One occurred while I was asleep and the other one randomly happened while I was watching a video. Both are attached.

 

[Tews]

Your .dmp files point to netw5v64.sys ( Your wireless adapter ) ... completely remove the old driver and download the latest driver for your adapter and test...

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


Loading Dump File [C:\Windows\Minidump\060710-22370-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 Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e1e000 PsLoadedModuleList = 0xfffff800`0305be50
Debug session time: Mon Jun  7 18:26:02.576 2010 (UTC - 4:00)
System Uptime: 0 days 3:56:38.574
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, fffff800033fc488}

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c60e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!HalpDmaNextContiguousPiece+114
fffff800`033fc488 458b02          mov     r8d,dword ptr [r10]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  fffff80000ba2190 -- (.trap 0xfffff80000ba2190)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80056bb1b0 rbx=0000000000000000 rcx=000000000000058c
rdx=000000000000037c rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033fc488 rsp=fffff80000ba2328 rbp=0000000000000000
 r8=000000000000058c  r9=00000000000baa4c r10=0000000000000000
r11=fffffa80056bb430 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
hal!HalpDmaNextContiguousPiece+0x114:
fffff800`033fc488 458b02          mov     r8d,dword ptr [r10] ds:0001:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8db69 to fffff80002e8e600

STACK_TEXT:  
fffff800`00ba2048 fffff800`02e8db69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba2050 fffff800`02e8c7e0 : fffffa80`04ffab38 fffffa80`054faed0 fffff800`00ba2240 fffff880`04865c18 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2190 fffff800`033fc488 : fffffa80`04d59130 fffffa80`06b99c84 fffff800`033fc524 fffffa80`054faed0 : nt!KiPageFault+0x260
fffff800`00ba2328 fffff800`033fc524 : fffffa80`054faed0 fffffa80`056bb430 fffffa80`04d326c0 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x114
fffff800`00ba2340 fffff800`033ff4fb : fffffa80`054faed0 fffffa80`056bb430 fffffa80`04d59130 fffff880`048611c7 : hal!HalpDmaMapScatterTransfer+0x34
fffff800`00ba2390 fffff800`033ff472 : fffffa80`054faed0 fffffa80`054faec8 00000000`0000058c 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff800`00ba2420 fffff800`033fe94f : fffffa80`056bb2b0 fffff800`033fc01e 00000000`00000003 00000000`00000004 : hal!IoMapTransfer+0x8e
fffff800`00ba2460 fffff800`033feafd : fffffa80`05375050 fffffa80`056bb430 00000000`00000001 fffffa80`00000000 : hal!HalpAllocateAdapterCallback+0xc7
fffff800`00ba2500 fffff800`033ff156 : fffffa80`056bb430 00000000`00000500 fffffa80`056bb400 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffff800`00ba2530 fffff800`033fe71f : fffffa80`04d9ec70 00000000`000005fc fffffa80`056bb430 fffffa80`03f66430 : hal!HalAllocateAdapterChannel+0x11a
fffff800`00ba2570 fffff880`016b37c0 : fffffa80`04fcf1a0 fffffa80`056bb0a0 00000000`000000a0 fffff880`04a9e537 : hal!HalBuildScatterGatherList+0x2f3
fffff800`00ba25e0 fffff880`04856b7d : fffffa80`053751a0 fffff880`04a9e130 fffffa80`0514e7c0 fffff780`00000014 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff800`00ba2680 fffffa80`053751a0 : fffff880`04a9e130 fffffa80`0514e7c0 fffff780`00000014 00000000`00000000 : netw5v64+0x5b7d
fffff800`00ba2688 fffff880`04a9e130 : fffffa80`0514e7c0 fffff780`00000014 00000000`00000000 000005fc`00000100 : 0xfffffa80`053751a0
fffff800`00ba2690 fffffa80`0514e7c0 : fffff780`00000014 00000000`00000000 000005fc`00000100 00000000`00000000 : netw5v64+0x24d130
fffff800`00ba2698 fffff780`00000014 : 00000000`00000000 000005fc`00000100 00000000`00000000 fffff880`0485efb9 : 0xfffffa80`0514e7c0
fffff800`00ba26a0 00000000`00000000 : 000005fc`00000100 00000000`00000000 fffff880`0485efb9 fffff880`04b1e5e0 : 0xfffff780`00000014


STACK_COMMAND:  kb

FOLLOWUP_IP: 
netw5v64+5b7d
fffff880`04856b7d ??              ???

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

---------