Frequent BSoD, random error messages.

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

>.>

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.

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.

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

Code:

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/CardRead...00.66_WHQL.zip

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.

Code:

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

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.

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

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. :)

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