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 during starcraft 2


24 Aug 2011   #1

Windows 7 Ultimate x64
 
 
BSOD during starcraft 2

Hi guys, got hit by a BSOD during sc2. Attached dumps

My System SpecsSystem Spec
.

24 Aug 2011   #2

Windows 8.1 Pro x64
 
 

Seems that there is a problem with the CPU itself

Run Prime 95 to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results

According to your dump file the issue is with your Processor. This occurs when the processor is non-responsive or is deadlocked.

Possible Solutions :

a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust

But its mainly caused by a defective CPU or outdated BIOS

Details about this bugcheck:
http://www.sevenforums.com/crash-loc...tml#post567135

Win 7 A Clock Interrupt... BSOD (101 Error)
Code:
*******************************************************************************
*                                                                             *
*                        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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003aa5180, The PRCB address of the hung processor.
Arg4: 0000000000000005, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`05bd9f08 fffff800`036df8f9 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`03aa5180 : nt!KeBugCheckEx
fffff880`05bd9f10 fffff800`036924b7 : 00000000`00000000 fffff800`00000005 00000000`00002710 fffff880`04cf6b51 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`05bd9fa0 fffff800`03bfb895 : fffff800`03c21460 fffff880`05bda150 fffff800`03c21460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`05bda0a0 fffff800`03684233 : 00000000`9533b18e fffff800`037fae80 fffff800`037fae80 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`05bda0d0 fffff800`0368d7f8 : fffff800`037fae80 fffff880`00000001 00000000`00000000 fffff880`05bda378 : nt!KiInterruptDispatchNoLock+0x163
fffff880`05bda260 fffff800`03649086 : fffff6fc`500464d8 fffffa80`088b8b60 fffff800`038ba5c0 fffff8a0`181af846 : nt!KeFlushMultipleRangeTb+0x258
fffff880`05bda330 fffff800`03648c84 : fffff8a0`08c9a000 00000000`00000000 00000000`00000001 fffff8a0`00024000 : nt!MiProtectPool+0x3a6
fffff880`05bda460 fffff800`03924107 : 00000000`002e8000 00000000`00001740 00000000`00001000 fffff8a0`00000000 : nt!ExProtectPool+0x178
fffff880`05bda4d0 fffff800`03921885 : 00000000`00000008 00000000`00001747 fffff8a0`08c83054 00000000`00000004 : nt!HvpSetRangeProtection+0x12f
fffff880`05bda530 fffff800`0392165c : fffff8a0`00024010 fffff8a0`00024010 fffff8a0`00037d00 00000000`002e8a30 : nt!HvMarkDirty+0x176
fffff880`05bda590 fffff800`0393ad33 : 01cc2dc3`86f1fe04 fffff880`05bda940 fffff8a0`00174de8 00000000`00000000 : nt!HvMarkCellDirty+0x150
fffff880`05bda5e0 fffff800`0393b59a : fffff8a0`18779950 fffff880`05bda768 fffffa80`00000003 fffffa80`0dbec180 : nt!CmSetValueKey+0x2e3
fffff880`05bda720 fffff800`03686f93 : ffffffff`80007268 fffff800`03961a92 fffff880`00000000 fffff800`00000003 : nt!NtSetValueKey+0x349
fffff880`05bda850 fffff800`03683530 : fffff880`01ddb90e ffffffff`80007268 00000000`0070006e fffff880`01dcf9c0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`05bdaa58 fffff880`01ddb90e : ffffffff`80007268 00000000`0070006e fffff880`01dcf9c0 fffff800`00000030 : nt!KiServiceLinkage
fffff880`05bdaa60 ffffffff`80007268 : 00000000`0070006e fffff880`01dcf9c0 fffff800`00000030 fffffa80`0dbec180 : kl1+0x17a90e
fffff880`05bdaa68 00000000`0070006e : fffff880`01dcf9c0 fffff800`00000030 fffffa80`0dbec180 fffff880`00000008 : 0xffffffff`80007268
fffff880`05bdaa70 fffff880`01dcf9c0 : fffff800`00000030 fffffa80`0dbec180 fffff880`00000008 fffff880`000e000c : 0x70006e
fffff880`05bdaa78 fffff800`00000030 : fffffa80`0dbec180 fffff880`00000008 fffff880`000e000c fffff880`01dcfa30 : kl1+0x16e9c0
fffff880`05bdaa80 fffffa80`0dbec180 : fffff880`00000008 fffff880`000e000c fffff880`01dcfa30 fffffa80`0dbec160 : 0xfffff800`00000030
fffff880`05bdaa88 fffff880`00000008 : fffff880`000e000c fffff880`01dcfa30 fffffa80`0dbec160 fffffa80`07b890f0 : 0xfffffa80`0dbec180
fffff880`05bdaa90 fffff880`000e000c : fffff880`01dcfa30 fffffa80`0dbec160 fffffa80`07b890f0 fffffa80`0dbec160 : 0xfffff880`00000008
fffff880`05bdaa98 fffff880`01dcfa30 : fffffa80`0dbec160 fffffa80`07b890f0 fffffa80`0dbec160 fffff880`01ddc239 : 0xfffff880`000e000c
fffff880`05bdaaa0 fffffa80`0dbec160 : fffffa80`07b890f0 fffffa80`0dbec160 fffff880`01ddc239 00000000`00000000 : kl1+0x16ea30
fffff880`05bdaaa8 fffffa80`07b890f0 : fffffa80`0dbec160 fffff880`01ddc239 00000000`00000000 fffffa80`0dbec160 : 0xfffffa80`0dbec160
fffff880`05bdaab0 fffffa80`0dbec160 : fffff880`01ddc239 00000000`00000000 fffffa80`0dbec160 fffffa80`07b890f0 : 0xfffffa80`07b890f0
fffff880`05bdaab8 fffff880`01ddc239 : 00000000`00000000 fffffa80`0dbec160 fffffa80`07b890f0 fffffa80`0dbec160 : 0xfffffa80`0dbec160
fffff880`05bdaac0 00000000`00000000 : fffffa80`0dbec160 fffffa80`07b890f0 fffffa80`0dbec160 fffffa80`00000008 : kl1+0x17b239


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_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------
My System SpecsSystem Spec
Reply

 BSOD during starcraft 2




Thread Tools



Similar help and support threads for2: BSOD during starcraft 2
Thread Forum
BSOD during Starcraft II BSOD Help and Support
Random BSOD when playing games, persistant BSOD with Starcraft 2 BSOD Help and Support
Solved BSOD When Playing StarCraft 2 BSOD Help and Support
BSOD playing Starcraft 2 BSOD Help and Support
dxgkrnl.sys BSOD with StarCraft II BSOD Help and Support
Starcraft 2 BSOD after 10-30 minutes BSOD Help and Support
Starcraft BSOD 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:35 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33