[Problem]BlueScreen podczas uruchamiania systemu WINDOWS 7


(Mclaren0) #1

Witam podczas włączania systemu wyskakuje BlueScreen. Dzieje się tak od wczoraj.[Wczoraj elektrownia wyłączyła prąd na 2sekundy poczym go włączyła Komputer był wtedy włączony] Problem w tym że np 10razy się nie da włączyć komputera nic nie daje uruchomienie PC w trybie awaryjnym itp i cały czas blue s. występuje wszystko się ładuje jest napis windowsa gdy już on zniknie pojawia się Blue Screen. Komputer mam postawiony w szafce z obu stron zakrytej więc postanowiłem go stamtąd wyciągnąć i nagle komputer się bez problemu włączył dodam że gdy był w szafce strasznie buczał i się chyba przegrzewał . Daje wam tu plik dmp może wam to coś mówi bo ja szukałem i nie znalazłem z góry dzięki za pomoc!

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C]

Mini Kernel Dump File: Only registers and stack trace are available


Symbol search path is: SRV*c:\symbole*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

Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030

Machine Name:

Kernel base = 0xfffff800`03251000 PsLoadedModuleList = 0xfffff800`03495670

Debug session time: Fri Aug 10 12:55:00.480 2012 (GMT+2)

System Uptime: 0 days 0:00:22.776

Loading Kernel Symbols

...............................................................

................................................................

.....

Loading User Symbols

Loading unloaded module list

....

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 7A, {fffff8a000dea840, ffffffffc000009c, 9ab738c0, fffff900c0908000}


Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : win32k.sys ( win32k+29b9 )


Followup: MachineOwner

---------


1: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************


KERNEL_DATA_INPAGE_ERROR (7a)

The requested page of kernel data could not be read in. Typically caused by

a bad block in the paging file or disk controller error. Also see

KERNEL_STACK_INPAGE_ERROR.

If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,

it means the disk subsystem has experienced a failure.

If the error status is 0xC000009A, then it means the request failed because

a filesystem failed to make forward progress.

Arguments:

Arg1: fffff8a000dea840, lock type that was held (value 1,2,3, or PTE address)

Arg2: ffffffffc000009c, error status (normally i/o status code)

Arg3: 000000009ab738c0, current process (virtual address for lock type 3, or PTE)

Arg4: fffff900c0908000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)


Debugging Details:

------------------



ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR


DISK_HARDWARE_ERROR: There was error with disk hardware


BUGCHECK_STR: 0x7a_c000009c


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT


PROCESS_NAME: csrss.exe


CURRENT_IRQL: 0


TRAP_FRAME: fffff88008aba890 -- (.trap 0xfffff88008aba890)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=000000000012fe25 rbx=0000000000000000 rcx=fffff900c0908000

rdx=fffff900c0abf898 rsi=0000000000000000 rdi=0000000000000000

rip=fffff960000e29b9 rsp=fffff88008abaa20 rbp=01cbd01376d311dd

 r8=0000000009d8ba36 r9=0000000000000000 r10=0000000000000000

r11=fffff88008abaab0 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 ov up ei ng nz ac pe cy

win32k+0x29b9:

fffff960`000e29b9 ?? ???

Resetting default scope


LAST_CONTROL_TRANSFER: from fffff8000333d542 to fffff800032d01c0


STACK_TEXT:  

fffff880`08aba5b8 fffff800`0333d542 : 00000000`0000007a fffff8a0`00dea840 ffffffff`c000009c 00000000`9ab738c0 : nt!KeBugCheckEx

fffff880`08aba5c0 fffff800`032f6fff : fffffa80`049e78f0 fffff880`08aba6f0 fffff880`08aa6c00 fffff800`032f70ae : nt! ?? ::FNODOBFM::`string'+0x3717a

fffff880`08aba6a0 fffff800`032dd789 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff800`032dc7c8 : nt!MiIssueHardFault+0x28b

fffff880`08aba730 fffff800`032ce2ee : 00000000`00000000 fffff900`c0908000 fffff880`08aba900 fffffa80`05472840 : nt!MmAccessFault+0x1399

fffff880`08aba890 fffff960`000e29b9 : 00000000`b5548436 fffff900`c0908000 fffff880`08abaa40 fffff960`000e33f6 : nt!KiPageFault+0x16e

fffff880`08abaa20 00000000`b5548436 : fffff900`c0908000 fffff880`08abaa40 fffff960`000e33f6 fffffa80`05472840 : win32k+0x29b9

fffff880`08abaa28 fffff900`c0908000 : fffff880`08abaa40 fffff960`000e33f6 fffffa80`05472840 ffffffff`80000228 : 0xb5548436

fffff880`08abaa30 fffff880`08abaa40 : fffff960`000e33f6 fffffa80`05472840 ffffffff`80000228 00000000`00000000 : 0xfffff900`c0908000

fffff880`08abaa38 fffff960`000e33f6 : fffffa80`05472840 ffffffff`80000228 00000000`00000000 fffffa80`05472840 : 0xfffff880`08abaa40

fffff880`08abaa40 fffffa80`05472840 : ffffffff`80000228 00000000`00000000 fffffa80`05472840 00000000`00000044 : win32k+0x33f6

fffff880`08abaa48 ffffffff`80000228 : 00000000`00000000 fffffa80`05472840 00000000`00000044 fffff880`08abaca0 : 0xfffffa80`05472840

fffff880`08abaa50 00000000`00000000 : fffffa80`05472840 00000000`00000044 fffff880`08abaca0 00000000`00000000 : 0xffffffff`80000228



STACK_COMMAND: kb


FOLLOWUP_IP: 

win32k+29b9

fffff960`000e29b9 ?? ???


SYMBOL_STACK_INDEX: 5


SYMBOL_NAME: win32k+29b9


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: win32k


IMAGE_NAME: win32k.sys


DEBUG_FLR_IMAGE_TIMESTAMP: 0


FAILURE_BUCKET_ID: X64_0x7a_c000009c_win32k+29b9


BUCKET_ID: X64_0x7a_c000009c_win32k+29b9


Followup: MachineOwner

---------


1: kd> lmvm win32k

start end module name

fffff960`000e0000 fffff960`003f5000 win32k T (no symbols)           

    Loaded symbol image file: win32k.sys

    Image path: \SystemRoot\System32\win32k.sys

    Image name: win32k.sys

    Timestamp: unavailable (00000000)

    CheckSum: 00000000

    ImageSize: 00315000

    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

1: kd> .trap 0xfffff88008aba890

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=000000000012fe25 rbx=0000000000000000 rcx=fffff900c0908000

rdx=fffff900c0abf898 rsi=0000000000000000 rdi=0000000000000000

rip=fffff960000e29b9 rsp=fffff88008abaa20 rbp=01cbd01376d311dd

 r8=0000000009d8ba36 r9=0000000000000000 r10=0000000000000000

r11=fffff88008abaab0 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 ov up ei ng nz ac pe cy

win32k+0x29b9:

fffff960`000e29b9 ??

Link:

http://rapidgator.net/file/31375852/081012-24445-01.dmp.html

(adam9870) #2

Reperacja nakładkowa bez utraty danych www.fixitpc.pl/topic/1234-reperacja-nak ... ty-danych/

Sprawdź sprzęt, zwłaszcza zasilacz jak-prawidlowo-sprawdzic-napiecia-zasilacza-komputerowego-t9809.html http://www.dobreprogramy.pl/GBM/Podstaw ... 25460.html

Pozdrawiam.


(Mclaren0) #3

problem znowu wystąpił. Znowu komputer się nie chciał włączyć pare razy ale się udało co może być powodem jakieś pomysły?

-- Dodane 11.08.2012 (So) 11:23 --

@ref