I have GPUView for personal use and am experiencing crashes after i run log.cmd with any setting...light, normal, min, etc. It seems it gets to processing level [19] then it crashes. The error i get has to do with dxetw.dll causing an unhandled exception 0xc0000005 which means its trying to read a memory address that doesn't exist. I can attach a system information file for you to view, and i can generate a dmp file if needed. At this point im simply wondering if this is a common issue with windows 7 64 bit clients? I don't see much reference to it and im at the point where I can't do much more due to the complex nature of the problem. It seems to have something to do with the ETL file. The Longhaul switch seems to work with log.cmd, but nothing else does, so im thinking it has something to do with the direct x component loggers themselves in the ETL file, or in GPUView. Are there known xperf issues? 

It seems that I can reinstall GPUView in some cases, change the compatibility mode of log.cmd and get it to work, where it doesn't hang on processing level [19], but eventually it will start to once ive loaded it several times. 

What kinds of things might i try? I was wondering if there are any support libraries i can install or removers I can run to maybe see if resetting the issue back to an earlier date (short of a system restore, which i'd rather not do, but im not sure at this point).

Any suggestions would be helpful.

OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
System Manufacturer Gigabyte Technology Co., Ltd.
System Type x64-based PC
Processor Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz, 3801 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. U1c, 3/8/2013
SMBIOS Version 2.7
Hardware Abstraction Layer Version = "6.1.7601.17514"
Total Physical Memory 3.96 GB
Available Physical Memory 2.18 GB

I can load the ETL file somewhere if people wanted to check it out, but to start im asking for any obvious suggestions.

Things ive tried:

Reinstallation of WPTx64

Compatability mode

Smaller etl files (regardless of size it crashes)

Seems like there is some odd issue between Kernel.etl and DX.etl because if i merge w/o either file, GPUview has no problems loading the result (merged.etl), but if i let log.cmd merge with both of those files, it gets to a point and crashes because of Dxetw.dll.

Does anyone know if this is a bug? Or have any suggestions i could try? Is there a way to reset the loggers back to some kind of default setting?