Typing on my keyboard makes explorer.exe crash.


Recommended Posts

So I recently upgraded from Windows 8.1 preview to 8.1 final, thinking it would be better.  I didn't actually "upgrade", I did a full new fresh install.  Well my GOD is it buggy as hell.  Any time I type into any windows dialog related to explorer.exe, whether it is typing in the address bar of Windows explorer, typing in the windows Run dialog, or typing in the command line in a program shortcut properties, the moment I press a single key on the keyboard, that window freezes.  It then turns grey, and after clicking on it a whole bunch, it disappears, along with every other open window/dialog, and my start menu, as is the characteristic when explorer.exe is killed.

 

This is really farking annoying.  Anyone have any idea why this is happening?  The exact same keyboard (Logitech MK320) worked fine in Windows 8.1 preview on the exact same hardware.  This happens whether I used Microsoft's built in keyboard drivers, and continued to happen when I switched to the official Logitech drivers.  It does not happen in any software that isn't related to explorer.exe, such as typing in Google Chrome, right now.

Link to comment
Share on other sites

Are you sure it's explorer crashing and not your video card resetting itself?

If you have out of date NVidia drivers you can experience the same sort of thing. I've had this happen a number of time on my desktop until I updated to latest drivers.

Link to comment
Share on other sites

Are you sure it's explorer crashing and not your video card resetting itself?

If you have out of date NVidia drivers you can experience the same sort of thing. I've had this happen a number of time on my desktop until I updated to latest drivers.

 

I'm sure, because its only the windows related to explorer.exe that close, and not the entire screen.  I just installed the latest AMD drivers.  Also there are a bajillion event logs of explorer.exe crashing in my action center:

Source
Windows Explorer

Summary
Stopped responding and was closed

Date
?1/?17/?2014 8:56 AM

Status
Not reported

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:	C:\Windows\explorer.exe

Problem signature
Problem Event Name:	AppHangB1
Application Name:	explorer.exe
Application Version:	6.3.9600.16384
Application Timestamp:	5215d379
Hang Signature:	9f30
Hang Type:	134217728
OS Version:	6.3.9600.2.0.0.256.48
Locale ID:	1033
Additional Hang Signature 1:	9f30159d3d3145f62a0c9d3fa645b94b
Additional Hang Signature 2:	6fb9
Additional Hang Signature 3:	6fb93c1a81c0cacd86b77c856096b9e0
Additional Hang Signature 4:	9f30
Additional Hang Signature 5:	9f30159d3d3145f62a0c9d3fa645b94b
Additional Hang Signature 6:	6fb9
Additional Hang Signature 7:	6fb93c1a81c0cacd86b77c856096b9e0

Link to comment
Share on other sites

Tried a different usb port, not sure if you have a mix of usb 2.0 & 3.0? 3.0 can be problematic if your motherboard doesn't have decent drivers. I have a gigabyte mobo which I had to disable usb 3.0 on as it's driver support is shoddy (Was produced when 3.0 was just emerging).

Was getting weird behaviours prior to disabling it.

What about testing another usb keyboard to rule out the logitech.

Link to comment
Share on other sites

Well I found the culprit; my keyboard works just fine when CrystalControl2 isn't running.  CC2 is one of the first programs I get when I reinstall windows, as it controls the LCD screen on my tower.  It worked just fine with 8.1 preview, but since the last version was released in 2009, I guess I shouldn't be too surprised that it finally broke in Windows 8.1 final.  As soon as I start up CC2, I can't type anything in explorer.exe, for some reason.  Even though CC2 doesn't use any keyboard hooks.  Weird.

 

Thanks for your help and quick replies, folks!

Link to comment
Share on other sites

According to their support forum you may be able to download a newer version of the driver by going into Device Manager, right-clicking the device and manually updating the drivers. Could be worth trying if you really want to use that. :)

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.