Wykryto wyłączony javascript

Aktualnie masz wyłączony javascript. Kilka funkcji może nie działać. Włącz ponownie javascript, aby korzystać z pełnej funkcjonalności.

blue screen po zalogowaniu się windows7

Rozpoczęty przez Adept , 21 07 2012 18:19

Zaloguj się, aby dodać odpowiedź

2 odpowiedzi w tym temacie

#1 Adept

Początkujący

71 postów

Napisano 21 07 2012 - 22:25

Witam!

Piszę szybo, bo w każdej chwili może mi wywalić.
Otóż nie wiem skąd, zaczęły mi się pojawiać BSOD'y podczas normalnego użytkowania kompa(nie grania).
Oto zrzuty:

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

Loading Dump File [C:\Windows\Minidump\072112-27892-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symsols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e0b000 PsLoadedModuleList = 0xfffff800`03048e50
Debug session time: Sat Jul 21 18:15:38.657 2012 (GMT+2)
System Uptime: 0 days 0:06:40.984
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*																			 *
*					 Bugcheck Analysis								 *
*																			 *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a00af66000, 0, fffff80003141079, 0}

Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiCompressRelocations+70 )
Followup: MachineOwner
---------
1: 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: fffff8a00af66000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80003141079, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------

Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b30e0
fffff8a00af66000
FAULTING_IP:
nt!MiCompressRelocations+70
fffff800`03141079 410fb701	 movzx eax,word ptr [r9]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800a6a9040 -- (.trap 0xfffff8800a6a9040)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003141079 rsp=fffff8800a6a91d0 rbp=000000000008fc28
r8=000000007ffff960 r9=fffff8a00af66000 r10=000000000006ed2c
r11=0000000000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0		 nv up ei pl nz na po nc
nt!MiCompressRelocations+0x70:
fffff800`03141079 410fb701	 movzx eax,word ptr [r9] ds:9100:fffff8a0`0af66000=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002efc1e4 to fffff80002e7cf00
STACK_TEXT:
fffff880`0a6a8ed8 fffff800`02efc1e4 : 00000000`00000050 fffff8a0`0af66000 00000000`00000000 fffff880`0a6a9040 : nt!KeBugCheckEx
fffff880`0a6a8ee0 fffff800`02e7afee : 00000000`00000000 00000000`00000003 fffffa80`04724300 fffff8a0`0aef8824 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`0a6a9040 fffff800`03141079 : 00000000`01000000 fffff800`03141461 fffffa80`0420f300 fffff800`031415a4 : nt!KiPageFault+0x16e
fffff880`0a6a91d0 fffff800`0313f932 : 00000000`000d56a0 00000000`01000000 00000000`00000001 00000000`00000004 : nt!MiCompressRelocations+0x70
fffff880`0a6a9220 fffff800`031755d1 : fffff8a0`0ac7e000 fffff880`0a6a9430 00000000`00000095 00000000`00000000 : nt!MiRelocateImage+0x4a2
fffff880`0a6a9390 fffff800`0316a893 : fffff880`0a6a95f0 00000000`00000000 fffff880`0a6a9698 00000000`00000001 : nt!MmCreateSection+0x825
fffff880`0a6a95a0 fffff800`032d9573 : 00000000`00000000 fffff8a0`0a28ed88 00000000`00000000 00000000`00000001 : nt!NtCreateSection+0x162
fffff880`0a6a9620 fffff800`032d9b01 : 00000000`00000000 fffff8a0`0a28ed88 fffffa80`04cfc510 fffff880`00000060 : nt!PfpFileBuildReadSupport+0x163
fffff880`0a6a9710 fffff800`032e1c1e : fffff8a0`00000000 fffff8a0`00000004 fffff8a0`00000015 00000000`00000001 : nt!PfpPrefetchFilesTrickle+0x121
fffff880`0a6a9810 fffff800`032e27b7 : 00000000`00000000 fffff880`0a6a9ca0 fffff880`0a6a9a08 fffff8a0`0176b060 : nt!PfpPrefetchRequestPerform+0x30e
fffff880`0a6a9960 fffff800`032eed8e : fffff880`0a6a9a08 00000000`00000001 fffffa80`069e8930 00000000`00000000 : nt!PfpPrefetchRequest+0x176
fffff880`0a6a99d0 fffff800`032f34be : 00000000`00000000 00000000`00e6f810 00000000`0000004f 00000000`00000001 : nt!PfSetSuperfetchInformation+0x1ad
fffff880`0a6a9ab0 fffff800`02e7c153 : fffffa80`06c59b60 00000000`00000000 00000000`00000001 00000000`00000001 : nt!NtSetSystemInformation+0xb91
fffff880`0a6a9c20 00000000`771115aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00e6f7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771115aa

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiCompressRelocations+70
fffff800`03141079 410fb701	 movzx eax,word ptr [r9]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiCompressRelocations+70
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiCompressRelocations+70
BUCKET_ID: X64_0x50_nt!MiCompressRelocations+70
Followup: MachineOwner
---------

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

Loading Dump File [C:\Windows\Minidump\072112-28142-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symsols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e4d000 PsLoadedModuleList = 0xfffff800`0308ae50
Debug session time: Sat Jul 21 18:07:02.387 2012 (GMT+2)
System Uptime: 0 days 0:02:40.838
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*																			 *
*					 Bugcheck Analysis								 *
*																			 *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a004966000, 0, fffff80003183079, 0}

Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiCompressRelocations+70 )
Followup: MachineOwner
---------
0: 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: fffff8a004966000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80003183079, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------

Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f50e0
fffff8a004966000
FAULTING_IP:
nt!MiCompressRelocations+70
fffff800`03183079 410fb701	 movzx eax,word ptr [r9]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800976d5d0 -- (.trap 0xfffff8800976d5d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003183079 rsp=fffff8800976d760 rbp=000000000008fc28
r8=000000007ffff960 r9=fffff8a004966000 r10=000000000006ed2c
r11=0000000000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0		 nv up ei pl nz na po nc
nt!MiCompressRelocations+0x70:
fffff800`03183079 410fb701	 movzx eax,word ptr [r9] ds:fffff8a0`04966000=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002f3e1e4 to fffff80002ebef00
STACK_TEXT:
fffff880`0976d468 fffff800`02f3e1e4 : 00000000`00000050 fffff8a0`04966000 00000000`00000000 fffff880`0976d5d0 : nt!KeBugCheckEx
fffff880`0976d470 fffff800`02ebcfee : 00000000`00000000 00000000`00000003 fffff800`03074a00 fffff800`02ee5e00 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`0976d5d0 fffff800`03183079 : fffffa80`060b7de0 fffff800`03183461 fffffa80`060b7de0 fffff800`031835a4 : nt!KiPageFault+0x16e
fffff880`0976d760 fffff800`03181932 : 00000000`000d56a0 00000000`01000000 00000000`00000001 00000000`00000004 : nt!MiCompressRelocations+0x70
fffff880`0976d7b0 fffff800`031b75d1 : fffff8a0`0286a000 fffff880`0976d9c0 00000000`00000095 00000000`00000000 : nt!MiRelocateImage+0x4a2
fffff880`0976d920 fffff800`031ac893 : fffff880`0976db80 00000000`00000000 00000000`00000000 00000000`00000001 : nt!MmCreateSection+0x825
fffff880`0976db30 fffff800`02ebe153 : fffffa80`063b2b60 00000000`030dde88 fffff880`0976dbc8 00000000`00000000 : nt!NtCreateSection+0x162
fffff880`0976dbb0 00000000`77c5035a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`030dde68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c5035a

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiCompressRelocations+70
fffff800`03183079 410fb701	 movzx eax,word ptr [r9]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiCompressRelocations+70
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiCompressRelocations+70
BUCKET_ID: X64_0x50_nt!MiCompressRelocations+70
Followup: MachineOwner
---------

A oto pierwszy BSOD, który to zapoczątkował:

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

Loading Dump File [C:\Windows\Minidump\072112-40326-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symsols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e04000 PsLoadedModuleList = 0xfffff800`03041e50
Debug session time: Sat Jul 21 15:09:13.601 2012 (GMT+2)
System Uptime: 0 days 0:46:41.053
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*																			 *
*					 Bugcheck Analysis								 *
*																			 *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a013566000, 0, fffff8000313a079, 0}

Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiCompressRelocations+70 )
Followup: MachineOwner
---------
0: 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: fffff8a013566000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000313a079, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------

Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ac0e0
fffff8a013566000
FAULTING_IP:
nt!MiCompressRelocations+70
fffff800`0313a079 410fb701	 movzx eax,word ptr [r9]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: rundll32.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800a5fb5d0 -- (.trap 0xfffff8800a5fb5d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000313a079 rsp=fffff8800a5fb760 rbp=000000000008fc28
r8=000000007ffff960 r9=fffff8a013566000 r10=000000000006ed2c
r11=0000000000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0		 nv up ei pl nz na po nc
nt!MiCompressRelocations+0x70:
fffff800`0313a079 410fb701	 movzx eax,word ptr [r9] ds:fffff8a0`13566000=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ef51e4 to fffff80002e75f00
STACK_TEXT:
fffff880`0a5fb468 fffff800`02ef51e4 : 00000000`00000050 fffff8a0`13566000 00000000`00000000 fffff880`0a5fb5d0 : nt!KeBugCheckEx
fffff880`0a5fb470 fffff800`02e73fee : 00000000`00000000 00000000`00000003 fffff800`0302ba00 fffff800`02e9ce00 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`0a5fb5d0 fffff800`0313a079 : 00000000`01000000 fffff800`0313a461 fffffa80`05ee7250 fffff800`0313a5a4 : nt!KiPageFault+0x16e
fffff880`0a5fb760 fffff800`03138932 : 00000000`000d56a0 00000000`01000000 00000000`00000001 00000000`00000004 : nt!MiCompressRelocations+0x70
fffff880`0a5fb7b0 fffff800`0316e5d1 : fffff8a0`13328000 fffff880`0a5fb9c0 00000000`00000095 00000000`00000000 : nt!MiRelocateImage+0x4a2
fffff880`0a5fb920 fffff800`03163893 : fffff880`0a5fbb80 00000000`00000000 00000000`00000000 00000000`00000001 : nt!MmCreateSection+0x825
fffff880`0a5fbb30 fffff800`02e75153 : fffffa80`046d5b60 00000000`001faed8 fffff880`0a5fbbc8 00000000`00000000 : nt!NtCreateSection+0x162
fffff880`0a5fbbb0 00000000`76e2035a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001faeb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e2035a

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiCompressRelocations+70
fffff800`0313a079 410fb701	 movzx eax,word ptr [r9]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiCompressRelocations+70
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiCompressRelocations+70
BUCKET_ID: X64_0x50_nt!MiCompressRelocations+70
Followup: MachineOwner
---------

Wiecie w czym tkwi problem?

Pozdr.

Nie wiem co jest. Po jakichś 10 blue screenach postanowiłem doszczętnie usunąć Dr.Web'a w trybie awaryjnym(jednego z podprogramów nie dało się w ogóle usunąć, ciągle dodawał się sam do autostartu itd.). Uruchomiłem kompa, chwilę posiedziałem i nic. To włączyłem grę, pograłem jakieś półtorej godziny i żadnego blue screena. Nie wiem, czy akurat i się udało, czy problemem był Dr.Web. Umie ktoś z ww. zrzutów odczytać, co było problemem?

Z góry dzięki za pomoc.

Użytkownik Tomasz6688 edytował ten post 21 07 2012 - 18:30
temat edytowałem

0

Do góry

#2 Qauke

Expert

5 156 postów

Napisano 21 07 2012 - 22:29

Możliwe że jakaś aplikacja/antywirus powodował takie problemy. Zainstaluj sobie NOD32 przeskanuj system jeżeli nic nie wykryje to będziesz miał odpowiedź na swój problem

1

Do góry

#3 Adept

Początkujący

71 postów

Napisano 22 07 2012 - 12:15

Przy próbie instalacji za pierwszym razem wyskoczył Blue Screen, a za drugim jakiś błąd spowodowany Dr.Web(mimo, że odinstalowywałem go z 5 razy, usuwałem wszystko itd.), ale spróbuję jeszcze raz -.-

//edit: udało się zainstalować, ale wyskoczył po instalacji kolejny Blue Screen. Zaraz przeskanuje kompa.
//edit2: nie mogę uruchomić skanowania, ani ochrony.
"Ochrona anty wirusowa jest wyłączona.
Inicjalizacja skanera nie powiodła się. Większość modułów nie będzie działać poprawnie."
//edit3: co najlepsze, w programach znowu pojawił się Dr.Web, mimo, że wczoraj odinstalowałem go całkowicie w trybie awaryjnym i przez cały dzień go nie było.
//edit4: w żaden sposób nie dam rady usunąć pozostałości po Dr.Web, w dodatku w programach nie ma dodanego Nod32, nie ma też jego deinstalatora, więc nie mogę jego także usunąć.

//edit5: odinstalowałem Dr.Web programem Revo Uninstaller. Nie mogę odinstalować Noda, który jest błędnie zainstalowany, przez co nie ma go w liście programów, nie mogę niczym go usunąć, ani wyłączyć autouruchamiania usługi ESET Service(która sama się włącza ponownie). BLue Screena wciąż występują(szczególnie wtedy, gdy używam np: jakiś programów do czyszczenia kompa, naprawiania, usuwania programów itd.)

Użytkownik Adept edytował ten post 22 07 2012 - 11:15