Help With a .DMP File

[tom59593]

Hey guys,

As of yesterday, I've started getting a BSOD every few hours with the error 'MULTIPLE IRP COMPLTE REQUESTS.' After a whole bunch of searching (which eventually led me to this forum!) I learned that there are minidump files which might be able to help me figure out my problem.

The issue is that I'm not quite sure how to open the file type--I can't seem to locate DUMPCHK.exe on my computer anywhere, and the files won't open in notepad. I went ahead and uploaded the last few in case someone was able to help me read through them for any hints to solve the problem:

http://thomaswinchester.com/files/minidump/012914-20953-01.dmp
http://thomaswinchester.com/files/minidump/012914-26000-01.dmp
http://thomaswinchester.com/files/minidump/013014-16953-01.dmp
http://thomaswinchester.com/files/minidump/013014-17875-01.dmp

If anyone could help me look through these for any ideas, it would be greatly appreciated. Alternatively, I could probably use some help learning how to open these on my own--I Google'd it for a while and kept finding the DUMPCHK.exe reference but can't seem to find the program.

THANKS IN ADVANCE FOR ANY HELP!!!

-Tom-

 

[neieus]

You can download a program called "whocrashed" and it will allow you to read the dump files.

 

[tom59593]

You can download a program called "whocrashed" and it will allow you to read the dump files.

Thanks! I went ahead and downloaded the software and ran a report...here's the contents (in the spoiler so it's collapsible):

Spoiler

On Thu 1/30/2014 5:33:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\013014-17875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x44 (0xFFFFFA800CD509B0, 0xF7A, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 1/30/2014 5:33:03 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hamdrv.sys (Hamdrv+0x1F0A)
Bugcheck code: 0x44 (0xFFFFFA800CD509B0, 0xF7A, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\drivers\hamdrv.sys
product: LogMeIn Hamachi Virtual Network Adapter
company: LogMeIn Inc.
description: LogMeIn Hamachi Virtual Miniport Driver
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hamdrv.sys (LogMeIn Hamachi Virtual Miniport Driver, LogMeIn Inc.).
Google query: LogMeIn Inc. MULTIPLE_IRP_COMPLETE_REQUESTS



On Thu 1/30/2014 8:02:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\013014-16953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x44 (0xFFFFFA801074B850, 0xF7A, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 1/30/2014 7:44:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\013014-18937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x44 (0xFFFFFA800EFA7960, 0xF7A, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 1/29/2014 11:09:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012914-18000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x44 (0xFFFFFA80105766A0, 0xF7A, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 1/29/2014 10:07:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012914-20953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x44 (0xFFFFFA800D23E770, 0xF7A, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 1/29/2014 9:58:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012914-26000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x44 (0xFFFFFA80131566F0, 0xF7A, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

A common culprit from these reports is the ntoskrnl.exe, but a quick Google search indicates that this doesn't seem like a likely cause of the issue. The only other module mentioned is the hamdrv.sys Hamachi driver. Perhaps this is the problem? I'll go ahead and try to reinstall Hamachi and see what happens.

Will report back with results in a while.

 

[neieus]

Based on what you provided you pretty much came to the same conclusion I have. I would assume that the hamndrv.sys is the true cause to your ntoskrnle.exe crashing.

Edit: Sorry had the wrong .sys file but the same idea applies.

I would look for that device and either update or in some cases down grade the drivers or remove it entirely from your computer to see if that resolves your problem.

 

[johnbl]

I could not see your dump files but would also think it is your remote access software
hamdrv.sys from https://secure.logmein.com/products/pro/

sounds like a simple driver bug, gets the data from the lower driver, confirms that it got it, then asks for it again but the lower driver does not have it any more. Or the driver keeps asking for the same data over and over until you get the bugcheck.

I would update or remove it.

Based on what you provided you pretty much came to the same conclusion I have. I would assume that the hamndrv.sys is the true cause to your ntoskrnle.exe crashing.

Edit: Sorry had the wrong .sys file but the same idea applies.

I would look for that device and either update or in some cases down grade the drivers or remove it entirely from your computer to see if that resolves your problem.