|
Little background first, like 2 months ago I split liquid onto my keyboard. That keyboard stopped working, but when I spilled on it I was trying to fix it. I dried it off and plugged it in and out a few times to see if it would work so I didn't have to buy a new one. There was an error once when I plugged in this keyboard though. There was an error installing the driver or something. It causes my entire CPU to freeze and I was forced to reset by hitting the button on my PC.
Anyway, ever since then, my PC has been acting a bit weird. When I boot up my PC, it hangs for a loooooooooooooong time after the windows logo (about 10-15 minutes). While it is hanging none of my devices (keyboard, mouse, monitor) are detected as in they don't light up. What I feel is causing this hanging is that when I got the error installing the driver for my old computer that I had spilled stuff on and my PC froze and I force restarted it, that bad driver or whatever is still on my hard disc. Basically, I want to know if there is anyway I can search for and detect the corrupt/bad driver and fix it or if there is a way I can fix it with windows? I don't have a system restore to that date so I can't do that. I just want to see if I can fix it before I resort to a reformat.
Thanks
|
How does the Device Manager look like? Is there a question mark or some other suspicious symbol displayed on one of the devices? If you look in the Properties window for a device, on one of the tabs you'll see a history of events that are tied to that particular device.
There is a "Windows Event Viewer" tool for browsing the logs on Windows. On the left pane of that tool, there's a "custom" view section, and one view named "administrative events" should already exist there. That view will show a collection of all warnings and errors that were recorded. Sort by the date/time column and look for the point in time where Windows was booting and where the long pause happened. It might show something suspicious there.
If you look around some more in the event viewer, you might also find that Windows logged normal messages that weren't warnings. I don't know if Windows works like this, so this might not be the case. If you find that it did record all kinds of stuff, you might be able to find the last thing it did before the pause, and the first thing it did after the pause.
|
|
|
|