BSOD playing games (0x1E/A/C5/F3...)

[GTDjulian]

Hey, just like a month ago I started having these blue screen every time I'm in the middle of a game (rarely while using Firefox too).
Errors that had at first were 0xA and 0xF3. I was reading some posts on this site about error codes that I have had, this means running memory tests with no errors, Furmark test, chkdsk and updating drivers (I did it with the help of Driver Identifier and Windows Update too) but dumps weren't solved .Instead, now I have errors like: 0xC5 ,0x1E ,0x3B ,0xD1 and sometimes it indicates .sys files but I have no idea about what to do.
The games I use to play are WoT (minimal graphics), Battlefield 2, Postal 2, etc. not big deal i guess...also there is good ventilation if you are thinking of high temperatures.
If there is any info you want to, let me know.

There is a .png too of Microsoft's Reliability Monitor (sorry for spanish)

 

[essenbe]

Hello, GTDjulian welcome to the forums. I am continuing to look at your files. In the meantime, please run a full scan with these

Scan with Kaspersky TDSSKiller:
Anti-rootkit utility TDSSKiller
Anti-rootkit utility TDSSKiller
ESET online scanner:
Free Virus Scan | Online Virus Scanner from ESET
Free Online Virus Scanner | ESET
Superantispyware
SUPERAntiSpyware | Remove Malware | Remove Spyware - AntiMalware, AntiSpyware, AntiAdware!
Malwarebytes Free
https://www.malwarebytes.org/downloads/
During the installation process of Malwarebytes, uncheck the 'start free trial'. Use it as an on demand scanner

If you are overclocking anything on your system, set everything back to default values.

 

[essenbe]

Here are your dump files so far

Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88005696975, fffff8800abec740, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+6f975 )

nt!KiKernelCalloutExceptionHandler+e
fffff800`0346e2be 90              nop
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
IMAGE_VERSION:  6.1.7601.18869
[COLOR=red]MODULE_NAME: hardware[/COLOR]
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
BUCKET_ID:  X64_IP_MISALIGNED

Use !analyze -v to get detailed debugging information.
BugCheck D1, {77357f27, 2, 0, fffff8800426e534}
[COLOR=red]Probably caused by : hardware ( USBPORT!USBPORT_AssertListEntryLog+24 )[/COLOR]
Followup: MachineOwner

Use !analyze -v to get detailed debugging information.
BugCheck D1, {ffffffffffffff8b, 2, 0, fffff88003e11dd4}
*** WARNING: Unable to verify timestamp for spom.sys
*** ERROR: Module load completed but symbols could not be loaded for spom.sys
[COLOR=red]Probably caused by : spom.sys[/COLOR] ( spom+424ce )
Followup: MachineOwner

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa803860c0a1, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880043bbed3, address which referenced memory

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800034f4fd8, Address of the instruction which caused the bugcheck
Arg3: fffff88007f56cd0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

For right now, please update all of your motherboard drivers from the Asus Web site for your board. Especially the Chipset driver and the Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC. Also make sure all of your Windows updates are currently up to date.

 

[GTDjulian]

Well, the scans cleaned a couple of threats but they did not solve the problem. Regarding the drivers, could you tell me where to find them? Thanks for the help

 

[essenbe]

Make sure this is your Motherboard. All of your drivers should be able to be found here GIGABYTE - Motherboard - Socket AM2+ - GA-MA78GM-US2H (rev. 1.0)

 

[GTDjulian]

Drivers updated...but windows still crashing, maybe i'm doing something wrong...
Do you need a new dump report?

P.D: atikmdag.sys causes seems to be more frecuent now and appear mostly when I play games

 

[essenbe]

Sure, we'll try it.

 

[GTDjulian]

ok, here it is

 

[essenbe]

Ok, here are the last 2 Dump Files

Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc000001d, fffff8000349e0b4, 2, fffffff00}
[COLOR=red]Probably caused by : memory_corruption[/COLOR] ( nt!MiDispatchFault+3f4 )
Followup: MachineOwner

Use !analyze -v to get detailed debugging information.
BugCheck C5, {18000000408, 2, 0, fffff800035b4b15}
[COLOR=red]Probably caused by : Pool_Corruption[/COLOR] ( nt!ExDeferredFreePool+249 )
Followup: Pool_corruption

Ok, you have run all the Virus scans I asked you to and uninstalled any Gigabyte Utilities and updated all of your Drivers? If so,

Please Run Memtest86+​

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask.

Also run Seatools for DOS on your WD Hard Drive http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part2

 

[GTDjulian]

Well, [FONT=&quot]recently appeared this "unknown device" within the storage controllers[FONT=&quot].[/FONT] Could this be the reason for any failure?[FONT=&quot] Also[FONT=&quot], [/FONT][/FONT][/FONT][FONT=&quot]I should mention that I reinstalled the Daemon Tools as there are people who advise this[/FONT], [FONT=&quot]and then appeared this unknown device[FONT=&quot] but [/FONT][/FONT]I don't know what could be the reason, I tried reconnecting the wires or update the driver, but will not let me. Besides the memory test, [FONT=&quot]is there something else I should do with this device?[/FONT]

 

[essenbe]

Your 'Unknown Device' is the Dameon tools I asked you to install. You have an Operating Systen with an OEM_SLP key. That is only good on the Acer/Gateway computer it came from the factory installed on. You have it installed on a Gigabyte Retail Motherboard, which can not be legal. The only way it could possibly be activated is by a hackers exploit which alters system files.

Counterfeit installations such as yours contain heavily modified code that causes the installation to behave it unexpected ways. Analyzing BSOD's and determining their causes on these sorts of installations is very unreliable. For this reason, many analysts won't attempt it.

My recommendation is to install a genuine Windows 7. This will minimize the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a Genuine Windows 7 installation, and are still experiencing BSOD's, we will be happy to help you solve them