I'm having a problem with Windows 2000 SP4. Lately, more and more problems have arisen with MS applications MGADIAG.EXE and GenuineCheck.exe (and support ActiveX controls thru the web-sites in support of Validation). This has also cropped up with Framework 1.1 Security Patch.
It seems that RDTSC instruction is used in Validation and CPUID instruction is used in FrameWork 1.1 Patch. When these applications execute, I get an illegal instruction 0xc000001D, and when I view the debug information, the offending instruction is CPUID or RDTSC.
All other updates/patches work from MS, but when downloading anything that is checked for Genuine Validation, it fails due to these instructions.
Both instructions are being used to determine CPU type, but it looks like that error correction for traps on non-Pentium CPUs is not being performed.
Other programs using these instructions work ... not these from MS.
I have a 486DX2-66v with 128MB RAM and Windows 2000 SP4. Like I said, everything has been working, even the previous versions of Windows Genuine Advantage (WGADIAG.EXE) and GenuineCheck.exe. The current versions GPF.
Is there anything that MS should be doing about trapping around these instructions when they fail ... to prevent GPFs? Aren't these any sort of security holes? If you know that a GPF is going to happen, can't you hook into that?
|
Similar Threads
