Frequent BSoD, random error messages.

K followed the directions, hopefully this is solved.
Thanks for the help...now I wait for the blue screen of death...the monster in my closet.

xthequwit said:

K followed the directions, hopefully this is solved.
Thanks for the help...now I wait for the blue screen of death...the monster in my closet.

We'll be here waiting to push that monster back into the closet. Good luck!

writhziden said:

xthequwit said:

K followed the directions, hopefully this is solved.
Thanks for the help...now I wait for the blue screen of death...the monster in my closet.

We'll be here waiting to push that monster back into the closet. Good luck!

...Oh hey...nice to see the cookie monster avatar again.

;.;

I was playing League with the gamepad plugged in, the entire computer froze for 5 seconds-ish I regained control for a few seconds, then it BSoD.

When asked to click the "Change settings" button on the Troubleshoot tab of the advanced settings, it is grey and I am unable to click it.
D:

xthequwit said:

When asked to click the "Change settings" button on the Troubleshoot tab of the advanced settings, it is grey and I am unable to click it.
D:

That just means your driver does not allow you to change settings. Ignore that step in the guide as it does not apply to you. Your display driver optimizes those settings without manual input.

writhziden said:

xthequwit said:

When asked to click the "Change settings" button on the Troubleshoot tab of the advanced settings, it is grey and I am unable to click it.
D:

That just means your driver does not allow you to change settings. Ignore that step in the guide as it does not apply to you. Your display driver optimizes those settings without manual input.

I figured, ok did the rest...safe mode cleansing and such.

The drivers failed two unspecified packages again, apparently no recourse.

To note, I noticed my belkin n52te doesnt list W7 as a supported OS.
without its drivers, its a comfortable keyboard...but with vista drivers it a timebomb maybe? Many fan sites recommended installing the vista's because "7 is just a pretty vista". Seemed crude but Im not one to throw a 70 dollar hand couch in the trash.

;.;

tl;dr: I installed vista drivers on w7 for a gamepad because Im dumb, have i summoned the harbingers of the apocalypse?

xthequwit said:

writhziden said:

xthequwit said:

When asked to click the "Change settings" button on the Troubleshoot tab of the advanced settings, it is grey and I am unable to click it.
D:

That just means your driver does not allow you to change settings. Ignore that step in the guide as it does not apply to you. Your display driver optimizes those settings without manual input.

I figured, ok did the rest...safe mode cleansing and such.

The drivers failed two unspecified packages again, apparently no recourse.

To note, I noticed my belkin n52te doesnt list W7 as a supported OS.
without its drivers, its a comfortable keyboard...but with vista drivers it a timebomb maybe? Many fan sites recommended installing the vista's because "7 is just a pretty vista". Seemed crude but Im not one to throw a 70 dollar hand couch in the trash.

;.;

tl;dr: I installed vista drivers on w7 for a gamepad because Im dumb, have i summoned the harbingers of the apocalypse?

Depends on how you installed them. As long as the installation procedure matched the methods described in Drivers - Install Vista Drivers on Windows 7, they should work fine. Occasionally, that method does cause conflicts, but since your keyboard is not showing up as a source of the blue screens after doing the USB fix, you are probably safe.

writhziden said:

Depends on how you installed them. As long as the installation procedure matched the methods described in Drivers - Install Vista Drivers on Windows 7, they should work fine. Occasionally, that method does cause conflicts, but since your keyboard is not showing up as a source of the blue screens after doing the USB fix, you are probably safe.

EDIT:I uninstalled the old ones first, promise.
Using the above tutorial
Installed the drivers with vista comp and admin enabled.
rebooted when prompted
the gamepad wasnt detected so I unplugged/replugged, windows searched for drivers and then...
Youll never guess.

BSOD!
;.;


It wasnt detecting it on start up before, but I didnt think much of it. Error code 43 in the device manager.

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xthequwit\123011-23859-01\123011-23859-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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 14:13:05.613 2011 (UTC - 7:00)
System Uptime: 0 days 0:05:31.847
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, fffff80002c9dbb6}

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+a5df )

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

0: 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: fffff80002c9dbb6, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ecc100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeSetEvent+16
fffff800`02c9dbb6 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:  fffff880031af1f0 -- (.trap 0xfffff880031af1f0)
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=fffff80002c9dbb6 rsp=fffff880031af380 rbp=0000000000000002
 r8=0000000000000000  r9=0000000000000000 r10=fffff88009d7f000
r11=fffff9800aa72f20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeSetEvent+0x16:
fffff800`02c9dbb6 f6037f          test    byte ptr [rbx],7Fh ds:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c991e9 to fffff80002c99c40

STACK_TEXT:  
fffff880`031af0a8 fffff800`02c991e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`031af0b0 fffff800`02c97e60 : 00000000`00000000 00000000`00040001 00000000`0000000e 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031af1f0 fffff800`02c9dbb6 : fffff800`02e4c260 00000000`00000280 fffffa80`06b2c340 fffff800`02cc3972 : nt!KiPageFault+0x260
fffff880`031af380 fffff880`09d7d5df : fffffa80`0848c340 00000000`00000000 fffffa80`07a81400 fffff980`0aa72ca0 : nt!KeSetEvent+0x16
fffff880`031af3f0 fffffa80`0848c340 : 00000000`00000000 fffffa80`07a81400 fffff980`0aa72ca0 00000000`00000000 : JmtFltr+0xa5df
fffff880`031af3f8 00000000`00000000 : fffffa80`07a81400 fffff980`0aa72ca0 00000000`00000000 fffffa80`07a81410 : 0xfffffa80`0848c340


STACK_COMMAND:  kb

FOLLOWUP_IP: 
JmtFltr+a5df
fffff880`09d7d5df ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  JmtFltr+a5df

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: JmtFltr

IMAGE_NAME:  JmtFltr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  46fd3439

FAILURE_BUCKET_ID:  X64_0xA_VRF_JmtFltr+a5df

BUCKET_ID:  X64_0xA_VRF_JmtFltr+a5df

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

Update the following drivers if possible:

Code:

JmtFltr	fffff880`09d73000	fffff880`09d7e580	Fri Sep 28 11:04:57 2007 (46fd3439)	0001641e	None	JmtFltr.sys
vhidmini	fffff880`07df8000	fffff880`07dfb680	Fri Sep 28 11:21:57 2007 (46fd3835)	0000ddea		vhidmini.sys

You may find them with the help of Driver Reference