BSOD while downloading?

dfxos · 24 Jan 2015

Recently I got BSODs while idle just downloading torrent files. I got this on Windows7, I tried 8 but didn't liked it and got back to 7. I looked at the last 2 dump files and there is some problem with the hall.dll file as I see

Arc · 24 Jan 2015

Hi dfxos.

Download and install Intel® PROSet/Wireless Software and Drivers for Windows.

Let us know the result.
_________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002e03477}

*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+b76b )

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f7100
GetUlongFromAddress: unable to read from fffff800030f71c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  uTorrent.exe

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

TRAP_FRAME:  fffff8800cfb3ae0 -- (.trap 0xfffff8800cfb3ae0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000000007ac
rdx=00000000000007ac rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e03477 rsp=fffff8800cfb3c78 rbp=0000000000000000
 r8=000000000000001c  r9=0000000000000000 r10=00000000000fffff
r11=fffffa80060f7ea0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
hal!HalpDmaNextContiguousPiece+0x103:
fffff800`02e03477 448b08          mov     r9d,dword ptr [rax] ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ebf169 to fffff80002ebfbc0

STACK_TEXT:  
fffff880`0cfb3998 fffff800`02ebf169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0cfb39a0 fffff800`02ebdde0 : fffffa80`075880a0 fffff880`08221c2e fffffa80`07559210 fffffa80`048eba50 : nt!KiBugCheckDispatch+0x69
fffff880`0cfb3ae0 fffff800`02e03477 : fffffa80`06e247f0 fffffa80`06923854 fffff800`02e03524 fffffa80`048eba50 : nt!KiPageFault+0x260
fffff880`0cfb3c78 fffff800`02e03524 : fffffa80`048eba50 fffffa80`060f7ea0 fffffa80`04ca7280 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103
fffff880`0cfb3c90 fffff800`02e064fb : fffffa80`048eba50 fffffa80`060f7ea0 fffffa80`06e247f0 fffffa80`07997fd8 : hal!HalpDmaMapScatterTransfer+0x34
fffff880`0cfb3ce0 fffff800`02e06472 : fffffa80`048eba50 fffffa80`048eba48 00000000`0000001c 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff880`0cfb3d70 fffff800`02e0594f : 00000000`00000000 fffff800`02e0301e 00000000`00000000 00000000`00000005 : hal!IoMapTransfer+0x8e
fffff880`0cfb3db0 fffff800`02e05afd : fffffa80`057ea050 fffffa80`060f7ea0 00000000`00000001 fffffa80`00000480 : hal!HalpAllocateAdapterCallback+0xc7
fffff880`0cfb3e50 fffff800`02e06156 : fffffa80`060f7ea0 00000000`00000200 fffffa80`060f7e00 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffff880`0cfb3e80 fffff800`02e0571f : fffffa80`070a7e40 00000000`000002fa fffffa80`060f7ea0 fffffa80`0592c020 : hal!HalAllocateAdapterChannel+0x11a
fffff880`0cfb3ec0 fffff880`018fb600 : fffffa80`0496f560 fffffa80`05b02050 fffffa80`000000a0 fffff880`0846ec40 : hal!HalBuildScatterGatherList+0x2f3
fffff880`0cfb3f30 fffff880`0822a76b : fffffa80`057ea1a0 00000000`00000000 fffffa80`04d8f020 fffff880`083cfaa0 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff880`0cfb3fd0 fffffa80`057ea1a0 : 00000000`00000000 fffffa80`04d8f020 fffff880`083cfaa0 00000000`00000000 : NETw5s64+0xb76b
fffff880`0cfb3fd8 00000000`00000000 : fffffa80`04d8f020 fffff880`083cfaa0 00000000`00000000 000002fa`00000100 : 0xfffffa80`057ea1a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETw5s64+b76b
fffff880`0822a76b ??              ???

SYMBOL_STACK_INDEX:  c

SYMBOL_NAME:  NETw5s64+b76b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETw5s64

IMAGE_NAME:  NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4aafedb7

FAILURE_BUCKET_ID:  X64_0xA_NETw5s64+b76b

BUCKET_ID:  X64_0xA_NETw5s64+b76b

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_netw5s64+b76b

FAILURE_ID_HASH:  {0f4dbd47-b659-1d41-ac70-28ebf6a221cb}

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

0: kd> lmvm NETw5s64
start             end                 module name
fffff880`0821f000 fffff880`088cc000   NETw5s64 T (no symbols)           
    Loaded symbol image file: NETw5s64.sys
    Image path: \SystemRoot\system32\DRIVERS\NETw5s64.sys
    Image name: NETw5s64.sys
    Timestamp:        Wed Sep 16 01:10:39 2009 (4AAFEDB7)
    CheckSum:         006A6E93
    ImageSize:        006AD000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

dfxos · 24 Jan 2015

Thanks for the reply my driver was a bit old...from 2009 lol.

I uninstalled my current drivers, downloaded and installed this one :

File name: Wireless_16.7.0_Ds64.exe
Version: 16.7.0 (Previously released)
Date: 12/17/2013
Size: 25.16 MB
Language: English
Operating Systems: Windows 7 *, Windows 7 (64-bit)*

I just notified that the driver version is 16.7.0, 2013, but when I checked Device manager the version is different

Anyway now hoping to get rid of the BSOD.

Arc · 25 Jan 2015

The date is different in device manager cause the release date is of the installer package, the actual driver is bit of old.

Anyway, let us know for any further BSOD.

dfxos · 26 Jan 2015

Well today there was another BSOD, but this time I think is something with my videocard lol.

I was downloading (again) and just browsing facebook when suddenly atikmdag.sys caused the BSOD. I think I must update my videocard drivers as wel.. attached dump files >

Arc · 27 Jan 2015

This time it is the display driver.

Code:

BugCheck 116, {fffffa8004a694e0, fffff88006e05c98, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+5c98 )

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

Which is too old.

Code:

    Image name: atikmpag.sys
    Timestamp:        Fri Jan 22 18:37:54 2010 (4B59A32A)

Update it from Download Drivers ... let us know the result.

dfxos · 01 Feb 2015

One week passed after I update my wireless and video drivers and everything seems good, no BSOD and other freezez, so far so good, thanks a lot Arc.

Arc · 02 Feb 2015

Good news. :)

Let us know for any further BSOD.