BSOD podczas uruchamiania systemu


(n33trox) #1

//edit: Proszę o przeniesienie tematu do odpowiedniego działu. Oczywiście nie zauważyłem działu poświęconemu Windows 7...

Od wczoraj mam jakiś bug w systemie. Wczoraj podczas uruchamiania kompa (koło godziny 18), już po pojawieniu się pulpitu wywaliło mi BSODa. Dziś na ekranie bootowania znów ten sam błąd i o podobnej porze. Ten bug się nie pojawia zawsze przy odpalaniu systemu. Do tej pory tylko 2 razy, a system odpalany był o wiele częściej w ciągu tych dwóch dni i nic nie wyskakiwało. Jednak wolałbym, żeby takie cuda się nie zdarzały. System to Windows 7 Professional 64 bit, SP1 + wszystkie aktualizacje zainstalowane.

Oto, co wypisuje WinDBG na ten temat:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64

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:\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

Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506

Machine Name:

Kernel base = 0xfffff800`02c62000 PsLoadedModuleList = 0xfffff800`02ea7670

Debug session time: Wed Aug 17 19:36:17.505 2011 (GMT+2)

System Uptime: 0 days 0:01:32.160

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

....

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck 50, {fffffa8301ea8bf8, 0, fffff80002dd1b52, 5}



Could not read faulting driver name

Probably caused by : rdyboost.sys ( rdyboost!ST_STORE::StReleaseRegion+4e )


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: fffffa8301ea8bf8, memory referenced.

Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.

Arg3: fffff80002dd1b52, If non-zero, the instruction address which referenced the bad memory

	address.

Arg4: 0000000000000005, (reserved)


Debugging Details:

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



Could not read faulting driver name


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f11100

 fffffa8301ea8bf8 


FAULTING_IP: 

nt!MmFreePagesFromMdl+c2

fffff800`02dd1b52 488b4728 mov rax,qword ptr [rdi+28h]


MM_INTERNAL_CODE: 5


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT


BUGCHECK_STR: 0x50


PROCESS_NAME: svchost.exe


CURRENT_IRQL: 0


TRAP_FRAME: fffff88008614630 -- (.trap 0xfffff88008614630)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000058000000000 rbx=0000000000000000 rcx=000fffffffffffff

rdx=00000000000a37ee rsi=0000000000000000 rdi=0000000000000000

rip=fffff80002dd1b52 rsp=fffff880086147c0 rbp=fffffa8004a8cc20

 r8=00000000100a383f r9=0000000000000000 r10=fffffa8003600250

r11=00000000000000c0 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe cy

nt!MmFreePagesFromMdl+0xc2:

fffff800`02dd1b52 488b4728 mov rax,qword ptr [rdi+28h] ds:7511:00000000`00000028=????????????????

Resetting default scope


LAST_CONTROL_TRANSFER: from fffff80002c893bf to fffff80002cdec40


STACK_TEXT:  

fffff880`086144c8 fffff800`02c893bf : 00000000`00000050 fffffa83`01ea8bf8 00000000`00000000 fffff880`08614630 : nt!KeBugCheckEx

fffff880`086144d0 fffff800`02cdcd6e : 00000000`00000000 fffffa83`01ea8bf8 fffffa80`036ccc00 00000000`00000006 : nt! ?? ::FNODOBFM::`string'+0x44791

fffff880`08614630 fffff800`02dd1b52 : 00000000`00000005 fffffa80`04a8cc18 fffffa80`04a8cbc0 fffff880`0192a002 : nt!KiPageFault+0x16e

fffff880`086147c0 fffff880`01913eb2 : 00000000`000000d0 fffffa80`04a8cbc0 fffffa80`04194118 00000000`000000d1 : nt!MmFreePagesFromMdl+0xc2

fffff880`08614820 fffff880`019137df : fffffa80`04194118 00000000`00000000 fffffa80`041e5fe6 fffffa80`00000000 : rdyboost!ST_STORE::StReleaseRegion+0x4e

fffff880`08614880 fffff880`019124ce : fffffa80`041940b0 00000000`00000001 fffffa80`041940b0 00000000`00000001 : rdyboost!ST_STORE::StDmCleanup+0x183

fffff880`086148c0 fffff880`01911a27 : fffffa80`041940b0 00000000`00000001 fffffa80`041940b0 fffff880`08614ca0 : rdyboost!SMKM_STORE::SmStCleanup+0x7a

fffff880`08614900 fffff880`0191198a : fffff880`019348f0 00000000`00000008 fffffa80`041940b0 fffff880`01934870 : rdyboost!SMKM_STORE_MGR::SmStoreMgrCallback+0x4b

fffff880`08614940 fffff880`019384b8 : fffff880`01934870 fffff880`08614ca0 00000000`00000000 fffffa80`06491b50 : rdyboost!SMKM_STORE_MGR::SmCleanup+0x9a

fffff880`08614970 fffff880`01919b26 : fffffa80`06491b50 fffffa80`06491b50 00000000`00000000 00000000`00000000 : rdyboost!SmdRBContextShutdown+0x94

fffff880`086149b0 fffff800`02ff9a97 : 00000000`00000000 fffffa80`059911e0 fffffa80`059912f8 fffffa80`06491b50 : rdyboost!SmdDispatchDeviceControl+0x3ce

fffff880`08614a10 fffff800`02ffa2f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607

fffff880`08614b40 fffff800`02cdded3 : ffffffff`ffffffff 0000007f`ffffffff 00000000`016eec30 00000980`00000030 : nt!NtDeviceIoControlFile+0x56

fffff880`08614bb0 00000000`7751138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

00000000`016eee28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7751138a



STACK_COMMAND: kb


FOLLOWUP_IP: 

rdyboost!ST_STORE::StReleaseRegion+4e

fffff880`01913eb2 33d2 xor edx,edx


SYMBOL_STACK_INDEX: 4


SYMBOL_NAME: rdyboost!ST_STORE::StReleaseRegion+4e


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: rdyboost


IMAGE_NAME: rdyboost.sys


DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7982e


FAILURE_BUCKET_ID: X64_0x50_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e


BUCKET_ID: X64_0x50_rdyboost!ST_STORE_SMD_TRAITS_::StReleaseRegion+4e


Followup: MachineOwner

---------

Widzę, że coś tam pisze o ReadyBoost. Tylko, że ja ReadyBoost nigdy nie używałem, żadnych sterowników do tego nie wgrywałem. Da się coś z tym zrobić, czy pozostaje format?


(takiktoś) #2

Problem może rozwiązać usunięcie tego sterownika ręcznie. Znajdź go w C:/Windows/system32/drivers Tam powinien być plik rdyboost.sys, który usuwasz. Problem powinien zniknąć. :slight_smile: