Problemas pantalla azul

Estoy teniendo problemas con la pantalla azul de windows 7 y se me reinicia el pc, no se cual es el motivo, ni puedo leer la pantalla azul por que es ilegible pero consegui el log , que les paso a copiar aqui. Por favor ayudenme a ver cual es el problema con mi pc.

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x8280f000 PsLoadedModuleList = 0x82959850
Debug session time: Thu Jul 31 20:51:45.202 2014 (UTC - 4:00)
System Uptime: 0 days 2:01:38.545
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00008884, The subtype of the bugcheck.
Arg2: 8451554c
Arg3: 843bc968
Arg4: 00000502

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

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

BUGCHECK_STR: 0x1a_8884

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 828d41d2 to 828edf20

STACK_TEXT:
8ce8fa74 828d41d2 0000001a 00008884 8451554c nt!KeBugCheckEx+0x1e
8ce8faa8 82837d2d 00000002 8514c000 8ce8fbac nt!MiRelinkStandbyPage+0x8b
8ce8fad4 82a8fe82 00000100 8514d050 af4d4823 nt!MmSetPfnListPriorities+0x15a
8ce8fb20 82a53fe7 82a40d01 af4d48e3 0000004f nt!PfpPfnPrioRequest+0x61
8ce8fbe0 82a5fcd2 0126ef1c 00000014 82a40d01 nt!PfSetSuperfetchInformation+0x176
8ce8fd20 8284d1ea 0000004f 00000000 00000014 nt!NtSetSystemInformation+0xbdd
8ce8fd20 76f870b4 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0126ce0c 00000000 00000000 00000000 00000000 0x76f870b4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRelinkStandbyPage+8b
828d41d2 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiRelinkStandbyPage+8b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78a09

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x1a_8884_nt!MiRelinkStandbyPage+8b

BUCKET_ID: 0x1a_8884_nt!MiRelinkStandbyPage+8b

Followup: MachineOwner




-----------------------------------------------------------------------------------------------
ESTE ES OTRO REPORTE


KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 8908e4c6, The address that the exception occurred at
Arg3: b1957a14, Trap Frame
Arg4: 00000000

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

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

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

FAULTING_IP:
Wdf01000!FxIoQueue::GetCallbackLockPtr+12
8908e4c6 8902 mov dword ptr [edx],eax

TRAP_FRAME: b1957a14 -- (.trap 0xffffffffb1957a14)
ErrCode = 00000002
eax=84e8e118 ebx=84dae048 ecx=84dae048 edx=7b18aa58 esi=84e755a0 edi=84e8e118
eip=8908e4c6 esp=b1957a88 ebp=b1957a88 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
Wdf01000!FxIoQueue::GetCallbackLockPtr+0x12:
8908e4c6 8902 mov dword ptr [edx],eax ds:0023:7b18aa58=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: adb.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 92f9ca1a to 8908e4c6

STACK_TEXT:
b1957a88 92f9ca1a 7b18aa58 00000004 00000010 Wdf01000!FxIoQueue::GetCallbackLockPtr+0x12
WARNING: Stack unwind information not available. Following frames may be wrong.
b1957ac8 92f9cd17 7b18aa58 00000004 00000010 motoandroid+0xa1a
b1957b04 89037ed3 7b251fb0 7b18aa58 00000004 motoandroid+0xd17
b1957b44 890379d4 7b18aa58 b1957b8c 84e755a0 Wdf01000!FxIoQueue::DispatchRequestToDriver+0x3c0
b1957b64 8903d397 84dae000 00000000 84dae048 Wdf01000!FxIoQueue::DispatchEvents+0x4af
b1957b84 89037509 84dae000 84e755a0 84e84f3c Wdf01000!FxIoQueue::QueueRequest+0x204
b1957bb8 8903a52e 84eda488 84de23d8 84eda488 Wdf01000!FxPkgIo::Dispatch+0x3ba
b1957be0 8903a39f 84de23d8 84eda488 84e8d188 Wdf01000!FxDevice::Dispatch+0x155
b1957bfc 82a48c1e 84de23d8 84eda488 84eda488 Wdf01000!FxDevice::DispatchWithLock+0x77
b1957c14 82c3cc09 84e8d188 84eda488 84eda5f4 nt!IofCallDriver+0x63
b1957c34 82c3fdf2 84de23d8 84e8d188 00000000 nt!IopSynchronousServiceTail+0x1f8
b1957cd0 82c86789 84de23d8 84eda488 00000000 nt!IopXxxControlFile+0x6aa
b1957d04 82a4f8c6 000000cc 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
b1957d04 771d70f4 000000cc 00000000 00000000 nt!KiSystemServicePostCall
01d3fdc8 00000000 00000000 00000000 00000000 0x771d70f4


STACK_COMMAND: kb

FOLLOWUP_IP:
motoandroid+a1a
92f9ca1a ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: motoandroid+a1a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: motoandroid

IMAGE_NAME: motoandroid.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 51520206

FAILURE_BUCKET_ID: 0x8E_motoandroid+a1a

BUCKET_ID: 0x8E_motoandroid+a1a

Followup: MachineOwner



Ayudenme!!!