Windows 10: xfti_pcdrv_l11_2_40_0016 causes error

When I tried to install this new driver, it installed, computer restarted and there was a yellow checkmark next to the creative sb x-fi in the device manager. I tried everything I can to get it to work to no avail. No sound, no nothing. I uninstalled it and went back to the old driver, but the creative counsel launcher would just default and have no sound. I even did a clean install of 1803 and just put in the new sound driver and did the same thing. I know creative released this driver for the new April update. Has anyone else had problems?

:)

 

Possible Causes of atikmdag errors

I was courious to see how many different causes there are to the infamous atikmdag.sys error that strikes widely across and has so for a long time, I am getting it myself also and it is really starting to wear me out. It is pretty annoying having a $520 Readeon 3870x2 card if you can't use it without errors.

So first of all, here is the apparant reason for my atikmdag error:

When I play a game, regardless of settings, clocks or anything else, the fan speed wil not be adjusting and the card will get hotter as it performs. As soon as the card gets hot enough, my system will attempt to speed up the fan and as soon as they do, I get the atikmdag error. I never hear the fan of my card go beyond 30% fan speed unless I push it using Rivatuner.

Anyone else got other apparant reasons?

By the way, here are the steps I have been trying to fix it

• Renaming atikmdag.sys to "atikomdag.sys(old)
• Set fan speed profiles in Rivatuner depending on temeprature thresholds
• Setting fixed fan speed in Rivatuner
• Installing only the ATI drivers without Catalyst Control Centre
• Replacing RAM blocks
• Trying older drivers

I have probably tried a few

 

System Error.

Event ID for each error? List those, will tell you what caused it on the Microsoft Knowledge Base.

 

Stop Error Caused by ntoskrnl.exe

Hi Luke,

For us to isolate your concern regarding the error that caused by ntoskrnl.exe, we would like to know the following:

• Were there any updates made on your computer prior to this concern?
• To make sure we have not missed on anything, what troubleshooting steps have you done so far?
• Send us a screenshot of the exact error message.

We look forward to your response.