Frequent BSoD, random error messages.

xthequwit said:

writhziden said:

xthequwit said:

so the jmtfltr is a driver used by my gamepad to read profiles on the gamepad.

this is a whole new paradigm of crap.

edit: Trying this mans idea
Dual-Boxing.com Forums - View Single Post - N52te - Anyone knows how to make it work under Windows 7?

Ill put my BSoD in gift wrap in a few minutes I suspect.

EDIT:
WHAT THE TRIPLE F!

Vhidmini.sys is also the name of the vista driver in the gamepad install.

Im gonna straight up commit murder.

It may be time for a new gamepad if this one is frustrating you this much... It does seem to cause quite a few problems with your system.

Happy new years bro.

Any advice on how to remove every piece of it from my system?
I never could dlete that file from driver store.

EDIT:
How to Delete a System File in Windows 7 or Vista - How-To Geek

bookmarking this^

Good info. Thanks. I would have walked you through how to do it in a different way, but that way works just as well and may actually be a little easier to follow. Thanks for sharing. I've added it to my faves as well.

Adventuring in the land of Skyrim, when sudden a BSoDragon attacks!
;.;

Could this be a bad motherboard situation?
Maybe memtest missed someone with the ram?

xthequwit said:

Adventuring in the land of Skyrim, when sudden a BSoDragon attacks!
;.;

Could this be a bad motherboard situation?
Maybe memtest missed someone with the ram?

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xthequwit\010112-15984-01\010112-15984-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 (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c05000 PsLoadedModuleList = 0xfffff800`02e4a670
Debug session time: Sun Jan  1 09:45:12.896 2012 (UTC - 7:00)
System Uptime: 0 days 4:57:24.115
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a0d8fda7b0, 0, fffff88003fa02eb, 5}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a0d8fda7b0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88003fa02eb, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb4100
 fffff8a0d8fda7b0 

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b
fffff880`03fa02eb 488b38          mov     rdi,qword ptr [rax]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  TESV.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88008d860a0 -- (.trap 0xfffff88008d860a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a0d8fda7b0 rbx=0000000000000000 rcx=0000000000000aab
rdx=000000000d450150 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003fa02eb rsp=fffff88008d86230 rbp=fffff88008d86a40
 r8=fffffa8007429150  r9=0000000000000002 r10=0000000000000025
r11=000000008002aac0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x39b:
fffff880`03fa02eb 488b38          mov     rdi,qword ptr [rax] ds:7228:fffff8a0`d8fda7b0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c2c3bf to fffff80002c81c40

STACK_TEXT:  
fffff880`08d85f38 fffff800`02c2c3bf : 00000000`00000050 fffff8a0`d8fda7b0 00000000`00000000 fffff880`08d860a0 : nt!KeBugCheckEx
fffff880`08d85f40 fffff800`02c7fd6e : 00000000`00000000 fffff8a0`d8fda7b0 fffff880`04e6c800 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`08d860a0 fffff880`03fa02eb : 00000000`00000009 00000000`0000000f fffffa80`091e2201 fffffa80`091e2210 : nt!KiPageFault+0x16e
fffff880`08d86230 fffff880`03f863e7 : fffffa80`0952e301 fffffa80`075f1230 00000000`0d450150 fffff880`000000de : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x39b
fffff880`08d86320 fffff880`03efefae : 00000000`00000000 00000000`00000200 fffff880`08d86a40 00000000`00000000 : dxgmms1!VidMmReferenceDmaBuffer+0x43
fffff880`08d86370 fffff880`03efe773 : fffff8a0`00000001 fffff8a0`0898c240 fffff880`08d869f0 00000000`00000000 : dxgkrnl!DXGCONTEXT::Render+0x326
fffff880`08d86980 fffff960`001af80e : 00000000`0ddfe6b0 fffffa80`08cd4060 00000000`7ef8f000 00000000`00000020 : dxgkrnl!DxgkRender+0x3e7
fffff880`08d86bf0 fffff800`02c80ed3 : fffffa80`08cd4060 00000000`00000334 00000000`00000000 fffffa80`08bc4a10 : win32k!NtGdiDdDDIRender+0x12
fffff880`08d86c20 00000000`739a164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0ddfe688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x739a164a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b
fffff880`03fa02eb 488b38          mov     rdi,qword ptr [rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b

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

Definitely could be RAM related. You ran only four passes, and we recommend at least five and preferably seven passes.

Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete.

I will run the MEMtests tonight, I just upped my voltage from "auto" whatever that was, it didnt say, to 1.65v

1.65v isnt crazy right?

xthequwit said:

I will run the MEMtests tonight, I just upped my voltage from "auto" whatever that was, it didnt say, to 1.65v

1.65v isnt crazy right?

What was it at when you first changed to manual? Upping it by 0.1 volts usually is enough to fix RAM problems due to low voltage.

writhziden said:

xthequwit said:

I will run the MEMtests tonight, I just upped my voltage from "auto" whatever that was, it didnt say, to 1.65v

1.65v isnt crazy right?

What was it at when you first changed to manual? Upping it by 0.1 volts usually is enough to fix RAM problems due to low voltage.

In the bios, the voltage was defined only by "auto"
I could set it back to auto and find out some other way, if you know how?

xthequwit said:

writhziden said:

xthequwit said:

I will run the MEMtests tonight, I just upped my voltage from "auto" whatever that was, it didnt say, to 1.65v

1.65v isnt crazy right?

What was it at when you first changed to manual? Upping it by 0.1 volts usually is enough to fix RAM problems due to low voltage.

In the bios, the voltage was defined only by "auto"
I could set it back to auto and find out some other way, if you know how?

If you change it to manual, it should show you what the auto setting was.

writhziden said:

xthequwit said:

writhziden said:

What was it at when you first changed to manual? Upping it by 0.1 volts usually is enough to fix RAM problems due to low voltage.

In the bios, the voltage was defined only by "auto"
I could set it back to auto and find out some other way, if you know how?

If you change it to manual, it should show you what the auto setting was.

its vertical list, with auto being at the top, above 1.2# volts.

so maybe it was less than 1.2?

xthequwit said:

writhziden said:

xthequwit said:

In the bios, the voltage was defined only by "auto"
I could set it back to auto and find out some other way, if you know how?

If you change it to manual, it should show you what the auto setting was.

its vertical list, with auto being at the top, above 1.2# volts.

so maybe it was less than 1.2?

I would check the manual of your motherboard for determining the voltage.

Edit: Did you change the DRAM voltage or a different voltage?