Minidump info

J

jim sturtz

i ran dumpchk on a recent minidump (see below for extract) and a pstat to
get a list of currently running drivers.

as i read the info from these i believe it is telling me the bootvid is the
culprit. can someone confirm that for me.

if so, why? i have been using the same driver since i installed winXP and
it operated perfectly for several weeks, then i started getting these dumps.
i have reinstalled the video driver several times, and even gone back to a
prior release trying to fix this.

thanks.

jim

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 13d1c000
PfnDataBase 80c51000
PsLoadedModuleList 8053f530
PsActiveProcessHead 80541578
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 000000d1
BugCheckParameter1 00000103
BugCheckParameter2 00000002
BugCheckParameter3 00000001
BugCheckParameter4 f8951efd
PaeEnabled 00000000
KdDebuggerDataBlock 805313e0
MiniDumpFields 00000dff


flpydisk.sys F88DE000 1920 1280 11392 Thu Aug 29 04:27:43 2002
vga.sys F88F6000 768 128 14848 Thu Aug 29 04:32:03 2002
Msfs.SYS F88FE000 896 128 11264 Fri Aug 17 16:50:02 2001
Npfs.SYS F8906000 1664 256 20352 Fri Aug 17 16:50:03 2001
Modem.SYS F891E000 1280 128 19968 Fri Aug 17 16:57:35 2001
TDTCP.SYS F8926000 15104 128 0 Fri Aug 17 16:46:43 2001
BOOTVID.dll F8946000 5632 3584 0 Fri Aug 17 16:49:09 2001
serenum.sys F89CE000 2688 128 7552 Fri Aug 17 16:50:13 2001
gameenum.sys F89D2000 1152 0 5120 Thu Aug 29 04:32:42 2002
ndistapi.sys F89D6000 5248 128 0 Fri Aug 17 16:55:29 2001
TDI.SYS F89DE000 9472 512 256 Fri Aug 17 16:57:25 2001
rasacd.sys F8A0A000 3840 128 512 Fri Aug 17 16:55:39 2001
KDCOM.DLL F8A36000 2560 256 1280 Fri Aug 17 16:49:10 2001
WMILIB.SYS F8A38000 512 0 1280 Fri Aug 17 17:07:23 2001
viaide.sys F8A3A000 2432 0 0 Thu Aug 29 04:27:48 2002
dmload.sys F8A3C000 2560 128 0 Fri Aug 17 16:58:15 2001
USBD.SYS F8AAE000 256 0 896 Fri Aug 17 17:02:58 2001
Fs_Rec.SYS F8AB2000 128 128 3584 Fri Aug 17 16:49:37 2001
Beep.SYS F8AB4000 1152 0 0 Fri Aug 17 16:47:33 2001
mnmdd.SYS F8AB6000 0 0 1792 Fri Aug 17 16:57:28 2001
RDPCDD.sys F8AB8000 0 0 1792 Fri Aug 17 16:46:56 2001
InCDrec.SYS F8ABA000 1664 128 0 Mon May 24 07:59:23 2004
ParVdm.SYS F8AF6000 1408 128 0 Fri Aug 17 16:49:49 2001
swenum.sys F8BA2000 384 0 640 Fri Aug 17 16:48:47 2001
Null.SYS F8BC1000 0 128 384 Fri Aug 17 16:47:39 2001
audstub.sys F8C40000 128 0 512 Fri Aug 17 16:59:40 2001
dxgthk.sys F8C68000 128 0 0 Fri Aug 17 16:53:12 2001
 
J

jim sturtz

just after posting this, while in excel, the system crashed again.

the message in the event viewere said
[[Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 7/12/2004
Time: 9:31:36 AM
User: N/A
Computer: SDSOFFICE
Description:
Error code 1000008e, parameter1 c0000005, parameter2 8051735d, parameter3
f32f99f8, parameter4 00000000]]

the dumpchk listing from it shows similar info the the parameter 4 which i
thot is supposed to point to the driver is 0, so it doesnt help.

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 03105000
PfnDataBase 80c51000
PsLoadedModuleList 8053f530
PsActiveProcessHead 80541578
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 1000008e
BugCheckParameter1 c0000005
BugCheckParameter2 8051735d
BugCheckParameter3 f32f99f8
BugCheckParameter4 00000000
PaeEnabled 00000000
KdDebuggerDataBlock 805313e0
MiniDumpFields 00000dff

when i read this minidump using windbg tho it is talking about a symantec
file i think, and something about a mis-alignment, whatever that is.

An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8051735d, The address that the exception occurred at
Arg3: f32f99f8, 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:
nt!RtlSetBit+d
8051735d 034204 add eax,[edx+0x4]

TRAP_FRAME: f32f99f8 -- (.trap fffffffff32f99f8)
ErrCode = 00000000
eax=0000042e ebx=00002165 ecx=00002173 edx=00000000 esi=8053f940
edi=0000000f
eip=8051735d esp=f32f9a6c ebp=f32f9aac iopl=0 nv up ei pl nz ac po
nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010216
nt!RtlSetBit+0xd:
8051735d 034204 add eax,[edx+0x4]
ds:0023:00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 8052f19f to 8051735d

STACK_TEXT:
f32f9a68 8052f19f 00000000 00002173 00000001 nt!RtlSetBit+0xd
f32f9aac 8053087b 00000001 e3165000 00000000 nt!MiAllocatePoolPages+0x99f
f32f9b14 f3701099 00000001 0000ed39 53646152 nt!ExAllocatePoolWithTag+0x109
WARNING: Stack unwind information not available. Following frames may be
wrong.
81a27a70 00000000 00000000 00000000 00000000 SAVRT+0x2f099


FOLLOWUP_IP:
SAVRT+2f099
f3701099 ?? ???

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: SAVRT+2f099

MODULE_NAME: SAVRT

IMAGE_NAME: SAVRT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 3d40d9c3

STACK_COMMAND: .trap fffffffff32f99f8 ; kb

BUCKET_ID: 0x8E_SAVRT+2f099

all ideas appreciated.

thanks.

jim
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top