Getting BSOD when going to sleep

Hi All
I saw relevant questions about this problem but non of the solutions helped me.

I get Blue Screen Frequently (about 3 times per 5) when I press the sleep button and pc turns off.

I updated both my windows and drivers but didn't work.

This is my Dump File:

https://www.dropbox.com/s/ybbdmj3o4a...37-01.dmp?dl=0

Code:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03254000 PsLoadedModuleList = 0xfffff800`03497890
Debug session time: Thu Oct  9 07:18:18.309 2014 (UTC - 4:00)
System Uptime: 0 days 4:21:52.308
*******************************************************************************
*                                                                             *
*                        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: ffffffff80000003, The exception code that was not handled
Arg2: fffff800032c19d0, The address that the exception occurred at
Arg3: fffff8800dfb03f8, Exception Record Address
Arg4: fffff8800dfafc50, Context Record Address

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP: 
nt!DbgBreakPoint+0
fffff800`032c19d0 cc              int     3

EXCEPTION_RECORD:  fffff8800dfb03f8 -- (.exr 0xfffff8800dfb03f8)
ExceptionAddress: fffff800032c19d0 (nt!DbgBreakPoint)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 0000000000000000

CONTEXT:  fffff8800dfafc50 -- (.cxr 0xfffff8800dfafc50)
rax=0000000000000000 rbx=fffffa800936bab0 rcx=22158ab79d380000
rdx=0000000000000008 rsi=0000057ff5d213a8 rdi=fffffa800a2def90
rip=fffff800032c19d0 rsp=fffff8800dfb0638 rbp=fffff88000e262e0
 r8=0000000000000001  r9=fffff80003307090 r10=fffffffffffffffb
r11=fffff8800dfb0638 r12=0000000000000001 r13=0000000000000000
r14=fffffa800a2def90 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
nt!DbgBreakPoint:
fffff800`032c19d0 cc              int     3
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_PARAMETER1:  0000000000000000

LAST_CONTROL_TRANSFER:  from fffff88000e3b790 to fffff800032c19d0

STACK_TEXT:  
fffff880`0dfb0638 fffff880`00e3b790 : fffff880`00e26000 fffffa80`0ba7a040 fffff880`00e262e0 0000057f`f5d213a8 : nt!DbgBreakPoint
fffff880`0dfb0640 fffff880`00e3914d : ffffffff`dc3cba00 0000057f`f5d213a8 fffff880`0dfb06b0 fffffa80`0a2dec60 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x70
fffff880`0dfb0680 fffff880`00e45a6c : fffffa80`0a2dec50 0000057f`f5d21300 fffffa80`0a2defc0 fffffa80`0a2dec60 : Wdf01000!FxIoQueue::StopProcessingForPower+0x1ed
fffff880`0dfb06d0 fffff880`00e45f14 : 00000000`00000000 fffff880`0dfb0700 fffffa80`0a2d85f0 fffffa80`0a2d8ae0 : Wdf01000!FxPkgIo::StopProcessingForPower+0x22c
fffff880`0dfb0740 fffff880`00e45db5 : 00000000`00000004 00000000`00000000 fffff880`00000000 fffffa80`08b5d5d0 : Wdf01000!FxPkgPnp::PowerGotoDx+0x64
fffff880`0dfb0780 fffff880`00e3c0f8 : 00000000`0000031a fffff880`0dfb08b0 00000000`ffff7fff fffffa80`0a2d8ae0 : Wdf01000!FxPkgPnp::PowerGotoDNotZero+0x9
fffff880`0dfb07b0 fffff880`00e3bda6 : fffff880`00ebbf60 fffffa80`0a2d8c98 fffffa80`0a2d8ae0 fffffa80`0a2d8ae0 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1d8
fffff880`0dfb0910 fffff880`00e3c627 : 00000000`00000000 fffff880`0dfb09f0 fffffa80`0a2d8c80 fffffa80`0a2d8ae0 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`0dfb0980 fffff880`00e46dd3 : 00000000`00000000 fffffa80`0a2d8ae0 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1b3
fffff880`0dfb0a20 fffff880`00e286f2 : 00000000`00000002 0000057f`f5f8bf78 fffffa80`0a2d8670 fffffa80`08779402 : Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x117
fffff880`0dfb0a70 fffff880`00e2779a : fffffa80`08779430 fffffa80`08779430 fffffa80`08779430 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x2aa
fffff880`0dfb0ad0 fffff880`00e27866 : fffffa80`08779430 00000000`00000000 fffffa80`0a2d8670 fffffa80`0a2d8670 : Wdf01000!FxDevice::Dispatch+0x19a
fffff880`0dfb0b10 fffff800`033e5eb5 : 00000000`00000001 00000000`00000000 fffffa80`0a2d8670 fffffa80`087794d8 : Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880`0dfb0b50 fffff800`0356573a : ffffffff`fa0a1f00 fffffa80`0ba7a040 00000000`00000080 00000000`00000000 : nt!PopIrpWorker+0x3c5
fffff880`0dfb0c00 fffff800`032ba8e6 : fffff880`03365180 fffffa80`0ba7a040 fffffa80`087e7360 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0dfb0c40 00000000`00000000 : fffff880`0dfb1000 fffff880`0dfab000 fffff880`0dfb0390 00000000`00000000 : nt!KxStartSystemThread+0x16


FOLLOWUP_IP: 
Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
fffff880`00e3b790 488b442440      mov     rax,qword ptr [rsp+40h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Wdf01000

IMAGE_NAME:  Wdf01000.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51c51641

STACK_COMMAND:  .cxr 0xfffff8800dfafc50 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70

BUCKET_ID:  X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70

Followup: MachineOwner

Thanks.

Blue Screen of Death (BSOD) Posting Instructions

Attach the resulting files to your post in this forum, not link to an external hosting site.

Attachment 336114

There are some important files missing from the logs, please run the tool again until it is complete and upload the unedited logs in your next post.

The logs are still incomplete.