MiniDump

MiniDump

Postby mllenas » Mon Oct 09, 2006 1:51 pm

Hi there, here is a minidump of my system which has been giving me BSOD since I formatted and reinstalled XP Pro SP2.

I'm assuming that the offending driver is zd1201u.sys (ZyAir B220 USB WiFi Adapter), but I'm confused as why there is another whole list of drivers after "Unable to load image zd1201u.sys, Win32 error 2"

Any ideas will be appreciated :D

------------------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini100906-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Mon Oct 9 14:28:45.584 2006 (GMT+2)
System Uptime: 0 days 1:42:45.166
Loading Kernel Symbols
...................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {4, 2, 1, 804ed24e}

Unable to load image zd1201u.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for zd1201u.sys
*** ERROR: Module load completed but symbols could not be loaded for zd1201u.sys
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*** WARNING: Unable to verify timestamp for ATMFD.DLL
*** ERROR: Module load completed but symbols could not be loaded for ATMFD.DLL
*** WARNING: Unable to verify timestamp for aswRdr.sys
*** ERROR: Module load completed but symbols could not be loaded for aswRdr.sys
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
*** WARNING: Unable to verify timestamp for Icam4USB.sys
*** ERROR: Module load completed but symbols could not be loaded for Icam4USB.sys
*** WARNING: Unable to verify timestamp for ALCXWDM.SYS
*** ERROR: Module load completed but symbols could not be loaded for ALCXWDM.SYS
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
*** WARNING: Unable to verify timestamp for timntr.sys
*** ERROR: Module load completed but symbols could not be loaded for timntr.sys
*** WARNING: Unable to verify timestamp for SISAGPX.sys
*** ERROR: Module load completed but symbols could not be loaded for SISAGPX.sys
*** WARNING: Unable to verify timestamp for aswTdi.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
*** WARNING: Unable to verify timestamp for drmk.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.sys
*** WARNING: Unable to verify timestamp for tifsfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for tifsfilt.sys
*** WARNING: Unable to verify timestamp for fdc.sys
*** ERROR: Module load completed but symbols could not be loaded for fdc.sys
*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
*** WARNING: Unable to verify timestamp for Aavmker4.SYS
*** ERROR: Module load completed but symbols could not be loaded for Aavmker4.SYS
*** WARNING: Unable to verify timestamp for mxopswd.sys
*** ERROR: Module load completed but symbols could not be loaded for mxopswd.sys
*** WARNING: Unable to verify timestamp for viaide.sys
*** ERROR: Module load completed but symbols could not be loaded for viaide.sys
*** WARNING: Unable to verify timestamp for PQNTDrv.SYS
*** ERROR: Module load completed but symbols could not be loaded for PQNTDrv.SYS
Probably caused by : zd1201u.sys ( zd1201u+6d0d )

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

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: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804ed24e, address which referenced memory

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


WRITE_ADDRESS: 00000004

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiActivateWaiterQueue+27
804ed24e 897004 mov dword ptr [eax+4],esi

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 804e87af to 804ed24e

STACK_TEXT:
f7961ca4 804e87af 804dc1a0 82c12248 00000000 nt!KiActivateWaiterQueue+0x27
f7961ccc f76f4d0d 00000000 00000000 00000000 nt!KeWaitForSingleObject+0x19a
WARNING: Stack unwind information not available. Following frames may be wrong.
f7961d1c f76f4dab 828ac000 82e3a370 0000f100 zd1201u+0x6d0d
f7961d44 f76f5c03 828ac000 00000011 00000001 zd1201u+0x6dab
f7961d64 f7356bfe 82c12674 828ac000 f7961dac zd1201u+0x7c03
f7961d74 804e426b 82c12674 00000000 82fc7b30 NDIS!ndisWorkItemHandler+0xe
f7961dac 8057be15 82c12674 00000000 00000000 nt!ExpWorkerThread+0x100
f7961ddc 804fa4da 804e4196 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
zd1201u+6d0d
f76f4d0d ?? ???

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: zd1201u

IMAGE_NAME: zd1201u.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3fcc52ed

SYMBOL_NAME: zd1201u+6d0d

FAILURE_BUCKET_ID: 0xA_W_zd1201u+6d0d

BUCKET_ID: 0xA_W_zd1201u+6d0d

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

------------------------------------------------------------------------------
mllenas
 
Posts: 1
Joined: Mon Oct 09, 2006 1:44 pm

Postby VDO » Mon Oct 09, 2006 6:05 pm

You are right, zd1201u.sys might have been responsible for crashing your system. Other drivers were listed because WinDbg.exe had tried to get symbol files for them from MS symbol store but they are not MS drivers.

If you want to see the date and other information about zd1201u.sys use the following command:

Code: Select all
kd>lmv m zd1201u


or

Code: Select all
kd>!lmi zd1201u


or from all drivers

Code: Select all
kd>lmv
VDO
Site Admin
 
Posts: 509
Joined: Mon May 01, 2006 10:34 am
Location: Dublin, Ireland

Postby kiran kumar s » Wed Nov 15, 2006 2:02 pm

The other drivres are not from the microsoft, and the winDbg tries to find the .pdb files for the other drivers, since they are third party drivers there will be no .pdb files avaliable, and these are the drivers that are loaded when the crash has happened and thats the reason, why windbg is showing a list of drivers for which the symbols are not found.
What makes a Man a Man is Not how he starts things ...
But how he decides to end them.
kiran kumar s
 
Posts: 1
Joined: Wed Nov 15, 2006 1:53 pm
Location: Bangalore,India


Return to Saving and collecting dumps

Who is online

Users browsing this forum: No registered users and 1 guest

cron