PC rebooting randomly

[Guest]

I PC keeps on rebooting randomly giving error
stop : 0x00000044 (0x891db200, 0x00000d62, 0x00000000,0x00000000)
Multiple_IRP_Complete_Requests

System details:

P4 2.4Ghz
2GB RAM
2 Dlink Nic cards
WinXP SP2 all latest patches

The computer has rebooted from a bugcheck. The bugcheck was:

0x00000044 (0x891db200, 0x00000d62, 0x00000000, 0x00000000). A dump was

saved in: D:\WINDOWS\MEMORY.DMP.

The computer has rebooted from a bugcheck. The bugcheck was:

0x100000d1 (0x00000000, 0x00000002, 0x00000001, 0xb2156f67). A dump was

saved in: D:\WINDOWS\Minidump\Mini061706-03.dmp.

The computer has rebooted from a bugcheck. The bugcheck was:

0x00000044 (0x8975d210, 0x00000d62, 0x00000000, 0x00000000). A dump was

saved in: D:\WINDOWS\Minidump\Mini061806-01.dmp.

D:\Program Files\Support Tools>dumpchk.exe

D:\WINDOWS\Minidump\Mini061806-01.dmp

Loading dump file D:\WINDOWS\Minidump\Mini061806-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00039000
PfnDataBase 81403000
PsLoadedModuleList 80883420
PsActiveProcessHead 808894d8
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 00000044
BugCheckParameter1 8975d210
BugCheckParameter2 00000d62
BugCheckParameter3 00000000
BugCheckParameter4 00000000
PaeEnabled 00000000
KdDebuggerDataBlock 80875060
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 000004ec
DriverListOffset 00003100
DriverCount 00000077
StringPoolOffset 00005458
StringPoolSize 00001058
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack 80878f94
DebuggerDataOffset 00002e70
DebuggerDataSize 00000290
DataBlocksOffset 000064b0
DataBlocksCount 00000004


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x80800000 PsLoadedModuleList = 0x80883420
Debug session time: Sun Jun 18 09:12:18 2006
System Uptime: 0 days 2:28:23
start end module name
80800000 80a14100 nt Checksum: 002198AF Timestamp: Wed

Mar 02 06:
29:37 2005 (42250FF9)

Unloaded modules:
b135e000 b1388000 kmixer.sys Timestamp: unavailable (00000000)
b143c000 b1466000 kmixer.sys Timestamp: unavailable (00000000)
f7527000 f7533000 DLKRTS.SYS Timestamp: unavailable (00000000)
b1cc1000 b1ceb000 kmixer.sys Timestamp: unavailable (00000000)
ba848000 ba849000 drmkaud.sys Timestamp: unavailable (00000000)
f76d7000 f76e4000 DMusic.sys Timestamp: unavailable (00000000)
b1ceb000 b1d0e000 aec.sys Timestamp: unavailable (00000000)
b1e3b000 b1e49000 swmidi.sys Timestamp: unavailable (00000000)
f79a7000 f79a9000 splitter.sys Timestamp: unavailable (00000000)
f77df000 f77e4000 Cdaudio.SYS Timestamp: unavailable (00000000)
f791f000 f7922000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

D:\Program Files\Support Tools>



The computer has rebooted from a bugcheck. The bugcheck was:

0x100000d1 (0x139b310b, 0x00000002, 0x00000001, 0x89ec3008). A dump was

saved in: D:\WINDOWS\Minidump\Mini061806-02.dmp.

D:\Program Files\Support Tools>dumpchk.exe

D:\WINDOWS\Minidump\Mini061806-02.dmp

Loading dump file D:\WINDOWS\Minidump\Mini061806-02.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 00039000
PfnDataBase 81403000
PsLoadedModuleList 80883420
PsActiveProcessHead 808894d8
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 100000d1
BugCheckParameter1 139b310b
BugCheckParameter2 00000002
BugCheckParameter3 00000001
BugCheckParameter4 89ec3008
PaeEnabled 00000000
KdDebuggerDataBlock 80875060
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 0000047c
DriverListOffset 00003090
DriverCount 00000076
StringPoolOffset 00005398
StringPoolSize 00001030
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack 80879004
DebuggerDataOffset 00002e00
DebuggerDataSize 00000290
DataBlocksOffset 000063c8
DataBlocksCount 00000003


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x80800000 PsLoadedModuleList = 0x80883420
Debug session time: Sun Jun 18 10:38:56 2006
System Uptime: 0 days 1:26:26
start end module name
80800000 80a14100 nt Checksum: 002198AF Timestamp: Wed

Mar 02 06:
29:37 2005 (42250FF9)

Unloaded modules:
b1564000 b158e000 kmixer.sys Timestamp: unavailable (00000000)
b1642000 b166c000 kmixer.sys Timestamp: unavailable (00000000)
b1b04000 b1b2e000 kmixer.sys Timestamp: unavailable (00000000)
f7abc000 f7abd000 drmkaud.sys Timestamp: unavailable (00000000)
b1bce000 b1bf1000 aec.sys Timestamp: unavailable (00000000)
b1f0e000 b1f1b000 DMusic.sys Timestamp: unavailable (00000000)
f76f7000 f7705000 swmidi.sys Timestamp: unavailable (00000000)
f799b000 f799d000 splitter.sys Timestamp: unavailable (00000000)
f77cf000 f77d4000 Cdaudio.SYS Timestamp: unavailable (00000000)
ba362000 ba365000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

D:\Program Files\Support Tools>

 

[Kerry Brown]

I PC keeps on rebooting randomly giving error
stop : 0x00000044 (0x891db200, 0x00000d62, 0x00000000,0x00000000)
Multiple_IRP_Complete_Requests

<snipped>

Both errors are usually the result of a problem with a driver. Have you
recently installed any new hardware or updated any drivers? Are you
overclocking the pc? Troubleshooting stop errors can be a tedious process.
Here is a starting point.

http://aumha.org/win5/kbestop.php

It is mostly a matter of elimination and quite often the problem turns out
to be a symptom of something else like bad ram, weak psu etc.

 

[Ron Martell]

The computer has rebooted from a bugcheck. The bugcheck was:

0x00000044 (0x8975d210, 0x00000d62, 0x00000000, 0x00000000). A dump was

The name for this error code is MULTIPLE_IRP_COMPLETE_REQUESTS and the
definition says

"This indicates that a driver has tried to requested an IRP be
completed that is already complete.
<snip>
This is a tough bug to find because the simplest case — a driver that
attempted to complete its own packet twice — is usually not the source
of the problem. More likely, two separate drivers each believe that
they own the packet, and each has attempted to complete it. The first
request succeeds, and the second fails, resulting in this bug check."


One of the drivers involved in this error is using memory address
0x8975d210 so it may be possible to track it further from that address
using the PSTAT utility.

However at this point I would suspect that the cause is likely
associated with the two D-Link network cards. If possible try
removing one of these cards, or at least replacing it with one from a
different manufacturer. That reduces the possibility of any sort of
electronic confusion between the two cards.

The computer has rebooted from a bugcheck. The bugcheck was:

0x100000d1 (0x139b310b, 0x00000002, 0x00000001, 0x89ec3008). A dump was

That error is called DRIVER_IRQL_NOT_LESS_OR_EQUAL

"A driver tried to access an address that is pageable (or that is
completely invalid) while the IRQL was too high.

This bug check is usually caused by drivers that have used improper
addresses."


In this instance the error originated with whatever device driver is
loaded at address 0x89ec3008 and it was trying to write to address
0x139b310b. Again PSTAT could help to trace this error further but I
think that we should wait until after you have tried removing/changing
one of the network cards as suggested above.

Good luck



Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."