BugCheck 7E caused by dxgmms1.sys (Radeon HD 5770/10.6 drvr)

Toggle sidebar Toggle sidebar
P

Pacal

Member
Nov 26, 2006
73
0
0
While playing bfbc2, I have been encountering BSOD's with code 7E which originate from dxgmms1.sys. I suspect something is awry with my memory, and I have replacements on order, but I was curious if others looking at the bugcheck analysis come to the same conclusion:

"ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s."

Diagnostic Checks Thus Far
HDD: Ran Seatools short and long tests - Passed
VIDEO: Replaced video card
MEM: Discovered 1/4 bad stick(s)/memtest86+, removed 2 & retained other two.
OS: Reinstalled several times
BIOS: OC'd or not, I still encounter this and other errors like PFN_LIST_CORRUPT


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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880041cad0c, fffff88003d68868, fffff88003d680d0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+94 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880041cad0c, The address that the exception occurred at
Arg3: fffff88003d68868, Exception Record Address
Arg4: fffff88003d680d0, 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:
dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+94
fffff880`041cad0c 488908 mov qword ptr [rax],rcx

EXCEPTION_RECORD: fffff88003d68868 -- (.exr 0xfffff88003d68868)
ExceptionAddress: fffff880041cad0c (dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+0x0000000000000094)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

CONTEXT: fffff88003d680d0 -- (.cxr 0xfffff88003d680d0)
rax=0000000000000000 rbx=fffff8a00cc0a500 rcx=0000000000000ac0
rdx=fffff8a00cf5fa70 rsi=fffff8a00cf5fa70 rdi=fffffa80073da650
rip=fffff880041cad0c rsp=fffff88003d68aa0 rbp=fffffa80073da540
r8=fffff88003d68b08 r9=fffff88003d68b10 r10=000000000000004f
r11=fffff8a00b2943b0 r12=0000000000000000 r13=fffff8a00cc0a4e0
r14=0000000000000000 r15=fffff88003d68ca0
iopl=0 nv up ei pl nz ac po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010216
dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+0x94:
fffff880`041cad0c 488908 mov qword ptr [rax],rcx ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: NULL_DEREFERENCE

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0b0e0
0000000000000000

FOLLOWUP_IP:
dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+94
fffff880`041cad0c 488908 mov qword ptr [rax],rcx

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff880041ba5e1 to fffff880041cad0c

STACK_TEXT:
fffff880`03d68aa0 fffff880`041ba5e1 : fffffa80`073db000 00000000`00000000 00000000`00000000 fffffa80`073d3000 : dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+0x94
fffff880`03d68b00 fffff880`041b8e13 : fffff8a0`0cf5fa70 fffffa80`073db000 fffffa80`047dec20 fffffa80`073db000 : dxgmms1!VIDMM_GLOBAL::NotifyAllocationEviction+0x59
fffff880`03d68b30 fffff880`041b4358 : fffffa80`046ea040 00000000`00000080 00000000`00000000 fffff880`03d68ca0 : dxgmms1!VIDMM_GLOBAL::processDeferredCommand+0x523
fffff880`03d68c50 fffff880`041d216d : fffffa80`00000000 fffffa80`07397010 00000000`0000000f fffff880`041d3f09 : dxgmms1!VidMmiProcessTerminationCommand+0x4c
fffff880`03d68ca0 fffff880`041d13f8 : fffff880`009ecf40 fffffa80`0762c1f0 00000000`00000000 fffffa80`07397010 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`03d68cd0 fffff880`041d0e96 : 00000000`00000000 fffffa80`0762c1f0 00000000`00000080 fffffa80`07397010 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`03d68d00 fffff800`02d78a86 : 00000000`039c6da0 fffffa80`073daa10 fffffa80`03968890 fffffa80`073daa10 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`03d68d40 fffff800`02ab1b06 : fffff880`009e8180 fffffa80`073daa10 fffff880`009f2fc0 fffff880`01214534 : nt!PspSystemThreadStartup+0x5a
fffff880`03d68d80 00000000`00000000 : fffff880`03d69000 fffff880`03d63000 fffff880`03d68690 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+94

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578

STACK_COMMAND: .cxr 0xfffff88003d680d0 ; kb

FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+94

BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+94

Followup: MachineOwner
---------
 
Last edited:
D

DaveSimmons

Elite Member
Aug 12, 2001
40,730
670
126
Are you overclocking and/or overvolting anything? Step 1 = set everything back to stock speed.
 
K

KIAman

Diamond Member
Mar 7, 2001
3,342
23
81
Try increasing your memory voltage a little.

Also
BIOS: OC'd or not, I still encounter this and other errors like PFN_LIST_CORRUPT
Click to expand...

Big red flag here. This is pointing to an error regarding memory paging to your HD or continued memory issues. What is your Pagefile settings? Have you tried to scan your HD for errors?
 
Last edited:
D

DaveSimmons

Elite Member
Aug 12, 2001
40,730
670
126
^ if you've corrupted the file system while overclocking you might even need to reformat and reinstall (with everything set to stock).
 
P

Pacal

Member
Nov 26, 2006
73
0
0
DaveSimmons:
I have rolled back my OC settings to defaults, but as I recall the problem persisted. I may give it another go with the stock settings. I have reinstalled the OS a few times now, although not at stock speed.


KIAMan:
DRAM Voltage: [2.24] (Power monitor reads 2.36v – chip label rec’s 2.35-2.5v)
Pagefile Setting: [Auto]
HDD: SeaTools Diagnostic Software Cleared All 3 Drives (Short & Long Tests)
 
P

Pacal

Member
Nov 26, 2006
73
0
0
Another BSOD, this time it's atikmdag.sys and it's a PAGE_FAULT_IN_NONPAGED_AREA (Bugcheck 50)

Look'n more and more like a memory problem...? I don't know what else I can do to verify the integrity of the HDD.


*******************************************************************************
* *
* 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: fffff8a003f989f8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88004b4414e, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf60e0
fffff8a003f989f8

FAULTING_IP:
atikmdag+33b14e
fffff880`04b4414e 8178083100bebe cmp dword ptr [rax+8],0BEBE0031h

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: BFBC2Game.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff880089544a0 -- (.trap 0xfffff880089544a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a003f989f0 rbx=0000000000000000 rcx=fffff8a003f99ae0
rdx=fffff880089546a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004b4414e rsp=fffff88008954638 rbp=0000000000000000
r8=fffffa8004510e30 r9=0000000000000080 r10=fffff88002fd3ca0
r11=fffffa8004473640 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
atikmdag+0x33b14e:
fffff880`04b4414e 8178083100bebe cmp dword ptr [rax+8],0BEBE0031h ds:1000:fffff8a0`03f989f8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002b3ee54 to fffff80002abe600

STACK_TEXT:
fffff880`08954338 fffff800`02b3ee54 : 00000000`00000050 fffff8a0`03f989f8 00000000`00000000 fffff880`089544a0 : nt!KeBugCheckEx
fffff880`08954340 fffff800`02abc6ee : 00000000`00000000 00000000`c0000001 fffff8a0`03f93500 fffff880`03a05ee3 : nt! ?? ::FNODOBFM::`string'+0x42877
fffff880`089544a0 fffff880`04b4414e : fffff880`04b3c7c1 fffff8a0`01c857d0 fffff880`0485366e fffffa80`03b11700 : nt!KiPageFault+0x16e
fffff880`08954638 fffff880`04b3c7c1 : fffff8a0`01c857d0 fffff880`0485366e fffffa80`03b11700 fffffa80`054da740 : atikmdag+0x33b14e
fffff880`08954640 fffff8a0`01c857d0 : fffff880`0485366e fffffa80`03b11700 fffffa80`054da740 fffffa80`03b11700 : atikmdag+0x3337c1
fffff880`08954648 fffff880`0485366e : fffffa80`03b11700 fffffa80`054da740 fffffa80`03b11700 00000000`00000000 : 0xfffff8a0`01c857d0
fffff880`08954650 fffffa80`03b11700 : fffffa80`054da740 fffffa80`03b11700 00000000`00000000 00000000`00000001 : atikmdag+0x4a66e
fffff880`08954658 fffffa80`054da740 : fffffa80`03b11700 00000000`00000000 00000000`00000001 fffff880`03bbbf9b : 0xfffffa80`03b11700
fffff880`08954660 fffffa80`03b11700 : 00000000`00000000 00000000`00000001 fffff880`03bbbf9b 00000000`c0000001 : 0xfffffa80`054da740
fffff880`08954668 00000000`00000000 : 00000000`00000001 fffff880`03bbbf9b 00000000`c0000001 fffffa80`07f98ec0 : 0xfffffa80`03b11700


STACK_COMMAND: kb

FOLLOWUP_IP:
atikmdag+33b14e
fffff880`04b4414e 8178083100bebe cmp dword ptr [rax+8],0BEBE0031h

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: atikmdag+33b14e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4bfea23e

FAILURE_BUCKET_ID: X64_0x50_atikmdag+33b14e

BUCKET_ID: X64_0x50_atikmdag+33b14e

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

Pacal

Member
Nov 26, 2006
73
0
0
In case anyone's curious.... Here are my BIOS settings. System spec's in my signature (I recently replaced GeForce 8800GTS w/ATI HD 5770).


Note:
Actual Power Levels for DRAM 2.352v / VCORE 1.424v
DRAM rec'd at 2.35~2.5 on chip and 2.2~2.4 on manufacturer's website (geil)

Asus Maximus Formula (X38) / v1403

Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
Ratio CMOS Setting : [9.0]
FSB Frequency : [400]
FSB Strap to North Bridge : [400]
PCI-E Frequency: [100]
DRAM Frequency: [DDR2-1066]
DRAM Command Rate : [2T]
DRAM Timing Control: Auto

DRAM Static Read Control: [Disabled]
Ai Clock Twister : [Strong]
Transaction Booster : [Enabled]
Boost Level : [0]

CPU Voltage : [1.43750v] Actual 1.424v
CPU PLL Voltage : [Auto]
North Bridge Voltage : [Auto]
DRAM Voltage : [2.24v] Actual 2.352v
FSB Termination Voltage : [Auto]
South Bridge Voltage : [Auto]
Loadline Calibration : [Enabled]
CPU GTL Reference : [Auto]
North Bridge GTL Reference : [Auto]
DDR2 Channel A REF Voltage : [Auto]
DDR2 Channel B REF Voltage : [Auto]
DDR2 Controller REF Voltage : [DDR2_REF]
SB 1.5V Voltage : [Auto]

NB LED Selection : NB Volt
SB LED Selection : SB Volt
CPU LED Selection : CPU VOlt
Voltiminder LED :

CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled

Advanced CPU Configuration
CPU Ratio Control : Manual
- Ratio CMOS Setting : [9.0]
C1E Suppport : Disabled
CPU TM Function : Disabled
Vanderpool Technology : Disabled
Execute Disable Bit : Disabled
Max CPUID Value Limit : Disabled

USB Configuration
USB Functions: Enabled
Legacy USB Support : Disabled
 
Last edited:
P

Pacal

Member
Nov 26, 2006
73
0
0
n7: I've done 2 passes on the dram using memtest86+ without issue. How many passes do you think are necessary in order to effectively diagnose the memory?

I was looking through a recent minidump from the aforementioned bsod and I noticed:
"READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf60e0
fffff8a003f989f8 "
Is this a memory address or range of addresses?
 
P

Pacal

Member
Nov 26, 2006
73
0
0
Jesusthewererabbit:

Thank you for reiterating that point- help's me know it's standard practice. I suppose I'll be reinstalling in the near distant future.
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom