BSOD at random

Code:

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

Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Low\Temporary Internet Files\Content.IE5\CNFYL1YI\Documents[1]\Windows_NT6_BSOD_jcgriff2\013111-33359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8283a000 PsLoadedModuleList = 0x82979570
Debug session time: Mon Jan 31 17:36:58.904 2011 (GMT-5)
System Uptime: 0 days 1:08:55.919
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, 8288e70f}
Unable to load image \SystemRoot\system32\DRIVERS\AGRSM.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AGRSM.sys
*** ERROR: Module load completed but symbols could not be loaded for AGRSM.sys
Probably caused by : AGRSM.sys ( AGRSM+3d8ed )
Followup: MachineOwner
---------
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: 00000000, 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: 8288e70f, address which referenced memory
Debugging Details:
------------------

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82999700
Unable to read MiSystemVaType memory at 829790c0
 00000000 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!KeWaitForSingleObject+373
8288e70f 8939            mov     dword ptr [ecx],edi
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
TRAP_FRAME:  8c6a3b34 -- (.trap 0xffffffff8c6a3b34)
ErrCode = 00000002
eax=858733c0 ebx=858733b8 ecx=00000000 edx=00000000 esi=861b7400 edi=861b74c0
eip=8288e70f esp=8c6a3ba8 ebp=8c6a3c0c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!KeWaitForSingleObject+0x373:
8288e70f 8939            mov     dword ptr [ecx],edi  ds:0023:00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from 8288e70f to 82872b5b
STACK_TEXT:  
8c6a3b34 8288e70f badb0d00 00000000 00000086 nt!KiTrap0E+0x2cf
8c6a3c0c 8eab38ed 858733b8 00000000 00000000 nt!KeWaitForSingleObject+0x373
WARNING: Stack unwind information not available. Following frames may be wrong.
8c6a3c84 8eab3b76 85861030 85837c9c 00000003 AGRSM+0x3d8ed
8c6a3ca8 82850eea 85861030 854cb030 00000016 AGRSM+0x3db76
8c6a3cc0 82868f36 85837cdc 85861030 8c6a3cd8 nt!IopPoHandleIrp+0x28
8c6a3cd0 82850551 8c6a3cf8 8eb82873 85861030 nt!IofCallDriver+0x55
8c6a3cd8 8eb82873 85861030 85837c08 8583b030 nt!PoCallDriver+0x10
8c6a3cf8 828509ff 8583b030 85837c08 00000000 modem!ModemPower+0xb1
8c6a3d50 82a21d16 85c547f8 ac3c2725 00000000 nt!PopIrpWorker+0x351
8c6a3d90 828c3159 828506ae 85c547f8 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

Agere SoftModem Driver
Description: SoftModem Device Driver
Company: Agere Systems

Update driver

Your Welcome
Im very hopeful that I found the problem.
Most of your dump reports came up with the same conclusion, which is rare
Good luck

Glad that I could sort the BSOD problem for you.
Take care.