BSOD memory+corruption

[Ercio]

Witam.
Od pewnego czasu zaczęły mi się pokazywać bluescreeny. Kiedyś grałem w League of Legends i mi też wywalało lecz po jakimś czasie to ustąpiło i teraz wogóle tego nie mam. Jednak ostatnio pobrałem grę Smite i tutaj notorycznie wywala mi co 20 min ... Sprawdziłem blue screena w programie Windows Debugging Tools oto co otrzymałem

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


Loading Dump File [C:\Windows\Minidump\070612-18421-01.dmp]
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 Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Kernel base = 0x82c45000 PsLoadedModuleList = 0x82d8f850
Debug session time: Fri Jul 6 18:42:45.866 2012 (GMT+2)
System Uptime: 0 days 0:25:01.819
Loading Kernel Symbols
.........................................................................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {c07c8754, 2, 1, 82cbc9b3}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

1: kd>
Implicit thread is now 84f6c440
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: c07c8754, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 82cbc9b3, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetUlongFromAddress: unable to read from 82daf718
Unable to read MiSystemVaType memory at 82d8f1a0
c07c8754

CURRENT_IRQL: 2

FAULTING_IP:
nt!SwapContext_PatchFxe+53
82cbc9b3 894204 mov [edx+0x4],eax

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 82cbc9b3 to 82c865cb

STACK_TEXT:
a1716b94 82cbc9b3 badb0d00 c07c8750 00000000 nt!KiTrap0E+0x2cf
a1716c0c 82cbc766 a1716c58 84f6c440 82d70d20 nt!SwapContext_PatchFxe+0x53
a1716c20 82cc369d 84f6c440 82d73f08 82d70d20 nt!KiSwapContext+0x26
a1716c58 82cc24f7 00000000 84f6c440 ffffffff nt!KiSwapThread+0x266
a1716c80 82cc21d5 84f6c440 84f6c500 00000074 nt!KiCommitThreadWait+0x1df
a1716cd8 82e6f9fd 82c13b01 00000000 a1716cfc nt!KeDelayExecutionThread+0x2aa
a1716d24 82c831ea 00000000 0e3bff38 0e3bff5c nt!NtDelayExecution+0x8d
a1716d24 76e470b4 00000000 0e3bff38 0e3bff5c nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0e3bff5c 00000000 00000000 00000000 00000000 0x76e470b4


STACK_COMMAND: .bugcheck ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
82cbcd6f - nt!KeFlushCurrentTb+1f
[ c3:00 ]
1 error : !nt (82cbcd6f)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BYTE

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE

BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE

Followup: memory_corruption
---------

[seba86mu]

Na początku sprawdź pamięć RAM programem Memtest86+:
=> http://www.hotfix.pl/instrukcja-obslugi ... m-a204.htm
Jeżeli posiadasz więcej niż jedną kość RAM wyjmij zbędne i testuj jedną.
Tak sprawdź każdą kość z osobna.