Windows 7: ntoskrnl.exe and igdkmd32.sys BSOD

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


Loading Dump File [C:\Users\K\Desktop\minidump files\051911-20716-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x83012000 PsLoadedModuleList = 0x8315b4d0
Debug session time: Wed May 18 23:21:16.650 2011 (GMT-4)
System Uptime: 0 days 0:09:37.211
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8313318b, b24fc74c, 0}

*** WARNING: Unable to verify timestamp for kerneld.x32
*** ERROR: Module load completed but symbols could not be loaded for kerneld.x32
Probably caused by : kerneld.x32 ( kerneld+4d0b )

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

0: 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: 8313318b, The address that the exception occurred at
Arg3: b24fc74c, 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: 
nt!ExFreePoolWithTag+6d0
8313318b 8b12            mov     edx,dword ptr [edx]

TRAP_FRAME:  b24fc74c -- (.trap 0xffffffffb24fc74c)
ErrCode = 00000000
eax=0000047c ebx=20206f49 ecx=00007d90 edx=00007d90 esi=000001ff edi=85338ae0
eip=8313318b esp=b24fc7c0 ebp=b24fc818 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!ExFreePoolWithTag+0x6d0:
8313318b 8b12            mov     edx,dword ptr [edx]  ds:0023:00007d90=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  aida64.exe

CURRENT_IRQL:  1

IRP_ADDRESS:  01770620

LAST_CONTROL_TRANSFER:  from 83093121 to 8313318b

STACK_TEXT:  
b24fc818 83093121 85338ae8 00000000 adc3948b nt!ExFreePoolWithTag+0x6d0
b24fc864 8308abbf 01770660 b24fc8ac b24fc8a4 nt!IopCompleteRequest+0xe6
b24fc8b4 b0f42d0b b2ff31d6 87a70250 88904c28 nt!IopfCompleteRequest+0x3b4
WARNING: Stack unwind information not available. Following frames may be wrong.
b24fcbfc 83049593 88904c28 85770620 85770620 kerneld+0x4d0b
b24fcc14 8323c98f 87a70250 85770620 85770690 nt!IofCallDriver+0x63
b24fcc34 8323fb61 88904c28 87a70250 00000000 nt!IopSynchronousServiceTail+0x1f8
b24fccd0 832863fc 88904c28 85770620 00000000 nt!IopXxxControlFile+0x6aa
b24fcd04 830501ea 0000021c 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
b24fcd04 770870b4 0000021c 00000000 00000000 nt!KiFastCallEntry+0x12a
0aa6d7b4 00000000 00000000 00000000 00000000 0x770870b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
kerneld+4d0b
b0f42d0b ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  kerneld+4d0b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: kerneld

IMAGE_NAME:  kerneld.x32

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9f8bf2

FAILURE_BUCKET_ID:  0x8E_kerneld+4d0b

BUCKET_ID:  0x8E_kerneld+4d0b

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

SENTINEL.SYS    9/26/2002 01:47:32 AM    0xa7c12a00    0x00012a00    0x3d929f74    0xa7c00000                            
cfosspeed.sys    2/10/2009 07:02:05 AM    0x8f2f5000    0x000c9000    0x49915ead    0x8f22c000