Saved Bookmarks
| 1. |
Solve : DirectX 9.0c REFUSES to install. Can't upgra? |
|
Answer» Today has been adventure. Here I am after 11 straight hours of working on my crashed computer.. which spawned from this DirectX problem. c0000269 Illegal system DLL relocation. The system DLL kernel32.dll was relocated in memory. The application will not run properly.The message would only appear for about 1/3 of a second, then the system would reboot and repeat this process. I actually had to record a video of my computer crashing and play it back and freezeframe it to see the error. To fix this problem, I ended up having to uninstall a few of the updates through the recovery console. At this point I was able to boot into safemode, but explorer.exe would crash immediately. So I had to launch system restore from the command prompt in safemode. After I formatted and reinstalled, I tried to install DirectX 9.0c right away and it failed as usual. The next thing I did was tried running my updates again since the system was running on a fresh install. The same thing happened. BSOD. I believe it was an undocumented bug in one of the updates. I came to the conclusion I'm never installing another windows update for as long as I live. One of the culprits was most likely one of the following (removing these three got rid of the BSOD): KB896424 KB890859 KB885835 Right now the system is running fine since I did system restore, but I can't install my critical updates. EDIT: I recently remembered that I had slipstreamed the SP2 RC1 into my copy of XP Professional (bad idea, I know) months back when the beta came out. This is why I have 9.0b instead of 9.0c. This may ALSO be why the windows updates are crashing my system, but I'm not 100% sure. And it may ALSO be related to why I cannot upgrade directx. I have a few new non-directx questions, so I'm going to create a new topic for this.One of the updates (KB885835) has caused problems in certain systems but as far as I'm aware, it's only caused the symptoms that you have described when problems (Infection) were already present on the system. Critical updates must be installed! Have a look [highlight]here[/highlight] with regard to kernel32 errors but it could be related to just about anything.Just out of curiosity, what makes you so certain I have a virus? Could it not just be a hardware/driver conflict of some sort?All I've said is that this behaviour is exhibited when certain infections are present. Having said that, it may be entirely due to some other cause or causes. I cannot be certain about anything with regards to your system as I have so little information about it. All I can offer at this moment are possible causes of the symptoms that your machine is exhibiting. At this moment, I'm pushing hardware/driver problems to the back of the queue because it's likely that if one of these were the cause, symptoms would have been exhibited before now. I may be wrong in that assumption. Perhaps the question that you should be asking of yourself is: Am I absolutely certain that I don't have any infections? Quote EDIT: First time around, I didn't see this edit. It changes the whole picture! It's CERTAINLY not a bad idea to slipstream service packs etc, but it certainly is a bad idea to slipstream BETAS! If I were you, I would download SP2, DX9c and any necessary firewall/anti virus/anti malware protection and burn them to CD. I would then reinstall XP from scratch with my original and genuine Windows CD. I would then install SP2, ensure everything is OK and back everything up. I would now install DX9c and test it further. If all is OK, back up again. Now I would install my firewall etc, go online and get the critical updates and test further. |
|