locked
Windows Explorer Crashes - Event ID: 1000 - Faulting Module Name: DUser.dll RRS feed

  • Question

  • [I'm experiencing a very similar problem & thus far have received little feedback elswhere so I thought that I'd post my information here in the hope that someone else may pick up on it. I’m desperate for a resolution!]

    My current system information is as follows:

    OS Name Microsoft Windows 7 Ultimate
    Version 6.1.7601 Service Pack 1 Build 7601
    Other OS Description Not Available
    OS Manufacturer Microsoft Corporation
    System Name RD-VAIO
    System Manufacturer Sony Corporation
    System Model VPCL22SFX
    System Type x64-based PC
    Processor Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz, 2201 Mhz, 4 Core(s), 8 Logical Processor(s)
    BIOS Version/Date American Megatrends Inc. R1132T7, 7/12/2011
    SMBIOS Version 2.7
    Windows Directory C:\Windows
    System Directory C:\Windows\system32
    Boot Device \Device\HarddiskVolume3
    Locale United States
    Hardware Abstraction Layer Version = "6.1.7601.17514"
    User Name RD-VAIO\Randy
    Time Zone Eastern Standard Time
    Installed Physical Memory (RAM) 8.00 GB
    Total Physical Memory 7.98 GB
    Available Physical Memory 4.15 GB
    Total Virtual Memory 20.0 GB
    Available Virtual Memory 16.1 GB
    Page File Space 12.0 GB
    Page File C:\pagefile.sys

    I have been incurring application errors with Windows Explorer at an alarming frequency during the past few days.

    The event log from a  recent error follows.

    Ideas? Thanks.

    Log Name: Application
    Source: Application Error
    Date: 11/26/2012 8:29:40 AM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: RD-VAIO
    Description:
    Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
    Faulting module name: EXPLORERFRAME.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c6a8
    Exception code: 0xc0000005
    Fault offset: 0x00000000000411ce
    Faulting process id: 0x1aec
    Faulting application start time: 0x01cdcb6e9824938a
    Faulting application path: C:\Windows\Explorer.EXE
    Faulting module path: C:\Windows\system32\EXPLORERFRAME.dll
    Report Id: 54378477-37cd-11e2-ad10-90004eb4d6e0
    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-11-26T13:29:40.000000000Z" />
    < EventRecordID>173330</EventRecordID>
    < Channel>Application</Channel>
    < Computer>RD-VAIO</Computer>
    < Security />
    < /System>
    < EventData>
    < Data>Explorer.EXE</Data>
    < Data>6.1.7601.17567</Data>
    < Data>4d672ee4</Data>
    < Data>EXPLORERFRAME.dll</Data>
    < Data>6.1.7601.17514</Data>
    < Data>4ce7c6a8</Data>
    < Data>c0000005</Data>
    < Data>00000000000411ce</Data>
    < Data>1aec</Data>
    < Data>01cdcb6e9824938a</Data>
    < Data>C:\Windows\Explorer.EXE</Data>
    < Data>C:\Windows\system32\EXPLORERFRAME.dll</Data>
    < Data>54378477-37cd-11e2-ad10-90004eb4d6e0</Data>
    < /EventData>
    < /Event>

    Hi,

    It seems this issue can be caused by corrupted ExplorerFrame.dll. Please check the following similar thread could help:

    Windows Explorer stops working

    http://social.technet.microsoft.com/Forums/en-US/w7itproperf/thread/169f3d8d-b31a-4208-9bdb-34ac09245c0f

    In addition, you can try to run SFC to scan the system files.

    1. Click Start, and then type cmd in the Start Search box.

    2. In the results area, right-click cmd.exe, and then click Run as administrator. You will be prompted to type the password for an administrator account. Click Continue if you are the administrator or type the administrator password. Then, click Continue.

    3. At the command prompt, type Sfc /scannow, and then press ENTER.

    The scan may take some time and prompt you to insert Windows Vista disc. After that, please restart the computer and re-register the file ExplorerFrame.dll and check the result.

    Hope this helps.

    Vincent Wang
    TechNet Community Support

    Hi Vincent-

    Thanks for the response!

    I ran the scan & it came back clean. Honestly, I don't think that I've ever experienced any integrity violations using scannow.

    Thanks much.

    -Randy

    A few updates...

    Instead of re-registering the ExplorerFrame.dll file, I ran the Update Readiness tool. It appeared to have worked until I tried accessing Windows Update. When I clicked on 'Optional Update', Explorer crashed again (event text below...DUser.dll culprit now).


    Running this tool did fix a long-running User Profile issue though where I had to click on my Admin picture before Windows would start.

    One thing that I noticed after running the Readiness tool is that the CheckSUR log noted 2 errors as follows:

    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.21645
    Package Version 17.0
    2012-11-28 17:03

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f) CBS Catalog Missing 0x00000002 servicing\Packages\Package_for_KB2661663~31bf3856ad364e35~amd64~~6.1.2.0.cat

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:
    Seconds executed: 672
    Found 1 errors
    CBS Catalog Missing Total count: 1

    Unavailable repair files:
    servicing\packages\Package_for_KB2661663~31bf3856ad364e35~amd64~~6.1.2.0.mum
    servicing\packages\Package_for_KB2661663~31bf3856ad364e35~amd64~~6.1.2.0.cat

    The new Explorer crash event details are:

    Log Name: Application
    Source: Application Error
    Date: 11/28/2012 5:36:31 PM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: RD-VAIO
    Description:
    Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
    Faulting module name: DUser.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdf26
    Exception code: 0xc0000005
    Fault offset: 0x0000000000001856
    Faulting process id: 0x590
    Faulting application start time: 0x01cdcdb65201a46c
    Faulting application path: C:\Windows\Explorer.EXE
    Faulting module path: C:\Windows\system32\DUser.dll
    Report Id: 0d9e75c7-39ac-11e2-8667-90004eb4d6e0
    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-11-28T22:36:31.000000000Z" />
    < EventRecordID>174386</EventRecordID>
    < Channel>Application</Channel>
    < Computer>RD-VAIO</Computer>
    < Security />
    < /System>
    < EventData>
    < Data>Explorer.EXE</Data>
    < Data>6.1.7601.17567</Data>
    < Data>4d672ee4</Data>
    < Data>DUser.dll</Data>
    < Data>6.1.7600.16385</Data>
    < Data>4a5bdf26</Data>
    < Data>c0000005</Data>
    < Data>0000000000001856</Data>
    < Data>590</Data>
    < Data>01cdcdb65201a46c</Data>
    < Data>C:\Windows\Explorer.EXE</Data>
    < Data>C:\Windows\system32\DUser.dll</Data>
    < Data>0d9e75c7-39ac-11e2-8667-90004eb4d6e0</Data>
    < /EventData>
    < /Event>

    I experienced another crash this morning, again when clicking on the dialog for an optional update in Windows Update:

    Log Name: Application
    Source: Application Error
    Date: 11/30/2012 8:02:06 AM
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: RD-VAIO
    Description:
    Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
    Faulting module name: DUser.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdf26
    Exception code: 0xc0000005
    Fault offset: 0x0000000000001856
    Faulting process id: 0x69c
    Faulting application start time: 0x01cdce8775bb8142
    Faulting application path: C:\Windows\Explorer.EXE
    Faulting module path: C:\Windows\system32\DUser.dll
    Report Id: 23ebd1c8-3aee-11e2-9228-90004eb4d6e0
    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-11-30T13:02:06.000000000Z" />
    <EventRecordID>175170</EventRecordID>
    <Channel>Application</Channel>
    <Computer>RD-VAIO</Computer>
    <Security />
    </System>
    <EventData>
    <Data>Explorer.EXE</Data>
    <Data>6.1.7601.17567</Data>
    <Data>4d672ee4</Data>
    <Data>DUser.dll</Data>
    <Data>6.1.7600.16385</Data>
    <Data>4a5bdf26</Data>
    <Data>c0000005</Data>
    <Data>0000000000001856</Data>
    <Data>69c</Data>
    <Data>01cdce8775bb8142</Data>
    <Data>C:\Windows\Explorer.EXE</Data>
    <Data>C:\Windows\system32\DUser.dll</Data>
    <Data>23ebd1c8-3aee-11e2-9228-90004eb4d6e0</Data>
    </EventData>
    < /Event>

    I can upload .dmp files if you need to see them.

    Anyone here have any thoughts? Thanks.

    RD

    Friday, November 30, 2012 8:06 PM

All replies

  • Can you provide the .dmp files via via Windows Live SkyDrive or similar site?

    The following link has information on using Windows Live SkyDrive:

    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

    Saturday, December 1, 2012 12:34 PM
  • Can you provide the .dmp files via via Windows Live SkyDrive or similar site?

    The following link has information on using Windows Live SkyDrive:

    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    Thanks so much for getting back to me! I'm in the process of uploading the last 3 .dmp files to my SkyDrive account now & will sen you the link when finished. Thanks.

    RD

    Saturday, December 1, 2012 10:03 PM
  • Can you provide the .dmp files via via Windows Live SkyDrive or similar site?

    The following link has information on using Windows Live SkyDrive:

    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

    The 3 .dmp files that I mentioned in my last response can be found here: https://skydrive.live.com/redir?resid=7C41C68C6993E70D!280&authkey=!AAmJ61tqCPpS6Oo.


    RD

    Saturday, December 1, 2012 10:47 PM
  • Can you try uninstalling "Network Magic" and see if the errors resolve.
    Sunday, December 2, 2012 3:17 AM
  • Can you try uninstalling "Network Magic" and see if the errors resolve.

    Will do, but I've been using that program for years & its never been an issue.

    Another user is also assisting & following are my responses to his initial two questions followed by other troubleshooting steps that I have taken thus far or are in progress.

    1. Did the issue started recently?

    [Yes. The first event occurred circa 11/26/12. Whether coincidence and/or related or not, I started having problems with my desktop themes at about the same time. Everything is blacked out & I've used about every fix to solve that problem, but no luck thus far. That said, I'll tackle the Explorer crash issue first then come back to this!]

    2. Have you made any changes to the computer prior to this issue?

    [I know I did but when I tried to use System Restore to restore several days prior to my first incident, all attempts at restoring failed, but that's a whole different issue. In my troublshooting per your suggestions for my current problem, I'll create a 'test' restore point to ensure that SR is nominal again.]

      • Booted Windows into Safe Mode
        1. Could not replicate explorer.exe crash since Windows Update not accessible in SM
      • Set test Restore Point using System Restore

    Process appeared to proceed nominally until Windows fully loaded on restart (see screenshot below)

    1. Booted Windows into Safe Mode
      1. Could not replicate explorer.exe crash since Windows Update not accessible in SM
    2. Set test Restore Point using System Restore
      1. Results
        1. Process appeared to proceed nominally until Windows fully loaded on restart
        2. Error Details: System Restore failed while restoring the registry from the restore point. An unspecified error occurred during System Restore. (0x800703f9)
    3. Ran sfc /scannow
      1. Results
        1. Microsoft Windows [Version 6.1.7601]
        2. Copyright (c) 2009 Microsoft Corporation. All rights reserved.
        3. C:\Users\Randy>sfc /scannow
        4. Beginning system scan. This process will take some time.
        5. Beginning verification phase of system scan.
        6. Verification 100% complete.
        7. Windows Resource Protection did not find any integrity violations.
    4. Ran Microsoft Safety Scanner (Quick Scan)
      1. Results
        1. The scan completed successfully and no viruses, spyware, and other potentially unwarranted software were detected.
        2. [Note: I run daily scheduled full scans using SUPERAntiSpyware & Microsoft Security Essentials & they never locate anything malicious other than tracking cookies.]
    5. Perform Clean Boot
      1. Results
      2.          In testing as of 1:49 PM ET, Sunday, December 2, 2012.

    So, it appears that I definitely have multiple issues occurring simultaneously.


    RD

    Sunday, December 2, 2012 7:28 PM
  • Can you try uninstalling "Network Magic" and see if the errors resolve.

    Will do, but I've been using that program for years & its never been an issue.

    Another user is also assisting & following are my responses to his initial two questions followed by other troubleshooting steps that I have taken thus far or are in progress.

    1. Did the issue started recently?

    [Yes. The first event occurred circa 11/26/12. Whether coincidence and/or related or not, I started having problems with my desktop themes at about the same time. Everything is blacked out & I've used about every fix to solve that problem, but no luck thus far. That said, I'll tackle the Explorer crash issue first then come back to this!]

    2. Have you made any changes to the computer prior to this issue?

    [I know I did but when I tried to use System Restore to restore several days prior to my first incident, all attempts at restoring failed, but that's a whole different issue. In my troublshooting per your suggestions for my current problem, I'll create a 'test' restore point to ensure that SR is nominal again.]

      • Booted Windows into Safe Mode
        1. Could not replicate explorer.exe crash since Windows Update not accessible in SM
      • Set test Restore Point using System Restore

    Process appeared to proceed nominally until Windows fully loaded on restart (see screenshot below)

    1. Booted Windows into Safe Mode
      1. Could not replicate explorer.exe crash since Windows Update not accessible in SM
    2. Set test Restore Point using System Restore
      1. Results
        1. Process appeared to proceed nominally until Windows fully loaded on restart
        2. Error Details: System Restore failed while restoring the registry from the restore point. An unspecified error occurred during System Restore. (0x800703f9)
    3. Ran sfc /scannow
      1. Results
        1. Microsoft Windows [Version 6.1.7601]
        2. Copyright (c) 2009 Microsoft Corporation. All rights reserved.
        3. C:\Users\Randy>sfc /scannow
        4. Beginning system scan. This process will take some time.
        5. Beginning verification phase of system scan.
        6. Verification 100% complete.
        7. Windows Resource Protection did not find any integrity violations.
    4. Ran Microsoft Safety Scanner (Quick Scan)
      1. Results
        1. The scan completed successfully and no viruses, spyware, and other potentially unwarranted software were detected.
        2. [Note: I run daily scheduled full scans using SUPERAntiSpyware & Microsoft Security Essentials & they never locate anything malicious other than tracking cookies.]
    5. Perform Clean Boot
      1. Results
      2.          In testing as of 1:49 PM ET, Sunday, December 2, 2012.

    So, it appears that I definitely have multiple issues occurring simultaneously.


    RD

    Next steps...

    1. Perform Clean Boot Process
      1. Step 1 of Process
        1. Results
          1. Opened Windows Update
          2. Clicked on One Optional Update à Windows Explorer Not Responding
          3. Event Log

    Log Name:      Application

    Source:        Application Error

    Date:          12/2/2012 4:13:09 PM

    Event ID:      1000

    Task Category: (100)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      RD-VAIO

    Description:

    Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4

    Faulting module name: DUser.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdf26

    Exception code: 0xc0000005

    Fault offset: 0x0000000000001856

    Faulting process id: 0x7c4

    Faulting application start time: 0x01cdd0d126f52f44

    Faulting application path: C:\Windows\Explorer.EXE

    Faulting module path: C:\Windows\system32\DUser.dll

    Report Id: 11fa94bb-3cc5-11e2-9dd8-90004eb4d6e0

    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-12-02T21:13:09.000000000Z" />

        <EventRecordID>176759</EventRecordID>

        <Channel>Application</Channel>

        <Computer>RD-VAIO</Computer>

        <Security />

      </System>

      <EventData>

        <Data>Explorer.EXE</Data>

        <Data>6.1.7601.17567</Data>

        <Data>4d672ee4</Data>

        <Data>DUser.dll</Data>

        <Data>6.1.7600.16385</Data>

        <Data>4a5bdf26</Data>

        <Data>c0000005</Data>

        <Data>0000000000001856</Data>

        <Data>7c4</Data>

        <Data>01cdd0d126f52f44</Data>

        <Data>C:\Windows\Explorer.EXE</Data>

        <Data>C:\Windows\system32\DUser.dll</Data>

        <Data>11fa94bb-3cc5-11e2-9dd8-90004eb4d6e0</Data>

      </EventData>

    </Event>

    1. Captured Application Error .evtx file
    2. Captured ALL Administrative Events Log in .evtx file & uploaded to SkyDrive account
    3. Uploaded latest .dmp file to SkyDrive account
    b.Step 2 of CB process pending as of 4:39 PM ET, Sunday, December 02, 2012


    RD

    Sunday, December 2, 2012 9:46 PM
  • Here are my complete set of troubleshooting steps to date. I'm now at a standstill as nothing has worked. Troubleshooting logs, files, etc. can be found on SkyDrive here: https://skydrive.live.com/redir?resid=7C41C68C6993E70D!280&authkey=!AAmJ61tqCPpS6Oo.

    Explorer Crash Troubleshooting Notes

      • Booted Windows into Safe Mode
        1. Could not replicate explorer.exe crash since Windows Update not accessible in SM
      • Set test Restore Point using System Restore
        1. Results
          1. Process appeared to proceed nominally until Windows fully loaded on restart
          2. Error Details: System Restore failed while restoring the registry from the restore point. An unspecified error occurred during System Restore. (0x800703f9)
      • Ran sfc /scannow
        1. Results
          1. Microsoft Windows [Version 6.1.7601]
          2. Copyright (c) 2009 Microsoft Corporation. All rights reserved.
          3. C:\Users\Randy>sfc /scannow
          4. Beginning system scan. This process will take some time.
          5. Beginning verification phase of system scan.
          6. Verification 100% complete.
          7. Windows Resource Protection did not find any integrity violations.
      • Ran Microsoft Safety Scanner (Quick Scan)
        1. Results
          1. The scan completed successfully and no viruses, spyware, and other potentially unwarranted software were detected.
          2. [Note: I run daily scheduled full scans using SUPERAntiSpyware & Microsoft Security Essentials & they never locate anything malicious other than tracking cookies.]
      • Perform Clean Boot Process
        1. Step 1 of Process
          1. Results
            1. Opened Windows Update
            2. Clicked on One Optional Update à Windows Explorer Not Responding
            3. Event Log

    Log Name:      Application

    Source:        Application Error

    Date:          12/2/2012 4:13:09 PM

    Event ID:      1000

    Task Category: (100)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      RD-VAIO

    Description:

    Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4

    Faulting module name: DUser.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdf26

    Exception code: 0xc0000005

    Fault offset: 0x0000000000001856

    Faulting process id: 0x7c4

    Faulting application start time: 0x01cdd0d126f52f44

    Faulting application path: C:\Windows\Explorer.EXE

    Faulting module path: C:\Windows\system32\DUser.dll

    Report Id: 11fa94bb-3cc5-11e2-9dd8-90004eb4d6e0

    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-12-02T21:13:09.000000000Z" />

        <EventRecordID>176759</EventRecordID>

        <Channel>Application</Channel>

        <Computer>RD-VAIO</Computer>

        <Security />

      </System>

      <EventData>

        <Data>Explorer.EXE</Data>

        <Data>6.1.7601.17567</Data>

        <Data>4d672ee4</Data>

        <Data>DUser.dll</Data>

        <Data>6.1.7600.16385</Data>

        <Data>4a5bdf26</Data>

        <Data>c0000005</Data>

        <Data>0000000000001856</Data>

        <Data>7c4</Data>

        <Data>01cdd0d126f52f44</Data>

        <Data>C:\Windows\Explorer.EXE</Data>

        <Data>C:\Windows\system32\DUser.dll</Data>

        <Data>11fa94bb-3cc5-11e2-9dd8-90004eb4d6e0</Data>

      </EventData>

    </Event>

    1. Captured Application Error .evtx file
    2. Captured ALL Administrative Events Log in .evtx file & uploaded to SkyDrive account
    3. Uploaded latest .dmp file to SkyDrive account
      1. Step 2 of CB process pending as of 4:39 PM ET, Sunday, December 02, 2012
      2. Skipped to Step 3 of CB process as test
        1. Results
          1. Started all startup programs, tasks, etc. with no discernible resolution
      3. Used CCleaner by Piriform to disable/delete unneeded/unwarranted startup programs, scheduled tasks, etc.
        1. Results
          1. [Important to note that CCleaner identified remnants of old McAfee installations so ran McAfee Automated Cleanup tool.]
          2. Attempted selecting optional update again in Windows Update à Windows Explorer has stopped working
          3. Captured event & .dmp files/logs
      4. Started Systernals Procman
        1. Results
          1. Began capturing events
          2. Attempted selecting optional update again in Windows Update à Windows Explorer has stopped working
          3. Captured Procman log of event details (uploaded to SkyDrive)
      5. on 12/2 to run overnight
        1. Results (morning of 12/3)
          1. Not completed due to memory drain & background VAIO process interruption (captured screenshots)
      6. Began Step 2 of CB Process
        1. Results
          1. Deselected ½ of Services & restarted
          2. Important to note that once again a McAfee component reappeared in Services; did thorough scan of C: drive & could not locate said components (hidden files visible); used McAfee tool again
          3. Attempted selecting optional update again in Windows Update à Windows Explorer has stopped working
          4. Captured event & .dmp files/logs (uploaded to SK)
      7. Uninstalled Network Magic & continued Step 2 of CB process
        1. Results
          1. Started nominally
          2. This time Windows Update indicated no optional update available so could not test to see if explorer.exe would crash
          3. Stopped explorer.exe manually in TM as experiment à no error messages generated
      8. Used msconfig & Services to select usual startup programs, tasks that I’ve used in the past for my needs
        1. Results
          1. Started nominally
          2. Attempted selecting optional update again in Windows Update à Windows Explorer has stopped working
          3. Captured event & .dmp files/logs (uploaded to SK)

    RD

    Monday, December 3, 2012 3:48 PM
  • Can you try uninstalling "Network Magic" and see if the errors resolve.

    Hello,

    Can you be of further help? I've provided several updates & haven't heard back. If you don't have the time to help any longer, please do let me know so that I can close this thread out. Thanks.


    RD

    Wednesday, December 5, 2012 11:40 PM
  • I took a look at the files you provided and the Event Viewer in particular shows many Application Errors and not just with Explorer.

    There was also errors indicating a problem with the file system structure.

    Have you run a chkdsk on the hard disk?

    Also, from the Event Viewer, Explorer crashed many times involving DropboxExt64.17.dll.

    Can you uninstall Dropbox and see if the Explorer crashes resolve?

    Thursday, December 6, 2012 2:43 AM
  • Thanks for getting back!

    Oh yea, a plethora of app errors, & not with just Explorer, is a understatement at best. :)

    I've run a chkdsk before but the last one was most likely early last week. I'll definitely give it another shot this morning.

    I noted the issue with Dropbox as well. I did a full uninstall & clean install earlier this week & haven't noticed it in the event errors in the last few days unless I missed something.

    I'll run chkdsk then u/l report to SD. I'm going to rearange the folders in order for folks to find things a bit quicker.


    RD

    Thursday, December 6, 2012 12:45 PM
  • I took a look at the files you provided and the Event Viewer in particular shows many Application Errors and not just with Explorer.

    There was also errors indicating a problem with the file system structure.

    Have you run a chkdsk on the hard disk?

    Also, from the Event Viewer, Explorer crashed many times involving DropboxExt64.17.dll.

    Can you uninstall Dropbox and see if the Explorer crashes resolve?

    After 8 long hours, chkdsk completed with no errors.

    I have uploaded the log for it & several event logs that I captured immediately after restarting the computer to SD (https://skydrive.live.com/redir?resid=7C41C68C6993E70D!343&authkey=!AOfbK8MsDT4Lc-g).

    There obviously not just one factor in play here as you'll see in the logs. One service popped up quite often & that was "Bonjour Service". If I remember correctly, it is connected to Apple products like QuickTime. I may be very wrong but I thought that it was worth mentioning.

    Thanks for your continued assistance!


    RD

    Thursday, December 6, 2012 11:51 PM
  • Did you uninstall Dropbox?

    If so, can you provide any .dmp files created since uninstalling Dropbox?

    Saturday, December 8, 2012 1:30 PM
  • Did you uninstall Dropbox?

    If so, can you provide any .dmp files created since uninstalling Dropbox?


    Sorry I didn't based on my previous answer but will do so & provide a new link to .dmp files.

    RD

    Saturday, December 8, 2012 3:26 PM
  • Did you uninstall Dropbox?

    If so, can you provide any .dmp files created since uninstalling Dropbox?


    I haven't uninstalled DB yet due to another new issue that is related occured. Please see my latest troubleshooting notes & files (4) at: https://skydrive.live.com/redir?resid=7C41C68C6993E70D!351&authkey=!AGm5-MhgnfRIDSE

    RD

    Saturday, December 8, 2012 8:32 PM
  • The new error references an "unknown" "faulting module":

    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

    Can you provide a dump file for the crash?

    Saturday, December 8, 2012 9:44 PM
  • The new error references an "unknown" "faulting module":

    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

    Can you provide a dump file for the crash?


    Sorry about. Uploading now to same folder.

    RD

    Saturday, December 8, 2012 10:01 PM
  • The user32.dll seems to be implicated in the crash.

    You previously said tried Safe Mode and you could not access Windows Update.

    Can you try "Safe Mode with Networking".

    Sunday, December 9, 2012 12:55 AM
  • The user32.dll seems to be implicated in the crash.

    You previously said tried Safe Mode and you could not access Windows Update.

    Can you try "Safe Mode with Networking".


    I cannot get WU to execute when in "Safe Mode with Networking". I captured several screenshots & uploaded to the same troubleshooting folder for 08Dec12, but in case the link may no longer be active, here is another: https://skydrive.live.com/redir?resid=7C41C68C6993E70D!351&authkey=!AGm5-MhgnfRIDSE

    RD

    Sunday, December 9, 2012 4:38 PM
  • can you provide the following file via Windows Live SkyDrive?:

    C:\Windows\windowsupdate.log

    Sunday, December 9, 2012 5:56 PM
  • can you provide the following file via Windows Live SkyDrive?:

    C:\Windows\windowsupdate.log


    Done. Same folder as before.

    RD

    Sunday, December 9, 2012 6:15 PM
  • can you provide the following file via Windows Live SkyDrive?:

    C:\Windows\windowsupdate.log

    Please see the following steps I took based on a 'whim' given a few things I had read. Didn't know if it would be cooincidental or not. Turned out to be the former. New files are here: https://skydrive.live.com/redir?resid=7C41C68C6993E70D!361&authkey=!ADTMN8--jW1gsKE

      • Based on my further research on an Outlook issue & given the frequency of Bonjour Services errors being identified in Events Viewer, uninstalled all Apple programs & Bonjour Service
        1. Results
      1. Attempted selecting optional update again in Windows Update à Windows Explorer has stopped working
      2. Captured event & .dmp files/logs (uploaded to SK)

    RD

    Sunday, December 9, 2012 9:39 PM
  • Looking at the windowsupdate.log shows several errors that may indicate a corruption of a system file(s).

    You can use the following article to assess the log:

    http://support.microsoft.com/kb/902093

    What I would suggest is to concentrate on fixing the issue with Windows Update as all other issues may be secondary.

    One thing, can you try another user account with administrator privileges (create one if necessary) and see if the same issue exists in that account.

    Sunday, December 9, 2012 10:45 PM
  • Looking at the windowsupdate.log shows several errors that may indicate a corruption of a system file(s).

    You can use the following article to assess the log:

    http://support.microsoft.com/kb/902093

    What I would suggest is to concentrate on fixing the issue with Windows Update as all other issues may be secondary.

    One thing, can you try another user account with administrator privileges (create one if necessary) and see if the same issue exists in that account.

    Yea, I figured as much. I'll definitely study the KB you suggested. In fact, I took a quick look & noticed the following about setting up verbose logging. Odd thing is that I don't have "Trace" in the key. Any ideas on why not?

    Understood about concentrating on one issue at a time! I'll try the user account suggestion & see what happens there.

    One other thought is given that I've been struggling with this for about 2 weeks now & getting great advice from experts like yourself, do you think that it's time to go ahead & 'reinstall'? Please take a look at this article by Fred Langa & let me know what you think, "Win7′s no-reformat, nondestructive reinstall" (https://windowssecrets.com/top-story/win7s-no-reformat-nondestructive-reinstall/). 

    How to enable extended logging



    Microsoft Product Support Services may ask you  to turn on  verbose logging.  To turn on  verbose logging,   add the following registry key with two   values:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Trace
    Value   name: Flags
    Value type: REG_DWORD
    Value data: 00000007

    Value   name: Level
    Value type: REG_DWORD
    Value data: 00000004
    This   registry key turns on  an extended tracing to the   %systemroot%\Windowsupdate.log  file. Additionally,  this   registry key turns on  an extended tracing to any attached debuggers.

    RD

    Sunday, December 9, 2012 11:27 PM
  • The Trace would not exist by default, it would have to be created.

    The article by Fred Langa would be similar to the following:

    http://www.sevenforums.com/tutorials/3413-repair-install.html

    That should work if the problems are from corrupted system file(s) and/or settings.

    If you do attempt a "repair install" back up any critical files beforehand.

    Monday, December 10, 2012 2:49 AM
  • The Trace would not exist by default, it would have to be created.

    The article by Fred Langa would be similar to the following:

    http://www.sevenforums.com/tutorials/3413-repair-install.html

    That should work if the problems are from corrupted system file(s) and/or settings.

    If you do attempt a "repair install" back up any critical files beforehand.

    Hmm, I guess I misinterepreted the explanation as I thought that it stated that I would add the new keys under an already present Trace sub. I'll go ahead & do it in case I want to attempt further troublshooting.

    Thanks for the link to the other article. From just a quick read, it appears that Fred's method is much easier. Believe me, I'll backup...may even perform a new disk image so that I capture everything.

    Thanks again & I'll keep you posted.


    RD

    Monday, December 10, 2012 1:19 PM
  • You're welcome, and good luck!
    Monday, December 10, 2012 3:16 PM
  • The Trace would not exist by default, it would have to be created.

    The article by Fred Langa would be similar to the following:

    http://www.sevenforums.com/tutorials/3413-repair-install.html

    That should work if the problems are from corrupted system file(s) and/or settings.

    If you do attempt a "repair install" back up any critical files beforehand.


    Well, this could only happen to me...Murphy's Law x100. :)

    The following excerpt is key:

    "If you’re not running Win7 SP1, skip ahead to the next section.
    You can also skip ahead if you’re repairing an SP1 setup with a Win7 setup DVD that already contains the SP1 files — but such disks are still relatively rare as of this writing.
    If you’re still reading this paragraph, then you’re most likely attempting to repair a Win7 SP1 setup with an original, pre-SP1 DVD. That’s OK, provided you take an important preparatory step.
    Win7 SP1 replaced many of your original system files with newer versions. If you try to install the older, original Win7 files over the newer SP1 files, the setup process will balk at what it sees as an erroneous downgrade.
    So, if you’re attempting to repair Win7 SP1 with a pre-SP1 DVD, you need to remove SP1 from the target PC before proceeding. Fortunately, that’s easy, as Figure 1 shows."

    I originally had Windows 7 Pro installed but performed a Windows Anytime Upgrade to Ultimate last June. I got a signed copy of the former during the Windows 7 Release Party promo.

    Key here is that I have SP1 installed, which has been confirmed by different tools. However, per the sentence above, "So, if you’re attempting to repair Win7 SP1 with a pre-SP1 DVD, you need to remove SP1 from the target PC before proceeding. Fortunately, that’s easy, as Figure 1 shows."

    My problem is that "Windows 7 and Windows Server 2008 R2 Service Pack 1 (KB976932) (windows6.1-KB976932-X64) is nowhere to be found on my system! Thus theoretically, I can't uninstall it if I can't find it.

    I've searched the Web for workarounds & nothing has resolved this new issue yet. Ideas?!


    RD

    Friday, December 14, 2012 1:20 PM