Computer Freezing / Crashing (BSOD) (ntkrnlmp.exe) (MULTIPLE_IRP_COMPLETE_REQUESTS)

Nov 11, 2018
1
0
10
0
My computer keeps crashing due to unknown reasons. I have done a bit of research and tried a few solutions but to no avail. A minidump of one the crashes is here below. I'd be happy to answer any questions to help my situation.

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.24260.amd64fre.win7sp1_ldr.180908-0600
Machine Name:
Kernel base = 0xfffff800`03a4a000 PsLoadedModuleList = 0xfffff800`03c84c90
Debug session time: Sun Nov 11 16:05:25.967 2018 (UTC - 5:00)
System Uptime: 0 days 0:00:11.779
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: fffffa800e654af0, Address of the IRP
Arg2: 0000000000000346
Arg3: 0000000000000000
Arg4: 0000000000000000

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

IRP_ADDRESS: fffffa800e654af0

FOLLOWUP_IP:
nt!IovCompleteRequest+de
fffff800`03f59e3e cc int 3

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: 0x44

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80003f59e3e to fffff80003add9a0

STACK_TEXT:
fffff880`03986aa8 fffff800`03f59e3e : 00000000`00000044 fffffa80`0e654af0 00000000`00000346 00000000`00000000 : nt!KeBugCheckEx
fffff880`03986ab0 fffff800`03f5f440 : fffffa80`08380b02 fffffa80`08380ba0 fffffa80`08380ba0 fffffa80`0e654af0 : nt!IovCompleteRequest+0xde
fffff880`03986b80 fffff800`03f5f4ac : fffff800`03c65100 00000000`00000080 00000000`00000001 00000000`00000000 : nt!ViPendingCompleteAfterWait+0x90
fffff880`03986bc0 fffff800`03d8cd10 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ViPendingWorkerThread+0x2c
fffff880`03986c00 fffff800`03ae39a6 : fffff880`03440180 fffffa80`06742b50 fffff880`0344f240 00000000`00000000 : nt!PspSystemThreadStartup+0x194
fffff880`03986c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!IovCompleteRequest+de

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5b94669f

FAILURE_BUCKET_ID: X64_0x44_VRF_nt!IovCompleteRequest+de

BUCKET_ID: X64_0x44_VRF_nt!IovCompleteRequest+de

Followup: MachineOwner
 
you would have to provide the actual memory dump file so it can be looked at with a windows debugger. ie to dump the list of drivers. some times there will be two drivers for the same device running from different directories. There are some old drivers that also process packets that they do not own.

you can download and run autoruns and hide the microsoft entries and see what is loaded. at least you can see the driver names and dates and uncheck ones that might be suspect.
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns


some old Logitech usb drivers from 2009 would not pass on usb packets to their intended driver.

generally, if you can not figure out the problem you just update the motherboard bios, and the motherboard drivers from the motherboard vendors website. then go to device vendors websites and update their drivers.

since you have a debugger you can dump the driver list with this command
lmiftsm






 

ASK THE COMMUNITY

TRENDING THREADS