Hello Nicholas1986,
I looked at both dumps.
The first dump was a stop 0x119 and appears to be caused by the video drivers:
STACK_TEXT:
83cf5970 907ca230 00000119 00000001 00003cff nt!KeBugCheckEx+0x1e
83cf5998 9072e0c0 00000000 0a000119 00000001 watchdog!WdLogEvent5+0x130
83cf59c4 9072a2fe 000010d7 00003cff 00000000 dxgkrnl!VidSchiVerifyDriverReportedFenceId+0x74
83cf59f8 9072a5c3 89c31000 83cf5b34 00000001 dxgkrnl!VidSchDdiNotifyInterruptWorker+0x15a
83cf5a14 8fe918bf 8916f968 83cf5b34 00000000 dxgkrnl!VidSchDdiNotifyInterrupt+0x68
WARNING: Stack unwind information not available. Following frames may be wrong.
83cf5b94 8fe906fe 8924e000 8917e34c c0000001 igdkmd32+0x888bf
83cf5bdc 8fe1d460 8924e000 00000000 00000000 igdkmd32+0x876fe <-- intel video driver
83cf5c24 9072a0f9 8924e000 00000000 83cf5c48 igdkmd32+0x14460
83cf5c34 83caf98d 89624a00 8916f968 00000000 dxgkrnl!DpiFdoMessageInterruptRoutine+0x17
83cf5c48 83c46ba1 89624a00 8916f968 00000000 nt!KiInterruptMessageDispatch+0x12
83cf5c48 84fee406 89624a00 8916f968 00000000 nt!KiInterruptDispatch+0x51
83cf5ce4 84fef34d 83cb0d86 892b09d0 83cfa790 intelppm+0x1406
83cf5cf8 83cb0cd4 892b5270 00000000 89729568 intelppm+0x234d <-- intel processor driver
83cf5d50 83ca8861 00000000 0000000e 00000000 nt!PoIdle+0x2d1
83cf5d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd
The second dump is exactly what Auggy described.
In addition to Auggy's suggestions, I would recommend updating the display driver as it is from 2008:
1: kd> lmvm igdkmd32
start end module name
8fe03000 904fc000 igdkmd32 (deferred)
Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
Image name: igdkmd32.sys
Timestamp: Thu Aug 14 12:15:01 2008 (48A46815)
Let us know if you have any questions.
Best regards,
Matthew_Ha