Witam, mam taki problem, od dawna dość pojawia mi się BS dziś zdołałem go uchwycić, niby system działa mi dobrze, ale w grach np obraz mi się tak jakby przesuwał falą, nie umiem inaczej tego wytłumaczyć. Proszę o pomoc załączam ss'a BS'a
http://www.fotosik.pl/pokaz_obrazek/34c4...21f95.html
Z góry dziękuję za pomoc.
Zajrzyj do folderu c:\windows\mindump i spakuj całą zawartość plików *.dmp jeśli są jakieś wystawiając to na hosting do pobrania i analizy.
Najpierw proszę zainstalować zbiór łat SP1
http://windows.microsoft.com/installwindows7sp1
Po restarcie następne poprawki (można partiami) ponieważ ten system nie jest patchowany a w połączeniu z coraz nowszymi sterownikami będą coraz częstsze problemy
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\bsody\031115-14601-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82e0e000 PsLoadedModuleList = 0x82f56810
Debug session time: Wed Mar 11 14: 04: 10.154 2015 (UTC + 2: 00)
System Uptime: 0 days 1: 15: 29.839
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
Unable to load image cdd.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {fc5905bc, 0, 825337ca, 0}
Could not read faulting driver name
Probably caused by : cdd.dll ( cdd+37ca )
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: fc5905bc, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 825337ca, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from 82f76718
Unable to read MiSystemVaType memory at 82f56160
fc5905bc
FAULTING_IP:
cdd+37ca
825337ca 83beac05000000 cmp dword ptr [esi+5ACh],0
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82329d9f to 825337ca
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9e09fc70 82329d9f ffaeab68 40001580 60121d99 cdd+0x37ca
9e09fc9c 82311d00 ffb8c748 60121d99 40001580 win32k!EngModifySurface+0xa84
9e09fd1c 82e5142a 60121d99 00000005 014bf66c win32k!EngAllocMem+0x4a05
9e09fd1c 76e564f4 60121d99 00000005 014bf66c nt!KiFastCallEntry+0x12a
014bf680 00000000 00000000 00000000 00000000 0x76e564f4
STACK_COMMAND: kb
FOLLOWUP_IP:
cdd+37ca
825337ca 83beac05000000 cmp dword ptr [esi+5ACh],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: cdd+37ca
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cdd
IMAGE_NAME: cdd.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bd992
FAILURE_BUCKET_ID: 0x50_cdd+37ca
BUCKET_ID: 0x50_cdd+37ca
Followup: MachineOwner
---------