DxDiag Diagnostic Problems

[DaelpixPhotos]

I ran the DxDiag for a game I'm having problems with and found these errors. Is there anyway I can try and fix them?

GPU:
The file aticfx64.dll,aticfx64.dll,aticfx64.dll,amdxc64.dll,aticfx32,aticfx32,aticfx32,amdxc32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL).  You may be able to get a WHQL logo'd driver from the hardware manufacturer.



---------------
Diagnostics
---------------

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 129098706855, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0



Problem signature:

P1: FlashPlayerPlugin_21_0_0_242.exe
P2: 21.0.0.242
P3: 10.0.10586.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 


+++ WER1 +++:
Fault bucket 128949964784, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0


Problem signature:
P1: lightroom.exe
P2: 5.7.0.10
P3: 10.0.10586.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 



+++ WER2 +++:
Fault bucket 129087166751, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0


Problem signature:

P1: Prominence-Win64-Shipping.exe
P2: 4.11.2.0
P3: 10.0.10586.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 




+++ WER3 +++:
Fault bucket 128948210791, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0



Problem signature:

P1: googleearth.exe
P2: 7.1.5.1557
P3: 10.0.10586.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 



+++ WER4 +++:
Fault bucket 116072445029, type 5
Event Name: BEX64
Response: Not available
Cab Id: 116091638217



Problem signature:

P1: svchost.exe_iphlpsvc
P2: 10.0.10586.0
P3: 5632d7ba
P4: webio.dll
P5: 10.0.10586.0
P6: 5632d55a
P7: 000000000002ebbd
P8: c0000409
P9: 00000000c0000008
P10: 




+++ WER5 +++:
Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0


Problem signature:

P1: svchost.exe_iphlpsvc
P2: 10.0.10586.0
P3: 5632d7ba
P4: webio.dll
P5: 10.0.10586.0
P6: 5632d55a
P7: 000000000002ebbd
P8: c0000409
P9: 00000000c0000008
P10: 



+++ WER6 +++:
Fault bucket 129065554233, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0



Problem signature:

P1: FlashPlayerPlugin_21_0_0_213.exe
P2: 21.0.0.213
P3: 10.0.10586.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 



+++ WER7 +++:
Fault bucket 129063769022, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0



Problem signature:

P1: drt.exe
P2: 1.1.111.4274
P3: 10.0.10586.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 



+++ WER8 +++:
Fault bucket 129091044651, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0


Problem signature:

P1: firefox.exe
P2: 46.0.1.5966
P3: 10.0.10586.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 


+++ WER9 +++:
Fault bucket 120359879629, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0



Problem signature:

P1: lightroom.exe
P2: 5.7.0.10
P3: 545ea461
P4: KERNEL32.DLL
P5: 10.0.10586.0
P6: 5632d5aa
P7: c000041d
P8: 00000000000250f0
P9: 
P10:

 

[DaelpixPhotos]

bump

 

[ubuysa]

Well....I'll help as much as I'm able to but I confess that I really don't know what's causing the DXDiag errors.

RADAR is a memory leak detection system built in to Windows. What this is telling you is that a process appears to have had a memory leak. However there are too many different processes reporting this for them all to have memory leaks, so this is something else.

BX64 is, I believe, a Data Execution Prevention (DEP) error. What this is telling you is that a process tried to execute code (or data) in an area of memory that didn't belong to it (this is to prevent malicious code exploits). Your BX64 errors seem to be happening in SVCHOST (which is a system process that hosts a wide variety of system processes) whilst running the IP Helper (iphlpsvc). This provides networking functionality for HomeGroup and IPv6. That's not really much help I think.

APPCRASH is, as you might imagine, an application error (Lightroom in this case). In your case problem seems to have been (unusually) in the 32-bit Windows kernel.

The common denominator in the first two certainly is RAM, that may also be the APPCRASH issue but we have no way of knowing.

First off, I'd be tempted to run Memtest overnight to check that there are no hardware RAM issues.

Then I'd run the system file checker (sfc /scannow) to be sure there are no system file errors.

If there are system file errors that were not able to be corrected then I'd repair the component store (dism /online /cleanup-image /restorehealth) and then run sfc again.

Also check that all drivers are up to date, especially the chipset, graphics and networking card drivers.

If these issues happened recently or after an update (Windows, driver, or other software) I'd be tempted to either; restore an earlier disk image, go back to a prior restore point, or manually back out whatever updates were installed. If the problem disappears then you'll know what caused it.

I'm afraid that's the best I can do for now......