Jest to jeden i ten sam błąd.
Proszę wykonanie dwóch kroków.
Pierwszym jest pobranie programu do zebrania najważniejszych informacji o systemie i jego pracy -
klik
Proszę go umieścić w katalogu c:\Users\użytkownik\Dokuments i uruchomić z prawami administratora czekając kilka minut na wykonanie zadania. W tym samym folderze utworzy się nowy podfolder z tą samą nazwą co nazwa pliku. Znajdą się tam pliki, które należy spakować i podesłać.
Dodatkowo prosiłbym o wykonanie raportu monitora wydajności z wiersza poleceń "perfmon.exe /report" i zapisanie w postaci pliku html.
Najlepiej wszystko spakować do jednego archiwum i podesłać.
Na początek zachęcam do aktualizacji bios i jeśli producent wypuścił łatki to także je zainstalować.
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\6\072212-23571-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap: Add: ignoring zero-sized range at ?fffff8a0`0551b6d2?
DbsSplayTreeRangeMap: Add: ignoring zero-sized range at ?fffff8a0`04741042?
DbsSplayTreeRangeMap: Add: ignoring zero-sized range at ?fffff8a0`00222022?
Symbol search path is: symsrv*symsrv.dll*c: \symb*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 Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`03050000 PsLoadedModuleList = 0xfffff800`03294670
Debug session time: Sun Jul 22 20: 56: 51.464 2012 (UTC + 2: 00)
System Uptime: 0 days 6: 03: 37.524
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000009F, {4, 258, fffffa8003fdc660, fffff80000b9c3d0}
Unable to load image \SystemRoot\system32\DRIVERS\btfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for btfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for btfilter.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8003fdc660, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c3d0
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 4
FAULTING_THREAD: fffffa8003fdc660
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800030c4bd2 to fffff800030d207a
STACK_TEXT:
fffff880`035b5600 fffff800`030c4bd2 : fffffa80`03fdc660 fffffa80`03fdc660 00000000`00000000 fffffa80`00000002 : nt!KiSwapContext+0x7a
fffff880`035b5740 fffff800`030d4f82 : 00000000`00000080 fffffa80`0dec4000 ffffecc1`00000017 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`035b57d0 fffff880`0af87183 : fffffa80`0dec4014 fffffa80`0d29a681 fffff880`035b5800 00000000`00000017 : nt!KeDelayExecutionThread+0x186
fffff880`035b5840 fffffa80`0dec4014 : fffffa80`0d29a681 fffff880`035b5800 00000000`00000017 00000000`00000000 : btfilter+0x2183
fffff880`035b5848 fffffa80`0d29a681 : fffff880`035b5800 00000000`00000017 00000000`00000000 fffff880`0af90199 : 0xfffffa80`0dec4014
fffff880`035b5850 fffff880`035b5800 : 00000000`00000017 00000000`00000000 fffff880`0af90199 fffff880`0afb77b0 : 0xfffffa80`0d29a681
fffff880`035b5858 00000000`00000017 : 00000000`00000000 fffff880`0af90199 fffff880`0afb77b0 ffffffff`ffe17b80 : 0xfffff880`035b5800
fffff880`035b5860 00000000`00000000 : fffff880`0af90199 fffff880`0afb77b0 ffffffff`ffe17b80 00000000`00000001 : 0x17
STACK_COMMAND: .thread 0xfffffa8003fdc660 ; kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff800030d23a2 - nt!SwapContext_PatchXSave+2
[ 01: 21 ]
fffff800030d2486 - nt!SwapContext_PatchXRstor+2 (+0xe4)
[ 09: 29 ]
fffff800030d2642 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bc)
[ 01: 21 ]
fffff800030d2728 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe6)
[ 09: 29 ]
4 errors : !nt (fffff800030d23a2-fffff800030d2728)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BIT_LARGE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT_LARGE
Followup: memory_corruption
---------
Post: #2![[Obrazek: 2089620800_1406976151.png]](http://obrazki.elektroda.pl/2089620800_1406976151.png)
