BSOD playing Starcraft 2, BCCode: 101

[xseper]

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)

 

[yowanvista]

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:
http://www.sevenforums.com/crash-loc...tml#post567135

Win 7 A Clock Interrupt... BSOD (101 Error)

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

 

[xseper]

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.

 

[yowanvista]

Is your CPU/RAM overclocked?

 

[xseper]

no

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

 

[xseper]

Bios updated
drivers updated
antyvirus uninstaled
alot of thinks uninstaled


problem still there
what to do next?

 

[yowanvista]

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.

 

[xseper]

here

 

[xseper]

format c:?

 

[Vir Gnarus]

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.

 

[xseper]

i ran veryfier annndddd.. my windows havent pas it! jackpa!!

win crased befor even started.

i atach minidump (dont know if it is proper, if not plese tell me)

 

[yowanvista]

A misbehaving driver is likely the cause, probably FNETURPX.SYS associated with FNet User Proxy Driver
FNet Corporation -
Uninstalling this software might help.

 

[xseper]

hmmm i lookt at this, and i assumed that was cdrom.sys; after uninstallind deamon tools it seems like fixed (i played SC2 by 25min and it wont crshed...

But i uninstall also this


@edit
i dont see FNet proxy driver in my computer ;/

 

[xseper]

but dll is - deleted


BIIIG thanks all

 

[Vir Gnarus]

That would explain it. The minidump didn't manage to retain much in the pending IRP that was causing the problems, but I did see Daemon Tool's dtsoftbus01.sys driver sitting in the raw stack of the running thread in which it was calling that driver. It's dated from Jan 2012, so unless they have a most recent bugfix of Daemon Tools, it would probably be best to use an alternative right now.

Analysts:

2: kd> !thread
GetPointerFromAddress: unable to read from fffff80003515000
THREAD fffffa80039d6680  Cid 0004.0040  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 2
Not impersonating
GetUlongFromAddress: unable to read from fffff80003454ba4
Owning Process            fffffa80039b8740       Image:         System
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      1064         
Context Switch Count      4460           IdealProcessor: 2             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address nt!ExpWorkerThread (0xfffff800032ecef0)
Stack Init fffff880033c4db0 Current fffff880033c3840
Base [COLOR=Green]fffff880033c5000 [/COLOR]Limit [COLOR=Blue]fffff880033bf000 [/COLOR]Call 0
Priority 13 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`033c39a8 fffff800`0376c3dc : 00000000`000000c9 00000000`0000023e fffffa80`05aea2c0 fffff980`0a9aaee0 : nt!KeBugCheckEx
fffff880`033c39b0 fffff800`0377647a : fffff800`0376a9f0 fffffa80`05aea2c0 fffff980`0a9aaee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`033c39f0 fffff800`0377734e : 00000000`0000023e 00000000`00000000 fffff980`0a9aaee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`033c3a40 fffff800`0378271f : fffffa80`061af820 fffffa80`0617fab0 fffffa80`0617fb68 fffff880`015a8228 : nt!VfErrorReport6+0x6e
fffff880`033c3b10 fffff800`03782b63 : fffffa80`0617fab0 00000000`00000002 fffffa80`05f0b060 fffff880`015a43f4 : nt!IovpCallDriver2+0x13f
fffff880`033c3b70 fffff800`03788c2e : fffff980`0a9aaee0 fffff980`0a9aaee0 00000000`00000002 fffffa80`05f0b060 : nt!VfAfterCallDriver+0x353
fffff880`033c3bc0 fffff880`00d680c2 : fffff880`00de17c0 fffffa80`0614ea20 00000000`00000025 fffffa80`0617fab0 : nt!IovCallDriver+0x57e
fffff880`033c3c20 fffff880`00d7d59f : fffffa80`063b8da0 00000000`00000000 fffff880`00000000 fffff880`083775d5 : Wdf01000!FxIoTarget::SubmitSync+0x24a
fffff880`033c3cd0 fffff880`0838be95 : fffffa80`00000020 fffffa80`063b8da0 fffffa80`0614ea20 00000000`00000001 : Wdf01000!imp_WdfRequestSend+0x24b
fffff880`033c3d20 fffff880`0838c2f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`033c3ee0 : cdrom!DeviceSendRequestSynchronously+0xc9
fffff880`033c3d80 fffff880`0838af04 : 0000057f`f9f447e8 fffff880`033c3ee0 fffffa80`060eb830 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
fffff880`033c3eb0 fffff880`08389825 : fffffa80`00000002 fffffa80`060bbb80 fffff880`083813b8 0000057f`f9f447e8 : cdrom!DeviceCacheDeviceInquiryData+0xbc
fffff880`033c3f80 fffff880`00dd29d4 : 00000000`00000000 fffff880`00000010 00000000`0000000c fffff880`00ddb620 : cdrom!DeviceEvtSelfManagedIoInit+0x105
fffff880`033c3fc0 fffff880`00dd294e : fffffa80`0612aeb0 00000000`0000000c fffff880`00ddb620 fffff880`00ddb600 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
fffff880`033c3ff0 fffff880`00dc6b9b : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00ddb620 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
fffff880`033c4060 fffff880`00dc66eb : 00000000`00000312 00000000`00000000 fffff880`00ddb600 fffff6fc`c00544e0 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
fffff880`033c4090 fffff880`00dc638e : fffffa80`0614db60 00000000`00000040 fffff880`00ddb3e0 00000000`00000040 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1db
fffff880`033c41c0 fffff880`00dc606c : 00000000`00000000 00000000`00000040 00000000`00000501 fffffa80`0614db60 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`033c4230 fffff880`00dd3b5e : 00000000`00000000 00000000`00000501 00000000`00000000 00000000`00000501 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d4
fffff880`033c42c0 fffff880`00dd3abb : 00000000`00000501 00000000`00000000 00000000`00000500 fffff800`037875ec : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
fffff880`033c42f0 fffff880`00dcf950 : fffffa80`0614db60 00000000`00000001 00000000`00000000 fffff880`00dd7ff0 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c7
fffff880`033c4370 fffff880`00dcf372 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`0614ee20 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3f8
fffff880`033c43e0 fffff880`00dcba45 : 00000000`00000000 fffffa80`0614ee20 00000000`00000108 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1e2
fffff880`033c4470 fffff880`00dcb841 : 00000000`00000101 00000000`00000108 00000000`00000108 fffff800`00000006 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
fffff880`033c44b0 fffff880`00dcb4fe : fffffa80`0614db60 fffff880`033c45e0 00000000`00000004 fffff880`00dda390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
fffff880`033c4520 fffff880`00dcb201 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`0614db60 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff880`033c4590 fffff880`00dc2d9c : 00000000`00000000 fffffa80`0614db60 00000000`00000002 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
fffff880`033c4620 fffff880`00dc1dd6 : fffffa80`0614cd30 00000000`00000002 00000000`00000000 fffffa80`0614db60 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20
fffff880`033c4650 fffff880`00d91245 : fffff980`0a82ee50 fffff980`0a82ee50 fffffa80`0614ee20 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`033c46c0 fffff880`00d9114b : fffffa80`0614ee20 fffff980`0a82ee50 00000000`00000002 fffffa80`0614ee20 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`033c46f0 fffff800`03788c16 : fffff980`0a82ee50 00000000`00000002 fffffa80`0614ee20 fffffa80`0614ee20 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`033c4730 fffff800`0369bd6e : fffff980`0a82ee50 fffffa80`06186830 fffffa80`0614ee20 fffffa80`061b9a40 : nt!IovCallDriver+0x566
fffff880`033c4790 fffff800`033d387d : fffffa80`05f0b060 fffffa80`06186830 fffff800`033dcfa0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`033c47d0 fffff800`036ab0b6 : fffff800`034e1940 fffffa80`0614a890 fffffa80`06186830 fffffa80`0614aa38 : nt!PnpStartDevice+0x11d
fffff880`033c4890 fffff800`036ab354 : fffffa80`0614a890 fffffa80`039e002b fffffa80`039ef010 00000000`00000001 : nt!PnpStartDeviceNode+0x156
fffff880`033c4920 fffff800`036cea86 : fffffa80`0614a890 fffffa80`039ef010 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
fffff880`033c4950 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x296

2: kd> dps [COLOR=Blue]fffff880033bf000 [/COLOR][COLOR=Green]fffff880033c5000[/COLOR]
fffff880`033bf000  ????????`????????
fffff880`033bf008  ????????`????????
fffff880`033bf010  ????????`????????
fffff880`033bf018  ????????`????????
fffff880`033bf020  ????????`????????
fffff880`033bf028  ????????`????????

...

fffff880`033c3b28  fffff880`015a8228Unable to load image \SystemRoot\system32\DRIVERS\[COLOR=Red]dtsoftbus01.sys[/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=Red]dtsoftbus01.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=Red]dtsoftbus01.sys[/COLOR]
 [COLOR=Red]dtsoftbus01[/COLOR]+0x5228

 

[xseper]

ok

is it everythink ok with my computer now, or should i do somethik?

 

[Vir Gnarus]

If you're not experiencing crashing anymore, than we can consider this a done deal. Daemon Tools did appear involved with the crash that DV discovered.

 

[xseper]

today i played about 1hour and happen the same (only later)

now im checking drivest but it seems ok

ataching latest dump

Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\041112-17721-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03267000 PsLoadedModuleList = 0xfffff800`034ac670
Debug session time: Wed Apr 11 19:25:45.035 2012 (UTC + 2:00)
System Uptime: 0 days 9:01:19.892
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
...........
TRIAGER: Could not open triage file : D:\programyWindows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : D:\programyWindows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff880009f3180, 1}

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

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff800`00b9ca28 fffff800`0333b8c9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009f3180 : nt!KeBugCheckEx
fffff800`00b9ca30 fffff800`032ee497 : fffffa80`00000000 fffff800`00000001 00000000`00002711 00000000`20004b82 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff800`00b9cac0 fffff800`03228895 : fffff800`0324e460 fffff800`00b9cc70 fffff800`0324e460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00b9cbc0 fffff800`032e0173 : fffff800`03459e80 fffffa80`0548d001 fffffa80`05406840 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff800`00b9cbf0 fffff800`032db990 : fffff800`03459e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x80


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

 

[Vir Gnarus]

I'm sorry, I shoulda realized we were chasing after shadows.

The 0x101 bugchecks had nothing to do with Daemon Tools. What happened with Daemon Tools is that when you turned Driver Verifier on, one of the checks you used was Force Pending I/O Requests. This is not a good check, and is known for causing false positives like what we experienced. While it does show a potential bug in Daemon Tools, it is not the cause of your problems.

Did you run Prime95 for over 7 hours? Did you remove or update the driver that Yowanvista mentioned?

Also, please provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load. It's preferred that for the high load one that you run it until your system crashes. It will still save what was left of the log. Send them to us to check.

You may also send us a kernel dump (MEMORY.DMP in Windows directory) by zipping it up and uploading it to a third party website. This will give us enough information to look at. I cannot guarantee that I know enough to analyze the crashdump and find an answer but it's far better than the minidumps you've been giving us.

 

[xseper]

Did you run Prime95 for over 7 hours?

no not yet

Did you remove or update the driver that Yowanvista mentioned?

Yes

You may also send us a kernel dump (MEMORY.DMP in Windows directory)

Cant find this file. theres no such file in windows folder

rest when i do this