Random BSOD when playing games.

[Dyybe]

So sometimes when i'm playing, the game crashes and i get a BSOD or the game crashes and when i launch the game again then i get BSOD

Only new hardware i have are my Crucial 256GB MX100 SSD and Western Digital WD1003FZEX Caviar Black 1TB HDD



My OS is in Finnish so i cant really copy paste the windows error log but

042612-18813-01.dmp
sysdata.xml

22315-28579-01.dmp
sysdata.xml

and eleven problems that look like this

WD-20120724-2100.dmp- (this number changes in each one)
sysdata.xml
WERInternalMetadata.xml

----

I also did a full computer scan with malware bytes, Super Anti-spyware and adwcleaner but they didn't find anything.

 

[essenbe]

Hello, Dyybe. I'll see if I can help with your problem. You only had 1 dump file,sted 2/23/15 which is what we go by to debug. So, that isn't a lot to go on and a month old.

Please make sure your system is configured for Small Memory Dumps. http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

The dump file listed

BugCheck 116, {fffffa800c3da2a0, fffff88003ecc848, 0, 2}
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: [COLOR=red]Module load completed but symbols could not be loaded for atikmpag.sys[/COLOR]
Probably caused by : atikmpag.sys ( atikmpag+b848 )
Followup: MachineOwner

atikmpag
start             end                 module name
fffff880`03ec1000 fffff880`03f57000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Thu [COLOR=red]Nov 20 20:08:54 2014[/COLOR] (546E9EB6)
    CheckSum:         00093077
    ImageSize:        00096000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please update your Graphics driver and see if it helps any, but I would like you to do it this way.

I am going to give you some links that will help you get a good clean install and not have any drivers you don't need that will conflict with other drivers. Download a WHQL driver from http://www.sevenforums.com/graphic-cards/329659-latest-amd-catalyst-video-driver-windows-7-a.html . Once you have them downloaded, uninstall you current driver from control panel. next clean up any left over drivers from following this tutorial http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html and select only ATI Display Drivers. After you have done that and rebooted, install the new driver, only select custom install and install only what you have to. Very few people need most of what they include. You do not need the audio/HDMI drivers as you already have that in your Motherboard drivers. Unless there is some reason you need them, the only thing you really need is the Display Driver. Let us know if that helped any.

 

[Dyybe]

Well i wrote the BSOD error message down now and it says 0x00000116

i followed your instruction and i changed the BSOD settings to Small Memory Dumps

My drivers are the newest ones available but it's possible that something went wrong when i installed them but that was 4 months ago though and the BSOD problems started to occur only a week ago.

I will install the drivers again tomorrow when i have more time.

and i made new ZIP with the DM log collector if that helps.

Thank you

 

[essenbe]

Dyybe, I looked at the dump file and it said that your graphics driver crashed but did not recover in the allotted time (TDR)

[COLOR=red]VIDEO_TDR_FAILURE[/COLOR] (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800c3da2a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003ecc848, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

I also saw a lot of errors from WLXTranscoder which I believe is a part of Windows Live Movie Maker. There seems to be several who are having the same problems. If you have any new software about the time this started, please advise me.

You are getting a lot of errors on a file I can find little about Nimi.exe and it comes from a program named Nimi Visuals, if you are familiar with that

Also, do you happen to have any Citrix software installed?

 

[Dyybe]

For some reason windows movie makers crashes when i try to import a MP4 video but after i used WINFF to convert it to MPEG then movie maker worked

Nimi visuals... i really don't remember installing anything like that and i can't find a program named like that on my computer.

and no i don't have any Citrix software installed

Thank you

 

[essenbe]

Check and make sure you have the latest version of Direct X How to install the latest version of DirectX

I have seen a couple of reports that if you have a card that only has Direct X 9 and import a MPEG into Windows Movie Maker. Movie Maker will not start or will crash. Your card should support direct X 11 I believe, but checking won't hurt.

 

[Dyybe]

Hello again

I followed your instructions and uninstalled my drivers and then re-installed them but now the game crashing is even more frequent

I also took out my GPU and cleaned but that didn't really do anything...

My GPU temperatures are also normal, 60C when i'm playing so that shouldn't be a problem either

and i made a new ZIP with the DM log collector too if that helps.

 

[essenbe]

The only dump file in the files you uploaded was 022315. The latest error in your MSinfo file was on 3/25/15 and was WXLTranscode which I believe is a Windows Live element.

The files you uploaded today appear to be the same as you uploaded last time. Please make sure your computer is configured for Small Memory Dumps. http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

 

[Dyybe]

it is configured for Small Memory Dumps

My computer BSOD twice today so kinda it's odd that the dumb file doesn't have anything new...

i attached a picture, it's in Finnish but the settings should be correct

 

[essenbe]

here is about all I know we can do to get it to create Minidump files.

Follow these steps:

1. Configure Windows to create minidumps:
Dump Files - Configure Windows to Create on BSOD

2. Set the paging file on C: to be the same size as the physically installed RAM:
Virtual Memory Paging File - Change

3. Set the Windows Error Reporting service to MANUAL:
Services - Start or Disable

This image has been resized. Click this bar to view the full image. The original image is sized 715x414 and weights 83KB.

4. Test to see that dump files are created:
- Open Windows Task Manager
- Navigate to the Processes tab
- Right-click on explorer.exe, and click Create Dump File

This image has been resized. Click this bar to view the full image. The original image is sized 800x501 and weights 244KB.

- Note the location of the saved file

- Check that location and confirm that explorer.dmp exists

This image has been resized. Click this bar to view the full image. The original image is sized 767x406 and weights 56KB.

 

[Dyybe]

Okay i followed you instruction and yes explorer.dmp exists

 

[essenbe]

OK, I guess we will have to wait for another BSOD and see if it worked.

 

[Dyybe]

Okay the explorer.dmp exists now

 

[essenbe]

Ok, what you uploaded is the same as before. Let's just wait for the next BSOD and see if it writes it to disk.