BSOD even after clean install

BSOD even after clean install19th March 2011, 1:28 am

Hello

Hoping you might be able to assist me.
My laptop randomly shuts down after blue screen comes up. I scanned pc with trend housecall/malware bytes/ cc cleaner/ s&d the full works to cover all bases but nothing showed up so i did clean install (which i had intended on doing anyway as way of spring clean!) anyhow even after clean install the bsod still keeps happening. I thought it might have been due to overheating so i did a physical clean of vents too, still to no avail Sad tearing

I have followed Captin Jack Sparrows instruction (i Hope!) & zipped mini dump folder
http://cid-9635a0f596e6ecdd.office.live.com/self.aspx/mini%20dmp/mini%20dump%20march%2011.zip.zip

this is the message that comes up on restart
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 6153

Additional information about the problem:
BCCode: a
BCP1: 00000064
BCP2: 00000002
BCP3: 00000001
BCP4: 82FC4EDE
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Help! & thanks in advance if you can help.

Re: BSOD even after clean install19th March 2011, 10:45 am

updated minidump file
http://cid-9635a0f596e6ecdd.office.live.com/browse.aspx/mini%20dmp?uc=1

thanks

Re: BSOD even after clean install24th March 2011, 1:14 pm

Hi there,

Seems like NETw4v32.sys i.e. Intel® Wireless WiFi Link Driver is causing the System to crash. I would recommend to download a new version from and Intel's website remove the current version you have and install the downloaded version.

Follow this guide it's for Windows 7 but should work for Vista as well

Code:


DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: d3257d18, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8d7e2096, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 821315ac
Unable to read MiSystemVaType memory at 821117e0
 d3257d18 

CURRENT_IRQL:  2

FAULTING_IP: 
NETw4v32+9096
8d7e2096 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Idle

TRAP_FRAME:  820f1b10 -- (.trap 0xffffffff820f1b10)
ErrCode = 00000000
eax=90a0a5a8 ebx=9096b150 ecx=90cab958 edx=9096b0f0 esi=90d8f528 edi=90d8f528
eip=8d7e2096 esp=820f1b84 ebp=820f1b98 iopl=0         nv up ei pl zr ac pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010256
NETw4v32+0x9096:
8d7e2096 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8d7e2096 to 8208fe14

STACK_TEXT:  
820f1b10 8d7e2096 badb0d00 9096b0f0 823a75a4 nt!KiTrap0E+0x2ac
WARNING: Stack unwind information not available. Following frames may be wrong.
820f1b80 90d8f528 90d8f528 8206ea92 87b81a20 NETw4v32+0x9096
820f1b98 8d7e22ea 90a0a5a8 9096b150 820f1bc0 0x90d8f528
820f1ba8 8d7e275c 90d8f528 9096b150 87ca50e8 NETw4v32+0x92ea
820f1bc0 82b4d2b2 00000000 9096b150 00000000 NETw4v32+0x975c
820f1bf0 820a9c92 9096b118 0096b0f0 745ee9eb ndis!ndisMTimerDpcX+0xb6
820f1ce8 820a9421 00000000 00000000 0005fa81 nt!KiTimerExpiration+0x659
820f1d50 8209147e 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
820f1d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x46


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETw4v32+9096
8d7e2096 ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  NETw4v32+9096

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETw4v32

IMAGE_NAME:  NETw4v32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45e199a5

FAILURE_BUCKET_ID:  0xD1_NETw4v32+9096

BUCKET_ID:  0xD1_NETw4v32+9096

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

............................................................................................
Regards,
Captain MVP

It is considered
courteous to post a reply if you have been able to resolve your problem, or received an answer to your question.

BSOD even after clean install

descriptionBSOD even after clean install19th March 2011, 1:28 am

descriptionRe: BSOD even after clean install19th March 2011, 10:45 am

descriptionRe: BSOD even after clean install24th March 2011, 1:14 pm

descriptionRe: BSOD even after clean install