Mozg666
Nowy
Liczba postów: 1
|
Blue Screen.
Witam
parę dni temu zaczął mnie prześladywać dosyć dziwny problem.Kiedy gram albo przeglądam coś na internecie pojawia się blue screen wczoraj stwierdziłem , że nawet format komputera zrobie i niestety nic to nie dało jest to dość dziwny problem bo 2 dni temu nie moglem normalnie komputera włączyć bo ciągle blue screen teraz normalnie siedzę nic mnie nie wywala. Jeszcze bym prosił kogoś kto się na tym dobrze zna żeby obczaił ten plik z folderu Minidump.
http://www.speedyshare.com/files/2997273...796-01.rar
Pozdrawiam
(Ten post był ostatnio modyfikowany: 21.08.2011 21:53 przez Mozg666.)
21.08.2011 21:53
|
thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Blue Screen.
Najpierw przeleć pamięć RAM memtestem86. Póki o nic szczególnego z dumpa nie wynika. Sprawcą jest proces systemowy, który próbuje zapisać coś do pamięci.
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\082111-19796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C: \Symbols;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`0284d000 PsLoadedModuleList = 0xfffff800`02a8ae50
Debug session time: Sun Aug 21 17: 52: 32.168 2011 (UTC + 2: 00)
System Uptime: 0 days 1: 18: 39.118
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff800009eb708, 2, 1, fffff800028c3f10}
Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+839 )
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: fffff800009eb708, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff800028c3f10, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002af50e0
fffff800009eb708
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiDeferredReadyThread+839
fffff800`028c3f10 48895008 mov qword ptr [rax+8],rdx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88002f1b3d0 -- (.trap 0xfffff88002f1b3d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800009eb700 rbx=0000000000000000 rcx=fffff880009eb700
rdx=fffffa800596c100 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028c3f10 rsp=fffff88002f1b560 rbp=0000000000000001
r8=0000000000000008 r9=0000000000000008 r10=fffff8000284d000
r11=fffff88002f1b5b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KiDeferredReadyThread+0x839:
fffff800`028c3f10 48895008 mov qword ptr [rax+8],rdx ds: 337f: fffff800`009eb708=???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800028be469 to fffff800028bef00
STACK_TEXT:
fffff880`02f1b288 fffff800`028be469 : 00000000`0000000a fffff800`009eb708 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f1b290 fffff800`028bd0e0 : 00000000`0000000a fffff880`009e7180 fffff880`009e7180 fffff800`028cb5e0 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b3d0 fffff800`028c3f10 : fffff880`02fd3180 fffffa80`06768910 00000000`00000000 fffffa80`05af24d0 : nt!KiPageFault+0x260
fffff880`02f1b560 fffff800`028ca3b7 : fffffa80`067be060 fffffa80`06a2a880 fffffa80`06a2a880 fffffa80`05f1d950 : nt!KiDeferredReadyThread+0x839
fffff880`02f1b5e0 fffff800`028cae7e : 0000000a`fcd06220 fffff880`02f1bc58 00000000`00049da9 fffff880`009eaaa8 : nt!KiProcessExpiredTimerList+0x157
fffff880`02f1bc30 fffff800`028ca697 : 00000002`cd80edc5 00000002`00049da9 00000002`cd80edb9 00000000`000000a9 : nt!KiTimerExpiration+0x1be
fffff880`02f1bcd0 fffff800`028c76fa : fffff880`009e7180 fffff880`009f1fc0 00000000`00000000 fffff800`029ddc80 : nt!KiRetireDpcList+0x277
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDeferredReadyThread+839
fffff800`028c3f10 48895008 mov qword ptr [rax+8],rdx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiDeferredReadyThread+839
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0xA_nt!KiDeferredReadyThread+839
BUCKET_ID: X64_0xA_nt!KiDeferredReadyThread+839
Followup: MachineOwner
---------
![[Obrazek: 2089620800_1406976151.png]](http://obrazki.elektroda.pl/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.
|
Post: #1
