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?

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.

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>

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.

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

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

All is fine, ATM.

Thanks Frankief.

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.

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

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.

No crashes today.....so far

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

No crashes today.