The reason for this posting was this comment (in Bulgarian) by Mladen, where he shares his bad time and also some of his desperation with Windows XP after installing the Bulgarian Phonetic keyboard layout, provided by Injinera.
The problem: Windows starts BSOD-ding after installation of one of the keyboard layouts, downloaded by Injinera’s site. The BSOD happens either immediately after logging on, or if you successfully logon, but try to switch the keyboard layout afterwards.
I had almost the same experience after I installed the same set of files (from the same place), which Mladen installed too. My notebook started to throw BSOD’s in about 50% of the system logons: very, very nasty problem, without any sign of hope there. And because I already trust Injinera as a very correct and stable source, I was sure that the problem should be somewhere else and not in the installed files. The provided files contain anyway only some convertion tables, and nothing more…
During my hard time few months ago, I noticed that if I’m not connected to the corporate network, the BSOD does not appear, or appears much rarely than if I was connected to the corpnet. Initially I suspected that somehow the system does not like the newly installed stuff and while trying to restore itself via the automated System Restore, if ends-up with this bad BSOD. Actually, I managed to have a working machine exactly by logging on without being connected to the corpnet (the notebook was undocked), and after logging on I was docking the notebook back.
Luckuly, during the time being this problem started to appear rarely and rarely (healing, magic – call it as you wish :)), and I almost forgot about it (although I was reminded from time to time by a BSOD in similar conditions at least once a month). However, Mladen’s comment raised this issue back.
I decided to try looking for solution, or at least a clue. After some search through Google, I’m almost confident that I have found the initial source of this problem. I will leave Mladen to experiment and report here :), because I am somehow not ready to risk my current stable situation. Fighting with few angry help-desk guys is not the best way 2005 to begin, isn’t it ;)?
Mladen, take a look here (originally I found this quote from this link, which in general has nothing to do with our problem). However, read carefully:
Based on the info you give … it would seem geoShell is choking on one of your startup items, or vise versa. I reckon it’s probably internat.exe that’s causing the trouble. This does nothing more than display that blue icon (with white text) in the system tray, providing you with a mouse interface to change your keyboard layout. internat.exe uses a “non- standard” method for displaying that icon in the systray (the method is actually undocumented), and it won’t display properly or perhaps even at all under geoShell. Luckily you can still switch layouts via the hotkey (left alt-shift I think.) Try disabling internat.exe and see what happens.
As it seems, this is similar behavior to what we do experience. Maybe it could help?
After some more digging out, I have found this (unfortunately, the only source I have about this is that “it was somewhere in MSDN”, and this is not a good way something to be referred to):
Internat.exe – You can end this process from Task Manager.
* Internat.exe runs at startup; it loads the different input locales
specified by the user. The locales to be loaded are taken from the following
HKEY_USERS.DEFAULTKeyboard LayoutPreload Internat.exe loads the “EN”
icon into the system tray, allowing the user to easily switch between
locales. This icon disappears when the process is stopped, but the locales
can still be changed through Control Panel.
I am leaving the experiment to you. Remove internat.exe (rename it in safe or rescue mode) and see what happens. Please, if you find a way to kill the problem – report it here as it could be of some else’s use. I will add more to this article, if there is some progress on that issue.