BSOD playing Starcraft 2, BCCode: 101

Page 1 of 5 123 ... LastLast

  1. Posts : 27
    windows 7 pro x64
       #1

    BSOD playing Starcraft 2, BCCode: 101


    Nazwa zdarzenia problemu: BlueScreen
    Wersja systemu operacyjnego: 6.1.7601.2.1.0.256.1
    Identyfikator ustawień regionalnych: 1045

    Dodatkowe informacje o problemie:
    BCCode: 101
    BCP1: 0000000000000031
    BCP2: 0000000000000000
    BCP3: FFFFF88003164180
    BCP4: 0000000000000002
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Pliki pomagające opisać problem:
    C:\Windows\Minidump\040712-15943-01.dmp
    C:\Windows\Temp\WER-23930-0.sysdata.xml

    Przeczytaj w trybie online nasze zasady zachowania poufności informacji:
    http://go.microsoft....88&clcid=0x0415

    Jeśli zasady zachowania poufności informacji w trybie online nie są dostępne, przeczytaj nasze zasady zachowania poufności informacji w trybie offline:
    C:\Windows\system32\pl-PL\erofflps.txt
    bluescreen always in 4-8minute of game. quality of graphics dont matter


    AMD a8 llano ; 2x2gb geil 1750 ; no aditional graphics (only integrated)
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    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


    Details about this bugcheck:
    https://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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff88003164180, 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:  System
    
    CURRENT_IRQL:  d
    
    STACK_TEXT:  
    fffff880`0c3ab528 fffff800`0331e8c9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03164180 : nt!KeBugCheckEx
    fffff880`0c3ab530 fffff800`032d1497 : fffff880`00000000 fffff800`00000002 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e2e
    fffff880`0c3ab5c0 fffff800`0320b895 : fffff800`03231460 fffff880`0c3ab770 fffff800`03231460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
    fffff880`0c3ab6c0 fffff800`032c3173 : 00000000`54c5824a fffff800`0343ce80 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
    fffff880`0c3ab6f0 fffff800`032cc792 : fffff800`0343ce80 fffffa80`00000001 00000000`00000000 fffff880`0c3ab978 : nt!KiInterruptDispatchNoLock+0x163
    fffff880`0c3ab880 fffff800`0330b7ac : fffff880`0c3abc58 00000000`00000000 00000000`00000000 fffff800`03309ba1 : nt!KeFlushMultipleRangeTb+0x252
    fffff880`0c3ab950 fffff800`033085e1 : fffffa80`06716040 00000000`00000000 fffff880`0c3abc58 00000000`00000000 : nt!MmSetAddressRangeModified+0x2b0
    fffff880`0c3aba50 fffff800`0330bf76 : fffffa80`048da8b0 00000000`00000001 fffffa80`00000001 00000000`00001000 : nt!CcFlushCache+0x561
    fffff880`0c3abb50 fffff800`0330c938 : fffff880`00000000 fffff880`0c3abc58 fffffa80`03f4e290 fffff800`034c88b8 : nt!CcWriteBehind+0x1c6
    fffff880`0c3abc00 fffff800`032d1001 : fffffa80`03a434f0 fffff800`035bd901 fffff800`034c88c0 00000000`00000005 : nt!CcWorkerThread+0x1c8
    fffff880`0c3abcb0 fffff800`03561fee : 00000000`07d1131c fffffa80`06716040 00000000`00000080 fffffa80`03a1e990 : nt!ExpWorkerThread+0x111
    fffff880`0c3abd40 fffff800`032b85e6 : fffff880`03164180 fffffa80`06716040 fffff880`0316efc0 fffff880`01266384 : nt!PspSystemThreadStartup+0x5a
    fffff880`0c3abd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    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
    ---------
      My Computer


  3. Posts : 27
    windows 7 pro x64
    Thread Starter
       #3

    Hi thanks.

    I ran thouse 3 tests with GIMPS 64. But i dont know i did it right. I tested about 5 minuts each. No errors occured. Tmperature while heviest test whre 69C, after droped to 21C.
      My Computer


  4. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #4

    Is your CPU/RAM overclocked?
      My Computer


  5. Posts : 27
    windows 7 pro x64
    Thread Starter
       #5

    no

    nothink is overclocked. But my ram have 1750hz but in bios it is 1033 on auto
      My Computer


  6. Posts : 27
    windows 7 pro x64
    Thread Starter
       #6

    Bios updated
    drivers updated
    antyvirus uninstaled
    alot of thinks uninstaled


    problem still there
    what to do next?
      My Computer


  7. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #7

    xseper said:
    Bios updated
    drivers updated
    antyvirus uninstaled
    alot of thinks uninstaled


    problem still there
    what to do next?
    Post another attachment, we'll see if the CPU is still blamed as the probable cause.
      My Computer


  8. Posts : 27
    windows 7 pro x64
    Thread Starter
       #8

    here
      My Computer


  9. Posts : 27
    windows 7 pro x64
    Thread Starter
       #9

    format c:?
      My Computer


  10. Posts : 1,314
    Windows 7 64-bit
       #10

    The unfortunate thing about 0x101 bugchecks is that minidumps are absolutely and completely worthless to analyze the cause of them. Only the running processor core's context is saved in a minidump, and since it was running, it obviously was not the one responsible for hanging and tripping the bugcheck.

    Just so you know, Prime95 tests shouldn't run at just 5 minutes. Rather, a single Prime95 run should be kept running for several hours. If you suspect we're dealing with processor failure here, then Large FFTs is the preferred test as it will heavily test the internal CPU cache by filling it to its max. I recommend about 7-9 hours.

    Also, of course, run Driver Verifier just to be sure we aren't dealing with some buggy driver code that's lingering somewhere. In addition, if you're willing, you can zip up and upload a kernel dump (MEMORY.DMP file located in Windows directory) to a 3rd-party site for us to access. That size of dump is sufficient enough to analyze with.
      My Computer


 
Page 1 of 5 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About 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 18:28.
Find Us