Gucioo_
Nowy
Liczba postów: 8
|
Poranne blue screen'y Acer Aspire 5741g
Niedawno kupiłem laptopa, (Acer Aspire 5741g) nic w nim nie wymieniałem ani go nie podkręcałem, a po kilku dniach codziennie rano (lub co dwa dni) wyskakuje mi blue screen zaraz po włączeniu komputera. Później gdy uruchamiam go ponownie wszystko działa perfekcyjnie aż do następnego ranka. Zrobiłem testy pamięci RAM memtestem86 i program ten nie wykrył żadnych błędów. Proszę o pomoc, bo sam nie mogę sobie poradzić z tym problemem już od miesiąca (robiłem nawet kilka formatów i w ogóle nie pomogły).
Dołączam info z programu debugging tools for windows:
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*c: \symbols*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 Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03001000 PsLoadedModuleList = 0xfffff800`0323ee50
Debug session time: Sat Dec 4 18: 44: 02.888 2010 (UTC + 1: 00)
System Uptime: 0 days 0: 01: 20.667
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd8018). Type ".hh dbgerr001" for details
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff80001070993, 8, fffff80001070993, 0}
Probably caused by : ntkrnlmp.exe ( nt! ? : FNODOBFM: `string'+42837 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff80001070993, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff80001070993, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
WRITE_ADDRESS: fffff80001070993
FAULTING_IP:
+3966323637343034
fffff800`01070993 ? ?
MM_INTERNAL_CODE: 0
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: SearchFilterHo
CURRENT_IRQL: 0
TRAP_FRAME: fffff88008da3a20 -- (.trap 0xfffff88008da3a20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa800875a1d0
rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001070993 rsp=fffff88008da3bb0 rbp=fffff88008da3ca0
r8=0000000000000000 r9=0000000000000000 r10=0000000000000001
r11=fffff88008da3ba0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
fffff800`01070993 ? ?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030f1f14 to fffff80003071740
STACK_TEXT:
fffff880`08da38b8 fffff800`030f1f14 : 00000000`00000050 fffff800`01070993 00000000`00000008 fffff880`08da3a20 : nt!KeBugCheckEx
fffff880`08da38c0 fffff800`0306f82e : 00000000`00000008 fffffa80`08759060 00000000`00000000 fffff800`035e4b7f : nt! ? : FNODOBFM: `string'+0x42837
fffff880`08da3a20 fffff800`01070993 : fffffa80`08759060 00000000`00b0fc58 fffff880`08da3bc8 fffff8a0`022f5060 : nt!KiPageFault+0x16e
fffff880`08da3bb0 fffffa80`08759060 : 00000000`00b0fc58 fffff880`08da3bc8 fffff8a0`022f5060 00000000`00000000 : 0xfffff800`01070993
fffff880`08da3bb8 00000000`00b0fc58 : fffff880`08da3bc8 fffff8a0`022f5060 00000000`00000000 0000007f`fffffff8 : 0xfffffa80`08759060
fffff880`08da3bc0 fffff880`08da3bc8 : fffff8a0`022f5060 00000000`00000000 0000007f`fffffff8 00000000`00000000 : 0xb0fc58
fffff880`08da3bc8 fffff8a0`022f5060 : 00000000`00000000 0000007f`fffffff8 00000000`00000000 00000000`00000000 : 0xfffff880`08da3bc8
fffff880`08da3bd0 00000000`00000000 : 0000007f`fffffff8 00000000`00000000 00000000`00000000 00000000`000000c4 : 0xfffff8a0`022f5060
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ? : FNODOBFM: `string'+42837
fffff800`030f1f14 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ? : FNODOBFM: `string'+42837
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x50_nt!_??_: FNODOBFM: _string_+42837
BUCKET_ID: X64_0x50_nt!_??_: FNODOBFM: _string_+42837
Followup: MachineOwner
---------
Teraz info z innego pliku
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Windows\Minidump\120210-23571-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e1b000 PsLoadedModuleList = 0xfffff800`03058e50
Debug session time: Thu Dec 2 11: 29: 19.488 2010 (UTC + 1: 00)
System Uptime: 0 days 0: 06: 05.267
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffff8a0087eba20, fffff8a0087eba20, fffff6fc5003f558}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+ca0 )
Followup: Pool_corruption
---------
2: 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: fffff8a0087eba20, the pool entry being checked.
Arg3: fffff8a0087eba20, the read back flink freelist value (should be the same as 2).
Arg4: fffff6fc5003f558, 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 fffff80002fbe130 to fffff80002e8b740
STACK_TEXT:
fffff880`033a1a58 fffff800`02fbe130 : 00000000`00000019 00000000`00000003 fffff8a0`087eba20 fffff8a0`087eba20 : nt!KeBugCheckEx
fffff880`033a1a60 fffff800`02fc04c1 : 00000000`00000000 fffff8a0`08388450 00000000`c0000016 fffff800`02e76119 : nt!ExDeferredFreePool+0xca0
fffff880`033a1af0 fffff800`0317fbfe : 00000000`ccb82c26 fffff8a0`01b86d00 fffff8a0`624e4d43 00000000`00000001 : nt!ExFreePoolWithTag+0x411
fffff880`033a1ba0 fffff800`0317fac8 : fffff8a0`0133e258 00000000`00000001 fffff8a0`007fe010 ffffffff`ffffffff : nt!CmpDereferenceNameControlBlockWithLock+0xd6
fffff880`033a1bd0 fffff800`0317e400 : 00000000`00000000 00000000`00000001 fffffa80`624e4d43 fffff880`058acbdc : nt!CmpCleanUpKcbCacheWithLock+0x34
fffff880`033a1c00 fffff800`0317e60b : 00000000`00000000 00000000`00000001 fffff8a0`007fe010 fffff800`0317e217 : nt!CmpDereferenceKeyControlBlockWithLock+0x150
fffff880`033a1c30 fffff800`0317e9c4 : 00000000`00000000 00000000`00000001 fffff8a0`007fe010 fffffa80`03622680 : nt!CmpDereferenceKeyControlBlock+0x11f
fffff880`033a1c80 fffff800`02e98961 : fffff800`0317e8dc fffff800`030305f8 fffffa80`03622680 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0xe8
fffff880`033a1cb0 fffff800`0312fc06 : ffffffff`faffbfff fffffa80`03622680 00000000`00000080 fffffa80`03608890 : nt!ExpWorkerThread+0x111
fffff880`033a1d40 fffff800`02e69c26 : fffff880`031d5180 fffffa80`03622680 fffff880`031dffc0 bfffdaff`fdbffdff : nt!PspSystemThreadStartup+0x5a
fffff880`033a1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExDeferredFreePool+ca0
fffff800`02fbe130 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ExDeferredFreePool+ca0
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+ca0
BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+ca0
Followup: Pool_corruption
i z jeszcze innego (gdyz w kazdym z 3 plikow informacyjnych o blue screenie sa inne informacje)
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Windows\Minidump\120410-23727-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03001000 PsLoadedModuleList = 0xfffff800`0323ee50
Debug session time: Sat Dec 4 18: 44: 02.888 2010 (UTC + 1: 00)
System Uptime: 0 days 0: 01: 20.667
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff80001070993, 8, fffff80001070993, 0}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ? : FNODOBFM: `string'+42837 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff80001070993, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff80001070993, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032a90e0
fffff80001070993
FAULTING_IP:
+3637346631636237
fffff800`01070993 ? ?
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: SearchFilterHo
CURRENT_IRQL: 0
TRAP_FRAME: fffff88008da3a20 -- (.trap 0xfffff88008da3a20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa800875a1d0
rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001070993 rsp=fffff88008da3bb0 rbp=fffff88008da3ca0
r8=0000000000000000 r9=0000000000000000 r10=0000000000000001
r11=fffff88008da3ba0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
fffff800`01070993 ? ?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030f1f14 to fffff80003071740
STACK_TEXT:
fffff880`08da38b8 fffff800`030f1f14 : 00000000`00000050 fffff800`01070993 00000000`00000008 fffff880`08da3a20 : nt!KeBugCheckEx
fffff880`08da38c0 fffff800`0306f82e : 00000000`00000008 fffffa80`08759060 00000000`00000000 fffff800`035e4b7f : nt! ? : FNODOBFM: `string'+0x42837
fffff880`08da3a20 fffff800`01070993 : fffffa80`08759060 00000000`00b0fc58 fffff880`08da3bc8 fffff8a0`022f5060 : nt!KiPageFault+0x16e
fffff880`08da3bb0 fffffa80`08759060 : 00000000`00b0fc58 fffff880`08da3bc8 fffff8a0`022f5060 00000000`00000000 : 0xfffff800`01070993
fffff880`08da3bb8 00000000`00b0fc58 : fffff880`08da3bc8 fffff8a0`022f5060 00000000`00000000 0000007f`fffffff8 : 0xfffffa80`08759060
fffff880`08da3bc0 fffff880`08da3bc8 : fffff8a0`022f5060 00000000`00000000 0000007f`fffffff8 00000000`00000000 : 0xb0fc58
fffff880`08da3bc8 fffff8a0`022f5060 : 00000000`00000000 0000007f`fffffff8 00000000`00000000 00000000`00000000 : 0xfffff880`08da3bc8
fffff880`08da3bd0 00000000`00000000 : 0000007f`fffffff8 00000000`00000000 00000000`00000000 00000000`000000c4 : 0xfffff8a0`022f5060
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ? : FNODOBFM: `string'+42837
fffff800`030f1f14 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ? : FNODOBFM: `string'+42837
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x50_nt!_??_: FNODOBFM: _string_+42837
BUCKET_ID: X64_0x50_nt!_??_: FNODOBFM: _string_+42837
Followup: MachineOwner
---------
Notatka została dodana nie znane . Ostatnia edycja dokonana 06.12.2010 23:47 przez Nostromo:
Kody wstawiamy w znaki code, poprawiłem tytuł i liczne błędy w poście (masz polską klawiaturę więc jej używaj).
|
Post: #1
