I had this prob. But it was definitely my Video Card driver corrupted. Keeps happening, don't yet know the root cause. Suspect Vid Card driver modifies an OS file at install as normal M-O. (stupid AND illegal) Then I ran and completed SFC. Which I suppose modified it back thus leaving no code to answer the interrupts and stop it from nagging. On reboot the brand new re-install of the Visiontek Driver (yes the visiontek not the ATI one, which will not work with my card for some reason even though it is actually an ATI chipset) but anyw on reboot it is corrupt again. But I have not verified SFC as the cause yet. But I know it CAN at times survive many reboots before it goes to 4e11 The affect of the problem is that something generates Hardware interupts like crazy eating up a majority of the CPU in the kernel. This leaves nothing for programs and I barely can reinstall the vid driver in that condition much less work. Tools I used to help debug this: 1. Sysinternals Proc Explorer! (have to download from www.microsoft.com) (This showed me the CPU time was not software but a hail of harware interupts) 2. Windows taskmgr.exe (just type taskmgr in run box) (TRICKY!!! ONLY when on the "Performance" tab (with the graphs) does the option "Show Kernel Times" appear.) When looking at the CPU column under the "Processes" tab it adds up to 100% always. But that is 100% of what part of the total CPU rate that is available AFTER you subtract the "kernel time" That is the margin that is above the red line after you make it appear. The system idle process is what is above the green line. The total of the processes CPU is what is between the red and green line, in my case is a very tiny bit. . . :((( Reinstall of Vid Card Driver fixes every time. Visiontek HD 2600 PRO AGP (yes AGP) WinXP SP3 Visiontek Driver v9.7 Good luck! Hope this helps get a fire lit under this absolutely ridiculous problem. (and create documentation that the ministry of truth can't erase if i am being hacked with individually - EOT
Log in to comment