Odpowiedz

BSOD: za każdym razem około 5 minut po włączeniu komputera

 
thermalfake
Ostatni Mohikanin

Liczba postów: 13.580
Post: #5

RE: BSOD 5 minut po uruchomieniu komputera


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\22\dump\Minidump\102812-21106-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product:  WinNt, suite:  TerminalServer SingleUserTS
Built by:  7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`04003000 PsLoadedModuleList = 0xfffff800`04247670
Debug session time:  Sun Oct 28 12: 32: 29.383 2012 (UTC + 1: 00)
System Uptime:  0 days 0: 04: 57.772
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {2b, 2, 0, fffff80004088e20}

Probably caused by :  win32k.sys ( win32k!xxxRealSleepThread+257 )

Followup:  MachineOwner
---------

1:  kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1:  000000000000002b, memory referenced
Arg2:  0000000000000002, IRQL
Arg3:  0000000000000000, bitfield :
    bit 0 :  value 0 = read operation, 1 = write operation
    bit 3 :  value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4:  fffff80004088e20, address which referenced memory

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


READ_ADDRESS:  GetPointerFromAddress:  unable to read from fffff800042b1100
000000000000002b

CURRENT_IRQL:   2

FAULTING_IP:  
nt!KeWaitForSingleObject+230
fffff800`04088e20 498b0e          mov     rcx,qword ptr [r14]

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0xA

PROCESS_NAME:   firefox.exe

TRAP_FRAME:   fffff8800aac3980 -- (.trap 0xfffff8800aac3980)
NOTE:  The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000004a8f rbx=0000000000000000 rcx=0000000000000002
rdx=000000000000000d rsi=0000000000000000 rdi=0000000000000000
rip=fffff80004088e20 rsp=fffff8800aac3b10 rbp=0000000000000000
r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=fffffa8007682750 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KeWaitForSingleObject+0x230:
fffff800`04088e20 498b0e          mov     rcx,qword ptr [r14] ds: 00000000`00000000=???
Resetting default scope

LAST_CONTROL_TRANSFER:   from fffff80004081569 to fffff80004081fc0

STACK_TEXT:  
fffff880`0aac3838 fffff800`04081569 :  00000000`0000000a 00000000`0000002b 00000000`00000002 00000000`00000000 :  nt!KeBugCheckEx
fffff880`0aac3840 fffff800`040801e0 :  fffff900`c06cb870 00000000`00000000 00000000`76d0b500 00000000`0000002b :  nt!KiBugCheckDispatch+0x69
fffff880`0aac3980 fffff800`04088e20 :  fffff900`c06cb870 fffff960`0013d43d fffff900`c06cb800 fffff800`0000000d :  nt!KiPageFault+0x260
fffff880`0aac3b10 fffff960`0013d417 :  fffff900`c06cb800 fffff960`0000000d 00000000`00000001 00000000`00000000 :  nt!KeWaitForSingleObject+0x230
fffff880`0aac3bb0 00001fa1`02010000 :  00000000`07f5cf10 00000000`74952e09 00000000`00000000 00000000`0000002b :  win32k!xxxRealSleepThread+0x257
fffff880`0aac3c50 00000000`07f5cf10 :  00000000`74952e09 00000000`00000000 00000000`0000002b 00000000`7606f5be :  0x1fa1`02010000
fffff880`0aac3c58 00000000`74952e09 :  00000000`00000000 00000000`0000002b 00000000`7606f5be 00000000`00000000 :  0x7f5cf10
fffff880`0aac3c60 00000000`00000000 :  00000000`0000002b 00000000`7606f5be 00000000`00000000 00000000`00200246 :  0x74952e09


STACK_COMMAND:   kb

FOLLOWUP_IP:  
win32k!xxxRealSleepThread+257
fffff960`0013d417 448be8          mov     r13d,eax

SYMBOL_STACK_INDEX:   4

SYMBOL_NAME:   win32k!xxxRealSleepThread+257

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  win32k

IMAGE_NAME:   win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:   5006fd0d

FAILURE_BUCKET_ID:   X64_0xA_win32k!xxxRealSleepThread+257

BUCKET_ID:   X64_0xA_win32k!xxxRealSleepThread+257

Followup:  MachineOwner
---------


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\22\dump\Minidump\102712-21418-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product:  WinNt, suite:  TerminalServer SingleUserTS
Built by:  7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`04050000 PsLoadedModuleList = 0xfffff800`04294670
Debug session time:  Sat Oct 27 12: 10: 04.208 2012 (UTC + 1: 00)
System Uptime:  0 days 0: 04: 16.988
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffff8a00e0060a0, fffff8a00e006080, fffff8a00e0060a0}

Probably caused by :  Pool_Corruption ( nt!ExDeferredFreePool+cbb )

Followup:  Pool_corruption
---------

3:  kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1:  0000000000000003, the pool freelist is corrupt.
Arg2:  fffff8a00e0060a0, the pool entry being checked.
Arg3:  fffff8a00e006080, the read back flink freelist value (should be the same as 2).
Arg4:  fffff8a00e0060a0, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR:   0x19_3

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

PROCESS_NAME:   System

CURRENT_IRQL:   0

LAST_CONTROL_TRANSFER:   from fffff800041f970f to fffff800040cefc0

STACK_TEXT:  
fffff880`031afa78 fffff800`041f970f :  00000000`00000019 00000000`00000003 fffff8a0`0e0060a0 fffff8a0`0e006080 :  nt!KeBugCheckEx
fffff880`031afa80 fffff800`041fb1a1 :  fffff800`043c1560 fffff8a0`0dff8760 fffffa80`036e4b50 fffff880`02f63180 :  nt!ExDeferredFreePool+0xcbb
fffff880`031afb10 fffff800`043b012c :  fffff800`042cc600 00000000`00000000 00000000`624e4d43 00000000`00000000 :  nt!ExFreePoolWithTag+0x411
fffff880`031afbc0 fffff800`043b01c0 :  fffff8a0`0366ccc0 00000000`d108d2f0 fffff8a0`007c5010 ffffffff`ffffffff :  nt!CmpDereferenceNameControlBlockWithLock+0xdc
fffff880`031afbf0 fffff800`043901ef :  fffff8a0`0366ccc0 fffff800`043ae730 fffff800`624e4d43 fffff800`00000000 :  nt!CmpCleanUpKcbCacheWithLock+0x34
fffff880`031afc20 fffff800`043ae921 :  fffff8a0`0366ccc0 00000000`ff2221a7 fffff8a0`007c5010 00000000`00000000 :  nt!CmpDereferenceKeyControlBlockWithLock+0x13f
fffff880`031afc50 fffff800`040d8641 :  fffff800`0426c2d8 fffffa80`036e4b50 00000000`00000000 00000000`00000000 :  nt!CmpDelayDerefKCBWorker+0x1f1
fffff880`031afcb0 fffff800`04365e5a :  ffffbf3f`fdfff5ff fffffa80`036e4b50 00000000`00000080 fffffa80`036ce040 :  nt!ExpWorkerThread+0x111
fffff880`031afd40 fffff800`040bfd26 :  fffff880`02f63180 fffffa80`036e4b50 fffff880`02f6dfc0 fdffbfff`3fffe77f :  nt!PspSystemThreadStartup+0x5a
fffff880`031afd80 00000000`00000000 :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KxStartSystemThread+0x16


STACK_COMMAND:   kb

FOLLOWUP_IP:  
nt!ExDeferredFreePool+cbb
fffff800`041f970f cc              int     3

SYMBOL_STACK_INDEX:   1

SYMBOL_NAME:   nt!ExDeferredFreePool+cbb

FOLLOWUP_NAME:   Pool_corruption

IMAGE_NAME:   Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:   0

MODULE_NAME:  Pool_Corruption

FAILURE_BUCKET_ID:   X64_0x19_3_nt!ExDeferredFreePool+cbb

BUCKET_ID:   X64_0x19_3_nt!ExDeferredFreePool+cbb

Followup:  Pool_corruption
---------

[Obrazek: 2089620800_1406976151.png]

W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.

01.11.2012 17:10

Znajdź wszystkie posty użytkownika
Odpowiedz cytując ten post
Odpowiedz


Wiadomości w tym wątku
RE: BSOD 5 minut po uruchomieniu komputera - thermalfake - 01.11.2012 17:10
Podobne wątki
Wątek: Autor Odpowiedzi: Wyświetleń: Ostatni post
BSOD Moloch4 0 936 05.07.2019 11:29
Ostatni post: Moloch4
BSOD Windows 7 luzbluzoner 0 1.452 17.12.2016 20:25
Ostatni post: luzbluzoner
Częsty ekrad BSOD kubajed 0 1.441 03.10.2016 17:46
Ostatni post: kubajed
Windows Media Player nie chce się włączyć po ponownym włączeniu funkcji mazanm 0 1.383 15.08.2016 23:27
Ostatni post: mazanm
Rozwiązany Win7 uruchamia się 7 minut pomocy GregPl 4 3.125 15.05.2016 09:50
Ostatni post: GregPl
Nowa instalacja, 3 BSOD avocado 0 1.448 20.11.2015 09:46
Ostatni post: avocado
« Starszy wątek | Nowszy wątek »

Temat został oceniony na 0 w skali 1-5 gwiazdek.
Zebrano 1 głosów.