BSOD in Windows 7

[Garion]

I'm still getting BSODs, but I have also updated to the latest ATI drivers. For some reason, my system isn't saving the BSODs right now. I'm trying to fix that and once I do, I will capture MEMORY.DMP info.I have also re-enabled debug info for DisplayLink.

[moisesmcardona]

Been using the v7.0 beta for a few days now. So far I haven't gotten a BSOD. My setup is an NVIDIA Geforce GT 650m with intel I7 graphics.

[Garion]

The system is completely unstable with the v7 driver and the latest driver from ATI. I have backed down to v6.1 and 12.1 drivers from ATI, and will probably do a new reinstall of Windows once I have time. All the crashes have caused problems with Windows.

[Garion]

I have completed a clean windows 7 install, and the BSODs are still there. The one attached happens when you log out of the system.

The full MEMORY.DMP is available at:

http://www.aloria.net/transfer/MEMORY.zip

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF88005CECFB5
BCP3: FFFFF8800A914C18
BCP4: FFFFF8800A914470
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88005cecfb5, The address that the exception occurred at
Arg3: fffff8800a914c18, Exception Record Address
Arg4: fffff8800a914470, 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:
atikmdag+9fb5
fffff880`05cecfb5 8b4108 mov eax,dword ptr [ecx+8]

EXCEPTION_RECORD: fffff8800a914c18 -- (.exr 0xfffff8800a914c18)
ExceptionAddress: 0000000000000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 97439669
Parameter[0]: fffffffffffff880
Parameter[1]: 0000000000000002
Parameter[2]: fffffffffffff880
Parameter[3]: 0000000000000000
Parameter[4]: 0000000000000000
Parameter[5]: 0000000000000009
Parameter[6]: 0000000000000000
Parameter[7]: 0000000000000000
Parameter[8]: 0000000000000000
Parameter[9]: fffffffffffffff8
Parameter[10]: 000000000000007f
Parameter[11]: 0000000000f4be60
Parameter[12]: fffffffffffff8a0
Parameter[13]: 0000000000000600
Parameter[14]: 0000000000000000
Attempt to read from address 0000000000000002

CONTEXT: fffff8800a914470 -- (.cxr 0xfffff8800a914470)
eax=00000001 ebx=fffff880 ecx=00000000 edx=c000000d esi=0a914e50 edi=fffff880
eip=05e94f60 esp=fffff880 ebp=00000000 iopl=0 vip ov dn ei pl nz na po nc
cs=f880 ss=50ac ds=4e50 es=0000 fs=0001 gs=0000 efl=06764f00
f880:4f60 ?? ???
Resetting default scope

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x7E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000005e94f60

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 0x5e94f60


FOLLOWUP_IP:
atikmdag+9fb5
fffff880`05cecfb5 8b4108 mov eax,dword ptr [ecx+8]

SYMBOL_NAME: atikmdag+9fb5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xfffff8800a914470 ; kb

BUCKET_ID: INVALID_KERNEL_CONTEXT