"Windows Explorer stopped working"

Page 1 of 2 12 LastLast

  1. Posts : 17,545
    Windows 10 Pro x64 EN-GB
       #1

    "Windows Explorer stopped working"


    Help needed, guys and gals!

    Didnīt know to which category my issue belongs so I put it here. Mods, feel free to move.

    Have had no crashes or other problems, have fallen in love with W7. But now there is a major problem. Until today Iīve been using my Logitech bluetooth KB & mouse (see specs) with W7 drivers without problems, but earlier today I got this stupid idea and installed Logitech Setpoint 4.72 to be able to use all the special functions and keys.

    Like Setpoint installation told me, I turned Firewall and Defender off. Installation was OK, Setpoint connection helper found KB and mouse. And then came this:
    Attachment 19627
    Notice please that the otion RESTART THE PROGRAM is not even present, only check solution and close or close.

    Problems details here:

    Problem signature:
    Problem Event Name: BEX64
    Application Name: explorer.exe
    Application Version: 6.1.7100.0
    Application Timestamp: 49ee974f
    Fault Module Name: StackHash_6c37
    Fault Module Version: 0.0.0.0
    Fault Module Timestamp: 00000000
    Exception Offset: 0000000000000000
    Exception Code: c0000005
    Exception Data: 0000000000000008
    OS Version: 6.1.7100.2.0.0.256.1
    Locale ID: 1033
    Additional Information 1: 6c37
    Additional Information 2: 6c3785e28f2114beca863a6e1294065e
    Additional Information 3: c30e
    Additional Information 4: c30ed29dde55986140e1f0bb37437293

    I can start programs using Task Manager > File > New Task, but all Windows features are disabled (Win-key shortcuts etc.). My dual screen system looks now like this:
    Attachment 19628
    (To the left screen 1 = laptop, where you normally had all the icons, gadgets and taskbar)

    Did a system restore, so Setpoint is no longer installed.

    What now?
    Last edited by Kari; 24 Jul 2009 at 11:57. Reason: Problem solved
      My Computer


  2. Posts : 17,545
    Windows 10 Pro x64 EN-GB
    Thread Starter
       #2

    Solved!


    This was a weird issue. And I was stupid enough to make it even worse: to secure my files, I decided to make a full backup before making a system image recovery. And so I did. A full backup. And a system image backup, meaning my backup system image HAD THIS FAULT, too. So after doing a system recovery using my system image, I still had the same problem. How stupid am I?

    But now everything is OK. I did a repair installation, and everything works.

    Still very happy with W7!
      My Computer


  3. Posts : 8,398
    ultimate 64 sp1
       #3

    Kari said:
    Still very happy with W7!
    that's the spirit! good to see you've solved your problem, and learned something too!
      My Computer


  4. Posts : 17,545
    Windows 10 Pro x64 EN-GB
    Thread Starter
       #4

    mickey megabyte said:
    ...and learned something too!
    Yes. But I still can not understand how my brain sometimes works: non-working system, so before I repair it using a system image (had one only couple of days old), I create a new one WITH THE FAULT, and then used that image.

    When you think it, itīs really stupid.
      My Computer


  5. Posts : 26
    Windows 7 X64
       #5

    Does that help, call yourself stupid?
      My Computer


  6. Posts : 17,545
    Windows 10 Pro x64 EN-GB
    Thread Starter
       #6

    raymm said:
    Does that help, call yourself stupid?
    You know, it's a bit surprising but sometimes it does help! This whole issue was my own fault (I call myself a professional! Hah!). With some low level brain usage this had never happened, that's why I called myself idiot, and it really helped.

    Kari
      My Computer


  7. Posts : 3
    Windows 7 RC build 7100 x64
       #7

    N00bness


    Sorry if its a bit noobish, but I didn't quite catch how exactly you fixed your problem. This would be a help for me, as your problem was pretty much an exact replica of mine (except for the program installation that started) I get the same error message with all of the same info (eg, prob event name, app name, time stamp, fault module name etc.) And I really would like some help.
      My Computer


  8. Posts : 17,545
    Windows 10 Pro x64 EN-GB
    Thread Starter
       #8

    Hello Jeddy and welcome to the SevenForums.

    Like I told above, I fixed this issue with a repair installation. Here's Brinks excellent tutorial how to do that.

    Repair installation is basically a modified in-place upgrade which repairs and reinstalls Windows system files leaving user files and installed applications intact.

    Kari
      My Computer


  9. Posts : 3
    Windows 7 RC build 7100 x64
       #9

    Thankyou for the link, I will attempt this now. :)
      My Computer


  10. Posts : 17,545
    Windows 10 Pro x64 EN-GB
    Thread Starter
       #10

    You are welcome. Good luck.

    Kari
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Đ Designer Media Ltd
All times are GMT -5. The time now is 05:42.
Find Us