bsod round 2

Hi there!

I can't understand why you tell us that kind of thing. But I will help you anyway because I don't want other people to misunderstood us. But as we serve you voluntarily, perhaps you can give us a little respect my friend :)

First of all, all of your stop codes are somehow suggest 3rd party antivirus are causing all of these. Please remove Norton/Symantec antivirus completely to see if the problem is solved.
Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

Install MSE instead:
Security Essentials Software Support | Microsoft Security Essentials

Code:

BugCheck 3B, {c0000005, fffff960001176fa, fffff8800932fb90, 0}

Probably caused by : win32k.sys ( win32k!RFONTOBJ::bMakeInactiveHelper+2e )

Followup: MachineOwner
---------
BugCheck 50, {fffff8a80476c008, 0, fffff80002d425d1, 5}


Could not read faulting driver name
Probably caused by : discache.sys ( discache!DisCreateObjectAttributeStore+ec )

Followup: MachineOwner
---------
BugCheck A, {fffffa8004a83090, 2, 0, fffff80002a7868b}

Probably caused by : memory_corruption ( nt!MiResolveMappedFileFault+8b )

Followup: MachineOwner
---------
BugCheck 1A, {41287, 0, 0, 0}

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

Followup: MachineOwner
---------
BugCheck 50, {fffff68004001a70, 0, fffff80002acd2e2, 2}


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

Followup: MachineOwner
---------
BugCheck 1A, {41284, fffff980082b6001, 3b5e, fffff780c0000000}

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

Followup: MachineOwner
---------
BugCheck 50, {fffffd7fffffffeb, 0, fffff80002a9e5ff, 7}


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

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

Run system file check please:
SFC /SCANNOW Command - System File Checker

Regard,

Tuan