Solved Frequent BSoD, random error messages.

[writhziden]

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\xthequwit\123111-21203-01\123111-21203-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`02c09000 PsLoadedModuleList = 0xfffff800`02e4e670
Debug session time: Sat Dec 31 10:30:06.329 2011 (UTC - 7:00)
System Uptime: 0 days 0:53:02.547
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa80e79b0448, 2, 1, fffff80002c8d72c}

Probably caused by : ndis.sys ( ndis!ndisReceiveWorkerThread+d0 )

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

1: 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: fffffa80e79b0448, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002c8d72c, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb8100
 fffffa80e79b0448 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeWaitForSingleObject+17c
fffff800`02c8d72c 4c8938          mov     qword ptr [rax],r15

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800724da80 -- (.trap 0xfffff8800724da80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80e79b0448 rbx=0000000000000000 rcx=fffffa80079b0448
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c8d72c rsp=fffff8800724dc10 rbp=0000000000000000
 r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
r11=fffff880009e8180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeWaitForSingleObject+0x17c:
fffff800`02c8d72c 4c8938          mov     qword ptr [rax],r15 ds:61a0:fffffa80`e79b0448=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c851e9 to fffff80002c85c40

STACK_TEXT:  
fffff880`0724d938 fffff800`02c851e9 : 00000000`0000000a fffffa80`e79b0448 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0724d940 fffff800`02c83e60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0724da80 fffff800`02c8d72c : 00000000`00000002 00000000`00000001 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x260
fffff880`0724dc10 fffff880`0152fe50 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`08621600 : nt!KeWaitForSingleObject+0x17c
fffff880`0724dcb0 fffff800`02f20fee : fffff880`06772690 fffffa80`07545b60 00000000`00000080 fffff800`02c7d757 : ndis!ndisReceiveWorkerThread+0xd0
fffff880`0724dd40 fffff800`02c775e6 : fffff880`02f64180 fffffa80`07545b60 fffffa80`07381b60 fffff880`01231cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`0724dd80 00000000`00000000 : fffff880`0724e000 fffff880`07248000 fffff880`0724da00 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ndis!ndisReceiveWorkerThread+d0
fffff880`0152fe50 440f20c5        mov     rbp,cr8

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  ndis!ndisReceiveWorkerThread+d0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ndis

IMAGE_NAME:  ndis.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79392

FAILURE_BUCKET_ID:  X64_0xA_ndis!ndisReceiveWorkerThread+d0

BUCKET_ID:  X64_0xA_ndis!ndisReceiveWorkerThread+d0

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

A system driver... Caused by: sytem file corruption, hardware failing, or a device driver that is incompatible with Windows. I note that

JmtFltr	fffff880`0750b000	fffff880`07516580	Fri Sep 28 11:04:57 2007 (46fd3439)	0001641e		JmtFltr.sys
vhidmini	fffff880`0487e000	fffff880`04881680	Fri Sep 28 11:21:57 2007 (46fd3835)	0000ddea		vhidmini.sys

are still loaded. Are they listed in C:\Windows\System32\Drivers as .sys and .sys.bak now?

 

[xthequwit]

The Jmtfltr looks like it made a new version of itself...

The vhidmini is the onboard network card, if I remove that I wont be able to get online, beside that I installed the newest drivers for it...it should be compatible? : /

 

[writhziden]

The Jmtfltr looks like it made a new version of itself...

The vhidmini is the onboard network card, if I remove that I wont be able to get online, beside that I installed the newest drivers for it...it should be compatible? : /

What date does the vhidmini show for you in device manager (start menu -> right click computer -> manage -> device manager (list on the left) -> expand network adapters -> right click the name of your network adapter with vhidmini as its driver -> Properties -> Driver tab)? Sometimes the dmp files can't verify the date, so I have to rely on the owner to check.

To prevent JmtFltr from recreating (after deleting it as you still have the backup), see Post #12 of that thread I gave instructions for a similar problem in. The Realtek part of that post does not apply to you, just the disabling installation through Windows Updates.

 

[xthequwit]

6/10/2011
Maybe I could use the drive sweeper program to get rid of the old version for sure and reinstall?

It doesnt seem to match the one on the website, I assumed that was due to the "all in 1" being the latest version and the driver package being...nvm.

I've set my settings to yours in #12 of the thread linked.

 

[writhziden]

6/10/2011
Maybe I could use the drive sweeper program to get rid of the old version for sure and reinstall?

It doesnt seem to match the one on the website, I assumed that was due to the "all in 1" being the latest version and the driver package being...nvm.

I've set my settings to yours in #12 of the thread linked.

Nah, you're not getting blue screens due to vhidmini, so it is probably fine. The date just isn't getting transferred properly to the dmp files. Worry about JmtFltr.sys first as it appears to cause issues with your system the most. If you continue to have problems with it, find all remnants of JmtFltr.sys (start menu -> all programs -> accessories -> command prompt -> type "cd.." [without quotes] -> type "cd .." [without quotes] -> type "dir /s *JmtFltr.sys*" [without quotes] and hit enter -> go to the directories listed that contain that driver and delete/rename them as previously done).

 

[xthequwit]

6/10/2011
Maybe I could use the drive sweeper program to get rid of the old version for sure and reinstall?

It doesnt seem to match the one on the website, I assumed that was due to the "all in 1" being the latest version and the driver package being...nvm.

I've set my settings to yours in #12 of the thread linked.

Nah, you're not getting blue screens due to vhidmini, so it is probably fine. The date just isn't getting transferred properly to the dmp files. Worry about JmtFltr.sys first as it appears to cause issues with your system the most. If you continue to have problems with it, find all remnants of JmtFltr.sys (start menu -> all programs -> accessories -> command prompt -> type "cd.." [without quotes] -> type "cd .." [without quotes] -> type "dir /s *JmtFltr.sys*" [without quotes] and hit enter -> go to the directories listed that contain that driver and delete/rename them as previously done).

The only remaining one is in windows/system32/driverstore, and I cant seem to gain access to that.

I suspect more trickery is involved.

 

[writhziden]

6/10/2011
Maybe I could use the drive sweeper program to get rid of the old version for sure and reinstall?

It doesnt seem to match the one on the website, I assumed that was due to the "all in 1" being the latest version and the driver package being...nvm.

I've set my settings to yours in #12 of the thread linked.

Nah, you're not getting blue screens due to vhidmini, so it is probably fine. The date just isn't getting transferred properly to the dmp files. Worry about JmtFltr.sys first as it appears to cause issues with your system the most. If you continue to have problems with it, find all remnants of JmtFltr.sys (start menu -> all programs -> accessories -> command prompt -> type "cd.." [without quotes] -> type "cd .." [without quotes] -> type "dir /s *JmtFltr.sys*" [without quotes] and hit enter -> go to the directories listed that contain that driver and delete/rename them as previously done).

The only remaining one is in windows/system32/driverstore, and I cant seem to gain access to that.

I suspect more trickery is involved.

Did you try accessing/changing it in safe mode?

 

[xthequwit]

Nah, you're not getting blue screens due to vhidmini, so it is probably fine. The date just isn't getting transferred properly to the dmp files. Worry about JmtFltr.sys first as it appears to cause issues with your system the most. If you continue to have problems with it, find all remnants of JmtFltr.sys (start menu -> all programs -> accessories -> command prompt -> type "cd.." [without quotes] -> type "cd .." [without quotes] -> type "dir /s *JmtFltr.sys*" [without quotes] and hit enter -> go to the directories listed that contain that driver and delete/rename them as previously done).

The only remaining one is in windows/system32/driverstore, and I cant seem to gain access to that.

I suspect more trickery is involved.

Did you try accessing/changing it in safe mode?

Even in safemode it wont let me delete it, access denied!:banghead:

 

[xthequwit]

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
http://www.dual-boxing.com/showpost.php?p=302576&postcount=6

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.

 

[writhziden]

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.

 

[xthequwit]

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/windows-vista/how-to-delete-a-system-file-in-windows-vista/

bookmarking this^

 

[writhziden]

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.

 

[xthequwit]

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?

 

[writhziden]

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?

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.

 

[xthequwit]

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?

 

[writhziden]

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.

 

[xthequwit]

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?

 

[writhziden]

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.

 

[xthequwit]

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?

 

[writhziden]

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?