Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Frequent BSoD, random error messages.

01 Jan 2012   #51
xthequwit

Windows professional 64 bit
 
 

Quote   Quote: Originally Posted by writhziden View Post
Quote   Quote: Originally Posted by xthequwit View Post
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:
http://www.howtogeek.com/howto/windo...windows-vista/

bookmarking this^


My System SpecsSystem Spec
.
01 Jan 2012   #52
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by xthequwit View Post
Quote   Quote: Originally Posted by writhziden View Post
Quote   Quote: Originally Posted by xthequwit View Post
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.
My System SpecsSystem Spec
01 Jan 2012   #53
xthequwit

Windows professional 64 bit
 
 

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?
My System SpecsSystem Spec
.

01 Jan 2012   #54
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by xthequwit View Post
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.
My System SpecsSystem Spec
01 Jan 2012   #55
xthequwit

Windows professional 64 bit
 
 

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?
My System SpecsSystem Spec
01 Jan 2012   #56
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by xthequwit View Post
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.
My System SpecsSystem Spec
01 Jan 2012   #57
xthequwit

Windows professional 64 bit
 
 

Quote   Quote: Originally Posted by writhziden View Post
Quote   Quote: Originally Posted by xthequwit View Post
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?
My System SpecsSystem Spec
01 Jan 2012   #58
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by xthequwit View Post
Quote   Quote: Originally Posted by writhziden View Post
Quote   Quote: Originally Posted by xthequwit View Post
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.
My System SpecsSystem Spec
01 Jan 2012   #59
xthequwit

Windows professional 64 bit
 
 

Quote   Quote: Originally Posted by writhziden View Post
Quote   Quote: Originally Posted by xthequwit View Post
Quote   Quote: Originally Posted by writhziden View Post

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?
My System SpecsSystem Spec
01 Jan 2012   #60
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by xthequwit View Post
Quote   Quote: Originally Posted by writhziden View Post
Quote   Quote: Originally Posted by xthequwit View Post

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?
My System SpecsSystem Spec
Reply

 Frequent BSoD, random error messages.




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Frequent BSOD cannt read error messages
Hi, Blue screens mainly occur while playing marvel heroes. But will also occur when streaming media over plex. I do not get any error codes or anything as the bsod is actually just the light blue screen but all of the writing is not legible. It really just looks like a blue screen with lines...
BSOD Help and Support
BSOD increasingly frequent crashes; varying error messages.
Hi. In the last months, I've been experiencing an increasing number of BSOD crashes, which now happen on a daily bases. In addition to that, my system (Windows 7 pro 64 bit) for some reason stopped saving minidump files, as of last september. I am therefore enclosing my Event Viewer...
BSOD Help and Support
BSOD after random, different error messages.
Some times I do not receive any error message. Sometimes I get "uncorrectable hardware error". This has been going on for a while but the crashes happen every two days or so. It is very annoying so I would be grateful for any help.
BSOD Help and Support
Getting a BSOD at random times, at least 6 different error messages.
Would really appreciate some help, as I have no idea what the problem is. I have ran dskchk /F...and nothing. I've also ran a scan on my disk, and nothing, so i dont think it's a virus. here is my msinfo.....
BSOD Help and Support
Random BSOD's, many different error messages.
Hello, a couple months ago i received a new computer, and ever since getting it i have been receiving constant bsod's. My most recent one was a cdd.dll inpage error
BSOD Help and Support
Random BSOD's with random error messages after a new setup
Hey! I recently upgraded my setup with an Asus M4A78LT-M mobo, Athlon II X4 640 processor and TakeMS 2x2GB 1333MHz DDR3 memory. After installing the parts I tried to boot to Windows but it always resulted in the same BSOD so I reinstalled my system. After installing Windows for the first time...
BSOD Help and Support


Our Sites

Site Links

About Us

Find 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 23:51.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App