Random BSOD under load (dump data)

Hi, I have just built a new pc for my brother and I'm having some problems with random blue screens. This generally occurs when he uses it for gaming or when its under high load etc.

I thought it could be the RAM but i ran memtest twice and it passed both times. I have read some other posts and they were asked for a dump file so here it is (got others if u need more info):

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000034, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 828b1028, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829b0718
Unable to read MiSystemVaType memory at 82990160
00000034

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiTryUnwaitThread+46
828b1028 8701 xchg eax,dword ptr [ecx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 8296ea84 -- (.trap 0xffffffff8296ea84)
ErrCode = 00000002
eax=00000001 ebx=00000034 ecx=00000034 edx=00000001 esi=00000000 edi=8699a138
eip=828b1028 esp=8296eaf8 ebp=8296eb1c iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!KiTryUnwaitThread+0x46:
828b1028 8701 xchg eax,dword ptr [ecx] ds:0023:00000034=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 828b1028 to 8288e82b

STACK_TEXT:
8296ea84 828b1028 badb0d00 00000001 8296eaa8 nt!KiTrap0E+0x2cf
8296eb1c 82884a79 82971d20 00000100 00000000 nt!KiTryUnwaitThread+0x46
8296eb3c 828b228d 82971d20 8296ebb0 8619a0c0 nt!KiSignalNotificationObject+0x36
8296eb80 828b1f7b 82971d20 00000001 82973680 nt!KiTimerWaitTest+0x1e6
8296ec68 828b1eae 82971d20 8296eca8 00000000 nt!KiProcessExpiredTimerList+0x8b
8296ecdc 828b020e 00004fe1 86911778 8297b280 nt!KiTimerExpiration+0x25c
8296ed20 828b0038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
8296ed24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTryUnwaitThread+46
828b1028 8701 xchg eax,dword ptr [ecx]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTryUnwaitThread+46

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac

FAILURE_BUCKET_ID: 0xA_nt!KiTryUnwaitThread+46

BUCKET_ID: 0xA_nt!KiTryUnwaitThread+46

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000034, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 828b1028, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829b0718
Unable to read MiSystemVaType memory at 82990160
00000034

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiTryUnwaitThread+46
828b1028 8701 xchg eax,dword ptr [ecx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 8296ea84 -- (.trap 0xffffffff8296ea84)
ErrCode = 00000002
eax=00000001 ebx=00000034 ecx=00000034 edx=00000001 esi=00000000 edi=8699a138
eip=828b1028 esp=8296eaf8 ebp=8296eb1c iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!KiTryUnwaitThread+0x46:
828b1028 8701 xchg eax,dword ptr [ecx] ds:0023:00000034=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 828b1028 to 8288e82b

STACK_TEXT:
8296ea84 828b1028 badb0d00 00000001 8296eaa8 nt!KiTrap0E+0x2cf
8296eb1c 82884a79 82971d20 00000100 00000000 nt!KiTryUnwaitThread+0x46
8296eb3c 828b228d 82971d20 8296ebb0 8619a0c0 nt!KiSignalNotificationObject+0x36
8296eb80 828b1f7b 82971d20 00000001 82973680 nt!KiTimerWaitTest+0x1e6
8296ec68 828b1eae 82971d20 8296eca8 00000000 nt!KiProcessExpiredTimerList+0x8b
8296ecdc 828b020e 00004fe1 86911778 8297b280 nt!KiTimerExpiration+0x25c
8296ed20 828b0038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
8296ed24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTryUnwaitThread+46
828b1028 8701 xchg eax,dword ptr [ecx]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTryUnwaitThread+46

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac

FAILURE_BUCKET_ID: 0xA_nt!KiTryUnwaitThread+46

BUCKET_ID: 0xA_nt!KiTryUnwaitThread+46

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

 

Please follow the instructions below so we can examine your set up. Please be as accurate as you can with the model numbers of your hardware components.

 

I used the PSU from his old computer when building the new pc to try and save some money so when i discovered it could be the problem he decided to just buy a new one. This however doesn't seem to have fixed the problem(although it is better). After fitting he was playing on games and stuff for a few hours without a problem but after installing some updates when shutting down it happened again, and once more after playing more later on.

I have also updated the system specs for my account to show the components used. The motherboard, cpu and ram are part of a bundle purchased from ebuyer and the graphics card was seperate. Is there any more diagnostics i can run or info i can give that would help find the cause of the problem?

 

Your system specs have not appeared, you didn't follow this instruction:

It should then show My System in the profile box below your member name.

I'll have a look at your specs before suggesting further action.