BSOD whenever playing games, 0x1E or 0x3B

Hi everyone,

So sorry to be just dropping in--I've been lurking since my first laptop (now on third) and I've been able to fix BSODs just reading. But this one's really a pain.

I get BSODs whenever I game--this happens whatever game I play, sometimes a few minutes after I start, sometimes a few hours. Often, WhoCrashed presents me with ntoskrnl.exe as the culprit, but sometimes involves ndis.sys, win32k.sys, etc etc... (attached the dumps I grabbed using SF Diagnostic tools). Also, if the mijxfilt.sys still shows up on the report, disregard that. I've long since uninstalled that (MotioninJoy).

System specs (for easy viewing):
HP Pavilion dv6-7009tx
Intel Core i7-3610QM
NVIDIA GT 650M GDDR5
64gb MyDigitalSSD BP3 mSATA (System Drive)
1TB WD Scorpio Blue

If it helps, I use ThrottleStop to disable my processor's turbo while gaming, though I can't find anyone BSODing while using it. I also use NVIDIAInspector to overclock, although the problem persists whether or not I do overclock. I've also tried not turning off turbo, but same thing.

Anyway, really appreciate it if you can help shed light on this. It's really been an annoying habit of this laptop.

Thanks guys!

Right, you appear to have memory corruption. Can you please run memtest86 for at least 8 passes. Follow these instructions.

RAM - Test with Memtest86+

But you also appear to have a video memory management which indicates a faulty graphics card. Please run furmark to stress test your GPU. Follow these instructions.

Video Card - Stress Test with Furmark

You also appear to have driver issues related to your Intel Centrino wireless-n 2230 network card

Before updating the driver please create a restore point. If you don't know how to create a restore point follow these instructions

System Restore Point - Create

Please update the driver here

Driver Details | Dell US

You also have problems with your MotioninJoy simulate Xbox 360 controller

Please remove it or update the driver here

MotioninJoy simulate Xbox 360 controller(virtual Xinput device) | MotioninJoy

Right, to be honest the BSODs are starting to look really random. To me it seems like a virus, can you please run your normal anti virus and download malwarebytes free to scan for viruses. When you're installing it make sure you untick the box that activates a 60 day trial of malwarebytes pro.

https://www.malwarebytes.org/free/

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002e8ae94, fffff8800e63dde0, 0}

Probably caused by : memory_corruption

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 10E, {16, fffffa801b97d4e0, 8000000000c000, 400}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+e9 ) <-- Graphics display crash

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000016, Driver broke the guaranteed DMA buffer model contract.
Arg2: fffffa801b97d4e0
Arg3: 008000000000c000
Arg4: 0000000000000400

Code:

fffff880`0d471000 fffff880`0d492000   MijXfilt   (no symbols)           
    Loaded symbol image file: MijXfilt.sys
    Image path: \SystemRoot\system32\DRIVERS\MijXfilt.sys
    Image name: MijXfilt.sys
    Timestamp:        Sun Mar 25 03:23:07 2012 (4F6E818B)
    CheckSum:         000201ED
    ImageSize:        00021000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Thank you, Thedoctor44!

Just to recap, I'll do the instructions in this order:

1. Malwarebytes scan (I have it installed, but also have Microsoft Security Essentials)
2. Memtest (Ran this already a few weeks before, but I don't think I reached 8 passes--took too long?)
3. Furmark - I regularly also stresstest the GPU--how can I tell if the video card is faulty using this?
4. Intel Centrino 2230 - Already updated this prior to the post, but will look for another update/clean install the driver.
5. Motioninjoy: I actually removed this already :)

I'll do this tonight and update you as necessary! Thank you for the help!

You need to run memtest86 for at least 8 passes because you can get errors later on.
If you see any artifacts or your computer crashes not long after running furmark it is a good indication the problem is your graphics card failing.

Okay I finally got to tinker with my laptop. Turns out one of the sticks was bad. What's weird though is that the errors take longer to show up when I transfer the bad stick in another slot. Is there any way I can diagnose a bad RAM slot?

Well you can run memtest86 to scan for errors. If memtest fails one stick you can move it to another slot, if it still fails it's probably bad RAM. If it passes then it's most likely a bad DIMM slot in the motherboard.
Follow these instructions on how to run memtest86

RAM - Test with Memtest86+

You should run memtest86 for at least 8 passes because there can be certain addresses in the physical memory that only causes errors when executed in a specific way so running more passes ensures a higher chance of the test being correct.

I did run Memtest86+, however I only had time for around four passes before I needed to use it :)) That's actually how I did it--I currently have the suspected bad stick out and the remaining good stick in there but I think I have to test it further.

Thanks for the help sir! I'll try more tests and mark it solved when I'm sure it's done.