SYSTEM_SERVICE_EXCEPTION 0x0000003b while playing games

Here is the Chkdsk result:
Attachment 293776

and here is the CrystalDisk info:
Attachment 293777

I've run the Seatools and it repaired the errors.
Before using Seatools for DOS:
Attachment 293779
After Seatools for DOS:
Attachment 293780

I'll report back if BSOD appears again.

crap here's the new BSOD
Attachment 293810

Hmm that caution is something to worry about.
What did SeaTools has to say about the drive, did it pass/fail the tests?

You need to update Windows right away!

Code:

lmvm dxgmms1
start             end                 module name
fffff880`04310000 fffff880`04356000   dxgmms1
    Loaded symbol image file: dxgmms1.sys
    Image path: dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Tue Aug 23 05:59:12 2011

• Driver Reference Table - dxgmms1.sys

Mine is dated April 10th 2013.

Seatools Fix the problem and it passes the test multiple times. I've also re-scan my ram overnight and it passes 10 tests. So i just need to update my windows 7 or just that dgxmms1.sys?

kdash07 said:

Seatools Fix the problem and it passes the test multiple times. I've also re-scan my ram overnight and it passes 10 tests. So i just need to update my windows 7 or just that dgxmms1.sys?

Yes update Windows in general.

It's my pleasure, thanks for the feedback :) .

Please start by removing IRST:

Code:

lmvm iaStor
Browse full module list
start             end                 module name
fffff880`01259000 fffff880`013ad000   iaStor   T (no symbols)           
    Loaded symbol image file: iaStor.sys
    Image path: iaStor.sys
    Image name: iaStor.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Feb 18 18:10:50 2011

• Driver Reference Table - iaStor.sys
• Arc said:

  Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features.
  Then Uninstall the driver from device manager.
  

  1. Right click on "my computer" icon and click "manage" on the context menu.
  2. It will open the "computer management" window.
  3. Select "Device Manager" in the left pane, It will list all the existing devices up.
  4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
  5. Select one Intel device item under it, right click, uninstall.
  6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
  7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Please upload a photograph of the back of your wireless adapter, including the FCC-ID
so we will be able to find a proper update.

Code:

lmvm bcmwl664
Browse full module list
start             end                 module name
fffff880`050ab000 fffff880`05535000   bcmwl664 T (no symbols)           
    Loaded symbol image file: bcmwl664.sys
    Image path: bcmwl664.sys
    Image name: bcmwl664.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Apr 17 15:27:30 2012

• Driver Reference Table - bcmwl664.sys

On all bug checks I'm unable to dump DV's settings, please verify that DV is enabled.

Code:

!verifier
fffff8000385bb20: Unable to get verifier list.

Run an elevated command prompt and type in verifier /query.

Start Menu> CMD - right click and Run as administrator.
Type verifier /query hit Enter and post a screenshot of the window.

dxgmms1.sys is update but it still faults on graphics routines despite running the recommended
known stable nVidia 314.22 release, something else is going on.

Code:

lmvm dxgmms1
Browse full module list
start             end                 module name
fffff880`04515000 fffff880`0455b000   dxgmms1    (deferred)             
    Mapped memory image file: c:\localsymbols\dxgmms1.sys\5164DC1346000\dxgmms1.sys
    Image path: dxgmms1.sys
    Image name: dxgmms1.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Apr 10 06:27:15 2013

I notice that in three out of the four bug checks flipped bits are present which usually
spell faulty hardware:

Code:

CONTEXT:  fffff88009cc6dd0 -- (.cxr 0xfffff88009cc6dd0)
rax=dffffa8008658bd0 rbx=fffff900c082d2a0 rcx=0000000000000002
rdx=0000000000000048 rsi=0000000000000004 rdi=fffff900c082d2a0
rip=fffff9600023c015 rsp=fffff88009cc77b0 rbp=fffff900c2d45c20
 r8=00000000000002bf  r9=0000000000000001 r10=000000008c000000
r11=0000000000000008 r12=0000000000000001 r13=0000000000000000
r14=0000000000000001 r15=0000000000000001
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
win32k!SetOrClrWF+0x69:
fffff960`0023c015 488b4808        mov     rcx,qword ptr [rax+8] ds:002b:dffffa80`08658bd8=????????????????

Code:

CONTEXT:  fffff88009184c80 -- (.cxr 0xfffff88009184c80)
rax=0000000000000005 rbx=fffff88003164180 rcx=dffff88009185cc0
rdx=0000000000000000 rsi=fffffa8003f3d060 rdi=fffffa8004797490
rip=fffff800036dae94 rsp=fffff88009185660 rbp=fffff88009185c70
 r8=0000000000000000  r9=000000000000000b r10=fffff80003662000
r11=fffff8800a103960 r12=fffff88003164180 r13=0000000000000000
r14=fffffa8007ac1b30 r15=fffff88003168f40
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!SwapContext_PatchXRstor:
fffff800`036dae94 0fae29          xrstor  [rcx]

Code:

CONTEXT:  fffff88003d407e0 -- (.cxr 0xfffff88003d407e0)
rax=dffff8a001511bb8 rbx=fffffa80088d2ce8 rcx=fffff8a001511a38
rdx=dffff8a001511bc0 rsi=fffffa80088d2ce0 rdi=0000000000000000
rip=fffff800036b976c rsp=fffff88003d411c0 rbp=fffffa80088d2ce8
 r8=ffffffffffffffff  r9=ffffffffffffffff r10=fffff8a001507720
r11=fffff8a001511bb8 r12=ffffffffffffffff r13=fffffa80061ff684
r14=0000000000004000 r15=fffffa8007286de0
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!RtlDeleteNoSplay+0x5c:
fffff800`036b976c 4c391a          cmp     qword ptr [rdx],r11 ds:002b:dffff8a0`01511bc0=????????????????

You didn't test the RAM eventually, after discovering the faulty module, which can also be a slot on the motherboard.

Testing the RAM:

koolkat77 said:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• Pay close attention to part 3 of the tutorial "If you have errors"
• Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.

Test for thermals and stability:

• Download HWinfo and post a Screenshot of the sensors window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
  
  • Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).
  
  

I already test the newly bought RAM last few days with the same slot and there is no error, it passes 10 test. I forgot to took a picture cuz i just woke up. But i'm sure there is no error and suddenly pressed ESC. I'll try The Thermals and stability

I reflashed my BIOS and it seems working perfectly. Thanks!