You can then check that IDTNC64.CPL is no longer present in C:\windows\system32. On rebooting the PC (use Ctrl-Alt-Del to power down if necessary) and restarting, Windows will automatically detect any missing audio drivers and install appropriate ones (not from IDT).
Type 'control panel' into the run box prompt and when the Control Panel appears, use Uninstall to seek out the offending IDT program - on my PC it had an icon of a musical note with the letters IDT next to it - and Uninstall. Provided you have just restarted your PC, you should be able to use a Windows Run Box (Win Key + R) before the crashes get too serious. IDTNC64.CPL is one component of that software and the correct solution is to uninstall the IDT audio altogether. I found some error in the Events Manager and this one was relevant "IDTNC64.cpl." "The root cause of the problem is that the audio software supplied by IDT and used by several PC manufacturers (Dell, HP and probably others) is not compatible with Windows 10. I found this solution and it worked for me. This sounds like a manufacturer sound audio issue for some of us. More to follow, however if anyone has heard about or has seen this issue post upgrade any hints about the cause of this problem would be appreciated. I know it must be a update of some sort, since on 29 July 2015 post install everything on this system worked fine and I had used it for the evening with no issues of any kind.
I have to review what if any updates may have been installed last night and will remove any updates that were installed post 29 July, 2015.
I haven't had anytime to explore possible root causes - I did, however prior to heading to work, updated the ATI graphics drives, however this did not stop the issue. Going into task manger and stopping explorer.exe obviously stops this and I can access the C: drive etc, but am not sure of the cause. I upgraded three of my computer to Windows 10 64bit on 29 July 2015 (build 10240), two of them I have no issues with, however one of them today, 31 July 2015, when I started it this morning once it had booted to the desktop explorer started a continuous crash loop.
0 kommentar(er)
