Please save my sanity: Random BSODs when gaming

#1
For the last two months I have been trying to get rid of my artifacting and bsod's. I now have a completely new system. I rma'd my graphics card and bought a second (new) one. here is my dumps and details. Thanks in advance for any help saving my sanity :cry_smile:

View attachment Seven Forums.zip
 


#2
Other info:
-I have adjusted my GPU (5870 cf x 2) fans.
-This is a fresh install on a new ssd (m4 128Gb).
-The bios, all drivers and Windows are all up to date.
-This is not a temperature problem for sure.
-I have more dumps on another hard drive, but they are all similar to these
-Yes I have lost my mind and confidence trying to just play a game without a hard hang or a bsod *help* which is why I am crusing these forums and googling bsod xxxxx at 4am on a sunday :disillusionment:

CPU-Z:
1.jpg 2.jpg 3.jpg 4.jpg 5.jpg 6.jpg 7.jpg
 


Last edited:

Trouble

Noob Whisperer
#3
Your two most recent dump files are indicating an issue with
MBfilt64.sys 7/30/2009 which as best as I can determine is associated with your Realtek High Definition Audio Device, however having the same or at least very similar device I do not have that driver on my system. So... you can try updating from here Realtek but it already looks like you have a pretty current if not the most recent driver from realtek.
So alternately you may want to consider searching for and renaming MBfilt64.sys to MBfilt64.OLD that should break it and prevent its' loading and showing up in any subsequent BSODs. Easily reversed if unintended problems occur.
Code:
BugCheck A, {0, 2, 0, fffff8000348cd75}
Unable to load image [COLOR=#ff0000][U][B]MBfilt64.sys[/B][/U][/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for[COLOR=#ff0000][U][B] MBfilt64.sys[/B][/U][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys
[U][B][COLOR=#ff0000]Probably caused by : MBfilt64.sys[/COLOR][/B][/U] ( MBfilt64+1817 )
Followup: MachineOwner
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: fffff8000348cd75, address which referenced memory
Debugging Details:
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036bb100
 0000000000000000 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!KeSetEvent+1e3
fffff800`0348cd75 488b00          mov     rax,qword ptr [rax]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
TRAP_FRAME:  fffff88003716950 -- (.trap 0xfffff88003716950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880103911e0
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000348cd75 rsp=fffff88003716ae0 rbp=0000000000000000
 r8=0000000000000000  r9=fffff8800336d180 r10=0000000000000000
r11=fffff8000363b260 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt!KeSetEvent+0x1e3:
fffff800`0348cd75 488b00          mov     rax,qword ptr [rax] ds:6b10:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800034881e9 to fffff80003488c40
STACK_TEXT:  
fffff880`03716808 fffff800`034881e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03716810 fffff800`03486e60 : 00000000`00000160 00000000`00000000 00000000`0000000d fffff880`103911d8 : nt!KiBugCheckDispatch+0x69
fffff880`03716950 fffff800`0348cd75 : fffffa80`11832a02 fffffa80`11832a00 00000000`00000000 fffff980`0dc34ea0 : nt!KiPageFault+0x260
fffff880`03716ae0 fffff880`0795a817 : fffff880`00000000 fffff980`00000008 fffff800`03631e00 fffffa80`11836f50 : nt!KeSetEvent+0x1e3
fffff880`03716b50 fffff880`00000000 : fffff980`00000008 fffff800`03631e00 fffffa80`11836f50 fffffa80`11832a00 : [U][B][COLOR=#ff0000]MBfilt64[/COLOR][/B][/U]+0x1817
fffff880`03716b58 fffff980`00000008 : fffff800`03631e00 fffffa80`11836f50 fffffa80`11832a00 fffff800`0392d2eb : 0xfffff880`00000000
fffff880`03716b60 fffff800`03631e00 : fffffa80`11836f50 fffffa80`11832a00 fffff800`0392d2eb fffffa80`11832a00 : 0xfffff980`00000008
fffff880`03716b68 fffffa80`11836f50 : fffffa80`11832a00 fffff800`0392d2eb fffffa80`11832a00 fffffa80`11832a00 : nt!ViPendingWorkers+0x120
fffff880`03716b70 fffffa80`11832a00 : fffff800`0392d2eb fffffa80`11832a00 fffffa80`11832a00 fffff980`0dc35000 : 0xfffffa80`11836f50
fffff880`03716b78 fffff800`0392d2eb : fffffa80`11832a00 fffffa80`11832a00 fffff980`0dc35000 fffff980`0dc34ea0 : 0xfffffa80`11832a00
fffff880`03716b80 fffff800`0392d36c : fffff800`03631e00 00000000`00000080 fffffa80`0d92eb30 00000000`00000100 : nt!ViPendingCompleteAfterWait+0x7b
fffff880`03716bc0 fffff800`03723fee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ViPendingWorkerThread+0x2c
fffff880`03716c00 fffff800`0347a5e6 : fffff880`009b3180 fffffa80`0d9db680 fffff880`009be0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03716c40 00000000`00000000 : fffff880`03717000 fffff880`03711000 fffff880`037168d0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND:  kb
FOLLOWUP_IP: 
[U][B][COLOR=#ff0000]MBfilt64[/COLOR][/B][/U]+1817
fffff880`0795a817 ??              ???
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  [U][B][COLOR=#ff0000]MBfilt64[/COLOR][/B][/U]+1817
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: [COLOR=#ff0000][U][B]MBfilt64[/B][/U][/COLOR]
IMAGE_NAME:  [COLOR=#ff0000][U][B]MBfilt64.sys[/B][/U][/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  4a7267b0
FAILURE_BUCKET_ID:  X64_0xA_[B][U][COLOR=#ff0000]MBfilt64[/COLOR][/U][/B]+1817
BUCKET_ID:  X64_0xA_[COLOR=#ff0000][U][B]MBfilt64[/B][/U][/COLOR]+1817
Followup: MachineOwner
If Blue Screens persist after correcting the above issue, please;
Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using Memtest 86+
Regards
Randy
 


#4
I ran memtest86+ for 9 hours with no errors, and MBfilt64 is for my creative sound hd titanium card. there were several hard hangs with no dumps and lots of different artifacting. here is my latest stuff:
 


Attachments

Last edited:

Elmer

Extraordinary Member
#5
Hi kujetic.

STOP 0x00000116: VIDEO_TDR_ERROR
Usual causes:
Video driver, overheating, bad video card, ?BIOS, ?Power to card.

Your latest dump file lists atikmpag.sys as the probable cause. This is a Graphics driver.
Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes. Random stop codes can often indicate hardware issues.


As a Priority:

You're getting a Stop Error Code 116
(Link) "It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust build up and subsequently inadequate cooling." - H2SO4
See link to begin troubleshooting: STOP 0x116: VIDEO_TDR_ERROR Troubleshooting.


RTCore64.sys Wed May 25 07:39:12 2005
RivaTuner or EVGA Precision. Has known issues with Windows 7. Uninstall


Bugcheck Analysis:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800ebc7010, fffff880042e08c8, 0, 2}

Unable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
[COLOR=#ff0000][B]Probably caused by : atikmpag.sys[/B][/COLOR] ( atikmpag+78c8 )

Followup: MachineOwner
 


Last edited:
This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top