A few days after I reloaded Windows XP Tablet PC Edition on the Compaq TC1000 and applied the updates, I've decided to install DirectX 9.0c.
However, when I tried to install the June 2010 and April 2011 updates, I receive this error message:
An internal system error occurred.
Please refer to DXError.log and DirectX.log in your Windows folder to determine the problem.
The message ends in the following:
Checking the DirectX Diagnostic Tool, the version of DirectX is identified as DirectX 9.0c (4.09.0000.0904). In the Display section of DirectX Diagnostic Tool, DirectDraw test results ran successfully. However, when I tested Direct3D, I received this error message:
Direct3D 7 test results: Test failed at step 8 (Creating 3D Device): HRESULT = 0x887602eb (error code)
Direct3D 8 test results: Test failed at step 8 (Creating 3D Device): HRESULT = 0x8007000e (Out of memory)
Direct3D 9 test results: Test failed at step 8 (Creating 3D Device): HRESULT = 0x8007000e (Out of memory)
The culprit to this error what that I received a STOP 0xF4 error when I attempted to detach the TC1000 monitor from the keyboard and on the next reboot, I received a STOP 0x24 meaning that the NTFS file system has gone corrupt. I had to pull out the CF card onto a PCMCIA adapter, attach it to the PCMCIA PCI slot on the back of my desktop computer and run CHKDSK /F to fix the problem.
Unfortunately, when CHKDSK /F was finished some of the files that required DirectX to work was deleted, resulting in the loss of Direct 3D functionality.
As a result of this, 3D screensavers supplied with Windows XP do not work anymore. For example, when trying to run the 3D Text screensaver, I receive a "No preview available" message.
Here are the log files for the June 2010 update: [attachment=37514:June2010-DirectX.txt] [attachment=37515:June2010-DXError.txt]
And here are the log files for the April 2011 update: [attachment=37516:April2011-DirectX.txt] [attachment=37517:April2011-DXError.txt]
Please keep in mind that as Windows XP is installed on a 32 GB CF card, how can I correct this error that was previously caused by NTFS corruption?
Edited by ppgrainbow, 17 November 2013 - 07:44 PM.