Mam kolejny problem. Z tydzień wcześniej podczas gry w Dotę 2 ze 4 razy komp się zwiesił i wywaliło blue screena. Zapomniałem już o tym, ale dzisiaj znowu, tym razem podczas gry w LoL'a(żeby nie było, że atakuje tylko 1 markę
) 2 razy mi scrashowało.Oto te 2 najnowsze logi(poprzednich już nie ma):
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\030313-16473-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Sun Mar 3 19:14:33.336 2013 (GMT+1)
System Uptime: 0 days 4:43:58.788
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {61, 0, fffff880009e8180, 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: 0000000000000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009e8180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: d
STACK_TEXT:
fffff880`0a418478 fffff800`02c69443 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009e8180 : nt!KeBugCheckEx
fffff880`0a418480 fffff800`02cc55f7 : fffffa80`00000000 fffff800`00000001 00000000`00002711 00000000`20004dfc : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`0a418510 fffff800`02c0c895 : fffff800`02c31460 fffff880`0a4186c0 fffff800`02c31460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0a418610 fffff800`02cb93f3 : fffff800`02e35e80 00000000`00000001 fffffa80`03cb2300 fffff880`00000008 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0a418640 fffff800`02c7c2c7 : fffff880`0a418820 fffff800`02cb895c fffff880`009e8180 fffff880`009f2f40 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0a4187d0 fffff800`02fb7e58 : 00000000`00000000 fffff880`0a418ca0 fffff800`02c4b000 fffffa80`057227b0 : nt!KeFlushProcessWriteBuffers+0x63
fffff880`0a418840 fffff800`02fb8e49 : 00000000`0388ae70 fffff800`02fb49ee 00000000`00000000 00000000`00000000 : nt!ExpQuerySystemInformation+0x1368
fffff880`0a418be0 fffff800`02cbc153 : fffffa80`04a20000 00000000`00000000 ffffffff`fffe7960 000007fe`00000000 : nt!NtQuerySystemInformation+0x4d
fffff880`0a418c20 00000000`76ea021a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00c3f158 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ea021a
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_2_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
oraz
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\030313-14726-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e8ae50
Debug session time: Sun Mar 3 19:32:53.909 2013 (GMT+1)
System Uptime: 0 days 0:17:46.236
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {61, 0, fffff880009e8180, 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: 0000000000000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009e8180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: d
STACK_TEXT:
fffff880`02f39508 fffff800`02c6b443 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009e8180 : nt!KeBugCheckEx
fffff880`02f39510 fffff800`02cc75f7 : fffffa80`00000000 fffff800`00000001 00000000`00002710 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`02f395a0 fffff800`02c0e895 : fffff800`02c33460 fffff880`02f39750 fffff800`02c33460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`02f396a0 fffff800`02cbb3f3 : 00000000`7a099b09 fffff800`02e37e80 fffffa80`00913f00 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`02f396d0 fffff800`02ccce00 : fffffa80`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`02f39860 fffff800`02cd2f70 : 00000000`000046e3 00000000`00000001 00000000`00000002 00000000`0000463c : nt!KeFlushMultipleRangeTb+0x260
fffff880`02f39930 fffff800`02d3fa0e : fffff800`02e49b40 fffff880`00000001 00000000`00000001 fffff880`02f39bb0 : nt!MiAgeWorkingSet+0x651
fffff880`02f39ae0 fffff800`02cd36e2 : 00000000`00000423 00000000`00000000 fffffa80`00000000 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`02f39b80 fffff800`02cd396f : 00000000`00000008 fffff880`02f39c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`02f39bd0 fffff800`02f62166 : fffffa80`03d0f680 00000000`00000080 fffffa80`03c70890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`02f39d40 fffff800`02c9d486 : fffff800`02e37e80 fffffa80`03d0f680 fffff800`02e45c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f39d80 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_2_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
Proszę o pomoc w znalezieniu przyczyny oraz rozwiązaniu problemu.
Pozdrawiam.
Użytkownik Adept edytował ten post 03 03 2013 - 21:20
