BSoD while playing games.

[CJN]

BSoD while playing games (0x000000101)

Hello guys and girls.

I recently had a new system built by my friend and it was running perfect for a day, then out of no where I started getting random BSoD during game-play.

Here is an image:

I have made a .zip file containing information about my PC system. If you don't mind having a look, I would be grateful!

All the parts on this build are brand new. And yes it is OC'd on the i5 to 4.6ghz. (maybe/probably the cause)

Regards,

CJN.

 

[marsmimar]

Hello CJN and welcome to Seven Forums.

I think OCing an i5 to 4.6 is pushing things a bit. Until you can get a handle on the BSODs, I'd suggest restoring default values. The stop error 0x101 is also known as a CLOCK_WATCHDOG_TIMEOUT. Very difficult to troubleshoot. One of the best troubleshooting guides I've seen is here:

http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88003165180, 2}

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: fffff88003165180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0b882048 fffff800`02cf3d5a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03165180 : nt!KeBugCheckEx
fffff880`0b882050 fffff800`02ca6ad7 : fffff880`00000000 fffff800`00000002 00000000`00002710 00000001`00000001 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0b8820e0 fffff800`03210895 : fffff800`03236460 fffff880`0b882290 fffff800`03236460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0b8821e0 fffff800`02c99513 : 00000000`53eaf1c5 fffff800`02e0fe80 00000000`0000001d fffff880`02f055cc : hal!HalpHpetClockInterrupt+0x8d
fffff880`0b882210 fffff800`02ca1de6 : fffff800`02e0fe80 fffff8a0`00000001 00000000`00000000 fffff880`0b8824a8 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0b8823a0 fffff800`02cbc5f1 : 00000000`00000000 00000000`00000008 00000000`00000001 fffff800`02efa8ae : nt!KeFlushMultipleRangeTb+0x266
fffff880`0b882470 fffff800`02cbf038 : 00000000`00000008 fffff880`0b8825c0 fffff8a0`15480000 00000000`00000001 : nt!MiFlushTbAsNeeded+0x1d1
fffff880`0b882580 fffff800`02dc5f86 : 00000000`00008000 fffffa80`0608c000 00000000`00000009 fffff800`02c9fe7a : nt!MiAllocatePagedPoolPages+0x4cc
fffff880`0b8826a0 fffff800`02cbcd50 : 00000000`00008000 fffffa80`0608c000 00000000`00000009 20206553`02c92a32 : nt!MiAllocatePoolPages+0x906
fffff880`0b8827e0 fffff800`02dc890e : 00000000`00000000 00000000`0a14e090 00000000`00000000 00000000`00008000 : nt!ExpAllocateBigPool+0xb0
fffff880`0b8828d0 fffff800`02cb02f6 : 00000000`00000000 00000000`00000009 fffff8a0`06ddb380 fffff800`02f8459f : nt!ExAllocatePoolWithTag+0x82e
fffff880`0b8829c0 fffff800`02f042d2 : 00000000`00000000 00000000`00008000 00000000`00000000 00000000`00000001 : nt!ExAllocatePoolWithQuotaTag+0x56
fffff880`0b882a10 fffff800`02f5d1a0 : fffff8a0`140f2530 fffff800`00008000 fffff880`0b882b01 fffff800`03164da0 : nt!PiControlGetInterfaceDeviceList+0x92
fffff880`0b882a90 fffff800`02c9c253 : fffffa80`0c12a5a0 00000000`0101ec10 fffff880`0b882b60 00000000`0101ec98 : nt!NtPlugPlayControl+0x100
fffff880`0b882ae0 00000000`76e5236a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0101ebd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e5236a


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner

 

[CJN]

Thanks for your reply.

Since my original post I have lowered my OC on the i5 to 4.20 Ghz.

My system has since been running great and currently getting 7.8 on Windows Index Score.

Happy days!

 

[marsmimar]

Sounds like you may have found the magic fix. If any other issues occur please post back.

 

[CJN]

Sounds like you may have found the magic fix. If any other issues occur please post back.

I sure will! Thanks again.