M1530 crashing

hey, my m1530 is around 2 months old. Recently it has started to crash frequently while playing world of warcraft. The crash doesn't always occur after I've been playing for a long time. Here's the information from Windows Debugger:

I really have no idea what I'm talking about, but I thought I saw driver fault in there somewhere. Is there a new version of a driver I can download to help with this problem?

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bc35438e, d6ba96e8, 0}



Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_DEVICE::ReferenceCommitment+31 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bc35438e, The address that the exception occurred at
Arg3: d6ba96e8, Trap Frame
Arg4: 00000000

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




EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
dxgkrnl!VIDMM_DEVICE::ReferenceCommitment+31
bc35438e 8902 mov dword ptr [edx],eax

TRAP_FRAME: d6ba96e8 -- (.trap 0xffffffffd6ba96e8)
ErrCode = 00000002
eax=b21cf8a4 ebx=00000000 ecx=b2221600 edx=00000000 esi=b27354fc edi=c726e000
eip=bc35438e esp=d6ba975c ebp=d6ba9760 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
dxgkrnl!VIDMM_DEVICE::ReferenceCommitment+0x31:
bc35438e 8902 mov dword ptr [edx],eax ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: Wow.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from bc3543f7 to bc35438e

STACK_TEXT:
d6ba9760 bc3543f7 b21cf870 00000000 b28a3414 dxgkrnl!VIDMM_DEVICE::ReferenceCommitment+0x31
d6ba9778 bc352476 00000000 b21cf870 00000001 dxgkrnl!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x5a
d6ba97e0 bc353dd3 d4f2fef8 00000000 b27e37a0 dxgkrnl!VIDMM_GLOBAL: repareDmaBuffer+0x6a9
d6ba98e8 bc351930 d0916d48 c725a008 d6ba9928 dxgkrnl!VidSchiSubmitRenderCommand+0x126
d6ba98f8 bc3339a1 d0916d48 d0916d48 b14b9860 dxgkrnl!VidSchiSubmitQueueCommand+0x61
d6ba9928 bc351876 c7213000 d6ba994c b14b9860 dxgkrnl!VidSchiSubmitQueueCommandDirect+0x1ae
d6ba9950 bc353a3d 01916d48 bc3d0100 dce204f8 dxgkrnl!VidSchiSubmitCommandPacketToQueue+0x171
d6ba9974 bc35764a b14b9860 d6ba9a94 00000000 dxgkrnl!VidSchSubmitCommand+0x2bf
d6ba9b90 bc356f30 d6ba9bac 6a8e7f76 0019f5ac dxgkrnl!DXGCONTEXT::Render+0x513
d6ba9d58 e1c58a1a 0019f5ac 0019f6f0 777d9a94 dxgkrnl!DxgkRender+0x272
d6ba9d58 777d9a94 0019f5ac 0019f6f0 777d9a94 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0019f6f0 00000000 00000000 00000000 00000000 0x777d9a94


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgkrnl!VIDMM_DEVICE::ReferenceCommitment+31
bc35438e 8902 mov dword ptr [edx],eax

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgkrnl!VIDMM_DEVICE::ReferenceCommitment+31

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4893b1df

FAILURE_BUCKET_ID: 0x8E_dxgkrnl!VIDMM_DEVICE::ReferenceCommitment+31

BUCKET_ID: 0x8E_dxgkrnl!VIDMM_DEVICE::ReferenceCommitment+31

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

 

I am not sure, but it might be related to the video driver!! Googling returned some similar discussion, concerning the nvidia driver.

 

Odd...
Normally what crashes the video drivers is nvlddmkm....

But yes, you could try and update the video drivers off the Dell site.
remember to uninstall -> safemode boot -> CCleaner or Driver sweeper ->reboot->install new drivers...