Interpreting Dump File

[SSAndre]

One of my users is getting a reboot shortly after logging in. I have scanned for viruses and found nothing. Here are the results from one of the dump files. I have done some searching for some of the Bugcheck codes and have been unsuccessful. My question is does anyone know of a good place to look for solutions to these problems? Or does anyone know how to interpret this particular output?

Any input would be appreciated. Thanks.

U:\>dumpchk -v C:\windows\minidump\mini090704-01.dmp
Loading dump file C:\windows\minidump\mini090704-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000893
DirectoryTableBase 00030000
PfnDataBase 85e66000
PsLoadedModuleList 8046e8f0
PsActiveProcessHead 8046e728
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 00000044
BugCheckParameter1 854fc948
BugCheckParameter2 00000cca
BugCheckParameter3 00000000
BugCheckParameter4 00000000
PaeEnabled 00000000
KdDebuggerDataBlock 8046fad8
MiniDumpFields 45474150

TRIAGE_DUMP32:
ServicePackBuild 00000400
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001050
UnloadedDriversOffset 00001088
PrcbOffset 00001860
ProcessOffset 00002250
ThreadOffset 000024e0
CallStackOffset 00002728
SizeOfCallStack 00000398
DriverListOffset 00002ac0
DriverCount 0000006e
StringPoolOffset 00004b68
StringPoolSize 00002068
BrokenDriverOffset 00000000
TriageOptions 00000045
TopOfStack 80473ea8


Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e8f0
Debug session time: Tue Sep 07 09:48:10 2004
System Uptime: not available
start end module name
80400000 805a5540 nt Checksum: 001A56A3 Timestamp: Thu Mar 04 19:
44:35 2004 (4047DB83)

Unloaded modules:
b6cfc000 b6d11000 VGA.dll Timestamp: unavailable (00000000)
b6cfc000 b6d11000 VGA.dll Timestamp: unavailable (00000000)
eb230000 eb23d000 DMusic.sys Timestamp: unavailable (00000000)
eb200000 eb20e000 swmidi.sys Timestamp: unavailable (00000000)
eb512000 eb514000 CVirtA.sys Timestamp: unavailable (00000000)
b7768000 b776c000 hidusb.sys Timestamp: unavailable (00000000)
b790d000 b7922000 VGA.dll Timestamp: unavailable (00000000)
eb180000 eb18e000 ialmrnt5.dll Timestamp: unavailable (00000000)
eb130000 eb139000 redbook.sys Timestamp: unavailable (00000000)
eb3e0000 eb3e5000 Cdaudio.SYS Timestamp: unavailable (00000000)
eb4bc000 eb4bf000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

 

[wolluf]

I'd give up trying to interpret the dump file - look at possible causes (hardware/software changes to machine, history of problems etc)

 

[fumei]

Forget the dump file. Even Microsoft seems to ignore them. There is probably only a handful of people anyway that can truly read them.

There are so many possible reasons for the behaviour. You are going to have to do a process of elimination, checking for hardware and software..

Just as a point of possible interest...I had a machine that did a reboot erratically. Drove me nuts. It turned out that the power line, the actual main line into the building, wavered, just a tiny bit. Being AC 'n all. But the amount was just a hair under the tolerance of the motherboard. So when the power on the line dropped just that hair below, the system detected it and did a reboot. Took me months to find that one.

Good luck.

Gerry

 

[SSAndre]

It is most likely some sort of odd situation, he is a remote user and when he brings his machine on-site we do not see this happening. So it is pointing to something at his home. I will try some troubleshooting on some of his hardware. Thanks for the input.