Skocz do zawartości


tablety.pl
Zdjęcie

BSOD laptop Toshiba - win 7 home




  • Zaloguj się, aby dodać odpowiedź
2 odpowiedzi w tym temacie

#1 max00R

max00R

    First Rank

  • Użytkownicy
  • 10 postów

Napisano 29 05 2014 - 16:29

Dzień dobry,

mam problem z bluescreenami na laptopie, zwykle podczas oglądania filmów.

windbg wskazywał wcześniej sterownik karty sieciowej,

Przeinstalowałem wszystkie sterowniki na najnowsze wersje, pozbyłem się śmieciowego oprogramowania, teraz windbg wskazuje na ntoskernel.exe, ale brakowało mu symboli, po dołożeniu ścieżki do symboli kernela mam pool corruption. W ogóle nie wiem o co chodzi. Załączam zrzut:


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Microsoft (R) Windows Debugger Version 6.3.9600.17029 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03253000 PsLoadedModuleList = 0xfffff800`03496890
Debug session time: Thu May 29 16:43:11.002 2014 (UTC + 2:00)
System Uptime: 0 days 0:43:31.547
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa8003adc680, fffffa8003adc680, fffffa8003adc680}

*** WARNING: Unable to verify timestamp for aswSP.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSP.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )

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

1: 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: fffffa8003adc680, the pool entry being checked.
Arg3: fffffa8003adc680, the read back flink freelist value (should be the same as 2).
Arg4: fffffa8003adc680, 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:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

LAST_CONTROL_TRANSFER:  from fffff800033fb4b3 to fffff800032c8bc0

STACK_TEXT:  
fffff880`038c4858 fffff800`033fb4b3 : 00000000`00000019 00000000`00000003 fffffa80`03adc680 fffffa80`03adc680 : nt!KeBugCheckEx
fffff880`038c4860 fffff880`01074d15 : 00000000`00000001 00000000`0000003a 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0xa53
fffff880`038c4950 fffff880`01075f81 : 00000000`00000065 00000000`00000065 00000000`0000003b 00000000`00000000 : fltmgr!FltpExpandShortNames+0x365
fffff880`038c49b0 fffff880`01075e1e : fffffa80`045def10 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!FltpGetNormalizedFileNameWorker+0xc1
fffff880`038c49f0 fffff880`01061b9d : c00000bb`06495f00 00000000`00000000 fffffa80`04eec570 fffff880`038c6000 : fltmgr!FltpCreateFileNameInformation+0xee
fffff880`038c4a50 fffff880`0105bbf6 : fffffa80`03b1b080 fffffa80`04eec170 fffffa80`04e1a108 fffff800`033fc30d : fltmgr!HandleStreamListNotSupported+0x15d
fffff880`038c4a90 fffff880`01062b44 : fffffa80`045d7000 00000000`00000000 fffffa80`04eec170 00000000`00000101 : fltmgr! ?? ::FNODOBFM::`string'+0x30f3
fffff880`038c4b10 fffff880`08aaf4a9 : fffffa80`045def10 fffffa80`05e547b0 00000000`00000001 fffff880`038c4c00 : fltmgr!FltGetFileNameInformation+0x184
fffff880`038c4ba0 fffffa80`045def10 : fffffa80`05e547b0 00000000`00000001 fffff880`038c4c00 00000000`00000000 : aswSP+0x654a9
fffff880`038c4ba8 fffffa80`05e547b0 : 00000000`00000001 fffff880`038c4c00 00000000`00000000 00000000`00000000 : 0xfffffa80`045def10
fffff880`038c4bb0 00000000`00000001 : fffff880`038c4c00 00000000`00000000 00000000`00000000 00000000`00000020 : 0xfffffa80`05e547b0
fffff880`038c4bb8 fffff880`038c4c00 : 00000000`00000000 00000000`00000000 00000000`00000020 fffff880`08aaef53 : 0x1
fffff880`038c4bc0 00000000`00000000 : 00000000`00000000 00000000`00000020 fffff880`08aaef53 fffffa80`05e547b0 : 0xfffff880`038c4c00


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+a53
fffff800`033fb4b3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+a53

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  6.1.7601.18409

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x19_3_nt!exdeferredfreepool+a53

FAILURE_ID_HASH:  {dfbdc8e1-ed53-6f10-9f53-216c75bb0283}

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


kolejny zrzut, po 15 min oglądania vod tvp

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


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03213000 PsLoadedModuleList = 0xfffff800`03456890
Debug session time: Thu May 29 17:55:21.526 2014 (UTC + 2:00)
System Uptime: 0 days 1:11:51.055
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff8000327f0e3}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff8000327f0e3

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

LAST_CONTROL_TRANSFER:  from fffff80003288169 to fffff80003288bc0

STACK_TEXT:  
fffff880`009ecc68 fffff800`03288169 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009ecc70 fffff800`03286632 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009ecdb0 fffff800`0327f0e3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`02f1ba50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeAccumulateTicks+0x33


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`03286632 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

IMAGE_VERSION:  6.1.7601.18409

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7f_8_nt!kidoublefaultabort+b2

FAILURE_ID_HASH:  {0367acc4-9bb4-ab69-5701-46a2011718e9}

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



#2 Pentium320

Pentium320

    Very Good Rank

  • Moderatorzy
  • 1019 postów
  • Płeć:Mężczyzna
  • Lokalizacja:Rumia (Trójmiasto)

Napisano 29 05 2014 - 17:48

Przetestuj pamięć bootowalną wersją Memtest86+: http://www.memtest.org/#downiso . Ściągasz, wrzucasz na pendrive lub wypalasz na płycie i uruchamiasz z niej komputer. Test może potrwać kilkadziesiąt minut i aż do komunikatu o zakończeniu testu ma nie być absolutnie żadnych błędów. Jakikolwiek błąd może świadczyć o uszkodzeniu pamięci.



#3 XanTyp

XanTyp

    Expert Rank

  • Admins
  • 3887 postów
  • Płeć:Mężczyzna
  • Lokalizacja:Headquarter

Napisano 29 05 2014 - 21:42

Będę tym wrednym i złośliwym, ale jeszcze jeden log w poście a nie wg zasad forum i zrobię porządek po swojemu.


Nawet, jeśli nie będę mógł pomóc, to może coś podpowiem:

1. Najpierw sięgnij do źródła, potem dopiero dzwoń po hydraulika.

2. Precyzja odpowiedzi zależy przed wszystkim od precyzji zadanego pytania.
3. Nie czytam w myślach, ale mogę powróżyć na specjalne życzenie (:





Użytkownicy przeglądający ten temat: 0

0 użytkowników, 0 gości, 0 anonimowych