Dell Latitude D620 with Vista Ultimate SP1

I would like some assistance with interpreting a couple minidumps

Randomly when I come out of standby I get a bsod with details:

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 00000000, The address that the exception occurred at
Arg3: 891636dc, Exception Record Address
Arg4: 891633d8, Context Record Address

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


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

FAULTING_IP:
+0
00000000 ?? ???

EXCEPTION_RECORD: 891636dc -- (.exr 0xffffffff891636dc)
ExceptionAddress: 00000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 00000000
Attempt to execute non-executable address 00000000

CONTEXT: 891633d8 -- (.cxr 0xffffffff891633d8)
eax=891637d0 ebx=82695500 ecx=854d6d30 edx=00000000 esi=85121b00 edi=854d6d30
eip=00000000 esp=891637a4 ebp=891638f8 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
00000000 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 9a

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

WRITE_ADDRESS: 00000000

FAILED_INSTRUCTION_ADDRESS:
+0
00000000 ?? ???

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 805e0adb to 00000000

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
891637a0 805e0adb 4943502e 00000000 891637d0 0x0
891638f8 805b7175 aa5586d0 aafb75b0 00000000 acpi!_NULL_IMPORT_DESCRIPTOR <PERF> (acpi+0x2fadb)
89163924 805ded54 8526e9e0 b357ad70 aafb7500 acpi!ACPIDevicePowerProcessPhase3+0x1bd
8916395c 805b9e4b 8526e9e0 aafb7500 00000000 acpi!_NULL_IMPORT_DESCRIPTOR+0x878
8916398c 826fd053 8526e9e0 8525e260 86283a20 acpi!ACPIGetProcessorID+0x123
891639a4 8c4ad880 aafb7500 86283a20 c00000bb nt!PspCreateProcess+0x2e7
891639c8 8c4ad334 b357ad78 aafb7500 aafb7500 dxgkrnl+0x57880
891639ec 8c49535c 86283968 aafb7500 aafb75dc dxgkrnl+0x57334
89163a10 826fd053 86283968 aafb7500 89163a90 dxgkrnl+0x3f35c
89163a28 827a5605 00000000 85263b70 aafe9a40 nt!PspCreateProcess+0x2e7
89163a44 827a553b 89163a6c 8264cf47 aafe9a40 nt!NtVdmControl+0x6b
89163a94 827a52d2 00000000 8264cf47 aafe9a40 nt!NtSetInformationToken+0x9dc
89163ad8 827a366b aafe9a40 00000000 85109978 nt!NtSetInformationToken+0x784
89163cd4 827a955e 852bf570 85109978 89163d00 nt!SepAccessCheckAndAuditAlarm+0x58b
89163d08 8264caf1 8274313c 8446f580 82773500 nt!ExpGetCurrentUserUILanguage+0x1aa
89163d44 8267941d 00000000 00000000 8446f580 nt!MiPfPutPagesInTransition+0x81
89163d7c 82816b18 00000000 2fd0563a 00000000 nt!DeleteNodeFromTree+0x87
89163dc0 8266fa3e 82679320 00000001 00000000 nt!ViDeadlockFree+0x2b
89163df8 00000000 00000000 00000000 00001f80 nt!MmPurgeSection+0x67


FOLLOWUP_IP:
dxgkrnl+57880
8c4ad880 ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: dxgkrnl+57880

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47918c64

STACK_COMMAND: .cxr 0xffffffff891633d8 ; kb

FAILURE_BUCKET_ID: 0x7E_NULL_IP_dxgkrnl+57880

BUCKET_ID: 0x7E_NULL_IP_dxgkrnl+57880

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

Attached Files

Mini Dumps.zip (85.3 KB, 1 views)

All MiniDumps list 0x7E Errors and are caused by "dxgkrnl.sys" which is the Direct X Graphics Kernel.
These Errors are normally caused by Hardware Incompatibility, Faulty Device Drivers Or System Service and possibly some software issues. Try updating Direct X and Graphics Card Drivers.

And also run one of the Memory tests below
Memtest86 - http://www.memtest.org/
Windows Memory Diagnostics Tools - http://oca.microsoft.com/en/windiag.asp