BSOD problem - BugCheck 50, {c258e758, 0, 89a47e26, 2}

Chris · Dec 25, 2007

Hi All,

I have bought a notebook for a year. I am using Vista Home Basic. My
computer sometimes crash by BSOD recently. The following is the debug log:-

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

Loading Dump File [D:\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Mon Dec 24 20:04:04.913 2007 (GMT+8)
System Uptime: 0 days 1:56:01.670
Loading Kernel Symbols
.................................................................................................................................................................
Loading User Symbols

Loading unloaded module list
.........
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {c258e758, 0, 89a47e26, 2}

*** ERROR: Module load completed but symbols could not be loaded for
NETw3v32.sys

Probably caused by : NETw3v32.sys ( NETw3v32+8e26 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or
it
is pointing at freed memory.
Arguments:
Arg1: c258e758, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 89a47e26, If non-zero, the instruction address which referenced the
bad memory
address.
Arg4: 00000002, (reserved)

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

READ_ADDRESS: c258e758

FAULTING_IP:
NETw3v32+8e26
89a47e26 8b3c91 mov edi,dword ptr [ecx+edx*4]

MM_INTERNAL_CODE: 2

IMAGE_NAME: NETw3v32.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45463982

MODULE_NAME: NETw3v32

FAULTING_MODULE: 89a3f000 NETw3v32

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: ad92638c -- (.trap 0xffffffffad92638c)
ErrCode = 00000000
eax=86201058 ebx=84f41fa8 ecx=8a147b58 edx=8e111b00 esi=84af2538 edi=84f41fd0
eip=89a47e26 esp=ad926400 ebp=ad926414 iopl=0 nv up ei pl nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212
NETw3v32+0x8e26:
89a47e26 8b3c91 mov edi,dword ptr [ecx+edx*4]
ds:0023:c258e758=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 81c8fbb4 to 81ca9ef2

STACK_TEXT:
ad926374 81c8fbb4 00000000 c258e758 00000000 nt!MmAccessFault+0x106
ad926374 89a47e26 00000000 c258e758 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be
wrong.
ad926414 89a48061 86201058 863df5a0 ad926440 NETw3v32+0x8e26
ad926424 89a47c77 84af2538 84f41fd0 862380b0 NETw3v32+0x9061
ad926440 89a55757 863df5a0 000000fa 00000001 NETw3v32+0x8c77
ad926468 89a47e46 862380b0 a635cb60 84f92fb0 NETw3v32+0x16757
ad926490 89a48061 86201058 863df5a0 ad9264bc NETw3v32+0x8e46
ad9264a0 89a47c77 a635cb60 84f92fb0 863df5a0 NETw3v32+0x9061
ad9264bc 89a547b2 863df5a0 0000000a 00000001 NETw3v32+0x8c77
ad926504 89aa8c87 863df5a0 ff000001 ad92654c NETw3v32+0x157b2
ad926524 89aa9985 861caa38 ff000001 ad92654c NETw3v32+0x69c87
ad926550 89aab769 84b80490 863499a4 84b80490 NETw3v32+0x6a985
ad9266f8 89a47e46 8635e8e8 84b80490 84ec7fb0 NETw3v32+0x6c769
ad926720 89a48061 8604aee0 861caa38 ad92674c NETw3v32+0x8e46
ad926730 89a47c77 84b80490 84ec7fb0 861ee300 NETw3v32+0x9061
ad92674c 89aa927b 861caa38 0000001b 00000001 NETw3v32+0x8c77
ad926798 89b15743 861ee300 ad926828 fd010101 NETw3v32+0x6a27b
ad926804 89b1a93d ad926828 89becd70 89be7e80 NETw3v32+0xd6743
ad926848 827b6397 861ee300 90df8c7c 860e6518 NETw3v32+0xdb93d
ad926890 826ff0d2 000e60e8 a1bc5730 c0000001 ndis!ndisMDoOidRequest+0x323
ad9268bc 826febc3 00000000 90df8c7c 90dfebc8
ndis!ndisFQueueRequestOnNext+0x22e
ad926924 a46777da a1bc5730 90df8c7c 90df8c78 ndis!NdisFOidRequest+0x139
ad926940 a4677b1c ad926960 90dfec68 90dfec68 nwifi!Dot11Request+0xee
ad926964 a4673c63 90df8008 00000000 fd010101 nwifi!Dot11ForwardRequest+0x44
ad9269e8 a4678c67 90df8008 fd010101 ad926cb8 nwifi!MPSetInformation+0x1e3
ad926a14 a467c439 90df8008 8a1ad0c0 ad926a84 nwifi!MP6Request+0xed
ad926a24 827b693e 90dfebc0 8a1ad0c0 a1bc5988 nwifi!FilterRequest+0x13
ad926a84 826ff062 00bc5730 8a773990 c0000001 ndis!ndisFDoOidRequest+0x199
ad926ab0 826febc3 00000000 8a1ad0c0 8a1ad140
ndis!ndisFQueueRequestOnNext+0x1be
ad926b18 8ae252c4 8a773990 8a1ad0c0 81fa4d90 ndis!NdisFOidRequest+0x139
ad926b38 827b693e 8a773190 ad926c1c 8a773990 pacer!PcFilterRequest+0x80
ad926b98 826fe3cb 00773990 00001388 ad926c1c ndis!ndisFDoOidRequest+0x199
ad926bd0 827cb6bc 860e60e8 ad926c1c 00000000 ndis!ndisQueueRequestOnTop+0x24e
ad926bf0 827e1b1f 00000000 00000000 00926c1c ndis!ndisQuerySetMiniport+0x166
ad926cac 827e341e 860e60e8 00000004 fd010101
ndis!ndisQuerySetMiniportDeviceState+0xbb
ad926cf8 827e3b5f 84b5e910 84b5e9c8 860e60e8 ndis!ndisSetPower+0x2c4
ad926d20 81c50b6e 84b5e9c8 8531a928 00000000 ndis!ndisPowerDispatch+0x1a3
ad926d7c 81e254e0 8a6f02b0 ad92d680 00000000 nt!PopIrpWorker+0x40f
ad926dc0 81c9159e 81c5075b 8a6f02b0 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
NETw3v32+8e26
89a47e26 8b3c91 mov edi,dword ptr [ecx+edx*4]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: NETw3v32+8e26

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x50_NETw3v32+8e26

BUCKET_ID: 0x50_NETw3v32+8e26

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

Please help to solve my problem, thank you!

Chris

Rick Rogers · Dec 25, 2007

Hi Chris,

Download and install the most recent driver release for your wireless
adapter. Even if it's the same version as you already have, overwrite it.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"Chris" <Chris@discussions.microsoft.com> wrote in message
news:AF4A0EA0-DCFB-4129-860E-0738B1243EDE@microsoft.com...
> Hi All,
>
> I have bought a notebook for a year. I am using Vista Home Basic. My
> computer sometimes crash by BSOD recently. The following is the debug
> log:-
>
>
> Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [D:\MEMORY.DMP]
> Kernel Summary Dump File: Only kernel address space is available
>
> Symbol search path is:
> SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
>
> Executable search path is:
> Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
> Product: WinNt, suite: TerminalServer SingleUserTS Personal
> Built by: 6000.16575.x86fre.vista_gdr.071009-1548
> Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
> Debug session time: Mon Dec 24 20:04:04.913 2007 (GMT+8)
> System Uptime: 0 days 1:56:01.670
> Loading Kernel Symbols
> ................................................................................................................................................................
> Loading User Symbols
>
> Loading unloaded module list
> ........
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 50, {c258e758, 0, 89a47e26, 2}
>
> *** ERROR: Module load completed but symbols could not be loaded for
> NETw3v32.sys
>
>
>
>
> Probably caused by : NETw3v32.sys ( NETw3v32+8e26 )
>
> Followup: MachineOwner
> ---------
>
>
>
>
> 1: kd> !analyze -v
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> PAGE_FAULT_IN_NONPAGED_AREA (50)
> Invalid system memory was referenced. This cannot be protected by
> try-except,
> it must be protected by a Probe. Typically the address is just plain bad
> or
> it
> is pointing at freed memory.
> Arguments:
> Arg1: c258e758, memory referenced.
> Arg2: 00000000, value 0 = read operation, 1 = write operation.
> Arg3: 89a47e26, If non-zero, the instruction address which referenced the
> bad memory
> address.
> Arg4: 00000002, (reserved)
>
> Debugging Details:
> ------------------
>
>
>
>
>
>
> READ_ADDRESS: c258e758
>
> FAULTING_IP:
> NETw3v32+8e26
> 89a47e26 8b3c91 mov edi,dword ptr [ecx+edx*4]
>
> MM_INTERNAL_CODE: 2
>
> IMAGE_NAME: NETw3v32.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 45463982
>
> MODULE_NAME: NETw3v32
>
> FAULTING_MODULE: 89a3f000 NETw3v32
>
> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>
> BUGCHECK_STR: 0x50
>
> PROCESS_NAME: System
>
> CURRENT_IRQL: 0
>
> TRAP_FRAME: ad92638c -- (.trap 0xffffffffad92638c)
> ErrCode = 00000000
> eax=86201058 ebx=84f41fa8 ecx=8a147b58 edx=8e111b00 esi=84af2538
> edi=84f41fd0
> eip=89a47e26 esp=ad926400 ebp=ad926414 iopl=0 nv up ei pl nz ac po
> nc
> cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
> efl=00010212
> NETw3v32+0x8e26:
> 89a47e26 8b3c91 mov edi,dword ptr [ecx+edx*4]
> ds:0023:c258e758=????????
> Resetting default scope
>
> LAST_CONTROL_TRANSFER: from 81c8fbb4 to 81ca9ef2
>
> STACK_TEXT:
> ad926374 81c8fbb4 00000000 c258e758 00000000 nt!MmAccessFault+0x106
> ad926374 89a47e26 00000000 c258e758 00000000 nt!KiTrap0E+0xdc
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> ad926414 89a48061 86201058 863df5a0 ad926440 NETw3v32+0x8e26
> ad926424 89a47c77 84af2538 84f41fd0 862380b0 NETw3v32+0x9061
> ad926440 89a55757 863df5a0 000000fa 00000001 NETw3v32+0x8c77
> ad926468 89a47e46 862380b0 a635cb60 84f92fb0 NETw3v32+0x16757
> ad926490 89a48061 86201058 863df5a0 ad9264bc NETw3v32+0x8e46
> ad9264a0 89a47c77 a635cb60 84f92fb0 863df5a0 NETw3v32+0x9061
> ad9264bc 89a547b2 863df5a0 0000000a 00000001 NETw3v32+0x8c77
> ad926504 89aa8c87 863df5a0 ff000001 ad92654c NETw3v32+0x157b2
> ad926524 89aa9985 861caa38 ff000001 ad92654c NETw3v32+0x69c87
> ad926550 89aab769 84b80490 863499a4 84b80490 NETw3v32+0x6a985
> ad9266f8 89a47e46 8635e8e8 84b80490 84ec7fb0 NETw3v32+0x6c769
> ad926720 89a48061 8604aee0 861caa38 ad92674c NETw3v32+0x8e46
> ad926730 89a47c77 84b80490 84ec7fb0 861ee300 NETw3v32+0x9061
> ad92674c 89aa927b 861caa38 0000001b 00000001 NETw3v32+0x8c77
> ad926798 89b15743 861ee300 ad926828 fd010101 NETw3v32+0x6a27b
> ad926804 89b1a93d ad926828 89becd70 89be7e80 NETw3v32+0xd6743
> ad926848 827b6397 861ee300 90df8c7c 860e6518 NETw3v32+0xdb93d
> ad926890 826ff0d2 000e60e8 a1bc5730 c0000001 ndis!ndisMDoOidRequest+0x323
> ad9268bc 826febc3 00000000 90df8c7c 90dfebc8
> ndis!ndisFQueueRequestOnNext+0x22e
> ad926924 a46777da a1bc5730 90df8c7c 90df8c78 ndis!NdisFOidRequest+0x139
> ad926940 a4677b1c ad926960 90dfec68 90dfec68 nwifi!Dot11Request+0xee
> ad926964 a4673c63 90df8008 00000000 fd010101
> nwifi!Dot11ForwardRequest+0x44
> ad9269e8 a4678c67 90df8008 fd010101 ad926cb8 nwifi!MPSetInformation+0x1e3
> ad926a14 a467c439 90df8008 8a1ad0c0 ad926a84 nwifi!MP6Request+0xed
> ad926a24 827b693e 90dfebc0 8a1ad0c0 a1bc5988 nwifi!FilterRequest+0x13
> ad926a84 826ff062 00bc5730 8a773990 c0000001 ndis!ndisFDoOidRequest+0x199
> ad926ab0 826febc3 00000000 8a1ad0c0 8a1ad140
> ndis!ndisFQueueRequestOnNext+0x1be
> ad926b18 8ae252c4 8a773990 8a1ad0c0 81fa4d90 ndis!NdisFOidRequest+0x139
> ad926b38 827b693e 8a773190 ad926c1c 8a773990 pacer!PcFilterRequest+0x80
> ad926b98 826fe3cb 00773990 00001388 ad926c1c ndis!ndisFDoOidRequest+0x199
> ad926bd0 827cb6bc 860e60e8 ad926c1c 00000000
> ndis!ndisQueueRequestOnTop+0x24e
> ad926bf0 827e1b1f 00000000 00000000 00926c1c
> ndis!ndisQuerySetMiniport+0x166
> ad926cac 827e341e 860e60e8 00000004 fd010101
> ndis!ndisQuerySetMiniportDeviceState+0xbb
> ad926cf8 827e3b5f 84b5e910 84b5e9c8 860e60e8 ndis!ndisSetPower+0x2c4
> ad926d20 81c50b6e 84b5e9c8 8531a928 00000000 ndis!ndisPowerDispatch+0x1a3
> ad926d7c 81e254e0 8a6f02b0 ad92d680 00000000 nt!PopIrpWorker+0x40f
> ad926dc0 81c9159e 81c5075b 8a6f02b0 00000000
> nt!PspSystemThreadStartup+0x9d
> 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
>
>
> STACK_COMMAND: kb
>
> FOLLOWUP_IP:
> NETw3v32+8e26
> 89a47e26 8b3c91 mov edi,dword ptr [ecx+edx*4]
>
> SYMBOL_STACK_INDEX: 2
>
> SYMBOL_NAME: NETw3v32+8e26
>
> FOLLOWUP_NAME: MachineOwner
>
> FAILURE_BUCKET_ID: 0x50_NETw3v32+8e26
>
> BUCKET_ID: 0x50_NETw3v32+8e26
>
> Followup: MachineOwner
> ---------
>
>
>
> Please help to solve my problem, thank you!
>
> Chris

Chris · Dec 25, 2007

Thanks! I have updated the driver for wireless adapter. How do you know my
problem is relate to the wireless adapter?

"Rick Rogers" wrote:

> Hi Chris,
>
> Download and install the most recent driver release for your wireless
> adapter. Even if it's the same version as you already have, overwrite it.
>
> --
> Best of Luck,
>
> Rick Rogers, aka "Nutcase" - Microsoft MVP
> http://mvp.support.microsoft.com/
> Windows help - www.rickrogers.org
> My thoughts http://rick-mvp.blogspot.com
>
> "Chris" <Chris@discussions.microsoft.com> wrote in message
> news:AF4A0EA0-DCFB-4129-860E-0738B1243EDE@microsoft.com...
> > Hi All,
> >
> > I have bought a notebook for a year. I am using Vista Home Basic. My
> > computer sometimes crash by BSOD recently. The following is the debug
> > log:-
> >
> >
> > Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
> > Copyright (c) Microsoft Corporation. All rights reserved.
> >
> >
> > Loading Dump File [D:\MEMORY.DMP]
> > Kernel Summary Dump File: Only kernel address space is available
> >
> > Symbol search path is:
> > SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
> >
> > Executable search path is:
> > Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
> > Product: WinNt, suite: TerminalServer SingleUserTS Personal
> > Built by: 6000.16575.x86fre.vista_gdr.071009-1548
> > Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
> > Debug session time: Mon Dec 24 20:04:04.913 2007 (GMT+8)
> > System Uptime: 0 days 1:56:01.670
> > Loading Kernel Symbols
> > ................................................................................................................................................................
> > Loading User Symbols
> >
> > Loading unloaded module list
> > ........
> > *******************************************************************************
> > *
> > *
> > * Bugcheck Analysis
> > *
> > *
> > *
> > *******************************************************************************
> >
> > Use !analyze -v to get detailed debugging information.
> >
> > BugCheck 50, {c258e758, 0, 89a47e26, 2}
> >
> > *** ERROR: Module load completed but symbols could not be loaded for
> > NETw3v32.sys
> >
> >
> >
> >
> > Probably caused by : NETw3v32.sys ( NETw3v32+8e26 )
> >
> > Followup: MachineOwner
> > ---------
> >
> >
> >
> >
> > 1: kd> !analyze -v
> > *******************************************************************************
> > *
> > *
> > * Bugcheck Analysis
> > *
> > *
> > *
> > *******************************************************************************
> >
> > PAGE_FAULT_IN_NONPAGED_AREA (50)
> > Invalid system memory was referenced. This cannot be protected by
> > try-except,
> > it must be protected by a Probe. Typically the address is just plain bad
> > or
> > it
> > is pointing at freed memory.
> > Arguments:
> > Arg1: c258e758, memory referenced.
> > Arg2: 00000000, value 0 = read operation, 1 = write operation.
> > Arg3: 89a47e26, If non-zero, the instruction address which referenced the
> > bad memory
> > address.
> > Arg4: 00000002, (reserved)
> >
> > Debugging Details:
> > ------------------
> >
> >
> >
> >
> >
> >
> > READ_ADDRESS: c258e758
> >
> > FAULTING_IP:
> > NETw3v32+8e26
> > 89a47e26 8b3c91 mov edi,dword ptr [ecx+edx*4]
> >
> > MM_INTERNAL_CODE: 2
> >
> > IMAGE_NAME: NETw3v32.sys
> >
> > DEBUG_FLR_IMAGE_TIMESTAMP: 45463982
> >
> > MODULE_NAME: NETw3v32
> >
> > FAULTING_MODULE: 89a3f000 NETw3v32
> >
> > DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
> >
> > BUGCHECK_STR: 0x50
> >
> > PROCESS_NAME: System
> >
> > CURRENT_IRQL: 0
> >
> > TRAP_FRAME: ad92638c -- (.trap 0xffffffffad92638c)
> > ErrCode = 00000000
> > eax=86201058 ebx=84f41fa8 ecx=8a147b58 edx=8e111b00 esi=84af2538
> > edi=84f41fd0
> > eip=89a47e26 esp=ad926400 ebp=ad926414 iopl=0 nv up ei pl nz ac po
> > nc
> > cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
> > efl=00010212
> > NETw3v32+0x8e26:
> > 89a47e26 8b3c91 mov edi,dword ptr [ecx+edx*4]
> > ds:0023:c258e758=????????
> > Resetting default scope
> >
> > LAST_CONTROL_TRANSFER: from 81c8fbb4 to 81ca9ef2
> >
> > STACK_TEXT:
> > ad926374 81c8fbb4 00000000 c258e758 00000000 nt!MmAccessFault+0x106
> > ad926374 89a47e26 00000000 c258e758 00000000 nt!KiTrap0E+0xdc
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > ad926414 89a48061 86201058 863df5a0 ad926440 NETw3v32+0x8e26
> > ad926424 89a47c77 84af2538 84f41fd0 862380b0 NETw3v32+0x9061
> > ad926440 89a55757 863df5a0 000000fa 00000001 NETw3v32+0x8c77
> > ad926468 89a47e46 862380b0 a635cb60 84f92fb0 NETw3v32+0x16757
> > ad926490 89a48061 86201058 863df5a0 ad9264bc NETw3v32+0x8e46
> > ad9264a0 89a47c77 a635cb60 84f92fb0 863df5a0 NETw3v32+0x9061
> > ad9264bc 89a547b2 863df5a0 0000000a 00000001 NETw3v32+0x8c77
> > ad926504 89aa8c87 863df5a0 ff000001 ad92654c NETw3v32+0x157b2
> > ad926524 89aa9985 861caa38 ff000001 ad92654c NETw3v32+0x69c87
> > ad926550 89aab769 84b80490 863499a4 84b80490 NETw3v32+0x6a985
> > ad9266f8 89a47e46 8635e8e8 84b80490 84ec7fb0 NETw3v32+0x6c769
> > ad926720 89a48061 8604aee0 861caa38 ad92674c NETw3v32+0x8e46
> > ad926730 89a47c77 84b80490 84ec7fb0 861ee300 NETw3v32+0x9061
> > ad92674c 89aa927b 861caa38 0000001b 00000001 NETw3v32+0x8c77
> > ad926798 89b15743 861ee300 ad926828 fd010101 NETw3v32+0x6a27b
> > ad926804 89b1a93d ad926828 89becd70 89be7e80 NETw3v32+0xd6743
> > ad926848 827b6397 861ee300 90df8c7c 860e6518 NETw3v32+0xdb93d
> > ad926890 826ff0d2 000e60e8 a1bc5730 c0000001 ndis!ndisMDoOidRequest+0x323
> > ad9268bc 826febc3 00000000 90df8c7c 90dfebc8
> > ndis!ndisFQueueRequestOnNext+0x22e
> > ad926924 a46777da a1bc5730 90df8c7c 90df8c78 ndis!NdisFOidRequest+0x139
> > ad926940 a4677b1c ad926960 90dfec68 90dfec68 nwifi!Dot11Request+0xee
> > ad926964 a4673c63 90df8008 00000000 fd010101
> > nwifi!Dot11ForwardRequest+0x44
> > ad9269e8 a4678c67 90df8008 fd010101 ad926cb8 nwifi!MPSetInformation+0x1e3
> > ad926a14 a467c439 90df8008 8a1ad0c0 ad926a84 nwifi!MP6Request+0xed
> > ad926a24 827b693e 90dfebc0 8a1ad0c0 a1bc5988 nwifi!FilterRequest+0x13
> > ad926a84 826ff062 00bc5730 8a773990 c0000001 ndis!ndisFDoOidRequest+0x199
> > ad926ab0 826febc3 00000000 8a1ad0c0 8a1ad140
> > ndis!ndisFQueueRequestOnNext+0x1be
> > ad926b18 8ae252c4 8a773990 8a1ad0c0 81fa4d90 ndis!NdisFOidRequest+0x139
> > ad926b38 827b693e 8a773190 ad926c1c 8a773990 pacer!PcFilterRequest+0x80
> > ad926b98 826fe3cb 00773990 00001388 ad926c1c ndis!ndisFDoOidRequest+0x199
> > ad926bd0 827cb6bc 860e60e8 ad926c1c 00000000
> > ndis!ndisQueueRequestOnTop+0x24e
> > ad926bf0 827e1b1f 00000000 00000000 00926c1c
> > ndis!ndisQuerySetMiniport+0x166
> > ad926cac 827e341e 860e60e8 00000004 fd010101
> > ndis!ndisQuerySetMiniportDeviceState+0xbb
> > ad926cf8 827e3b5f 84b5e910 84b5e9c8 860e60e8 ndis!ndisSetPower+0x2c4
> > ad926d20 81c50b6e 84b5e9c8 8531a928 00000000 ndis!ndisPowerDispatch+0x1a3
> > ad926d7c 81e254e0 8a6f02b0 ad92d680 00000000 nt!PopIrpWorker+0x40f
> > ad926dc0 81c9159e 81c5075b 8a6f02b0 00000000
> > nt!PspSystemThreadStartup+0x9d
> > 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
> >
> >
> > STACK_COMMAND: kb
> >
> > FOLLOWUP_IP:
> > NETw3v32+8e26
> > 89a47e26 8b3c91 mov edi,dword ptr [ecx+edx*4]
> >
> > SYMBOL_STACK_INDEX: 2
> >
> > SYMBOL_NAME: NETw3v32+8e26
> >
> > FOLLOWUP_NAME: MachineOwner
> >
> > FAILURE_BUCKET_ID: 0x50_NETw3v32+8e26
> >
> > BUCKET_ID: 0x50_NETw3v32+8e26
> >
> > Followup: MachineOwner
> > ---------
> >
> >
> >
> > Please help to solve my problem, thank you!
> >
> > Chris
>
>

Rick Rogers · Dec 25, 2007

Hi,

The report you gave specifies that the loaded module at the time is
netw3v32.sys, a file that supports your wireless adapter, and the error code
is 0x50, a driver file error. Most likely there is a problem with that file
and it needs to be updated or replaced. There is a small outside chance that
the actual problem emanates from interference from other software, but it's
unlikely as the details are pretty much restricted to lines of code within
that file.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"Chris" <Chris@discussions.microsoft.com> wrote in message
news:917A6505-3B09-4102-86F7-0E702ECA5701@microsoft.com...
> Thanks! I have updated the driver for wireless adapter. How do you know my
> problem is relate to the wireless adapter?
>
> "Rick Rogers" wrote:
>
>> Hi Chris,
>>
>> Download and install the most recent driver release for your wireless
>> adapter. Even if it's the same version as you already have, overwrite it.
>>
>> -- v
>> Best of Luck,
>>
>> Rick Rogers, aka "Nutcase" - Microsoft MVP
>> http://mvp.support.microsoft.com/
>> Windows help - www.rickrogers.org
>> My thoughts http://rick-mvp.blogspot.com
>>
>> "Chris" <Chris@discussions.microsoft.com> wrote in message
>> news:AF4A0EA0-DCFB-4129-860E-0738B1243EDE@microsoft.com...
>> > Hi All,
>> >
>> > I have bought a notebook for a year. I am using Vista Home Basic. My
>> > computer sometimes crash by BSOD recently. The following is the debug
>> > log:-
>> >
>> >

<snip log>

>> > ---------
>> >
>> >
>> >
>> > Please help to solve my problem, thank you!
>> >
>> > Chris
>>
>>

Chris · Dec 25, 2007

Oh.yes. netw3v32.sys is the driver name for my wireless adapter. However, I
cannot find a more update version of it. I just overwrote it with the same
version. Let's see the blue screen problem has been fixed or not. Thank you
very much!

Chris

"Rick Rogers" wrote:

> Hi,
>
> The report you gave specifies that the loaded module at the time is
> netw3v32.sys, a file that supports your wireless adapter, and the error code
> is 0x50, a driver file error. Most likely there is a problem with that file
> and it needs to be updated or replaced. There is a small outside chance that
> the actual problem emanates from interference from other software, but it's
> unlikely as the details are pretty much restricted to lines of code within
> that file.
>
> --
> Best of Luck,
>
> Rick Rogers, aka "Nutcase" - Microsoft MVP
> http://mvp.support.microsoft.com/
> Windows help - www.rickrogers.org
> My thoughts http://rick-mvp.blogspot.com
>
> "Chris" <Chris@discussions.microsoft.com> wrote in message
> news:917A6505-3B09-4102-86F7-0E702ECA5701@microsoft.com...
> > Thanks! I have updated the driver for wireless adapter. How do you know my
> > problem is relate to the wireless adapter?
> >
> > "Rick Rogers" wrote:
> >
> >> Hi Chris,
> >>
> >> Download and install the most recent driver release for your wireless
> >> adapter. Even if it's the same version as you already have, overwrite it.
> >>
> >> -- v
> >> Best of Luck,
> >>
> >> Rick Rogers, aka "Nutcase" - Microsoft MVP
> >> http://mvp.support.microsoft.com/
> >> Windows help - www.rickrogers.org
> >> My thoughts http://rick-mvp.blogspot.com
> >>
> >> "Chris" <Chris@discussions.microsoft.com> wrote in message
> >> news:AF4A0EA0-DCFB-4129-860E-0738B1243EDE@microsoft.com...
> >> > Hi All,
> >> >
> >> > I have bought a notebook for a year. I am using Vista Home Basic. My
> >> > computer sometimes crash by BSOD recently. The following is the debug
> >> > log:-
> >> >
> >> >
>
> <snip log>
>
> >> > ---------
> >> >
> >> >
> >> >
> >> > Please help to solve my problem, thank you!
> >> >
> >> > Chris
> >>
> >>
>
>