3
Contributors
8
Replies
9
Views
9 Years
Discussion Span
Last Post by mperu99
0

this is the content of you debug file ,

w22n51.sys file used by/for:

Product name: Intel® Wireless LAN Adapter
Description: Intel® Wireless LAN Driver
Company: Intel® Corporation

\====================
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Jack\Desktop\mini111708-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbolssp3
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Mon Nov 17 08:09:02.005 2008 (GMT-4)
System Uptime: 0 days 0:36:13.563
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
......................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
Unable to load image w22n51.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for w22n51.sys
*** ERROR: Module load completed but symbols could not be loaded for w22n51.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {ff1501f0, 2, 0, 804d9b64}

Probably caused by : w22n51.sys ( w22n51+6a112 )

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

0

after read through some forums, they suggested install a new driver.
here is the link of someone happened to be in the same situation as I am.
here intel driver
thanks caperjack.. i hope no more bsod

0

after read through some forums, they suggested install a new driver.
here is the link of someone happened to be in the same situation as I am.
here intel driver
thanks caperjack.. i hope no more bsod

your welcome ,hope all goes well

0

Can someone analyze my minidump if i send it to you????


thanks.

i will have a look ,no guarantees ,but you have to attach it here ,i don't give out my email address

0

I have to admit im new to this debug shit and reall have no answer for you ,but here is the content on the file you linked .maybe someone else know what it all means .
=============================
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: ba4fcf93, The address that the exception occurred at
Arg3: f76e6a2c, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
ks!DispatchDeviceIoControl+26
ba4fcf93 ff10 call dword ptr [eax]

TRAP_FRAME: f76e6a2c -- (.trap 0xfffffffff76e6a2c)
ErrCode = 00000000
eax=0a06000b ebx=89f969f0 ecx=89472590 edx=89472590 esi=8a0cfa60 edi=8a0afb80
eip=ba4fcf93 esp=f76e6aa0 ebp=f76e6aa8 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
ks!DispatchDeviceIoControl+0x26:
ba4fcf93 ff10 call dword ptr [eax] ds:0023:0a06000b=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: winlogon.exe

LAST_CONTROL_TRANSFER: from 804e13c9 to ba4fcf93

STACK_TEXT:
f76e6aa8 804e13c9 89f969f0 89472590 89472590 ks!DispatchDeviceIoControl+0x26
f76e6aa8 ffffffff 89f969f0 89472590 89472590 nt!KiTrap0D+0x483
WARNING: Frame IP not in any known module. Following frames may be wrong.
f76e6b54 f76e6b7c a650531e 0000006e 8a0afb80 0xffffffff
f76e6b58 a650531e 0000006e 8a0afb80 00000016 0xf76e6b7c
f76e6b7c a6505417 8a1aa110 8a0afb80 00000016 wdmaud!GetControlNodes+0x2a
f76e6bb0 a6505813 00000000 00000016 00000001 wdmaud!OpenSysAudioPin+0xe5
f76e6bec a6504a83 00000092 00000016 89f1f1f0 wdmaud!OpenWavePin+0x3e2
f76e6c18 a6504382 895232c8 89f1f1f0 00000000 wdmaud!Dispatch_OpenPin+0xb7
f76e6c40 804e13c9 00000010 89d37000 80701410 wdmaud!SoundDispatch+0x430
f76e6c40 89f935e8 00000010 89d37000 80701410 nt!KiTrap0D+0x483
f76e6cd4 00000000 89f26348 8a5c02e8 f76e6d48 0x89f935e8


STACK_COMMAND: kb

FOLLOWUP_IP:
ks!DispatchDeviceIoControl+26
ba4fcf93 ff10 call dword ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ks!DispatchDeviceIoControl+26

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ks

IMAGE_NAME: ks.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48025c12

FAILURE_BUCKET_ID: 0x8E_ks!DispatchDeviceIoControl+26

BUCKET_ID: 0x8E_ks!DispatchDeviceIoControl+26

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

0

I have to admit im new to this debug shit and reall have no answer for you ,but here is the content on the file you linked .maybe someone else know what it all means .
=============================
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: ba4fcf93, The address that the exception occurred at
Arg3: f76e6a2c, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
ks!DispatchDeviceIoControl+26
ba4fcf93 ff10 call dword ptr [eax]

TRAP_FRAME: f76e6a2c -- (.trap 0xfffffffff76e6a2c)
ErrCode = 00000000
eax=0a06000b ebx=89f969f0 ecx=89472590 edx=89472590 esi=8a0cfa60 edi=8a0afb80
eip=ba4fcf93 esp=f76e6aa0 ebp=f76e6aa8 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
ks!DispatchDeviceIoControl+0x26:
ba4fcf93 ff10 call dword ptr [eax] ds:0023:0a06000b=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: winlogon.exe

LAST_CONTROL_TRANSFER: from 804e13c9 to ba4fcf93

STACK_TEXT:
f76e6aa8 804e13c9 89f969f0 89472590 89472590 ks!DispatchDeviceIoControl+0x26
f76e6aa8 ffffffff 89f969f0 89472590 89472590 nt!KiTrap0D+0x483
WARNING: Frame IP not in any known module. Following frames may be wrong.
f76e6b54 f76e6b7c a650531e 0000006e 8a0afb80 0xffffffff
f76e6b58 a650531e 0000006e 8a0afb80 00000016 0xf76e6b7c
f76e6b7c a6505417 8a1aa110 8a0afb80 00000016 wdmaud!GetControlNodes+0x2a
f76e6bb0 a6505813 00000000 00000016 00000001 wdmaud!OpenSysAudioPin+0xe5
f76e6bec a6504a83 00000092 00000016 89f1f1f0 wdmaud!OpenWavePin+0x3e2
f76e6c18 a6504382 895232c8 89f1f1f0 00000000 wdmaud!Dispatch_OpenPin+0xb7
f76e6c40 804e13c9 00000010 89d37000 80701410 wdmaud!SoundDispatch+0x430
f76e6c40 89f935e8 00000010 89d37000 80701410 nt!KiTrap0D+0x483
f76e6cd4 00000000 89f26348 8a5c02e8 f76e6d48 0x89f935e8


STACK_COMMAND: kb

FOLLOWUP_IP:
ks!DispatchDeviceIoControl+26
ba4fcf93 ff10 call dword ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ks!DispatchDeviceIoControl+26

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ks

IMAGE_NAME: ks.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48025c12

FAILURE_BUCKET_ID: 0x8E_ks!DispatchDeviceIoControl+26

BUCKET_ID: 0x8E_ks!DispatchDeviceIoControl+26

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

Well its a start... and i thank you for getting it this far.. maybe someone can understand it better than both you and I and we can all learn from it

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.