Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD usually while playing KSP

25 Jun 2015   #1

Windows 7 Home Premium (64)
BSOD usually while playing KSP

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?

My System SpecsSystem Spec
27 Jun 2015   #2

Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10

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                                    *
*                                                                             *
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.
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:

PROCESS_NAME:  svchost.exe
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
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

FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME:  Unknown_Image
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.< 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                                    *
*                                                                             *
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.
Arg1: fffff8a011a5e2d2, Virtual address for the attempted execute.
Arg2: d150000235d7b963, PTE contents.
Arg3: fffff88003367770, (reserved)
Arg4: 0000000000000002, (reserved)
Debugging Details:

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
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
LAST_CONTROL_TRANSFER:  from fffff80002b508cf to fffff80002ad4a40
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

fffff880`0561eb83 4883a5c000000000 and     qword ptr [rbp+0C0h],0
SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+fcb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME:  dxgmms1.sys
IMAGE_VERSION:  6.1.7601.18126
FAILURE_BUCKET_ID:  X64_0xFC_dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+fcb
BUCKET_ID:  X64_0xFC_dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+fcb
FAILURE_ID_HASH_STRING:  km:x64_0xfc_dxgmms1!vidmm_global::preparedmabuffer+fcb
FAILURE_ID_HASH:  {4dc4497d-686e-53c4-63ba-2a59e59e8002}
Followup: MachineOwner

My System SpecsSystem Spec

 BSOD usually while playing KSP

Thread Tools

Similar help and support threads
Thread Forum
BSOD while playing videos or playing games (LoL) Error STOP : 0x00007A
Hello sevenforums Community, since about month im getting Bluescreens, which never happened before in 4 years. It usually get the when i watch streams on twitch (which didnt happen since 1 week on my account though) or currently while playing League of Legends. But they dont come every game, so...
BSOD Help and Support
BSOD playing some games/recently playing FIFA World
The title speaks for itself, i have dump files listed below, and i would really like to fix this problem. Thank you in advance.
BSOD Help and Support
BSOD playing too long, watching a video and playing a game or gmod
I get BSOD whenever I am on my computer for 6 hours or over, watching a video and playing a game, or while playing gmod in general. My comp specs are on my profile as best as I could get. My computer runs 68C 26% fanspeed when not playing any games and gets as hot as 86C when playing games. and my...
BSOD Help and Support
BSOD Whilst playing Browsing and Playing game's
Hi I'm new to this forum and was wondering if i could get some help or advice on what the problem might be the PC is only 3 months old and has had four recent blue screen errors over the time i have been using it and i was wondering if this is a hardware or system failure that i may need to...
BSOD Help and Support
BSOD on a daily basis, mostly when playing playing Heroes of Newerth.
Hello A few weeks ago I mounted a new hard drive that had data recovered from a damaged one. And since then I've been getting blue screens almost everyday. Prior to that the machine was working fine. I did not notice a specific time for it to happen, but generally when I am playing "Heroes of...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:39.
Twitter Facebook Google+