BSOD Errors: 0x0000001E - 0x000000C1 - 0x00000024 And so on

See how old the driver is.

Code:

fffff880`09220000 fffff880`093b3000   Dnetr28ux T (no symbols)           
    Loaded symbol image file: Dnetr28ux.sys
    Image path: \SystemRoot\system32\DRIVERS\Dnetr28ux.sys
    Image name: Dnetr28ux.sys
    Timestamp:        Thu Apr 28 11:48:18 2011 (4DB906AA)
    CheckSum:         00193FD2
    ImageSize:        00193000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If that is the latest one, you need to stop using that adapter and get a new one.

BTW, you want more errors? If so, ANOD Network Security Filter Driver is also failing.

Code:

fffff800`00b9b578  fffff880`03f7b9c2Unable to load image \SystemRoot\system32\DRIVERS\anodlwfx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for anodlwfx.sys
*** ERROR: Module load completed but symbols could not be loaded for anodlwfx.sys
 anodlwfx+0x19c2

And that is too old.

Code:

fffff880`03f7a000 fffff880`03f83000   anodlwfx T (no symbols)           
    Loaded symbol image file: anodlwfx.sys
    Image path: \SystemRoot\system32\DRIVERS\anodlwfx.sys
    Image name: anodlwfx.sys
    Timestamp:        Fri Mar 06 15:40:08 2009 (49B0F680)
    CheckSum:         0000A8C3
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I would suggest to uninstall those.

Intel USB3 Drivers are failing, too.

Code:

fffff800`00b9c680  fffffa80`0ed28402
fffff800`00b9c688  fffff880`09056b36Unable to load image \SystemRoot\system32\DRIVERS\iusb3hub.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3hub.sys
 iusb3hub+0x18b36
--------------------------------------------------------------------------------------------
fffff800`00b9bd30  fffff880`05589f60Unable to load image \SystemRoot\system32\DRIVERS\iusb3xhc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
 iusb3xhc+0x79f60

But those are not very old.

Code:

fffff880`05510000 fffff880`055d3000   iusb3xhc T (no symbols)           
    Loaded symbol image file: iusb3xhc.sys
    Image path: \SystemRoot\system32\DRIVERS\iusb3xhc.sys
    Image name: iusb3xhc.sys
    Timestamp:        Fri Mar 29 18:06:19 2013 (51558AC3)
    CheckSum:         000C59AC
    ImageSize:        000C3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

So it seems to be the port error where the DLink adaptor is connected .... which is old. Still, dont take a chance ... search for updates in https://downloadcenter.intel.com/default.aspx

Got enough of errors? Happy now?

The process of troubleshooting is one by one ..... and the DLInk is the prima facie issue, which should be dealt with at first. So I wanted to concentrate on it only at first.

Your crash dumps are not showing any finite probable cause.

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 the memtest results free from errors, 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. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
__________________________________________________________________________
BSOD ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5002, fffff70001080000, 3283, 107137fffffffe}

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

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005002, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000003283
Arg4: 00107137fffffffe

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8604e6d798, 0, fffff80002c8e6eb, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+27f )

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

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8604e6d798, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002c8e6eb, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

Five verifier enabled minidumps ... and 4 different situations.

Code:

BugCheck BE, {fffff8a016634774, a0d00003664dd321, fffff88008d6b0d0, c}

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

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

Code:

BugCheck 4E, {2, 204eef, 42efff, 1240}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1d9 )

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

Code:

BugCheck 4E, {2, 24595f, 42efff, 800}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b )

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

Code:

BugCheck C1, {180229f600000000, 1000, 0, 81}

Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+11f )

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

Code:

BugCheck C1, {fffff98018dd6ee0, fffff98018dd60a9, ab0118, 23}

Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+9a )

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

It cannot be a driver error. It is hardware error. Better you ask for RMA the computer/motherboard.

On what date have you changed the board?

Have you performed a clear reinstall on it?

It is showing a stop 0x3B, which is very common in nature, but very difficult to identify the source.

I think it is better to go for a clean reinstall.