BSOD playing online game, ntoskrnl.exe

[Khazbin]

Hello and thanks in advance to anyone that helps.

While playing an online game, Mabinogi to be exact, if that makes a difference, I've recently started getting BSODs ranging from as soon as the game boots up to 20 or so minutes into playing. I have played the game on this machine in the past with no problems whatsoever, not even lag.

The BSOD always claims that a clock interrupt was not received on a secondary processor in the allotted time.

I tried checking the dump files through Windbg to no real avail - for whatever reason it fails to read the symbols folder and redownloading the thing didn't help any, so I downloaded BlueScreenViewer and WhoCrashed, both of whom came up with the error being something to do with ntoskrnl.exe.

I've already tried doing a memtest, which went through 9 passes with 0 errors. I've reinstalled Windows 7, checked that all my drivers are up to date as far as I can tell, and also reinstalled the game. I don't know what else to try, so here I am. I'm somewhat tech savvy, but instructions on how to do whatever fixes you can think of would be greatly appreciated.

 

[koolkat77]

Hello Khazbin,

You could read this thread: http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\KHAZ-Sat_01_10_2015__85150_87\010915-33883-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0364b000 PsLoadedModuleList = 0xfffff800`0388e890
Debug session time: Sat Jan 10 08:14:36.359 2015 (UTC + 6:00)
System Uptime: 0 days 0:25:57.670
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {21, 0, fffff880009b3180, 4}

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: 0000000000000021, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b3180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_6_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Client.exe

CURRENT_IRQL:  d

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

STACK_TEXT:  
fffff880`09215528 fffff800`03717a4a : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`009b3180 : nt!KeBugCheckEx
fffff880`09215530 fffff800`036ca6f7 : 00000000`00000000 fffff800`00000004 00000000`00002710 fffffa80`0de30010 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`092155c0 fffff800`0360c895 : fffff800`03632460 fffff880`09215770 fffff800`03632460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`092156c0 fffff800`036bd113 : 00000000`1addd4fc fffff800`0383be80 fffff880`09216000 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
fffff880`092156f0 fffff800`036f6483 : fffff800`0383be80 fffff800`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`09215880 fffff800`036f53cd : 00000000`00000000 00000000`00000001 00000000`000007d3 00000000`00000001 : nt!KxFlushEntireTb+0x93
fffff880`092158c0 fffff800`037199b0 : 00000000`00000002 fffff680`00174000 00000000`00000001 00000000`74162450 : nt!KeFlushTb+0x119
fffff880`09215940 fffff800`036cd89d : fffffa80`0488dc30 fffff880`09215a00 00000000`0008e300 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xada2
fffff880`09215980 fffff800`036becee : 00000000`00000001 00000000`2e800000 00000000`00000001 00000000`3ad0fb68 : nt!MmAccessFault+0xa7d
fffff880`09215ae0 00000000`740eae7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0018a540 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x740eae7a


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:  X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_clock_watchdog_timeout_6_proc_analysis_inconclusive

FAILURE_ID_HASH:  {912a7e46-2f82-28ad-f0b8-e698db5bcf77}

Followup: MachineOwner
---------