Multiple BSOD on my PC

Code:

ID produktu:                         00426-OEM-8992662-00173 ==> ASUS OEM
Datum p…vodn¡ instalace:             10.12.2013, 20:28:14
¬as spuçtØn¡ syst‚mu:                11.6.2014, 12:26:48
Vìrobce syst‚mu:                     Gigabyte Technology Co., Ltd.

Hi pogasta.

You cannot have an ASUS license on a retail Gigabyte motherboard unless it is counterfeit; and stop 0x3B BSODs are most possible for a counterfeit installation.

Code:

BugCheck 3B, {c0000005, fffff800034c4504, fffff880094a88c0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+d4 )

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

Get a valid retail license from microsoft to activate your installation.

0X3B BSODs are often caused by system files corruptions. Counterfeit installations are not capable to get the updates properly, and some files are modified in it, too.

So if a stop 0x3B appears to a counterfeit installation, it is the first thing that is to be rectified.

The new one is a Memory Management BSOD.

Code:

BugCheck 1A, {41790, fffffa800b65f020, ffff, 0}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3a2 )

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

Either the RAM is causing issue or any driver passing bad info to the memory.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

After 14 hours of Memtest no error apeared. So i turned on Driver Verifier and my system crashed again after like 8 hours of running. BTW: I found out that PC usualy crash when I am watching streams (fullscreen) in my Google Chrome)

Disable driver verifier. It is not a driver issue.

Code:

BugCheck 1A, {41284, 3c485001, 7075, fffff70001080000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 )

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

STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel

Two possibilities are already minimized, and kernel errors should not be there after you clean installed with an original media and duly updated it.

Have you performed a clean reinstall to rectify the previous counterfeit installation?