BSOD while playing sertain games

Hello there i have a fairly new computer and i have gotten alot of BSOD recently. I have gotten them while playing games like. Leauge of Legends, World of warcraf, Battlefield 3, i never gotten this before and i dont know what too do could you give me a hand Svenforums :)?


P.S sorry for my bad spelling (if i misspelled somthing)

Welcome aboard.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800e00a9e0, fffffa800e00acc0, fffff80002f86460}

Probably caused by : csrss.exe

Followup: MachineOwner
---------

It is a storage SSD related crash. First try to update the firmware of your OCZ-AGILITY3 and let us know the situation.

In addition to Arc's suggestion, note that you are having two antiviruses installed that would create conflicts anyway.

Code:

Start Menu\Programs\avast! Free Antivirus	Public:Start Menu\Programs\avast! Free Antivirus	Public
Start Menu\Programs\Spybot - Search & Destroy	Public:Start Menu\Programs\Spybot - Search & Destroy	Public

Please uninstall Avast & Spybot. They are known to cause instability on some systems. Malware Bytes and Microsoft Security Essentials are a great combination.

Also get the latest drivers for the SteelSeries Bus Enumerator

Code:

Probably caused by : SteelBus64.sys ( SteelBus64+12ea )
---------
0: kd> lmvm SteelBus64
start             end                 module name
fffff880`04600000 fffff880`0461f000   SteelBus64 T (no symbols)           
    Loaded symbol image file: SteelBus64.sys
    Image path: \SystemRoot\system32\DRIVERS\SteelBus64.sys
    Image name: SteelBus64.sys
    Timestamp:        Fri Jun 24 20:05:26 2011 (4E0499A6)
    CheckSum:         000277E2
    ImageSize:        0001F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Driver Reference Table

Keep us posted

Follow this link ... OCZ Technology

Code:

fffff880`0c6f8688  fffff800`02fcce50 nt!ObpLookupObjectName
fffff880`0c6f8690  fffff880`015f1409 fileinfo!FIStreamGetInfo+0x1bd
fffff880`0c6f8698  fffff880`0159c000 fltmgr!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`0c6f86a0  fffff880`015ba528 fltmgr!__PchSym_ <PERF> (fltmgr+0x1e528)
fffff880`0c6f86a8  fffff880`0159c000 fltmgr!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`0c6f86b0  fffff880`015bb188 fltmgr!__PchSym_ <PERF> (fltmgr+0x1f188)
fffff880`0c6f86b8  fffff880`015e8000 fileinfo!FILockInitialize <PERF> (fileinfo+0x0)
fffff880`0c6f86c0  fffff880`015ee27c fileinfo!PiRegStateDiscriptor <PERF> (fileinfo+0x627c)
fffff880`0c6f86c8  fffff880`015e8000 fileinfo!FILockInitialize <PERF> (fileinfo+0x0)
fffff880`0c6f86d0  fffff880`015ee1a4 fileinfo!PiRegStateDiscriptor <PERF> (fileinfo+0x61a4)
fffff880`0c6f86d8  fffff880`0159c000 fltmgr!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`0c6f86e0  fffff880`015ba210 fltmgr!__PchSym_ <PERF> (fltmgr+0x1e210)
fffff880`0c6f86e8  fffff880`0159c000 fltmgr!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`0c6f86f0  fffff880`015ba114 fltmgr!__PchSym_ <PERF> (fltmgr+0x1e114)
fffff880`0c6f86f8  fffff880`0159c000 fltmgr!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`0c6f8700  fffff880`015bb1dc fltmgr!__PchSym_ <PERF> (fltmgr+0x1f1dc)
fffff880`0c6f8708  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`0c6f8710  fffff800`02ef1b34 nt!BBTBuffer <PERF> (nt+0x299b34)
fffff880`0c6f8718  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`0c6f8720  fffff800`02ef18e8 nt!BBTBuffer <PERF> (nt+0x2998e8)
fffff880`0c6f8728  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`0c6f8730  fffff800`02ef1990 nt!BBTBuffer <PERF> (nt+0x299990)
fffff880`0c6f8738  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`0c6f8740  fffff800`02ef1b28 nt!BBTBuffer <PERF> (nt+0x299b28)
fffff880`0c6f8748  fffff800`02c58000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`0c6f8750  fffff800`02ef1c0c nt!BBTBuffer <PERF> (nt+0x299c0c)
fffff880`0c6f8758  fffff880`0c6f8f88
fffff880`0c6f8760  fffff880`015a27b0 fltmgr!FltpGetFileNameInformation+0x520

fltmgr.sys is the Microsoft Filesystem Filter Manager. So you decide if it is anything new or not.

Moreover:

Code:

fffff880`0c6f8338  fffff880`01640e54 Ntfs!NtfsExtendedCompleteRequestInternal+0x114
fffff880`0c6f8388  fffff880`016414a0 Ntfs!NtfsLookupAllocation+0x1f0
fffff880`0c6f8398  fffff880`016e3ee9 Ntfs!LfsWriteLogRecordIntoLogPage+0x329
fffff880`0c6f8488  fffff880`016eac14 Ntfs!LfsWrite+0x404
fffff880`0c6f8490  fffffa80`108b5f00
fffff880`0c6f8498  fffff880`0c6f8690
fffff880`0c6f84a0  00000000`00000000
fffff880`0c6f84a8  fffffa80`108b5f00
fffff880`0c6f84b0  00000000`00000001
fffff880`0c6f84b8  fffffa80`09933e54
fffff880`0c6f84d8  fffff880`016414a0 Ntfs!NtfsLookupAllocation+0x1f0
fffff880`0c6f84e8  fffff880`016e3ee9 Ntfs!LfsWriteLogRecordIntoLogPage+0x329

And so on .

So you decide your course of action.

At the same time, it indicates something not very good.

Code:

CHKIMG_EXTENSION: !chkimg -lo 50 -db !fltmgr
6 errors : !fltmgr (fffff880015a20bc-fffff880015a2fa4)
fffff880015a20b0  25  88  01  00  00  44  0f  b6  e2  48  89  81 *ba  00  00  00 %....D...H......
...
fffff880015a24e0  48  00  00  ff *11  37  cc  00  00  f6  47  20  01  0f  84  b7 H....7....G ....
...
fffff880015a27b0  ff  15  62  c9 *40  00  48  8d  ae  90  00  00  00  48  8b  cd ..b.@.H......H..
...
fffff880015a2970  00  00  00  4c  8b  4f  38  48  8b  4f  08  4c *cb  c5  ba  01 ...L.O8H.O.L....
...
fffff880015a2d20  39  0b  0f  85 *4c  2a  00  00  45  84  ed  74  23  48  83  7d 9...L*..E..t#H.}
...
fffff880015a2fa0  b4  c1  00  00 *b3  c0  41  bb  11  00  00  00  f0  4c  0f  b1 ......A......L..

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff8800c6f87e0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

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

RAM - Test with Memtest86+
Run it for at least eight passes. Preferably overnight.

Also, Serch for any available update for your graphics card after September.
Video Card - Stress Test with Furmark

Let us know the result.

Well .... if the result is ... another crash ... I haven't done the earlier things though ..... you need not to report anything.

Just checking dumps cannot solve BSOD problems. It is follow the results and courses of actions obtained from dump checks.
I wish you will be able to understand what I am saying.