Frequent BSoD, random error messages.

Page 4 of 8 FirstFirst ... 23456 ... LastLast

  1. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #31

    xthequwit said:
    writhziden said:
    xthequwit said:
    Any guesses why someone would be getting so many random BSoDs?
    This is getting really frustrating.
    If you want, you can disable Verifier now and let it run for a few days and see if you continue to get them. I think we rooted out most of the causes at this point. :)
    delete existing settings if I remember correctly.

    done, rebooting. Ill bring back more blue screens for you to hang on your wall ;.;
    Good luck!
      My Computer


  2. Posts : 34
    Windows professional 64 bit
    Thread Starter
       #32

    Plugged in the gamepad again, windows just doesnt like it.
    I did the vista installation for the drivers, I guess its just not going to work.

    Ill leave it unplugged and wait to crash with my other usb devices ;.;
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #33

    You still haven't updated the following drivers:
    Code:
    JmtFltr	fffff880`07942000	fffff880`0794d580	Fri Sep 28 11:04:57 2007 (46fd3439)	0001641e		JmtFltr.sys
    vhidmini	fffff880`0484c000	fffff880`0484f680	Fri Sep 28 11:21:57 2007 (46fd3835)	0000ddea		vhidmini.sys
      My Computer


  4. Posts : 34
    Windows professional 64 bit
    Thread Starter
       #34

    writhziden said:
    You still haven't updated the following drivers:
    Code:
    JmtFltr	fffff880`07942000	fffff880`0794d580	Fri Sep 28 11:04:57 2007 (46fd3439)	0001641e		JmtFltr.sys
    vhidmini	fffff880`0484c000	fffff880`0484f680	Fri Sep 28 11:21:57 2007 (46fd3835)	0000ddea		vhidmini.sys
    I went to the website and downloaded the drivers, then ran the setup...I dont know what else to do to update them.
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #35

    xthequwit said:
    writhziden said:
    You still haven't updated the following drivers:
    Code:
    JmtFltr	fffff880`07942000	fffff880`0794d580	Fri Sep 28 11:04:57 2007 (46fd3439)	0001641e		JmtFltr.sys
    vhidmini	fffff880`0484c000	fffff880`0484f680	Fri Sep 28 11:21:57 2007 (46fd3835)	0000ddea		vhidmini.sys
    I went to the website and downloaded the drivers, then ran the setup...I dont know what else to do to update them.
    Guess they aren't updateable... One option you do have is to rename them. Go into C:\Windows\System32\Drivers and just name JmtFltr.sys to JmtFltr.sys.bak and rename vhidmini.sys to vhidmini.sys.bak

    Then see what problems they cause so you know what software/hardware they are part of.

    You may have to rename them in Safe Mode since they may be in use in normal mode. Good luck!
    Last edited by writhziden; 31 Dec 2011 at 01:11. Reason: Additional information/instructions
      My Computer


  6. Posts : 34
    Windows professional 64 bit
    Thread Starter
       #36

    writhziden said:
    xthequwit said:
    writhziden said:
    You still haven't updated the following drivers:
    Code:
    JmtFltr	fffff880`07942000	fffff880`0794d580	Fri Sep 28 11:04:57 2007 (46fd3439)	0001641e		JmtFltr.sys
    vhidmini	fffff880`0484c000	fffff880`0484f680	Fri Sep 28 11:21:57 2007 (46fd3835)	0000ddea		vhidmini.sys
    I went to the website and downloaded the drivers, then ran the setup...I dont know what else to do to update them.
    Guess they aren't updateable... One option you do have is to rename them. Go into C:\Windows\System32\Drivers and just name JmtFltr.sys to JmtFltr.sys.bak and rename vhidmini.sys to vhidmini.sys.bak

    Then see what problems they cause so you know what software/hardware they are part of.

    You may have to rename them in Safe Mode since they may be in use in normal mode. Good luck!
    I uninstalled the drivers for the NIC and reinstalled them.
    7.46.610.2011 version
    6/10/2011 date

    Realtek
    I took the one at the top, the newest....right?

    I renamed the other without safemode, hell would deleting it help?
    I seriously dont have a memory card reader installed.

    Edit: early morning grief inc, trying to plug in my pad again.
    Last edited by xthequwit; 31 Dec 2011 at 07:19. Reason: zzz
      My Computer


  7. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #37

    xthequwit said:

    I uninstalled the drivers for the NIC and reinstalled them.
    7.46.610.2011 version
    6/10/2011 date

    Realtek
    I took the one at the top, the newest....right?

    I renamed the other without safemode, hell would deleting it help?
    I seriously dont have a memory card reader installed.

    Edit: early morning grief inc, trying to plug in my pad again.
    The one at the top is the newest, so you did well. :)

    It isn't necessary to delete them; renaming them will prevent them from being loaded. See how your computer does for a week (post back if you have any crashes before then), and let us know if the system is more stable. :)
      My Computer


  8. Posts : 34
    Windows professional 64 bit
    Thread Starter
       #38

    writhziden said:
    xthequwit said:

    I uninstalled the drivers for the NIC and reinstalled them.
    7.46.610.2011 version
    6/10/2011 date

    Realtek
    I took the one at the top, the newest....right?

    I renamed the other without safemode, hell would deleting it help?
    I seriously dont have a memory card reader installed.

    Edit: early morning grief inc, trying to plug in my pad again.
    The one at the top is the newest, so you did well. :)

    It isn't necessary to delete them; renaming them will prevent them from being loaded. See how your computer does for a week (post back if you have any crashes before then), and let us know if the system is more stable. :)
    I had the gamepad in again, its working for some time then it crashes.

    I installed the firmware, and drivers as instructed and they both seemed to take.
    On startup the device still isnt recognized.
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #39

    Code:
    Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xthequwit\123111-14531-01\123111-14531-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 (3 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`02c17000 PsLoadedModuleList = 0xfffff800`02e5c670
    Debug session time: Sat Dec 31 07:43:25.661 2011 (GMT-7)
    System Uptime: 0 days 1:35:31.879
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {0, 2, 8, 0}
    
    Probably caused by : hidusb.sys ( hidusb!HumReadReport+13f )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: 0000000000000000, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec6100
     0000000000000000 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    +0
    00000000`00000000 ??              ???
    
    PROCESS_NAME:  League of Lege
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    TRAP_FRAME:  fffff88002f93520 -- (.trap 0xfffff88002f93520)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000002 rbx=0000000000000000 rcx=fffffa80080d0a08
    rdx=0000000050456302 rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000000000 rsp=fffff88002f936b8 rbp=fffffa80088db010
     r8=0000000050456300  r9=0000000000000000 r10=fffff88002f64b80
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    00000000`00000000 ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002c931e9 to fffff80002c93c40
    
    FAILED_INSTRUCTION_ADDRESS: 
    +0
    00000000`00000000 ??              ???
    
    STACK_TEXT:  
    fffff880`02f936b8 fffff880`01095c0e : fffffa80`080d01a0 fffff880`0109b17a fffffa80`09529e10 fffffa80`076684e0 : 0x0
    fffff880`02f936c0 fffff880`010a66c3 : fffffa80`076684e0 fffffa80`088db010 fffffa80`080d0050 fffffa80`09529e10 : USBPORT!MPf_GetEndpointStatus+0x82
    fffff880`02f936f0 fffff880`010b68ce : fffffa80`080d0050 fffffa80`09529e10 fffffa80`080d0050 fffffa80`06b8fac0 : USBPORT!USBPORT_Core_QueueTransferUrb+0xd7
    fffff880`02f93730 fffff880`010b64b8 : fffffa80`06b8fac0 fffffa80`08686010 fffffa80`09529e10 fffffa80`080d0050 : USBPORT!USBPORT_BulkOrInterruptTransfer+0xca
    fffff880`02f937b0 fffff880`010bee74 : fffffa80`08686010 fffffa80`082b0009 fffffa80`08686010 fffffa80`09529e10 : USBPORT!USBPORT_ProcessURB+0xb44
    fffff880`02f93860 fffff880`01098af4 : 00000000`00000000 fffffa80`082b5050 fffffa80`08ecda00 fffffa80`08686010 : USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x138
    fffff880`02f938a0 fffff880`0435e566 : fffffa80`0863d050 fffffa80`0894b060 fffffa80`08686010 fffffa80`0863d1a0 : USBPORT!USBPORT_Dispatch+0x1dc
    fffff880`02f938e0 fffff880`0438ed8f : 00000000`00000000 00000000`00000000 fffffa80`0894b060 00000000`00000801 : usbhub!UsbhFdoUrbPdoFilter+0xde
    fffff880`02f93910 fffff880`0435cfb7 : fffffa80`088db868 00000000`00000000 fffffa80`08686010 fffffa80`08953a38 : usbhub!UsbhPdoInternalDeviceControl+0x373
    fffff880`02f93960 fffff880`01686ec4 : 00000000`00000000 fffffa80`08953b38 00000000`00000002 fffffa80`08953a38 : usbhub!UsbhGenDispatch+0x57
    fffff880`02f93990 fffff880`01683812 : fffffa80`088db868 fffffa80`08686010 00000000`00000324 fffffa80`08686010 : usbccgp!UsbcForwardIrp+0x30
    fffff880`02f939c0 fffff880`01683aba : fffffa80`08953a38 00000000`00220003 fffffa80`08686010 fffffa80`088db868 : usbccgp!DispatchPdoUrb+0xfa
    fffff880`02f93a00 fffff880`0168172e : 00000000`0000000f fffffa80`088db860 fffffa80`088db868 fffffa80`08686010 : usbccgp!DispatchPdoInternalDeviceControl+0x17a
    fffff880`02f93a30 fffff880`03aba48f : fffffa80`088db710 fffffa80`08686001 00000000`00000000 00000000`000007ff : usbccgp!USBC_Dispatch+0x2de
    fffff880`02f93ab0 fffff880`03ab9f5b : fffffa80`08686290 fffffa80`088ef801 fffff880`02f93b70 fffffa80`088ef6e0 : hidusb!HumReadReport+0x13f
    fffff880`02f93b00 fffff880`03e99555 : fffffa80`089ae501 fffffa80`089ae5d0 fffffa80`08686010 00000000`00000008 : hidusb!HumInternalIoctl+0x137
    fffff880`02f93b70 fffff880`03e99d75 : fffffa80`089ae5d0 fffffa80`088ef850 00000000`00000000 00000000`00000008 : HIDCLASS!HidpSubmitInterruptRead+0xdd
    fffff880`02f93bd0 fffff800`02c97021 : fffffa80`08686293 00000000`00000000 fffffa80`088ef601 fffffa80`08686000 : HIDCLASS!HidpInterruptReadComplete+0x37d
    fffff880`02f93c60 fffff880`010a7631 : fffffa80`080d0050 fffffa80`09529e00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
    fffff880`02f93d50 fffff880`010a7b0f : fffffa80`075d0502 fffffa80`08686010 00000000`ffffffff fffffa80`080d0eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
    fffff880`02f93e30 fffff880`010a566f : fffffa80`080d0eb0 fffffa80`080d01a0 fffffa80`080d1050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
    fffff880`02f93e90 fffff880`01096f89 : fffffa80`080d0050 00000000`00000000 fffffa80`080d0e02 fffffa80`080d0eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
    fffff880`02f93ed0 fffff800`02c9f0ac : fffff880`02f64180 fffffa80`080d0eb0 fffffa80`080d0ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
    fffff880`02f93f00 fffff800`02c96765 : 00000000`00000000 fffffa80`07668b60 00000000`00000000 fffff880`01096db0 : nt!KiRetireDpcList+0x1bc
    fffff880`02f93fb0 fffff800`02c9657c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`09079be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    
    
    STACK_COMMAND:  .trap 0xfffff88002f93520 ; kb
    
    FOLLOWUP_IP: 
    hidusb!HumReadReport+13f
    fffff880`03aba48f 488b4c2460      mov     rcx,qword ptr [rsp+60h]
    
    SYMBOL_STACK_INDEX:  e
    
    SYMBOL_NAME:  hidusb!HumReadReport+13f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hidusb
    
    IMAGE_NAME:  hidusb.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665
    
    FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_hidusb!HumReadReport+13f
    
    BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_hidusb!HumReadReport+13f
    
    Followup: MachineOwner
    ---------
    You can try going through the steps in USB Driver - General Fix for Problems a second time, and if you continue to have issues after doing that again (remember to keep your gamepad unplugged through the process), then you might consider replacing the gamepad.
      My Computer


  10. Posts : 34
    Windows professional 64 bit
    Thread Starter
       #40

    Just listening to music, gamepad wasnt plugged it at all.
      My Computer


 
Page 4 of 8 FirstFirst ... 23456 ... LastLast

  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 17:52.
Find Us