![]() ![]() I use 'BlueScreen View' to see info on my BSOD's, and the vast majority of them point to 'ntkrnlpa.exe'. Although it isn't set to change things after 15-30minutes, I think it may be related to windows checking its instructions at certain intervals. I have it set to go to screensaver after 60min, turn display(s) off at 2 hours, but never go to sleep/hibernation. *- At this point, I have reason to believe the problem may be stemming from a combination of Windows device driver support, and something to do with how the system handles power state changes. Other devices act similarly either losing the custom mappings set in software, or losing all functionality, entirely. Keyboard loses custom mappings after approx. It suddenly got much worse, and I don't know what's changed. However, as of, I am getting regular failures. I could limp along with it in that state for 6-12 months, until I'm ready to build a whole new machine. I was still trying to get help on other support forums, but without much response. *- As of, PC was operating mostly ok, but with intermittant failures. I apologize for any formatting and tense issues. *Some of this was written one or two months ago, when I was first repairing it, then late in the process when I drafted a new support request. And Mice and Other Pointing Devices\HID-compliant mouse. Also, Device Manager is displaying multiple entries of most devices in: Human Interface Devices\HID-compliant consumer control device, HID-compliant device, USB Input Device. However, I believe that this should already be installed. Currently, Windows Update is instructing me to install: NVIDIA - system - nForce HyperTransport Bridge. Devices most affected: Steelseries Merc keyboard with zBoard/zEngine software, Logitech mouse and Marble trackball with SetPoint uberOptions software, MCE remote controls and intelliremote software, Zune, Logitech G930 headset, USB hub, Windows Explorer. ![]() I must be able to trust that my hardware is doing what I tell it to do. If I don't immediately catch the mistake, this can have serious consequences. One of the worst cases is when dragging multiple entries, the mouse will behave as though I took my finger off the button for a split second thereby dropping those files in an incorrect directory. Sometimes mouse will lag or jump to a different part of the screen. This issue may seem small, but with regards to much of what I do, this can actually be critically important. This can manifest as a failure to register a keystroke, button press, or mouse click, or the mouse taking a second to register that I am moving it. Mouse, keyboard, remote controls occasionally experience momentary failure. Internal hardware components appear to be be experiencing similar issues. All peripheral devices are affected randomly. ![]() Sometimes it is necessary to reboot the computer. Sometimes it is necessary to plug into different USB port. Some devices will work again after unplugging and replugging USB. ![]() Sometimes, during session, a peripheral device will suddenly cease responding. Sometimes, at startup, one or more peripheral devices will not be recognized, or its associated software will not be loaded properly. I need my computer operational and I need my devices to properly use their custom functions, in order to use the PC. I am partially disabled, while recovering from a serious injury. Either a problem in each, individual driver handling or a systemic corruption of the way the registry handles support of all drivers (a common root cause for all drivers).Ĭan I track down a single error in the registry which affects all drivers support? Or would reinstalling every device and its associated software correct each device individually?Ī full re-installation of Windows is not an option at this time. Something having to do with the way device drivers are handled. I believe the problem is in the Registry. But now I am left with intermittent device failures. Went through the system and the registry with a fine tooth comb, solved the blue screen issue. After installing different, standalone PhysX (PhysX-SystemSoftware.msi), resulted in persistent Blue Screen on startup. Was forced to install, uninstall, reinstall multiple times. ATI drivers were extremely difficult to uninstall. Did not uninstall ATI prior to installation of Nvidia. Replaced graphics card, from ATI to Nvidia. Suspect registry error or corrupted system file. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |