BSOD usually while playing KSP

[CriminalJelly]

Hi,
Recently my PC has been jibbing out while I have been playing video games, mainly Kerbal Space Program. Originally I thought that it might be a recent update to the game so rolled it back to a "previous stable release", but that hasn't solved anything.

I don't know where to begin to identify the problem. Can anyone offer a solution or best course of action please?
Thanks

 

[ICIT2LOL]

Hello and welcome CJ sorry for the wait. Now your dumps do contain some stuff that frankly has me scratching around.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, fffff88002fd5180, 3}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002fd5180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.
Debugging Details:
------------------

BUGCHECK_STR:  [COLOR=red]CLOCK_WATCHDOG_TIMEOUT_4_PROC[/COLOR]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  [COLOR=red]svchost.exe[/COLOR]
CURRENT_IRQL:  d
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`0af6e188 fffff800`02b31e4a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02fd5180 : nt!KeBugCheckEx
fffff880`0af6e190 fffff800`02ae5267 : 03000000`00000000 fffff800`00000003 00000000`00002710 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`0af6e220 fffff800`02a29895 : fffff800`02a4f460 fffff880`0af6e3d0 fffff800`02a4f460 fffff880`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0af6e320 fffff800`02ad6f93 : 00000000`6301c595 fffff800`02c5ae80 00000027`00000034 fffffa80`06faabfc : hal!HalpHpetClockInterrupt+0x8d
fffff880`0af6e350 fffff800`02ae0576 : fffff800`02c5ae80 64536553`00000001 00000000`00000000 fffff880`0af6e5e8 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0af6e4e0 fffff800`02afadc1 : 00000000`00000000 00000000`00000008 00000000`00000001 fffff8a0`1095e1d0 : nt!KeFlushMultipleRangeTb+0x266
fffff880`0af6e5b0 fffff800`02afd7f8 : 00000000`00000008 fffff880`0af6e700 fffff8a0`118b5000 00000000`00000001 : nt!MiFlushTbAsNeeded+0x1d1
fffff880`0af6e6c0 fffff800`02c0ff86 : 00000000`00008000 fffffa80`06f9d000 00000000`00000009 fffff800`02add2aa : nt!MiAllocatePagedPoolPages+0x4cc
fffff880`0af6e7e0 fffff800`02afb520 : 00000000`00008000 fffffa80`06f9d000 00000000`00000009 20206553`02ade802 : nt!MiAllocatePoolPages+0x906
fffff880`0af6e920 fffff800`02c1344e : 00000000`00000000 fffffa80`0ab35a60 00000000`00000000 00000000`00008000 : nt!ExpAllocateBigPool+0xb0
fffff880`0af6ea10 fffff800`02aeeac6 : 00000000`00000000 00000000`00000009 fffff8a0`00dae060 fffff800`02dc608b : nt!ExAllocatePoolWithTag+0x82e
fffff880`0af6eb00 fffff800`02d45ff6 : 00000000`00000000 00000000`00008000 00000000`00000000 00000000`00000001 : nt!ExAllocatePoolWithQuotaTag+0x56
fffff880`0af6eb50 fffff800`02d9dcbc : fffff8a0`101c5b60 fffff800`00008000 fffff880`0af6ec01 fffff800`02faeda0 : nt!PiControlGetInterfaceDeviceList+0x92
fffff880`0af6ebd0 fffff800`02ad9cd3 : fffffa80`0d178b50 00000000`010bedd0 fffff880`0af6eca0 00000000`010bee58 : nt!NtPlugPlayControl+0x100
fffff880`0af6ec20 00000000`77c2ec2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`010bed98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c2ec2a

STACK_COMMAND:  kb
SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME:  Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP:  0
IMAGE_VERSION:  
FAILURE_BUCKET_ID:  [COLOR=red]X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE[/COLOR]
BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_clock_watchdog_timeout_4_proc_analysis_inconclusive
FAILURE_ID_HASH:  {d61e255a-5a6a-8ac9-10f0-973c0c42bda6}
Followup: MachineOwner

What I can suggest is that you run these if you haven't already and check the temps on the machine with Speccy.
https://www.piriform.com/speccy/download


http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/433-disk-check.html< if necessary include the /f and /r in the command line as per Option2

Your first dump has some references to a DirectX MMS that is related to a Windows update and I would try to find the latest one and uninstall it and see what goes.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************[/FONT]
[FONT="Arial"]ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8a011a5e2d2, Virtual address for the attempted execute.
Arg2: d150000235d7b963, PTE contents.
Arg3: fffff88003367770, (reserved)
Arg4: 0000000000000002, (reserved)[/FONT]
[FONT="Arial"]Debugging Details:
------------------[/FONT]
[FONT="Arial"]
CUSTOMER_CRASH_COUNT:  1[/FONT]
[FONT="Arial"]DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT[/FONT]
[FONT="Arial"]BUGCHECK_STR:  0xFC[/FONT]
[FONT="Arial"]PROCESS_NAME:  System[/FONT]
[FONT="Arial"]CURRENT_IRQL:  0[/FONT]
[FONT="Arial"]ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre[/FONT]
[FONT="Arial"]TRAP_FRAME:  fffff88003367770 -- (.trap 0xfffff88003367770)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a011a6af08 rbx=0000000000000000 rcx=fffff8a011a6ab60
rdx=fffff8a011a6ae50 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8a011a5e2d2 rsp=fffff88003367908 rbp=fffff8a011a6ae50
 r8=00000000c01e0101  r9=0000000000000000 r10=fffff8a006afe000
r11=0000000000000007 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fffff8a0`11a5e2d2 53              push    rbx
Resetting default scope[/FONT]
[FONT="Arial"]LAST_CONTROL_TRANSFER:  from fffff80002b508cf to fffff80002ad4a40[/FONT]
[FONT="Arial"]STACK_TEXT:  
fffff880`03367608 fffff800`02b508cf : 00000000`000000fc fffff8a0`11a5e2d2 d1500002`35d7b963 fffff880`03367770 : nt!KeBugCheckEx
fffff880`03367610 fffff800`02ad2b6e : 00000000`00000008 fffff8a0`11a5e2d2 fffff8a0`054eef00 00000000`c01e0116 : nt! ?? ::FNODOBFM::`string'+0x4189c
fffff880`03367770 fffff8a0`11a5e2d2 : fffff880`0561eb83 00000000`0000004a 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`03367908 fffff880`0561eb83 : 00000000`0000004a 00000000`00000000 00000000`00000001 fffffa80`00000000 : 0xfffff8a0`11a5e2d2
fffff880`03367910 fffff880`056387d9 : 00000000`00000000 fffff8a0`00268170 fffffa80`00000000 fffffa80`07965310 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xfcb
fffff880`03367ae0 fffff880`05638514 : fffff880`02f68f40 fffff880`05637f00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`03367cd0 fffff880`05638012 : 00000000`00000000 fffffa80`0c2125e0 00000000`00000080 fffffa80`0b9f5410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`03367d00 fffff800`02d6eaba : 00000000`01c5b4e7 fffffa80`0aa31b50 fffffa80`07029040 fffffa80`0aa31b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`03367d40 fffff800`02ac6426 : fffff880`02f64180 fffffa80`0aa31b50 fffff880`02f6efc0 fffff880`03367e40 : nt!PspSystemThreadStartup+0x5a
fffff880`03367d80 00000000`00000000 : fffff880`03368000 fffff880`03362000 fffff880`03367680 00000000`00000000 : nt!KiStartSystemThread+0x16[/FONT]
[FONT="Arial"]
STACK_COMMAND:  kb[/FONT]
[FONT="Arial"]FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+fcb
fffff880`0561eb83 4883a5c000000000 and     qword ptr [rbp+0C0h],0[/FONT]
[FONT="Arial"]SYMBOL_STACK_INDEX:  4[/FONT]
[FONT="Arial"]SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+fcb[/FONT]
[FONT="Arial"]FOLLOWUP_NAME:  MachineOwner[/FONT]
[FONT="Arial"]MODULE_NAME: dxgmms1[/FONT]
[FONT="Arial"]IMAGE_NAME:  [COLOR=red]dxgmms1.sys[/COLOR][/FONT]
[FONT="Arial"]DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13[/FONT]
[FONT="Arial"]IMAGE_VERSION:  6.1.7601.18126[/FONT]
[FONT="Arial"]FAILURE_BUCKET_ID:  X64_0xFC_dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+fcb[/FONT]
[FONT="Arial"]BUCKET_ID:  X64_0xFC_dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+fcb[/FONT]
[FONT="Arial"]ANALYSIS_SOURCE:  KM[/FONT]
[FONT="Arial"]FAILURE_ID_HASH_STRING:  [COLOR=red]km:x64_0xfc_dxgmms1!vidmm_global::preparedmabuffer+fcb[/COLOR][/FONT]
[FONT="Arial"]FAILURE_ID_HASH:  {4dc4497d-686e-53c4-63ba-2a59e59e8002}[/FONT]
[FONT="Arial"]Followup: MachineOwner