Blue screen error 0x00000044; "Kernel Mode Driver Framework Runtime"

[astrodoc]

Blue screen error 0x00000044; "Kernel Mode Driver Framework Runtime"

This shut down occurs ONLY when I am using 3 peripheral usb devices simultaeously and it doesn't happen right away. Sometimes it's an hour and sometimes it's several hours before it crashes. Now there is an executive program that is controlling all of the usb devices, if that makes any difference or not. It never happens any other time. The zip file from your dmp log application is attached.
Thanks
Dave

 

[koolkat77]

Welcome. Caused by USB-to-Serial Cable Driver/GembirdUAS112 Driver Reference Table


May be you want to install an older driver version and see if that helps.

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\OBSERVATORY-Fri_11_21_2014_140649_77\112114-17940-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`0344c000 PsLoadedModuleList = 0xfffff800`0368f890
Debug session time: Fri Nov 21 13:06:35.615 2014 (UTC + 6:00)
System Uptime: 0 days 4:17:12.232
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 44, {fffffa80088e3a90, eae, 0, 0}

*** WARNING: Unable to verify timestamp for ser2pl64.sys
*** ERROR: Module load completed but symbols could not be loaded for ser2pl64.sys
Probably caused by : ser2pl64.sys ( ser2pl64+ede8 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa80088e3a90, Address of the IRP
Arg2: 0000000000000eae
Arg3: 0000000000000000
Arg4: 0000000000000000

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


IRP_ADDRESS:  fffffa80088e3a90

FOLLOWUP_IP: 
ser2pl64+ede8
fffff880`093b1de8 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x44

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

DEVICE_OBJECT: fffffa800957b070

TAG_NOT_DEFINED_c000000f:  FFFFF88002F22FB0

LAST_CONTROL_TRANSFER:  from fffff800034aa8c0 to fffff800034c1bc0

STACK_TEXT:  
fffff880`02f22b58 fffff800`034aa8c0 : 00000000`00000044 fffffa80`088e3a90 00000000`00000eae 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f22b60 fffff880`00c0c789 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x413f2
fffff880`02f22c50 fffff880`00c0adc1 : fffffa80`088e3a90 00000000`00000000 00000000`00000000 fffffa80`07f09e20 : Wdf01000!FxRequest::CompleteInternal+0x65d
fffff880`02f22ce0 fffff880`093b1de8 : fffffa80`07f09e20 0000057f`f80f61d8 fffff880`02f22e78 00000000`00000000 : Wdf01000!imp_WdfRequestCompleteWithInformation+0x189
fffff880`02f22d40 fffffa80`07f09e20 : 0000057f`f80f61d8 fffff880`02f22e78 00000000`00000000 00000000`00000000 : ser2pl64+0xede8
fffff880`02f22d48 0000057f`f80f61d8 : fffff880`02f22e78 00000000`00000000 00000000`00000000 00000000`00000011 : 0xfffffa80`07f09e20
fffff880`02f22d50 fffff880`02f22e78 : 00000000`00000000 00000000`00000000 00000000`00000011 fffffa80`0669e600 : 0x0000057f`f80f61d8
fffff880`02f22d58 00000000`00000000 : 00000000`00000000 00000000`00000011 fffffa80`0669e600 fffff880`093b0a6d : 0xfffff880`02f22e78


STACK_COMMAND:  kb

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  ser2pl64+ede8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ser2pl64

IMAGE_NAME:  ser2pl64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53edb799

FAILURE_BUCKET_ID:  X64_0x44_ser2pl64+ede8

BUCKET_ID:  X64_0x44_ser2pl64+ede8

Followup: MachineOwner
---------

1: kd> lmvm ser2pl64
start             end                 module name
fffff880`093a3000 fffff880`093d4000   ser2pl64 T (no symbols)           
    Loaded symbol image file: ser2pl64.sys
    Image path: \SystemRoot\system32\DRIVERS\ser2pl64.sys
    Image name: ser2pl64.sys
    Timestamp:        Fri Aug 15 13:32:41 2014 (53EDB799)
    CheckSum:         000332CD
    ImageSize:        00031000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 Clean boot

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

 Hard Drive Diagnostics

• Double click and open my computer.
• Right click on desired drive and hit properties.
• Click on tools tab and Check now.

Read complete instructions on the tutorial: http://www.sevenforums.com/tutorials/433-disk-check.html

Other Tests:

 

• Upload a screenshot of your hard disk using Crystal Disk Info.
• Make a hard drive test from the hard drive manufacturers website.
• Test your Hard Drive with SeaTools.

 Temp Monitoring

Check for heating issues using Speccy or HWMonitor.

• Speccy - System Information - Free Download
• HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

Upload a screen shot with either of the tools: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[astrodoc]

Ok thanks. Is it possible the driver was corrupted or damaged? I ran the system file checker and there were several files that were repaired, however I could not read the data in the folder to see which files were fixed. After I did this the computer did not crash. Perhaps I just got lucky?
Thanks

 

[koolkat77]

Thanks for the update.

Keep updating the thread for further BSODs.