Topic Title: Bug with no external monitor connected to Radeon HD 7870 XT
Topic Summary: It is not possible to install a Radeon HD next to a internal HD3000 without connecting a screen to it
Created On: 01/13/2013 04:04 PM
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
View similar topics View similar topics
View topic in raw text format. Print this topic.
 01/13/2013 04:04 PM
User is offline View Users Profile Print this message

Author Icon
hansmuster
Peon

Posts: 2
Joined: 01/13/2013

This bug has been confirmed by 4 persons so far:

 

Setup:

Any Intel i5/i7 etc setup with integrated HD3000/4000 graphics and a second PCIe Radeon HD card.

Windows 7 64bit

Catalyst 12.x stable + 12.11 beta drivers (any beta)

 

If a Radeon HD 7870 (confirmed with standard + Tahiti LE) + 7700 series card is installed in such an Intel internal HD iGPU system and no monitor is connected to it (e.g. if you only want to use the card for OpenCL computation) then the following errors will happen:


DWM.exe instantly crashes after bootup:

Description
Faulting Application Path: C:\Windows\System32\dwm.exe

Problem signature
Problem Event Name: BEX64
Application Name: Dwm.exe
Application Version: 6.1.7600.16385
Application Timestamp: 4a5bc541
Fault Module Name: atiuxp64.dll
Fault Module Version: 8.14.1.6290
Fault Module Timestamp: 50997922
Exception Offset: 000000000000ffb5
Exception Code: c0000417
Exception Data: 0000000000000000
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1031
Additional Information 1: 4c98
Additional Information 2: 4c986f1afca156bb44beaea3a8be6c0d
Additional Information 3: 48d9
Additional Information 4: 48d9de7e50286b1747df3c693c2b246f


The same thing happens to any directx/opengl app but most of the time with simple stackfaults like:

Description
Faulting Application Path: C:\Program Files (x86)\Kishonti Informatics\CLBenchmark 1.1.2 Desktop Community Edition\CLBenchmarkDesktopCommunity.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: CLBenchmarkDesktopCommunity.exe
Application Version: 0.0.0.0
Application Timestamp: 507d3dbc
Fault Module Name: StackHash_0a9e
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 00000000
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1031
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789


Description
Faulting Application Path: C:\Program Files (x86)\Internet Explorer\iexplore.exe

Problem signature
Problem Event Name: BEX
Application Name: iexplore.exe
Application Version: 9.0.8112.16457
Application Timestamp: 50a2f9e3
Fault Module Name: atiuxpag.dll
Fault Module Version: 8.14.1.6290
Fault Module Timestamp: 50baff19
Exception Offset: 0000d73f
Exception Code: c0000417
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1031
Additional Information 1: 4a2d
Additional Information 2: 4a2d6864df2f476e5b19e40b06c0bd1f
Additional Information 3: 9bf2
Additional Information 4: 9bf2352c6d4a5fbabd1481f3627f78c2


This seems connected to ATIs Powerxpress DLLs which provide switchable optimus like technology to AMD platforms. If there is no screen connected to the radeon / not set primary it seems to still try to use the card for offload calculation and then write either in that memory region or of that of the hd3000 for rendering and stackfaults.

 

If i uninstall the Radeon from system settings and reboot it will detect the card again, install the drivers and everything is ok. Probably because the drivers (or powerxpress) have not hooked themselves into the system.

 

Everytime i reboot i of course have to uninstall the radeon first, otherwise the errors will happen again instantly after bootup.

 

This issue has been confirmed with the exact same errors / stack faults etc by 4 people so far.

 

Exact card model / driver version don't mather. This seems to be a generic amd driver issue.

 

Thanks a lot

 01/13/2013 04:09 PM
User is offline View Users Profile Print this message

Author Icon
hansmuster
Peon

Posts: 2
Joined: 01/13/2013

This also seems to be centered primarily around the issue that the catalyst drivers think that only the pcie gpu is the primary screen / only active gpu.

 

If you boot with an external screen connected which puts the radeon as primary screen everything is fine. If you then set the hd3000 screen as primary screen in system settings the same errors will start to happen. Catalyst control center will show the hd3000 as primary screen but either the driver still seems to write to some buffer of the radeon which does not exist in that way anymore or it is trying to write to the hd3000 buffers without proper access.

Statistics
84974 users are registered to the AMD Support and Game forum.
There are currently 4 users logged in.

FuseTalk Hosting Executive Plan v3.2 - © 1999-2014 FuseTalk Inc. All rights reserved.