Solved Frequent BSoD, random error messages.

[xthequwit]

I see two?

Jmtfltr and vhidmini

DONE AND DONE, btw is this a hobby for you?
You seem to post a lot.

Uh, the smart board thing, said that I dont have any devices attached that would require its driver?
Its installed anyway...I guess just incase?

Also this other one is for hardware I dont have installed.
Theres no memory card reader in my machine....

>.>

 

[writhziden]

The memory card one is in case you installed one in your machine. It was outdated, so a good idea to update even if you aren't using it in case you need it in the future. Plus it caused a blue screen.

And yes, this is a hobby.

I also noticed something going through your dmp files: Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.

 

[xthequwit]

I dont want to spoil anything but the reason Im posting may have to do with another BSoD.

Trying to install firmware for the gamepad definetly caused this one, I was mid update when it happened.
Im starting to get the impression I wont be using this thing much longer.

: /

EDIT: Ive begun to pile kindling around the base of my computer.
EDIT 2 for 1 special, BSoD while the device was plugged in and I wasnt using it or trying to update it.

 

[writhziden]

You may have to disable Driver Verifier while you update your gamepad.

 

[writhziden]

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xthequwit\123011-28265-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e96670
Debug session time: Fri Dec 30 15:26:43.913 2011 (GMT-7)
System Uptime: 0 days 1:13:04.163
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002cd1bb6}

Unable to load image \SystemRoot\system32\drivers\JmtFltr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for JmtFltr.sys
*** ERROR: Module load completed but symbols could not be loaded for JmtFltr.sys
Probably caused by : JmtFltr.sys ( JmtFltr+a83c )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002cd1bb6, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f00100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeSetEvent+16
fffff800`02cd1bb6 f6037f          test    byte ptr [rbx],7Fh

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880031af260 -- (.trap 0xfffff880031af260)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cd1bb6 rsp=fffff880031af3f0 rbp=0000000000000002
 r8=0000000000000000  r9=0000000000000000 r10=fffff88006e60000
r11=fffff88002f64180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KeSetEvent+0x16:
fffff800`02cd1bb6 f6037f          test    byte ptr [rbx],7Fh ds:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ccd1e9 to fffff80002ccdc40

STACK_TEXT:  
fffff880`031af118 fffff800`02ccd1e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`031af120 fffff800`02ccbe60 : fffff980`11a92df0 00000000`00000000 00000000`c000000e 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031af260 fffff800`02cd1bb6 : fffffa80`08775760 fffffa80`08775760 00000000`00000040 00000000`00000000 : nt!KiPageFault+0x260
fffff880`031af3f0 fffff880`0980a83c : fffffa80`082ce8c0 00000000`00000000 fffffa80`09395900 fffff980`1a4eaca0 : nt!KeSetEvent+0x16
fffff880`031af460 fffffa80`082ce8c0 : 00000000`00000000 fffffa80`09395900 fffff980`1a4eaca0 fffffa80`00000000 : JmtFltr+0xa83c
fffff880`031af468 00000000`00000000 : fffffa80`09395900 fffff980`1a4eaca0 fffffa80`00000000 fffffa80`09395940 : 0xfffffa80`082ce8c0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
JmtFltr+a83c
fffff880`0980a83c ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  JmtFltr+a83c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: JmtFltr

IMAGE_NAME:  JmtFltr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  46fd3439

FAILURE_BUCKET_ID:  X64_0xA_VRF_JmtFltr+a83c

BUCKET_ID:  X64_0xA_VRF_JmtFltr+a83c

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

2: kd> lmvm JmtFltr
start             end                 module name
fffff880`09800000 fffff880`0980b580   JmtFltr  T (no symbols)           
    Loaded symbol image file: JmtFltr.sys
    Image path: \SystemRoot\system32\drivers\JmtFltr.sys
    Image name: JmtFltr.sys
    Timestamp:        Fri Sep 28 11:04:57 2007 (46FD3439)
    CheckSum:         0001641E
    ImageSize:        0000B580
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That driver for JmtFltr is still 2007... Any idea what hardware that is attached to? If not, try disabling it through device manager and see if it fixes that issue.

If you cannot find it in device manager, you can update it via ftp://driver.jmicron.com.tw/CardReader/Windows/JMB38X_WinDrv_R1.00.66_WHQL.zip

 

[xthequwit]

More BSoDs
I was hopeful that not having the usb device plugged in would solve my problems so I was tempted to try and unlock a core.
Potentially making an unstable system more unstable is always smart.

Otherwise I was watching a livestream.

 

[writhziden]

[list=1]
[*]Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xthequwit\123011-16484-01\123011-17328-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c18000 PsLoadedModuleList = 0xfffff800`02e5d670
Debug session time: Fri Dec 30 21:12:21.773 2011 (GMT-7)
System Uptime: 0 days 5:36:45.221
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88009dbadb0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+19c92 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88009dbadb0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
+0
fffff880`09dbadb0 d8bcdb0980f8ff  fdivr   dword ptr [rbx+rbx*8-77FF7h]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec7100
 0000000000000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88009dbbcd8 -- (.exr 0xfffff88009dbbcd8)
ExceptionAddress: fffff88004281c92 (Rt64win7+0x0000000000019c92)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88009dbbd80 -- (.trap 0xfffff88009dbbd80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80094ca590
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004281c92 rsp=fffff88009dbbf10 rbp=fffffa80094ca000
 r8=0000000000000b78  r9=00000000000000b0 r10=000000000000ffff
r11=fffffa80094ca000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
Rt64win7+0x19c92:
fffff880`04281c92 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d204fb to fffff80002c94c40

STACK_TEXT:  
fffff880`09dbacf8 fffff800`02d204fb : 00000000`0000001e ffffffff`c0000005 fffff880`09dbadb0 00000000`00000000 : nt!KeBugCheckEx
fffff880`09dbad00 fffff800`02ce8bb4 : 00000000`00000000 00000000`00000000 00000001`0000000d 000000c0`00000008 : nt!KipFatalFilter+0x1b
fffff880`09dbad40 fffff800`02cc0a7c : 00000000`0166b000 00000000`00000001 fffff880`09dbc000 fffffa80`06bba000 : nt! ?? ::FNODOBFM::`string'+0x83d
fffff880`09dbad80 fffff800`02cc04fd : fffff800`02dd7c24 fffff880`09dbd280 00000000`00000000 fffff800`02c18000 : nt!_C_specific_handler+0x8c
fffff880`09dbadf0 fffff800`02cbf2d5 : fffff800`02dd7c24 fffff880`09dbae68 fffff880`09dbbcd8 fffff800`02c18000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`09dbae20 fffff800`02cd0361 : fffff880`09dbbcd8 fffff880`09dbb530 fffff880`00000000 00000000`00000005 : nt!RtlDispatchException+0x415
fffff880`09dbb500 fffff800`02c942c2 : fffff880`09dbbcd8 00000000`0000003c fffff880`09dbbd80 fffffa80`094da380 : nt!KiDispatchException+0x135
fffff880`09dbbba0 fffff800`02c92bca : fffffa80`06b29710 fffffa80`0a180210 00000000`00000000 00000000`00000005 : nt!KiExceptionDispatch+0xc2
fffff880`09dbbd80 fffff880`04281c92 : fffffa80`094d0000 00000000`00000000 00000000`0000003c fffffa80`094da380 : nt!KiGeneralProtectionFault+0x10a
fffff880`09dbbf10 fffffa80`094d0000 : 00000000`00000000 00000000`0000003c fffffa80`094da380 fffffa80`094d0901 : Rt64win7+0x19c92
fffff880`09dbbf18 00000000`00000000 : 00000000`0000003c fffffa80`094da380 fffffa80`094d0901 fffffa80`094d0ae0 : 0xfffffa80`094d0000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Rt64win7+19c92
fffff880`04281c92 ??              ???

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  Rt64win7+19c92

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Rt64win7

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a718af3

FAILURE_BUCKET_ID:  X64_0x1E_VRF_Rt64win7+19c92

BUCKET_ID:  X64_0x1E_VRF_Rt64win7+19c92

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

3: kd> lmvm Rt64win7
start             end                 module name
fffff880`04268000 fffff880`042a6000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Thu Jul 30 05:58:43 2009 (4A718AF3)
    CheckSum:         000460F2
    ImageSize:        0003E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xthequwit\123011-16484-01\123011-16484-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c1d000 PsLoadedModuleList = 0xfffff800`02e62670
Debug session time: Fri Dec 30 21:28:32.873 2011 (GMT-7)
System Uptime: 0 days 0:15:39.123
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000097d2e, fffff880092cd780, 0}

Probably caused by : win32k.sys ( win32k!XCLIPOBJ::vSetup+4e )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000097d2e, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880092cd780, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
win32k!XCLIPOBJ::vSetup+4e
fffff960`00097d2e 8b421c          mov     eax,dword ptr [rdx+1Ch]

CONTEXT:  fffff880092cd780 -- (.cxr 0xfffff880092cd780)
rax=0000000000000000 rbx=fffff880092ce200 rcx=0000000000000000
rdx=fffff900c0f90700 rsi=fffff900c00b2070 rdi=00000000000000a0
rip=fffff96000097d2e rsp=fffff880092ce160 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=fffff880092ce2e0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000001 r15=fffff900c43efd60
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
win32k!XCLIPOBJ::vSetup+0x4e:
fffff960`00097d2e 8b421c          mov     eax,dword ptr [rdx+1Ch] ds:002b:fffff900`c0f9071c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x3B

PROCESS_NAME:  consent.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff96000097d2e

STACK_TEXT:  
fffff880`092ce160 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!XCLIPOBJ::vSetup+0x4e


FOLLOWUP_IP: 
win32k!XCLIPOBJ::vSetup+4e
fffff960`00097d2e 8b421c          mov     eax,dword ptr [rdx+1Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!XCLIPOBJ::vSetup+4e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ecdcd5a

STACK_COMMAND:  .cxr 0xfffff880092cd780 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_VRF_win32k!XCLIPOBJ::vSetup+4e

BUCKET_ID:  X64_0x3B_VRF_win32k!XCLIPOBJ::vSetup+4e

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


[/list]

Your first blue screen with Verifier running was due to your Realtek Gigabit Ethernet NIC driver. You should update your Realtek Gigabit Ethernet NIC driver (Driver Reference).

The second was a system file. If you unlocked the core, that was probably the result as system based crashes can be hardware related.

 

[xthequwit]

Any guesses why someone would be getting so many random BSoDs?
This is getting really frustrating.

 

[writhziden]

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.

 

[xthequwit]

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 ;.;

 

[writhziden]

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!

 

[xthequwit]

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 ;.;

 

[writhziden]

You still haven't updated the following drivers:

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

 

[xthequwit]

You still haven't updated the following drivers:

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.

 

[writhziden]

You still haven't updated the following drivers:

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!

 

[xthequwit]

You still haven't updated the following drivers:

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.

 

[writhziden]

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.

 

[xthequwit]

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.

 

[writhziden]

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 http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html 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.

 

[xthequwit]

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