+- Windows 7 Forum: konfiguracja, optymalizacja, porady, gadżety • (https://windows7forum.pl)
+-- Dział: Pomoc i wsparcie, Windows 7 (/pomoc-i-wsparcie-windows-7-26-f)
+--- Dział: Konfiguracja i optymalizacja Windows 7 (/konfiguracja-i-optymalizacja-windows-7-9-f)
+--- Wątek: Windows 7 - jak rozwiązać problem z Blue screenem? (/windows-7-jak-rozwiazac-problem-z-blue-screenem-19640-t)
Windows 7 - jak rozwiązać problem z Blue screenem? - qwe2 - 04.11.2011 19:21
BSOD złapany podczas gry w Battlefielda 3
plik dmp: http://www.sendspace.pl/file/6439b96237b837069282e3f
ktoś pomoże i powie jakie jest źródło problemu?
RE: Blue screen - peciaq - 04.11.2011 19:35
Probably caused by : ntoskrnl.exe
Czyli prawdopodobnie przez ten plik. Częsty problem, wpisz w wyszukiwarce na naszym forum nazwę tego pliku, albo frazę KERNEL i poczytaj wątki.
RE: Windows 7 - jak rozwiązać problem z Blue screenem? - thermalfake - 04.11.2011 22:59
Ja mam coś innego, chyba, że masz innego bluescreen'a.
Jaką masz konfigurację sprzętową ?
Błąd typowo sprzętowy lub oprogramowania antywirusowego z softem/grą.
Chodzi tu o procesor gdzie rdzenie nie dogadują się między sobą jak należy.
http://windows7forum.pl/bsod-podczas-uzytkowania-0x00000101-t-17369.html
http://www.sevenforums.com/crashes-debugging/27503-another-bsod-thread-sorry-p.html
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G: \Downloads\110411-14008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03055000 PsLoadedModuleList = 0xfffff800`03292e50
Debug session time: Fri Nov 4 18: 15: 07.282 2011 (UTC + 1: 00)
System Uptime: 0 days 2: 08: 43.578
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, fffff88002f64180, 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: fffff88002f64180, 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: Origin.exe
CURRENT_IRQL: d
STACK_TEXT:
fffff880`07645248 fffff800`03073443 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f64180 : nt!KeBugCheckEx
fffff880`07645250 fffff800`030cf5f7 : 00000000`00000000 fffff800`00000002 00000000`00002711 fffff880`0763d000 : nt! ? : FNODOBFM: `string'+0x4e3e
fffff880`076452e0 fffff800`03016895 : fffff800`0303b460 fffff880`07645490 fffff800`0303b460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`076453e0 fffff800`030c33f3 : 00000000`5ce2d9a7 fffffa80`0165dfe0 fffffa80`07174010 fffffa80`076d3e60 : hal!HalpHpetClockInterrupt+0x8d
fffff880`07645410 fffff800`030fc5d5 : fffffa80`07b44030 fffffa80`076d3f01 fffffa80`07928bb0 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`076455a0 fffff800`030fac59 : 00000000`00000000 00000000`00000001 fffff880`07645630 fffff800`030fac75 : nt!KxFlushEntireTb+0xc5
fffff880`076455e0 fffff800`03120da0 : 00000000`00000001 fffff680`0006e180 00000000`00000001 00000000`00000001 : nt!KeFlushTb+0x119
fffff880`07645660 fffff800`030e471f : fffff680`0006e180 fffff880`07645700 fffff8a0`02e98b40 fffffa80`0989ec78 : nt! ? : FNODOBFM: `string'+0xad32
fffff880`076456a0 fffff800`030e11a6 : 00000000`00000000 00000000`0dc30000 fffff880`076458f0 fffff680`0006e180 : nt!MiResolveDemandZeroFault+0x1ff
fffff880`07645790 fffff800`030c4fee : 00000000`00000000 fffffa80`07729830 00000000`004acc00 00000000`0dd30000 : nt!MmAccessFault+0x5c6
fffff880`076458f0 fffff800`033e1c52 : fffffa80`07729800 fffff800`00000001 fffffa80`06a029f0 fffffa80`07729801 : nt!KiPageFault+0x16e
fffff880`07645a80 fffff800`030c6153 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x142
fffff880`07645b70 00000000`73722dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`06b9ebc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73722dd9
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
---------