Random BSOD's, Page Fault Errors

Code:

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


Use !analyze -v to get detailed debugging information.


BugCheck 50, {fffffa00006f56d8, 0, fffff801c58228f2, 2}


*** WARNING: Unable to verify timestamp for bcmwl63a.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl63a.sys


Could not read faulting driver name
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : memory_corruption


Followup:     memory_corruption
---------


5: kd> lmvm bcmw163a
Browse full module list
start             end                 module name
5: kd> lmvm bcmwl63a
Browse full module list
start             end                 module name
fffff809`eced0000 fffff809`edb76000   bcmwl63a T (no symbols)           
    Loaded symbol image file: bcmwl63a.sys
    Image path: \SystemRoot\system32\DRIVERS\bcmwl63a.sys
    Image name: bcmwl63a.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri May 15 07:38:53 2015 (555515ED)
    CheckSum:         00AAC138
    ImageSize:        00CA6000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The problem seems to lie with an outdated broadcom adapter driver.

Check for an updated driver here, if you havent already done so:
Support

Alternatively, see if Windows Update offers to download an updated driver and use that instead.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa00006f56d8, 0, fffff801c58228f2, 2}

*** WARNING: Unable to verify timestamp for bcmwl63a.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl63a.sys

Could not read faulting driver name
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

5: kd> lmvm bcmwl63a
Browse full module list
start             end                 module name
fffff809`eced0000 fffff809`edb76000   bcmwl63a T (no symbols)           
    Loaded symbol image file: bcmwl63a.sys
    Image path: \SystemRoot\system32\DRIVERS\bcmwl63a.sys
    Image name: bcmwl63a.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri May 15 07:38:53 2015 (555515ED)
    CheckSum:         00AAC138
    ImageSize:        00CA6000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You need to double-check things. You are getting the same BSOD with exactly the same driver with exactly the same date.

You certainly have an issue with the network device/driver:

Code:

Event[16421]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2017-01-22T18:53:03.438
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: aniqpirzada
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xfffffc80006f56d8, 0x0000000000000000, 0xfffff800740978f2, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: acf716d7-8952-4603-a499-4a71653298fa.

Event[16422]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2017-01-22T18:52:59.469
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: aniqpirzada
  Description: 
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event[16423]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2017-01-22T18:52:59.470
  Event ID: 172
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: aniqpirzada
  Description: 
Connectivity state in standby: Disconnected, Reason: NIC compliance