BSOD after wake from sleep

Both the crash dumps are pointing to NVIDIA High Definition Audio.

As you have onboard Realtek, you should not use ndidia audio. Let Realtek play the lead role there.

• Uninstall All nvidia items in Control Panel > Programs and features
  
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • GeForce Experience
  • PhysX
  • nvidia Update
  
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

For more details about a trouble free display driver installation, follow it: NVIDIA Drivers - Avoid Problems

Now wait and observe how the computer works. Let us know for any further BSOD.
___________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800598c696, fffff880035af388, fffff880035aebe0}

Probably caused by : nvhda64v.sys ( nvhda64v+25696 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800598c696, The address that the exception occurred at
Arg3: fffff880035af388, Exception Record Address
Arg4: fffff880035aebe0, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nvhda64v+25696
fffff880`0598c696 4c8b10          mov     r10,qword ptr [rax]

EXCEPTION_RECORD:  fffff880035af388 -- (.exr 0xfffff880035af388)
ExceptionAddress: fffff8800598c696 (nvhda64v+0x0000000000025696)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT:  fffff880035aebe0 -- (.cxr 0xfffff880035aebe0;r)
rax=0000000000000000 rbx=0000000000000001 rcx=fffffa800eda75a0
rdx=fffff88005979f48 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800598c696 rsp=fffff880035af5c0 rbp=fffff880035af630
 r8=0000000000000000  r9=0000000000000001 r10=0000000000000000
r11=0000000000000000 r12=fffffa800f1b0790 r13=fffffa800f1b0ca8
r14=0000000000000005 r15=fffffa800f1b07a0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nvhda64v+0x25696:
fffff880`0598c696 4c8b10          mov     r10,qword ptr [rax] ds:002b:00000000`00000000=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000001 rcx=fffffa800eda75a0
rdx=fffff88005979f48 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800598c696 rsp=fffff880035af5c0 rbp=fffff880035af630
 r8=0000000000000000  r9=0000000000000001 r10=0000000000000000
r11=0000000000000000 r12=fffffa800f1b0790 r13=fffffa800f1b0ca8
r14=0000000000000005 r15=fffffa800f1b07a0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nvhda64v+0x25696:
fffff880`0598c696 4c8b10          mov     r10,qword ptr [rax] ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034c1100
GetUlongFromAddress: unable to read from fffff800034c11c0
 0000000000000000 Nonpaged pool

FOLLOWUP_IP: 
nvhda64v+25696
fffff880`0598c696 4c8b10          mov     r10,qword ptr [rax]

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000001 to fffff8800598c696

STACK_TEXT:  
fffff880`035af5c0 00000000`00000001 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : nvhda64v+0x25696
fffff880`035af5c8 00000000`00000001 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : 0x1
fffff880`035af5d0 00000000`00000000 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvhda64v+25696

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvhda64v

IMAGE_NAME:  nvhda64v.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53cd2111

STACK_COMMAND:  .cxr 0xfffff880035aebe0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nvhda64v+25696

BUCKET_ID:  X64_0x7E_nvhda64v+25696

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_nvhda64v+25696

FAILURE_ID_HASH:  {891041bb-b6cd-437c-575f-bab8bce96f90}

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

6: kd> lmvm nvhda64v
start             end                 module name
fffff880`05967000 fffff880`0599b000   nvhda64v T (no symbols)           
    Loaded symbol image file: nvhda64v.sys
    Image path: \SystemRoot\system32\drivers\nvhda64v.sys
    Image name: nvhda64v.sys
    Timestamp:        Mon Jul 21 19:47:53 2014 (53CD2111)
    CheckSum:         0003B8CC
    ImageSize:        00034000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4