BSOD

Riesen_Meal

I don't know if I am posting in the right place or not (mod's feel free to move if not in correct forum) but I am regularly getting a BSOD on my Win 7 laptop once or twice a day sometimes....

A bit of googling said it may be a RAM issue but I re-seated the ram and all seems fine on that end, I did a fresh install of Win 7 yesterday thinking that my installation had become corrupted somehow but alas it just came back and it's annoying me now, the only real programs I have installed are Chrome, VLC, XBMC, Utorrent, then I was beginning to think it was Chrome causing it, as it always seems to happen with Chrome open...

I have actually disabled IE from the programs list as I don't use it, could that have anything to do with it even?

Its an old enough laptop (bout 4 or 5 years) but this is a fairly new thing....

I updated to SP1 and everything yesterday, I could roll back....

I have attached a Pastebin of the error if anyone has any idea what it could be I'm open to suggestions, I'm fairly handy with stuff like this normally but can't figure this one for the life of me, hence the posting....

http://pastebin.com/zMD2DyXi

Capt'n Midnight

If you suspect RAM then run either the manufacturers diagnostics or download memtest

run overnight /extended period

Riesen_Meal

Capt'n Midnight wrote: »

If you suspect RAM then run either the manufacturers diagnostics or download memtest

run overnight /extended period

Ive never had RAM go bad on me though, is it even possible? Its the same RAM thats been in it since day one!

The only reason I suspected it was RAM was when I googled the error, it lead me to a thread here with a lad with a similar error, he re-seated his RAM and it was fine, it's an odd one all the same, will try memtest....

Cheers

Fysh

Fieldog wrote: »

Ive never had RAM go bad on me though, is it even possible? Its the same RAM thats been in it since day one!

The only reason I suspected it was RAM was when I googled the error, it lead me to a thread here with a lad with a similar error, he re-seated his RAM and it was fine, it's an odd one all the same, will try memtest....

Cheers

If RAM couldn't fail just like any other electronic component, why would it be suggested as something to check?

If you think that RAM might be the issue, the two tests are either: a) remove all but one memory module and test to see if you can reproduce the problem (swapping out memory modules after a given amount of time) or b) download and burn a copy of memtest86, boot from it and leave it running for at least 12 hours and see what it reports.

How are you in terms of other maintenance? Have you error-checked/defragged your hard drive recently? Have you installed any new drivers (perhaps ones supplied by Windows Update)?

The Acronis Drive Monitor is a handy utility for checking SMART drive status - it should tell you if there's anything seriously problematic with your hard drive.

Riesen_Meal

Fysh wrote: »

If RAM couldn't fail just like any other electronic component, why would it be suggested as something to check?

If you think that RAM might be the issue, the two tests are either: a) remove all but one memory module and test to see if you can reproduce the problem (swapping out memory modules after a given amount of time) or b) download and burn a copy of memtest86, boot from it and leave it running for at least 12 hours and see what it reports.

How are you in terms of other maintenance? Have you error-checked/defragged your hard drive recently? Have you installed any new drivers (perhaps ones supplied by Windows Update)?

The Acronis Drive Monitor is a handy utility for checking SMART drive status - it should tell you if there's anything seriously problematic with your hard drive.

Thanks for the suggestions Fysh, downloaded memtest and stuck it on a key ready to go, just have to wait til I have a chance to leave it run overnight for 12 hours!

Windows update may have installed a bad driver somewhere alright, that was my initial thought as it kind of just appeared from nowhere....

I have not defragged it in a while so I will also give that a go along with Acronis....

Thanks for the tips, will report back after the above 3 suggestions....

Rambo

can you post up the mini dump files not enough info on the file you posted up
you can get from this folder C:\Windows\Minidump

just saw the file i need
C:\Windows\Minidump\091013-27814-01.dmp
I will have look for you ok

Riesen_Meal

Rambo wrote: »

can you post up the mini dump files not enough info on the file you posted up
you can get from this folder C:\Windows\Minidump

just saw the file i need
C:\Windows\Minidump\091013-27814-01.dmp
I will have look for you ok

Here you go -

https://app.box.com/s/73zdzwgi2beshopp3m4p

Thanks Rambo....

Rambo

Fieldog wrote: »

Here you go -

https://app.box.com/s/73zdzwgi2beshopp3m4p

Thanks Rambo....

here the output

CURRENT_IRQL: 2

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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TAG_NOT_DEFINED_c000000f: FFFFF80000BA2FB0

TRAP_FRAME: fffff80000b9bf60 -- (.trap 0xfffff80000b9bf60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000000008c8
rdx=00000000000008c8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003018477 rsp=fffff80000b9c0f8 rbp=0000000000000000
r8=000000000000003c r9=0000000000000000 r10=00000000000fffff
r11=fffffa8005382140 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe nc
hal!HalpDmaNextContiguousPiece+0x103:
fffff800`03018477 448b08 mov r9d,dword ptr [rax] ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800030d41a9 to fffff800030d4c00

STACK_TEXT:
fffff800`00b9be18 fffff800`030d41a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9be20 fffff800`030d2e20 : 00000000`00002000 fffffa80`05521000 00000000`001dce32 fffffa80`06ba7610 : nt!KiBugCheckDispatch+0x69
fffff800`00b9bf60 fffff800`03018477 : fffffa80`06efdf40 fffffa80`067a7738 fffff800`03018524 fffffa80`06ba7610 : nt!KiPageFault+0x260
fffff800`00b9c0f8 fffff800`03018524 : fffffa80`06ba7610 fffffa80`05382140 fffffa80`0484e3c0 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103
fffff800`00b9c110 fffff800`0301b4fb : fffffa80`06ba7610 fffffa80`05382140 fffffa80`06efdf40 fffff880`040361c7 : hal!HalpDmaMapScatterTransfer+0x34
fffff800`00b9c160 fffff800`0301b472 : fffffa80`06ba7610 fffffa80`06ba7608 00000000`0000003c 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff800`00b9c1f0 fffff800`0301a94f : 00000000`00000000 fffff800`0301801e 00000000`00000000 00000000`00000003 : hal!IoMapTransfer+0x8e
fffff800`00b9c230 fffff800`0301aafd : fffffa80`05006050 fffffa80`05382140 00000000`00000001 fffffa80`000000ac : hal!HalpAllocateAdapterCallback+0xc7
fffff800`00b9c2d0 fffff800`0301b156 : fffffa80`05382140 00000000`00000500 fffffa80`05382100 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffff800`00b9c300 fffff800`0301a71f : fffffa80`07bde010 00000000`000005f4 fffffa80`05382140 fffffa80`0694d280 : hal!HalAllocateAdapterChannel+0x11a
fffff800`00b9c340 fffff880`014c7750 : fffffa80`064fce00 fffffa80`054c6b40 00000000`000000a0 fffff880`04272f27 : hal!HalBuildScatterGatherList+0x2f3
fffff800`00b9c3b0 fffff880`0402bb7d : fffffa80`050061a0 fffff880`04272b20 fffffa80`03fb48e0 fffff780`00000014 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff800`00b9c450 fffffa80`050061a0 : fffff880`04272b20 fffffa80`03fb48e0 fffff780`00000014 00000000`00000000 : netw5v64+0x5b7d
fffff800`00b9c458 fffff880`04272b20 : fffffa80`03fb48e0 fffff780`00000014 00000000`00000000 000005f4`00000100 : 0xfffffa80`050061a0
fffff800`00b9c460 fffffa80`03fb48e0 : fffff780`00000014 00000000`00000000 000005f4`00000100 00000000`00000000 : netw5v64+0x24cb20
fffff800`00b9c468 fffff780`00000014 : 00000000`00000000 000005f4`00000100 00000000`00000000 fffff880`04033fb9 : 0xfffffa80`03fb48e0
fffff800`00b9c470 00000000`00000000 : 000005f4`00000100 00000000`00000000 fffff880`04033fb9 fffff880`042f2f80 : 0xfffff780`00000014


STACK_COMMAND: kb

FOLLOWUP_IP:
netw5v64+5b7d
fffff880`0402bb7d ?? ???

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

---

Appears to be your wifi network card driver is at fault here (netw5v64.sys)
I would suggest you update driver, or rolback to a early version before update.


Just saw this driver is from 2009 is this correct
Image path: \SystemRoot\system32\DRIVERS\netw5v64.sys
Image name: netw5v64.sys
Timestamp: Thu Mar 26 16:21:24 2009 (49CBAB84)

You are not the only one with this bad driver by intel
https://communities.intel.com/message/128830

Riesen_Meal

Thanks a lot for the reply Rambo, must have been the Windows Auto-update of the driver and it got it wrong, I am going to roll it back now to the default driver and see does it make a difference, it always appeared usually if I was downloading a large file or was streaming from Youtube, thanks for putting my mind at ease, I thought it was Chrome for a while also....

Much appreciated,

Dave

Edit : Added the latest wireless driver from Intel...

No bsod as of yet, will keep my eye on it...

Fysh

Glad to hear that it's apparently sorted, and thank you for coming back to confirm you've been able to fix the problem. (Hopefully if anyone else gets hit by this in future they'll find this thread and know how to fix it).

TheBoffin

Just for future reference, you can (if you wish) exclude drivers from updating automatically to prevent this from happening.

http://support.microsoft.com/kb/2500967