Randomly BSOD on my new PC - win32k.sys (win32k+0xC4283)

Hello. Good Day to all. Permission to post. I just search for my problem and i didn't find any answers yet.

I'm receiving a BSOD several times i keep getting BSOD mostly when browsing with google chrome.

What i did so far :

-I just installed whocrashed and found an error (you can see it in the bottom).

-Reformat my PC (still no luck)

-Run memtest in 12 hrs and didn't find any error

-Update my video driver and fix 1 BSOD problem while playing games!

UPDATE: I just attached the sf diagnostic result.

My PC Specs :

-AMD FX-8320
-GIGABYTE 990 FXA-UD3
-8 GB 2x4 GSKILLS RIP JAW RAM
-ASUS DIRECT CU HD 7850 1GB 256BIT
-1 TB HDD WESTERN DIGITAL
-SEASONIC PSU 520W
-AEROCOOL STRIKE X ADVANCE WITH 3 FANS

*Please help me fix the BSOD it's really annoying my PC is one month old and i'm keep getting this

Thanks in advance!


Here's some result of Whocrashed :


[ALREADY FIX]

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 1/18/2014 6:29:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011714-17971-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x6CF9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000676CF9, 0xFFFFF88008AA0110, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


On Sat 1/18/2014 6:29:05 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cdd.dll (cdd+0x6CF9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000676CF9, 0xFFFFF88008AA0110, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



[DIDN'T FIX YET]

On Fri 1/17/2014 5:58:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011614-21200-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4283)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000D4283, 0xFFFFF8800896F060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[LATEST ERROR NEED HELP!]

On Sat 1/25/2014 7:56:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012514-21855-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8800177C58D)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF8800177C58D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


On Sat 1/25/2014 7:56:45 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netio.sys (NETIO!NetioUpdateNetBufferListContext+0xBCD)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF8800177C58D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

AODDriver2.sys Thu Sep 12 09:36:40 2013 (523136C8)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
Driver Reference Table - AODDriver2.sys

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from http://ati.amd.com (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Avira is contributing to your BSOD's. Please remove it and Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

Good and Free system security combination.

Download and install all updates including service pack 1: Learn how to install Windows 7 Service Pack 1 (SP1)

Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Run Disk Check on your Hard Drive(s): Disk Check

Reduce items at start-up: Startup Programs - Change

Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

Post screenshot(s) of your Hard Drive(s) using Crystal Disk Info Software: CrystalDiskInfo - Software - Crystal Dew World

Run a Hard Drive test: https://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html


Check for heating issues using Speccy or HWmonitor

Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums

Keep us posted.

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jan 26 01:56:45.276 2014 (UTC + 6:00)
System Uptime: 0 days 0:14:03.743
BugCheck D1, {8, 2, 0, fffff8800177c58d}
Probably caused by : NETIO.SYS ( NETIO!CalloutStreamDataInit+1d )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 18 12:29:05.591 2014 (UTC + 6:00)
System Uptime: 0 days 3:15:23.074
BugCheck 3B, {c0000005, fffff96000676cf9, fffff88008aa0110, 0}
Probably caused by : cdd.dll ( cdd+6cf9 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan 17 11:58:22.235 2014 (UTC + 6:00)
System Uptime: 0 days 4:22:50.718
BugCheck 3B, {c0000005, fffff960000d4283, fffff8800896f060, 0}
Probably caused by : win32k.sys ( win32k!HmgLockEx+a3 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``