Re: MEMORY_MANAGEMENT (1a) problem
- From: "Alexander Grigoriev" <alegr@xxxxxxxxxxxxx>
- Date: Tue, 3 Jun 2008 06:36:10 -0700
What does your driver does in general?
"?????" <ZivHuang@xxxxxxxxx> wrote in message
news:d32d98b7-9838-4519-9a13-880912d53150@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi all,
I encountered a problem when I tested power management functionality
about my driver.
I got a crash dump, but I don't know how to figure the problem out.
_<
The dump message is below.
How to analyze such kind of prolem and find the root cause?
Thanks. ^_^
.........................................................................................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for
details
Loading unloaded module list
..................................................
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {8886, 846704dc, 845021f8, 107}
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for
details
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for
details
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromList+59 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00008886, The subtype of the bugcheck.
Arg2: 846704dc
Arg3: 845021f8
Arg4: 00000107
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for
details
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for
details
BUGCHECK_STR: 0x1a_8886
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 818ac539 to 818e5163
STACK_TEXT:
ad86e788 818ac539 0000001a 00008886 846704dc nt!KeBugCheckEx+0x1e
ad86e7a8 81838e9f 883a56f0 8e3ed000 547c0000 nt!MiUnlinkPageFromList
+0x59
ad86e7fc 819f078b 92edd008 c0566ac8 00000002 nt!MiValidateImagePages
+0x3ae
ad86e828 819f9691 92edd008 c0566ac8 884e1828 nt!MiSwitchBaseAddress
+0x4c
ad86e84c 81a5d0c6 92edd008 00000000 00000000 nt!MiRelocateImageAgain
+0xd6
ad86e960 81a611d8 ad86e9b4 0000000d ad86ea08 nt!MmCreateSection+0x51d
ad86e9d4 819b6dcc ad86ea64 0000000d ad86ea08 nt!NtCreateSection+0x177
ad86ea50 81aa49c4 ad86eaec aa458448 00000001 nt!PfpFileBuildReadSupport
+0xe4
ad86eaa8 819b732a ad86eaec 00000001 ad86ebe4 nt!PfpPrefetchFiles+0x18e
ad86eb00 819b754c aa450000 483df50f ad86ebf8 nt!
PfpPrefetchRequestPerform+0x310
ad86eb54 819f63b6 ad86ebe4 81910901 483df243 nt!PfpPrefetchRequest
+0x16e
ad86ec18 81a0fbf7 01e5f744 00000014 81910901 nt!
PfSetSuperfetchInformation+0x182
ad86ed50 8186fa7a 0000004f 00000000 00000014 nt!NtSetSystemInformation
+0x908
ad86ed50 77029a94 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be
wrong.
01e5f75c 00000000 00000000 00000000 00000000 0x77029a94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiUnlinkPageFromList+59
818ac539 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiUnlinkPageFromList+59
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x1a_8886_VRF_nt!MiUnlinkPageFromList+59
BUCKET_ID: 0x1a_8886_VRF_nt!MiUnlinkPageFromList+59
Followup: MachineOwner
---------
.
- References:
- MEMORY_MANAGEMENT (1a) problem
- From: 泛若不繫舟
- MEMORY_MANAGEMENT (1a) problem
- Prev by Date: Re: Can 1394b S800 be supported by windows xp sp3?
- Next by Date: Re: Packet alignment constraint in WinUSB
- Previous by thread: MEMORY_MANAGEMENT (1a) problem
- Next by thread: Diff between VS2005 compiler and DDK
- Index(es):
Relevant Pages
|
