BSOD in any browser. Memory Management. Driver Issue

Page 2 of 2 FirstFirst 12
  1.    #11

    Code:
    2013-11-24 20:08:12, Info                  CSI    000002e9 [SR] Verify complete
    2013-11-24 20:08:12, Info                  CSI    000002ea [SR] Repairing 1 components
    2013-11-24 20:08:12, Info                  CSI    000002eb [SR] Beginning Verify and Repair transaction
    2013-11-24 20:08:12, Info                  CSI    000002ec Hashes for file member \SystemRoot\WinSxS\amd64_atiilhag.inf_31bf3856ad364e35_6.1.7600.16385_none_019357585ef99a63\atidxx32.dll do not match actual file [l:24{12}]"atidxx32.dll" :
      Found: {l:32 b:WsLGpTlqQbNS99ITCkqpWCzfIJgq5ufH2QBefxh9+GE=} Expected: {l:32 b:9vls4vOnyihVVKkUR4IMmVvkUqTHr6om2OnpYSG5FAo=}
    2013-11-24 20:08:12, Info                  CSI    000002ed [SR] Cannot repair member file [l:24{12}]"atidxx32.dll" of atiilhag.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    2013-11-24 20:08:12, Info                  CSI    000002ee Hashes for file member \SystemRoot\WinSxS\amd64_atiilhag.inf_31bf3856ad364e35_6.1.7600.16385_none_019357585ef99a63\atidxx32.dll do not match actual file [l:24{12}]"atidxx32.dll" :
      Found: {l:32 b:WsLGpTlqQbNS99ITCkqpWCzfIJgq5ufH2QBefxh9+GE=} Expected: {l:32 b:9vls4vOnyihVVKkUR4IMmVvkUqTHr6om2OnpYSG5FAo=}
    2013-11-24 20:08:12, Info                  CSI    000002ef [SR] Cannot repair member file [l:24{12}]"atidxx32.dll" of atiilhag.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    Try a Repair Install firstly. It seems like hash mismatches.
      My Computer

  2.    #12

    Code:
    BugCheck C9, {6, 103, fffff9800c1a6c10, 0}
    
    Probably caused by : InputFilter_FlexDef2b.sys ( InputFilter_FlexDef2b+1c30 )
    Code:
    1: kd> !irp fffff9800c1a6c10
    Irp is active with 11 stacks 8 is current (= 0xfffff9800c1a6ed8)
     No Mdl: No System Buffer: Thread fffffa800a803680:  Irp stack trace.  Pending has been returned
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0 10 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
     [ 1b, 0]   0 10 fffffa800d9c2440 00000000 fffff880040a0120-fffff880031bd198    
    	      fffffa800d9c2440: Could not read device object or _DEVICE_OBJECT not found
    	usbfilter
    			Args: 00000000 00000000 00000000 00000000
     [ 1b, 0]   0 10 fffffa800d9d1be0 00000000 fffff80003715540-00000000    
    	      fffffa800d9d1be0: Could not read device object or _DEVICE_OBJECT not found
    	nt!ViFilterStartCompletionRoutine
    			Args: 00000000 00000000 00000000 00000000
     [ 1b, 0]   0 10 fffffa800d6a5e00 00000000 fffff8800619c200-fffff880031bd3b0    
    	      Cannot read _DRIVER_OBJECT at fffffa800b8f7e70
    	InputFilter_FlexDef2b
    			Args: 00000000 00000000 00000000 00000000
    >[ 1b, 0]   0 e0 fffffa800d6a5b80 00000000 fffff80003715540-00000000 Success Error Cancel 
    	      Cannot read _DRIVER_OBJECT at fffffa800d9e0b40
    	nt!ViFilterStartCompletionRoutine
    			Args: 00000000 00000000 00000000 00000000
     [ 1b, 0]   0 e0 fffffa800d6a5940 00000000 fffff880061a5c68-fffff880031bd500 Success Error Cancel 
    	      Cannot read _DRIVER_OBJECT at fffffa800b8f7e70
    	hidusb!HumPnpCompletion
    			Args: 00000000 00000000 00000000 00000000
     [ 1b, 0]   0 e0 fffffa800d6a6b40 00000000 fffff880061b479c-fffff880031bd570 Success Error Cancel 
    	      fffffa800d6a6b40: Could not read device object or _DEVICE_OBJECT not found
    	HIDCLASS!HidpSynchronousCallCompletion
    			Args: 00000000 00000000 00000000 00000000
     [ 1b, 0]   0 e0 fffffa800d6a6b40 00000000 fffff80003389cf0-fffffa800da07e80 Success Error Cancel 
    	      fffffa800d6a6b40: Could not read device object or _DEVICE_OBJECT not found
    	nt!PnpDeviceCompletionRoutine
    			Args: 00000000 00000000 00000000 00000000
    Code:
    1: kd> lmvm InputFilter_FlexDef2b
    start             end                 module name
    fffff880`0619b000 fffff880`061a4000   InputFilter_FlexDef2b T (no symbols)           
        Loaded symbol image file: InputFilter_FlexDef2b.sys
        Image path: \SystemRoot\system32\DRIVERS\InputFilter_FlexDef2b.sys
        Image name: InputFilter_FlexDef2b.sys
        Timestamp:        Sat Jun 19 01:36:01 2010 (4C1C10F1)
        CheckSum:         000111CA
        ImageSize:        00009000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Your Dongguan Siliten Electronic Co. - Flex Define HID Keyboard Driver seems to be causing problems, please update the driver from here - DONGWAN472017

    Code:
    1: kd> !dpx
    Start memory scan  : 0xfffff880031bd2a8 ($csp)
    End memory scan    : 0xfffff880031be000 (Stack Base)
    
                   rsp : 0xfffff880031bd2a8 : 0xfffff800037290c2 : nt!IovCompleteRequest+0xc2
    0xfffff880031bd2a8 : 0xfffff800037290c2 : nt!IovCompleteRequest+0xc2
    0xfffff880031bd2f8 : 0xfffff80003726737 : nt!VerifierKeWaitForSingleObject+0x177
    0xfffff880031bd318 : 0xfffff8000372fc00 : nt!IovCallDriver+0x550
    The driver has marked a IRP as pending in the IRP stack, but has called nt!IoCompleteRequest, when the IRP has finished being processed, it still holds the STATUS_PENDING flag.

    nt!IoCompleteRequest Definition:

    Code:
    VOID 
      IoCompleteRequest(
        IN PIRP  Irp,
        IN CCHAR  PriorityBoost
        );
    The first parameter is a pointer to the IRP to be completed.

    Code:
    1: kd> lmvm usbfilter
    
    start             end                 module name
    fffff880`0409c000 fffff880`040ad000   usbfilter T (deferred)             
        Image path: \SystemRoot\system32\DRIVERS\usbfilter.sys
        Image name: usbfilter.sys
        Timestamp:        Wed Aug 29 02:27:12 2012 (503D6FF0)
        CheckSum:         00016B8F
        ImageSize:        00011000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Please update your AMD USB Filter Driver, which is most likely to be part of the chipset driver package - Support & Drivers

    I would also check your model or motherboard support page.
      My Computer


  3. Posts : 8
    Windows 7 Home Premium 64 bit
    Thread Starter
       #13

    I guess "Your Dongguan Siliten Electronic Co. - Flex Define HID Keyboard Driver seems to be causing problems, please update the driver from here - DONGWAN472017" is my HP Keyboard??

    The website is not clear on updating. Test 1, Test 2, Test 3?? I have no issue putting in a Dell keyboard (I own a bunch) and deleting the old drivers. When I went to the Device & Printers, selected the keyboard, under properties, all options (delete, update ...) were greyed out. Seems it is using the microsoft default drivers. In which case why is it giving me this problem and more importantly, how do I delete them? Thanks.

    Ran out of time tonight for more work.
      My Computer

  4.    #14

    Post a screenshot of the Device Manager greyed out boxes - Screenshots and Files - Upload and Post in Seven Forums

    Have you tried deleting the driver from it's folder?

    Code:
    C:\system32\DRIVERS\InputFilter_FlexDef2b.sys
      My Computer


  5. Posts : 8
    Windows 7 Home Premium 64 bit
    Thread Starter
       #15

    I did swap keyboards and things are at least much better. Have been busy outside of the computer so I can't say for sure everything is fixed. Today I deleted the driver (from both operating systems). I will run the driver verifier again and see what happens.

    Thanks very much for your help.
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 21:02.
Find Us