Explorer Crashes

I'm running Fences Pro on Win 7 64 without problems.  Are you running any other program or programs that might be causing the problem?

Fences is compatible with win 7 64.  I've been running it ever since its release [fences] without issue, and certainly without 'Explorer crashes'.

The issue will be with something else specific to your computer....;)

I have the same situation.

Everything was working great and MS came out with a .Net update for 64 machines that will not install.  The security update they pushed through 2 days earlier seems to have caused the problem.

They definitely broke something.  They will never admit it, I am sure of that.

Once they get the 64 bit .Net upgrade to work, I am hoping fences will work too.

BT  btischler@hsillc.com

Here is the exact update that caused the problem in my opinion

Update for Microsoft .NET Framework 4 on Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2 for x64-based Systems (KB2468871)

Installation date: ‎2/‎22/‎2012 3:17 AM

Installation status: Failed

Error details: Code 643

Update type: Recommended

Install this update to resolve issues in Microsoft .NET Framework 4. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.

More information: http://go.microsoft.com/fwlink/?LinkID=210664

Help and Support: http://support.microsoft.com

It has failed for the last week.

I have not had any failed updates, but explorer crashes (as in locks up) pretty often lately.

Like 8 to 10 times today. I have tried different scenarios of turning off/on several Stardock apps without any real success.

My Explorer crashes are directly related to Windowblinds somehow>

Log Name:      Application
Source:        Application Error
Date:          2/24/2012 10:17:28 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MyObsession
Description:
Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
Faulting module name: WBLIND64.dll, version: 7.3.1.0, time stamp: 0x4f2000dd
Exception code: 0xc0000005
Fault offset: 0x000000000003268a
Faulting process id: 0x894
Faulting application start time: 0x01ccf3352d793bfd
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\PROGRA~2\Stardock\OBJECT~1\WindowBlinds\WBLIND64.dll
Report Id: 01f30207-5f70-11e1-abde-00219b1f07b5
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-02-25T05:17:28.000000000Z" />
    <EventRecordID>32113</EventRecordID>
    <Channel>Application</Channel>
    <Computer>MyObsession</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Explorer.EXE</Data>
    <Data>6.1.7601.17567</Data>
    <Data>4d672ee4</Data>
    <Data>WBLIND64.dll</Data>
    <Data>7.3.1.0</Data>
    <Data>4f2000dd</Data>
    <Data>c0000005</Data>
    <Data>000000000003268a</Data>
    <Data>894</Data>
    <Data>01ccf3352d793bfd</Data>
    <Data>C:\Windows\Explorer.EXE</Data>
    <Data>C:\PROGRA~2\Stardock\OBJECT~1\WindowBlinds\WBLIND64.dll</Data>
    <Data>01f30207-5f70-11e1-abde-00219b1f07b5</Data>
  </EventData>
</Event>

I know I'll look stupid for asking but, where did you find that Frankief?

No, not stupid! Just open your event viewer and look for errors, hi lite it and in the right panel click "view all instances of this event" You can copy and paste the text from the actual error. Quickest way to get there is to type in "event" in the start menu.

I know it's event viewer. What category in event viewer?

How often is it happening?

Control Panel/ Programs and Features/ Microsoft .NET Framework 4 Client Profile. Select "Repair .NET Framework 4 Client Profile to its original state". 

It is in the "errors" under "event viewer local" Happens several times a day and always when I am hovering around the right side of a window to expand or close it.

I seem to have found my problem.....nVidia gfx driver update.

All is fine, ATM.

Thanks Frankief.

Happy to be of some minor assistance!

Well, that was premature. The graphics driver seemed to fix it, but 15 minutes later, it happened again.

Dunno if that was meant for me, but I did it.

There is no "Errors" under event viewer local?

I can find undr "Windows Logs" "Applications"

Hope you can read this, I didn't draw too well with the "snipping tool"!

In keeping with my penchant for weird I opened my event viewer local as per Frankief's instructions. The very first entry is dated 3/28/2011. Printer Service - Spooler Operation failure. Time was 3:30 a.m. My question is how is it possible considering I've only had this laptop less than three months?

My problem still exists.....I may be looking at a reinstall.

This is on the new PC I just built. SSD and all new parts except for the HDDs.

Uvah, any events that occurred while your machine was being set up at the factory will still show up under the event viewer. They have to run the machine to get everything pre installed and working properly.

No crashes today.....so far

I am experiencing the same issues with Explorer crashing Win 7 64 bit.  Mainly, this occurs when I drag a file onto a folder on my desktop.

I am using the latest version of Fences, and believe that it may be due to the Microsoft update, as I did not experience this issue prior to the update.

Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x13bc
Faulting application start time: 0x01ccf5b9d40b3950
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 16e38700-61ad-11e1-9c09-00044b03d6c6

All is good here. I reinstalled both Windowblinds and rolled back to a previous graphics driver.

No crashes today.