cancel
Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

aazmp
Journeyman III

Catalyst 14.4 and CodeXL crush

Problem with catalyst 14.4 whql and CodeXL.

Before 14.3 beta was installed - worked ok.

When i run application as usual - works fine. Outbut of encoded video bit by bit repeats output with 14.3b. Performance is the same.

Application trace in CodeXL also runs correctly.

But when i try to see Performance Counters - system crashes. CodeXL manages to print little info about output into cmd and system restarts without any delay.

Tried CodeXL 14 and 13 - both crash.

Returned to 14.3b - everything is working again.

System:

Windows 7 x64

Radeon HD 7850 + FX 6300

P.S

tested app Aazmp/vp8oclenc · GitHub

first it runs couple CPU OpenCL kernels (these are probably the ones that run correctly and can be seen in cmd log)

and then GPU kernels (i guess they are the reason of crash, but i am not sure. System restarts very quickly).

0 Likes
1 Solution
kalyanpk
Staff

Hi,

The system crash/bluescreen appears to be a regression introduced in the Catalyst 14.4 release.  It affects gathering performance counter data for any OpenCL application on any Southern Islands device. We recommend not using this driver release with CodeXL if you have a Southern Islands device.

Thanks,

Kalyan P

View solution in original post

0 Likes
3 Replies
kalyanpk
Staff

Hi,

The system crash/bluescreen appears to be a regression introduced in the Catalyst 14.4 release.  It affects gathering performance counter data for any OpenCL application on any Southern Islands device. We recommend not using this driver release with CodeXL if you have a Southern Islands device.

Thanks,

Kalyan P

0 Likes

Hi,

I'm new here.  I'm running into the below BSOD when executing CodeXL GPU performance counters on two different systems.  One system is a Windows 8.1 x64 with a R9 290x and the other is a Windows 7 x64 with a HD7970.  I do have the latest 14.4 drivers on both systems.  It this the same issue?

Unknown bugcheck code (a0000001)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000005
Arg2: 0000000000000001
Arg3: 0000000000000000
Arg4: 0000000000000000

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


DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA0000001

PROCESS_NAME:  System

CURRENT_IRQL:  a

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

DPC_STACK_BASE:  FFFFF880009CCFB0

EXCEPTION_RECORD:  fffff80002e85709 -- (.exr 0xfffff80002e85709)
ExceptionAddress: 0000f024848d484a
   ExceptionCode: 3725ba0f
  ExceptionFlags: 0f00186c
NumberParameters: -1936898048
   Parameter[0]: 410000123ab94100
   Parameter[1]: c7d78b40008000b8
   Parameter[2]: 4800000602282444
   Parameter[3]: c700000090248489
   Parameter[4]: 0004000000982484
   Parameter[5]: 00009c24ac890000
   Parameter[6]: 9ce820246c894800
   Parameter[7]: 4802ff8341000e30
   Parameter[8]: 004818868748c58b
   Parameter[9]: 3e74ff2b44607d00
   Parameter[10]: ffc9331274ff3b44
   Parameter[11]: e88b480012da5a15
   Parameter[12]: 6538eb3824448948
   Parameter[13]: 00000020250c8b48
   Parameter[14]: e8d2333824448d4c

LAST_CONTROL_TRANSFER:  from fffff88011306ece to fffff80002e7cbc0

STACK_TEXT: 
fffff880`009c5708 fffff880`11306ece : 00000000`a0000001 00000000`00000005 00000000`00000001 00000000`00000000 : nt!KeBugCheckEx
fffff880`009c5710 fffff880`113161e0 : 00000000`00000000 fffffa80`0981a6b0 fffffa80`06deec58 fffff880`031e0180 : atikmdag+0x28ece
fffff880`009c5750 fffff880`1135f045 : fffffa80`06fa2010 fffffa80`06fa2010 fffffa80`06fa2770 fffff880`0870748b : atikmdag+0x381e0
fffff880`009c5780 fffff880`11360b44 : 00000000`00000000 fffff880`113157a3 00000000`00000000 00000000`00000000 : atikmdag+0x81045
fffff880`009c5800 fffff880`11360c81 : fffffa80`07035f20 fffff880`009c5971 00000000`00000000 fffffa80`06fa2010 : atikmdag+0x82b44
fffff880`009c5880 fffff880`11360d4d : 00000000`00000000 00000000`00000000 fffffa80`070c0000 fffff880`08703c63 : atikmdag+0x82c81
fffff880`009c58c0 fffff880`11360e85 : 00000000`00000000 fffff880`00000000 fffff880`00000000 fffff880`11319fdf : atikmdag+0x82d4d
fffff880`009c59d0 fffff880`1136a098 : fffffa80`0700f210 fffffa80`0701b870 fffffa80`0700d000 fffff880`11369eb6 : atikmdag+0x82e85
fffff880`009c5a20 fffff880`1135d8cc : fffffa80`00000000 fffffa80`0700d000 fffff880`009c5b80 00000000`00000001 : atikmdag+0x8c098
fffff880`009c5a70 fffff880`11303c35 : fffffa80`062381c0 fffffa80`03aa40c0 fffff880`031eafc0 00000003`00000030 : atikmdag+0x7f8cc
fffff880`009c5aa0 fffff880`084b82de : 00000000`00000000 fffff880`031eafc0 fffffa80`0636f120 00000000`00000001 : atikmdag+0x25c35
fffff880`009c5ad0 fffff800`02e78a1c : 00000000`00000000 fffff880`031eafc0 fffffa80`03aa40c0 00000000`00000000 : atikmpag+0x92de
fffff880`009c5b00 fffff880`0835b7f2 : fffff800`02e85709 00000000`00000000 fffffa80`06396dd8 00000000`00000000 : nt!KiInterruptDispatch+0x16c
fffff880`009c5c98 fffff800`02e85709 : 00000000`00000000 fffffa80`06396dd8 00000000`00000000 00000000`000478e5 : amdppm!C1Halt+0x2
fffff880`009c5ca0 fffff800`02e7489c : fffff880`031e0180 fffff880`00000000 00000000`00000000 fffff880`08610588 : nt!PoIdle+0x52a
fffff880`009c5d80 00000000`00000000 : fffff880`009c6000 fffff880`009c0000 fffff880`009c5d40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP:
atikmdag+28ece
fffff880`11306ece cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  atikmdag+28ece

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53508a3c

IMAGE_VERSION:  8.1.1.1390

FAILURE_BUCKET_ID:  X64_0xA0000001_atikmdag+28ece

BUCKET_ID:  X64_0xA0000001_atikmdag+28ece

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa0000001_atikmdag+28ece

FAILURE_ID_HASH:  {fe9ca8bf-417e-7edf-c2ea-22e52071137a}

0 Likes

Update.  I downloaded the 14.6 Beta drivers and I can now run GPU performance counters just fine.