BSOD playing games and recording

halppl0x said:

Could you recommend me a free antivirus?

Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

That is the best free protection.

The zip you uploaded does not contain any crash dump.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

halppl0x said:

Should I be forcing it using the driver verifier?

When I run thatmy computer bluescreens right after the windows logo, and I have to system restore.

Let us see a BSOD in the normal situation at first, then if it is needed, we will definitely use verifier. But only in need ..... verifier is not for using abruptly.

Now it feels bad to me .... even a clean install cannot do anything good there.

Will spend a couple of attempts on the driver issues .... here is the first .....

Code:

fffff880`0753e208  fffff880`110cc920Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0x3b920

Uninstall the installed display driver using Display Driver Uninstaller. Then install the CCC 14.4 WHQL only.

See how it goes. Report us for the next BSOD.
__________________________________________________

Code:

BugCheck 19, {3, fffffa800696c670, fffffa800696c670, ffeba96cffd79a60}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

Now try driver verifier .... but dont forget to create a system restore point before doing it.

Code:

BugCheck 50, {fffffb9ee64e712b, 0, fffff80002e75265, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+52b )

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