cancel
Showing results for 
Search instead for 
Did you mean: 

Graphics

Adept II
Adept II

Re: R9 380X black screen

I started to play DOOM. I played 3-4 hours with 6-7 gaming sessions; i had no black screens/BSODs/TDR crashes until now. I only have one event: game frozen but alt-tabbing and ending the process worked. I am using 16.9.2 and Clockblocker.

Do Clockblocker work for you? This application helps too much on me. But it doesn't permanently resolve the issues.

0 Kudos
Adept I
Adept I

Re: R9 380X black screen

It's a driver issue. I already had to RMA my card awhile back because it actually went bad, got a new card, put it on the same driver at the time and still got the exact same issues. A couple drivers later and the issues were fixed. If I go back to the old drivers I can recreate the problem indefinitely. The only reason people keep having problems is because it's related to the game you are trying to play. My issues were with Dark Souls, I know alot of people has problems with Nba 2k, others with other games. As some drivers get fixed for certain games, other people run into problems with the games they play. I doubt AMD will be able to 100% fix the problem because it's a variety of games that they have to fix to work properly with the new drivers, and if they don't know that it's broken with that specific game to begin with, they can't work on the issue. Plus considering were already on the next gen of cards, it's probably less and less people working on the issues that pop up.  As for those of you still on 15.11.1 and back, I suggest 16.7, 16.8, and 16.9 drivers, as the newest ones at-least clear the black-screen issues allowing you to go back to desktop rather then hard resetting.

0 Kudos
Adept II
Adept II

Re: R9 380X black screen

15.11.1 doesn't fix my problems. Clockblocker helps but doesn't %100 resolve the issues. Did you try this tool?

And you're right. Considering people begin to use new cards;we are doomed to be forgotten soon.

0 Kudos
Adept II
Adept II

Re: R9 380X black screen

Doom crashed again, game freezes but i have able to access task manager and end process. I have no idea if this is related to graphics card or not. Access violations are can be a full software bug. But i had some page fault in non paged area errors in RoTR, so i suspect RAM and VRAM. And the most important thing is exception address is the same on both crashes! Faulty sector?

Here's the crash log 1:

Callstack Function(desc)    Line Bytes File       Process       Address

--------------------------- ---- ----- ----       -------       -------

GetGameSystemInterface()    ...  +     0x5b1819d0 DOOMx64vk.exe

GetGameSystemInterface()    ...  +     0x5b1892a4 DOOMx64vk.exe

GetGameSystemInterface()    ...  +     0x5b184667 DOOMx64vk.exe

GetGameSystemInterface()    ...  +     0x5b3887dd DOOMx64vk.exe

BaseThreadInitThunk()       ...  +     0xa2318364 KERNEL32.DLL

RtlUserThreadStart()        ...  +     0xa2485e91 ntdll.dll   

Register Info              

---------------------------

EDI:    0x0000000000000000  ESI: 0x2492492492492493  EAX:   0x0000000000000002

EBX:    0x000000016D6D2160  ECX: 0x0000000000000001  EDX:   0x0000000000000100

EIP:    0x000000015B1819D0  EBP: 0x000000016D6D20E0  SegCs: 0x0000000000000033

EFlags: 0x0000000000010246  ESP: 0x000000007B5CFDA0  SegSs: 0x000000000000002B

Exception Info             

---------------------------

ExpCode:          0xC0000005 (Access Violation)

ExpFlags:         0       

ExpAddress:       0x000000015B1819D0

Build & Runtime Info      

---------------------------

User:             FATIHNEW5      

Version:          20160808-123534-peach-almond      

File Path:        C:\Program Files (x86)\Doom\DOOMx64vk.exe      

System Time:      10/6/2016 19:40:04      

Build String:     20160808-123534-peach-almond      

VT File Path:           

VMTR Override:    generated/pagefiles      

Launch Command:   "C:\Program Files (x86)\Doom\DOOMx64vk.exe" C:\Program Files (x86)\Doom\DOOMx64.exe +r_renderAPI -2       

Memory Info               

---------------------------

In Use:           61%    

MB Physical RAM:  8089      

MB Physical Free: 3122      

MB Paging File:   10446      

MB Paging Free:   1290      

MB User Address:  134217728      

MB User Free:     134210651      

CPU Info                  

---------------------------

Num Packages:     1      

Num Cores:        3      

Num Logical:      6      

CPU ID:           Generic      

CPU MHz:          3512   

Callstack Function(desc)    Line Bytes File       Process       Address

--------------------------- ---- ----- ----       -------       -------

GetGameSystemInterface()    ...  +     0x5b1819d0 DOOMx64vk.exe

GetGameSystemInterface()    ...  +     0x5b1892a4 DOOMx64vk.exe

GetGameSystemInterface()    ...  +     0x5b184667 DOOMx64vk.exe

GetGameSystemInterface()    ...  +     0x5b3887dd DOOMx64vk.exe

BaseThreadInitThunk()       ...  +     0xa2318364 KERNEL32.DLL

RtlUserThreadStart()        ...  +     0xa2485e91 ntdll.dll 

Register Info            

---------------------------

EDI:    0x0000000000000000  ESI: 0x2492492492492493  EAX:   0x0000000000000002

EBX:    0x000000016D6D2160  ECX: 0x0000000000000001  EDX:   0x0000000000000100

EIP:    0x000000015B1819D0  EBP: 0x000000016D6D20E0  SegCs: 0x0000000000000033

EFlags: 0x0000000000010246  ESP: 0x000000007B5CFDA0  SegSs: 0x000000000000002B

Exception Info           

---------------------------

ExpCode:          0xC0000005 (Access Violation)

ExpFlags:         0     

ExpAddress:       0x000000015B1819D0

Build & Runtime Info    

---------------------------

User:             *****  

Version:          20160808-123534-peach-almond    

File Path:        C:\Program Files (x86)\Doom\DOOMx64vk.exe    

System Time:      10/6/2016 19:40:04    

Build String:     20160808-123534-peach-almond    

VT File Path:         

VMTR Override:    generated/pagefiles    

Launch Command:   "C:\Program Files (x86)\Doom\DOOMx64vk.exe" C:\Program Files (x86)\Doom\DOOMx64.exe +r_renderAPI -2     

Memory Info             

---------------------------

In Use:           61%  

MB Physical RAM:  8089    

MB Physical Free: 3122    

MB Paging File:   10446    

MB Paging Free:   1290    

MB User Address:  134217728    

MB User Free:     134210651    

CPU Info                

---------------------------

Num Packages:     1    

Num Cores:        3    

Num Logical:      6    

CPU ID:           Generic    

CPU MHz:          3512 

Crash log 2:

Callstack Function(desc)    Line Bytes File       Process       Address

--------------------------- ---- ----- ----       -------       -------

GetGameSystemInterface()    ...  +     0x5b1819d0 DOOMx64vk.exe

GetGameSystemInterface()    ...  +     0x5b1892a4 DOOMx64vk.exe

GetGameSystemInterface()    ...  +     0x5b184667 DOOMx64vk.exe

GetGameSystemInterface()    ...  +     0x5b3887dd DOOMx64vk.exe

BaseThreadInitThunk()       ...  +     0x12f68364 KERNEL32.DLL

RtlUserThreadStart()        ...  +     0x13505e91 ntdll.dll   

Register Info              

---------------------------

EDI:    0x0000000000000000  ESI: 0x2492492492492493  EAX:   0x0000000000000002

EBX:    0x00000000A4BC2180  ECX: 0x0000000000000001  EDX:   0x0000000000000100

EIP:    0x000000015B1819D0  EBP: 0x00000000A4BC2100  SegCs: 0x0000000000000033

EFlags: 0x0000000000010206  ESP: 0x000000007BA7FDA0  SegSs: 0x000000000000002B

Exception Info             

---------------------------

ExpCode:          0xC0000005 (Access Violation)

ExpFlags:         0       

ExpAddress:       0x000000015B1819D0

Build & Runtime Info      

---------------------------

User:             ******     

Version:          20160808-123534-peach-almond      

File Path:        C:\Program Files (x86)\Doom\DOOMx64vk.exe      

System Time:      10/8/2016 10:31:20      

Build String:     20160808-123534-peach-almond      

VT File Path:           

VMTR Override:    generated/pagefiles      

Launch Command:   "C:\Program Files (x86)\Doom\DOOMx64vk.exe" C:\Program Files (x86)\Doom\DOOMx64.exe +r_renderAPI -2       

Memory Info               

---------------------------

In Use:           62%    

MB Physical RAM:  8089      

MB Physical Free: 3071      

MB Paging File:   10393      

MB Paging Free:   1735      

MB User Address:  134217728      

MB User Free:     134211137      

CPU Info                  

---------------------------

Num Packages:     1      

Num Cores:        3      

Num Logical:      6      

CPU ID:           Generic      

CPU MHz:          3512   

Do guys any idea what can cause this?

0 Kudos
Adept I
Adept I

Re: R9 380X black screen

On 16.10.1 I still can't run 3dMark, since only starting it causes a freeze. Heaven/Valley ran fine, but Heaven once froze right after finishing the Benchmark. Two times I fell asleep while watching Netflix and when I woke up: Black Screen. So obviously a freeze again.

For me the solution is pretty simple: If AMD doesn't fix this issue till the end of the year, I'm done with them. Won't recommend them to anyone anymore and these 7970's will be my last AMD Cards. It's simply ridicolous how AMD is taking care of this. It's obviously a low priority for them, or their programmers are simply too unqualified to solve this (or a mix of both) and I'm not willing to pay hundreds of € just to get s**t on by the manufacturer like here.

In the past, AMDs reputation always has been their bad af drivers. For a god damn good reason...I'm not aware of a single time when you could really say that AMD got better Driver-Support than the green team in the past 5 years or so. And this issue is bringing it all to a whole new level SINCE OVER A YEAR. Have been red for over 10 years and I seriously don't know why anymore. AMD doesn't care enough about this and about us, so why should we still support them in any single way. I've got enough of this.

0 Kudos
Adept II
Adept II

Re: R9 380X black screen

Actually getting rid of AMD is not a solution NVIDIA drivers are bad as AMD's, and in some ways they are worse. They released some drivers that cause hardware malfunction in the past years. They have a lot of driver problems too. It's not about choosing AMD or NVIDIA, it's about the GPU choice and luck. There are a lot of people who use Tonga GPUs without any serious problems; we are the minority. And having an uncommon problem is the worst thing.

I never thought this was a %100 driver issue. Drivers only change the symptoms, some of them show black screen, some of them have TDR crashes, some of them only crash the game. But one thing is certain: We can't play games without crashes. This looks like GPU voltage-power-frequency relationship problem. And if it's; the problem is actually hardware.

I can't detect any common hardware or software on our systems. Maybe we need another topic that messages only contain very detailed system information to run our "investigation".

Our cards are EOL now, and there's no hope for any fix. The people who know all the drill are keeping their silence.

Elite
Elite

Re: R9 380X black screen

Idk about all, but for me it IS driver issue.

If 15.7.1 works without any glitches and bugs(it means hardware is ok) so why any younger driver allways HAS some bugs and glitches?

Anyway, globally im agree with you.

Adept II
Adept II

Re: R9 380X black screen

Did you try Black Ops 3 and GTA V on 15.7.1. They both crash with 15.7.1 on my system even when i fixed the clock speed.

0 Kudos
Elite
Elite

Re: R9 380X black screen

Im not a realy big gamer, dont play many titles, but with all drivers after 15.7.1 i have some of this issues:

-jumping clocks

-some applications wont launch, even those who tbh does not need power of GPU

-black screens

-OpenGL lags and crashes

Now im sitting with 16.7.2 and have OpenGL have troubles.

All next drivers restrict me to use some software, its just wont launch

Adept II
Adept II

Re: R9 380X black screen

The Red Screen crash happened again. Mirror's Edge Catalyst and 16.10.1 crashed. There was a solid red screen, sound stuttered and system completely locked up. I had a hard reset on PC and i looked the minidump folder. Crash debug:

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: fffff8092cf971a0, The address that the exception occurred at

Arg3: ffff9d00993bf098, Exception Record Address

Arg4: ffff9d00993be8c0, Context Record Address

Debugging Details:

------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

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

FAULTING_IP:

dxgmms2!VIDMM_LINEAR_POOL::FindBlockRun+c0

fffff809`2cf971a0 488b77e8 mov rsi,qword ptr [rdi-18h]

EXCEPTION_RECORD: ffff9d00993bf098 -- (.exr 0xffff9d00993bf098)

ExceptionAddress: fffff8092cf971a0 (dxgmms2!VIDMM_LINEAR_POOL::FindBlockRun+0x00000000000000c0)

ExceptionCode: c0000005 (Access violation)

  ExceptionFlags: 00000000

NumberParameters: 2

  Parameter[0]: 0000000000000000

  Parameter[1]: ffffffffffffffff

Attempt to read from address ffffffffffffffff

CONTEXT: ffff9d00993be8c0 -- (.cxr 0xffff9d00993be8c0)

rax=ffffb88740897d00 rbx=ffffe58268dc2410 rcx=0000000000000000

rdx=0000000060880573 rsi=444004040041414b rdi=070767070160e681

rip=fffff8092cf971a0 rsp=ffff9d00993bf2d0 rbp=a5a177140085858f

r8=ffffb88740897d00 r9=ffffb88741b8fa60 r10=ffff9d00993bf9b1

r11=ffff9d00993bf418 r12=0000000000000001 r13=000000000015a000

r14=ffffb88741b8fa88 r15=ffffe58268dc2410

iopl=0 nv up ei pl nz ac po cy

cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010217

dxgmms2!VIDMM_LINEAR_POOL::FindBlockRun+0xc0:

fffff809`2cf971a0 488b77e8 mov rsi,qword ptr [rdi-18h] ds:002b:07076707`0160e669=????????????????

Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

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: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPagedPoolEnd

unable to get nt!MmNonPagedPoolStart

unable to get nt!MmSizeOfNonPagedPoolInBytes

ffffffffffffffff

FOLLOWUP_IP:

dxgmms2!VIDMM_LINEAR_POOL::FindBlockRun+c0

fffff809`2cf971a0 488b77e8 mov rsi,qword ptr [rdi-18h]

BUGCHECK_STR: AV

EXCEPTION_STR: 0x0

LAST_CONTROL_TRANSFER: from fffff8092cf97c8c to fffff8092cf971a0

STACK_TEXT: 

ffff9d00`993bf2d0 fffff809`2cf97c8c : ffffb887`41b8fa60 00000000`00000000 ffff9d00`993bf3f0 ffffb887`41b8fa60 : dxgmms2!VIDMM_LINEAR_POOL::FindBlockRun+0xc0

ffff9d00`993bf370 fffff809`2cf96f21 : ffffb887`4157f920 00000000`00000000 ffffe582`625e2e00 fffff809`2cf57d09 : dxgmms2!VIDMM_LINEAR_POOL::Allocate+0x88

ffff9d00`993bf420 fffff809`2cf94e11 : 00000000`00040000 00000000`00000000 00000000`00000001 fffff802`b414cd01 : dxgmms2!VIDMM_SEGMENT::ReserveResource+0x2a1

ffff9d00`993bf4e0 fffff809`2cfa89ed : 00000000`00000000 ffffe582`625e2e00 00000000`00000000 ffffb887`41bf8458 : dxgmms2!VIDMM_MEMORY_SEGMENT::ReserveResource+0x31

ffff9d00`993bf520 fffff809`2cfcdcdf : ffff9d00`00000000 ffffe582`625e2e00 00000000`00000000 ffffb887`00000000 : dxgmms2!VIDMM_GLOBAL::AcquireGPUResourcesFromPreferredSegmentSet+0x12d

ffff9d00`993bf5a0 fffff809`2cfa6104 : ffffb887`4605a010 00000000`00000000 ffffb887`4210c000 ffffe582`625e2e00 : dxgmms2!VIDMM_GLOBAL::FindResourcesForOneAllocation+0x24e1f

ffff9d00`993bf5e0 fffff809`2cfaa06e : ffffb887`41fee800 ffff9d00`9741e180 ffffb887`43688080 00000000`ffffffff : dxgmms2!VIDMM_GLOBAL::PageInOneAllocation+0x124

ffff9d00`993bf6f0 fffff809`2cfbcf73 : 00000000`00000001 00000000`00da7a64 ffff9d00`993bfa60 00000000`00000001 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0x66e

ffff9d00`993bf960 fffff802`b408f729 : ffff9d00`977e1180 ffffb887`41fee800 fffff809`2cfbc540 ffffe582`50c1a310 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xa23

ffff9d00`993bfc10 fffff802`b41dc876 : ffff9d00`977e1180 ffffb887`41fee800 fffff802`b408f6e8 00000000`00000000 : nt!PspSystemThreadStartup+0x41

ffff9d00`993bfc60 00000000`00000000 : ffff9d00`993c0000 ffff9d00`993ba000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgmms2!VIDMM_LINEAR_POOL::FindBlockRun+c0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5801a824

STACK_COMMAND: .cxr 0xffff9d00993be8c0 ; kb

FAILURE_BUCKET_ID: X64_AV_dxgmms2!VIDMM_LINEAR_POOL::FindBlockRun+c0

BUCKET_ID: X64_AV_dxgmms2!VIDMM_LINEAR_POOL::FindBlockRun+c0

Followup: MachineOwner

In Google searches i never get any useful information. Everyone repeat same suggestions and no one can interpret these BSOD crash dumps. I'm completely pissed off. Microsoft said it's very common bugcheck.

0 Kudos