Hello,
First reinstall your Graphic driver.
Use driversweeper to remove your current Graphic driver.
Guru3D - Driver Sweeper
AMD.com | Support & Downloads
I would recommend you to install just the VGA driver without CCC.
Beside that I'm suspecting your VGA card is overheating since you said that the problem start in 30 minutes into an hour or two while gaming.
Video Card - Stress Test with Furmark
Code:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c17000 PsLoadedModuleList = 0xfffff800`02e54e50
Debug session time: Thu Jan 13 01:15:17.334 2011 (GMT-8)
System Uptime: 0 days 4:12:55.536
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff9a0108b5340, 0, fffff880055becee, 5}
Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff9a0108b5340, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880055becee, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebf0e0
fffff9a0108b5340
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
fffff880`055becee 488b18 mov rbx,qword ptr [rax]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff880039e6750 -- (.trap 0xfffff880039e6750)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff9a0108b5340 rbx=0000000000000000 rcx=fffffa800a455000
rdx=fffffa8009907e30 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880055becee rsp=fffff880039e68e0 rbp=fffffa80099edb98
r8=fffffa8005b1c301 r9=0000000000000000 r10=0000000000000000
r11=0000000000000166 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x22:
fffff880`055becee 488b18 mov rbx,qword ptr [rax] ds:cb60:fffff9a0`108b5340=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002d068c1 to fffff80002c87740
STACK_TEXT:
fffff880`039e65e8 fffff800`02d068c1 : 00000000`00000050 fffff9a0`108b5340 00000000`00000000 fffff880`039e6750 : nt!KeBugCheckEx
fffff880`039e65f0 fffff800`02c8582e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`039e6750 fffff880`055becee : 00000000`ffffd94a 00000000`00000000 fffffa80`0a218000 fffffa80`0a218b20 : nt!KiPageFault+0x16e
fffff880`039e68e0 fffff880`055bbed3 : 00000000`00000000 fffffa80`0add8930 00000000`00000040 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x22
fffff880`039e6910 fffff880`055d665d : 00000000`00000000 fffff8a0`0abc02a0 fffffa80`00000000 fffffa80`05b1c3c0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`039e6ae0 fffff880`055d6398 : fffff880`009ee040 fffff880`055d5d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`039e6cd0 fffff880`055d5e96 : 00000000`00000000 fffffa80`05ff16b0 00000000`00000080 fffffa80`0a38f410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`039e6d00 fffff800`02f2bc06 : 00000000`01b3847e fffffa80`0a38cb60 fffffa80`05508740 fffffa80`0a38cb60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`039e6d40 fffff800`02c65c26 : fffff880`009e9180 fffffa80`0a38cb60 fffff880`009f40c0 fffff880`0164b810 : nt!PspSystemThreadStartup+0x5a
fffff880`039e6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
fffff880`055becee 488b18 mov rbx,qword ptr [rax]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ccf7c90
FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
Followup: MachineOwner
---------
Quote