Blue screen crash from game

I will take a look. It appears to be a hardware problem.
Error code 124 is a special error code pointing to hardware. Your other dump is error code A and it blames hardware.

Please read this article on your bugcheck 124: [2-Int] Stop 0x124 - what it means and what to try

I suggest you start by testing your RAM. Read the tutorial linked below and follow the instructions:

RAM - Test with Memtest86+

Post back with your results.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 8648301c, b20c2000, 175}

Probably caused by : hardware

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


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_090110-19203-01.zip\090110-17453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x83040000 PsLoadedModuleList = 0x83188810
Debug session time: Wed Sep  1 15:22:22.667 2010 (GMT-4)
System Uptime: 0 days 0:06:23.292
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {3, 2, 1, 830ca40e}

Probably caused by : hardware ( nt!KiAcquireThreadStateLock+28 )

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

3: 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: 00000003, 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: 830ca40e, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 831a8718
Unable to read MiSystemVaType memory at 83188160
 00000003 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiAcquireThreadStateLock+28
830ca40e 9c              pushfd

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  gta4Browser.ex

TRAP_FRAME:  82bba738 -- (.trap 0xffffffff82bba738)
ErrCode = 00000002
eax=00000003 ebx=88db1454 ecx=00000000 edx=82bba85c esi=00000000 edi=88db1420
eip=830ca40e esp=82bba7ac ebp=82bba7c0 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!KiAcquireThreadStateLock+0x28:
830ca40e 9c              pushfd
Resetting default scope

MISALIGNED_IP: 
nt!KiAcquireThreadStateLock+28
830ca40e 9c              pushfd

LAST_CONTROL_TRANSFER:  from 830ca40e to 8308682b

STACK_TEXT:  
82bba738 830ca40e badb0d00 82bba85c 003f42d3 nt!KiTrap0E+0x2cf
82bba7c0 830e0739 82bba7d4 033d72f0 033d7238 nt!KiAcquireThreadStateLock+0x28
82bba7e4 8327d8c1 b38bd04e 00000000 00008000 nt!KeQueryValuesThread+0x6c
82bba880 83274456 033d3da0 00008000 82bbacd0 nt!ExpGetProcessInformation+0x1ed
82bbad00 8327650c 00000005 00000000 00000000 nt!ExpQuerySystemInformation+0x1086
82bbad1c 8308344a 00000005 033d3da0 00008000 nt!NtQuerySystemInformation+0x76
82bbad1c 772664f4 00000005 033d3da0 00008000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f644 00000000 00000000 00000000 00000000 0x772664f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiAcquireThreadStateLock+28
830ca40e 9c              pushfd

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiAcquireThreadStateLock+28

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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

That is good news; we have eliminated that as a cause. Continue to troubleshoot as outlined in the thread above. Post back with what you find.

Excellent troubleshooting on your part. I'm glad to hear the you found and solved the problem. Thanks for letting us know. Post back an a couple of days and if you are still running without problems - and I think you will be - we will ask the moderators to mark this thread as solved.