1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Windows Explorer Crashes

Discussion in 'Windows XP' started by kenlanderson, 2004/07/06.

Thread Status:
Not open for further replies.
  1. 2004/07/06
    kenlanderson

    kenlanderson Inactive Thread Starter

    Joined:
    2003/12/16
    Messages:
    60
    Likes Received:
    0
    Hi,
    When I am using Windows Explorer in My Documents/My Pictures/my folders to view pictures, delete files, invoke movie editor, it will crash on me. I also have My Video folder under My Documents with videos. This may happen after every 4-8 operations. My Pictures folder is about 2.5 GB, My Videos close to 4 GB and My Documents folder (which includes My Pictures & My Videos folder) is about 7.5 GB. I don't remember when this started happening but it has happened more frequently in the past months.

    I have searched BBS, MS knowledge base and used Google but do not find any help. I have XP SP1, with all critical updates. NFTS file syste, make efforts to keep system maintained, e.g., Norton Sys Manager, Adware, SpyBot, defrag, Disk Cleaner, empty Recycle Bin, run disk error checking

    When using Windows Explorer on smaller files, Word Documents, I do not seem to have this problem very often. Is this Explorer problem related to larger files, e.g., up to 600-700 KB and occasionally over 1 GB for videos? Or too many folders/files or something else that I need to check into?

    I have just started to place my digital files in a folder by themselves to see if that helps my problem - too early to tell yet.

    Thanks for you help,
    Ken
    :)
     
    Last edited: 2004/07/06
  2. 2004/07/06
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,890
    Likes Received:
    387
    Is an error message posted on your screen when WE crashes? If so, please post the details.

    Immediately after a WE crash right click on My Computer > Manage > Event Viewer > System and see if there is an error message, flagged with a red spot. Double click on the message to open, click on the icon below the up/down arrows to copy to clipboard and paste in a reply here. Check Applications too.
     

  3. to hide this advert.

  4. 2004/07/06
    kenlanderson

    kenlanderson Inactive Thread Starter

    Joined:
    2003/12/16
    Messages:
    60
    Likes Received:
    0
    Thanks for your quick response.
    I got error msg with WE at top of msg box and says that WE has encountered a problem and needs to close. We are sorry for the inconvenience...
    Then I have a chance to send the problem to MS - I don't any more but I have sent it.

    I had done 2-3 rename functions in WE to try to cause the problem and then on a rename of a 550KB file, I got the error msg.

    On Manage, Event View, System, there is no error msg.

    On the Application, the following error msg:
    Event Type: Error
    Event Source: Application Error
    Event Category: None
    Event ID: 1000
    Date: 7/6/2004
    Time: 4:08:44 PM
    User: N/A
    Computer: KEN-DELL
    Description:
    Faulting application explorer.exe, version 6.0.2800.1106, faulting module nvcpl.dll, version 6.14.10.5672, fault address 0x000270d8.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 41 70 70 6c 69 63 61 74 Applicat
    0008: 69 6f 6e 20 46 61 69 6c ion Fail
    0010: 75 72 65 20 20 65 78 70 ure exp
    0018: 6c 6f 72 65 72 2e 65 78 lorer.ex
    0020: 65 20 36 2e 30 2e 32 38 e 6.0.28
    0028: 30 30 2e 31 31 30 36 20 00.1106
    0030: 69 6e 20 6e 76 63 70 6c in nvcpl
    0038: 2e 64 6c 6c 20 36 2e 31 .dll 6.1
    0040: 34 2e 31 30 2e 35 36 37 4.10.567
    0048: 32 20 61 74 20 6f 66 66 2 at off
    0050: 73 65 74 20 30 30 30 32 set 0002
    0058: 37 30 64 38 0d 0a 70d8..

    Since the file being sent to MS makes this msg too long I will post in another reply.
     
  5. 2004/07/06
    kenlanderson

    kenlanderson Inactive Thread Starter

    Joined:
    2003/12/16
    Messages:
    60
    Likes Received:
    0
    Continued from my previous post.

    Following is the content of the file being sent to MS (accompat.txt)
    <?xml version= "1.0" encoding= "UTF-16 "?>
    <DATABASE>
    <EXE NAME= "SYSTEM INFO" FILTER= "GRABMI_FILTER_SYSTEM ">
    <MATCHING_FILE NAME= "ADVAPI32.DLL" SIZE= "558080" CHECKSUM= "0x7B6E5DDA" BIN_FILE_VERSION= "5.1.2600.1106" BIN_PRODUCT_VERSION= "5.1.2600.1106" PRODUCT_VERSION= "5.1.2600.1106" FILE_DESCRIPTION= "Advanced Windows 32 Base API" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "5.1.2600.1106 (xpsp1.020828-1920)" ORIGINAL_FILENAME= "advapi32.dll" INTERNAL_NAME= "advapi32.dll" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x9315E" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "5.1.2600.1106" UPTO_BIN_PRODUCT_VERSION= "5.1.2600.1106" LINK_DATE= "08/29/2002 10:40:40" UPTO_LINK_DATE= "08/29/2002 10:40:40" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "gdi32.dll" SIZE= "257536" CHECKSUM= "0xB0D6141C" BIN_FILE_VERSION= "5.1.2600.1346" BIN_PRODUCT_VERSION= "5.1.2600.1346" PRODUCT_VERSION= "5.1.2600.1346" FILE_DESCRIPTION= "GDI Client DLL" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "5.1.2600.1346 (xpsp2.040109-1800)" ORIGINAL_FILENAME= "gdi32" INTERNAL_NAME= "gdi32" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x4CFC1" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "5.1.2600.1346" UPTO_BIN_PRODUCT_VERSION= "5.1.2600.1346" LINK_DATE= "03/30/2004 01:48:36" UPTO_LINK_DATE= "03/30/2004 01:48:36" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "KERNEL32.DLL" SIZE= "930304" CHECKSUM= "0xCBCCF8A9" BIN_FILE_VERSION= "5.1.2600.1106" BIN_PRODUCT_VERSION= "5.1.2600.1106" PRODUCT_VERSION= "5.1.2600.1106" FILE_DESCRIPTION= "Windows NT BASE API Client DLL" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "5.1.2600.1106 (xpsp1.020828-1920)" ORIGINAL_FILENAME= "kernel32" INTERNAL_NAME= "kernel32" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0xE7ED3" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "5.1.2600.1106" UPTO_BIN_PRODUCT_VERSION= "5.1.2600.1106" LINK_DATE= "08/29/2002 10:40:40" UPTO_LINK_DATE= "08/29/2002 10:40:40" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "ntdll.dll" SIZE= "654336" CHECKSUM= "0xC568C00F" BIN_FILE_VERSION= "5.1.2600.1217" BIN_PRODUCT_VERSION= "5.1.2600.1217" PRODUCT_VERSION= "5.1.2600.1217" FILE_DESCRIPTION= "NT Layer DLL" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "5.1.2600.1217 (xpsp2.030429-2131)" ORIGINAL_FILENAME= "ntdll.dll" INTERNAL_NAME= "ntdll.dll" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0xA5841" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "5.1.2600.1217" UPTO_BIN_PRODUCT_VERSION= "5.1.2600.1217" LINK_DATE= "05/01/2003 23:56:10" UPTO_LINK_DATE= "05/01/2003 23:56:10" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "ole32.dll" SIZE= "1183744" CHECKSUM= "0x7BA6A54E" BIN_FILE_VERSION= "5.1.2600.1362" BIN_PRODUCT_VERSION= "5.1.2600.1362" PRODUCT_VERSION= "5.1.2600.1362" FILE_DESCRIPTION= "Microsoft OLE for Windows" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "5.1.2600.1362 (xpsp2.040109-1800)" ORIGINAL_FILENAME= "OLE32.DLL" INTERNAL_NAME= "OLE32.DLL" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x12ED04" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "5.1.2600.1362" UPTO_BIN_PRODUCT_VERSION= "5.1.2600.1362" LINK_DATE= "03/06/2004 02:16:11" UPTO_LINK_DATE= "03/06/2004 02:16:11" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "OLEAUT32.DLL" SIZE= "569344" CHECKSUM= "0x276CFFB1" BIN_FILE_VERSION= "3.50.5016.0" BIN_PRODUCT_VERSION= "3.50.5016.0" PRODUCT_VERSION= "3.50.5016.0" FILE_DESCRIPTION= "Microsoft OLE 3.50 for Windows NT(TM) and Windows 95(TM) Operating Systems" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft OLE 3.50 for Windows NT(TM) and Windows 95(TM) Operating Systems" FILE_VERSION= "3.50.5016.0" INTERNAL_NAME= "OLEAUT32.DLL" LEGAL_COPYRIGHT= "Copyright © Microsoft Corp. 1993-1999." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x999AF" LINKER_VERSION= "0x0" UPTO_BIN_FILE_VERSION= "3.50.5016.0" UPTO_BIN_PRODUCT_VERSION= "3.50.5016.0" LINK_DATE= "08/29/2002 10:40:34" UPTO_LINK_DATE= "08/29/2002 10:40:34" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "shell32.dll" SIZE= "8240640" CHECKSUM= "0x1D64017A" BIN_FILE_VERSION= "6.0.2800.1233" BIN_PRODUCT_VERSION= "6.0.2800.1233" PRODUCT_VERSION= "6.00.2800.1233" FILE_DESCRIPTION= "Windows Shell Common Dll" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "6.00.2800.1233 (xpsp2.030604-1804)" ORIGINAL_FILENAME= "SHELL32.DLL" INTERNAL_NAME= "SHELL32" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x7E4A55" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "6.0.2800.1233" UPTO_BIN_PRODUCT_VERSION= "6.0.2800.1233" LINK_DATE= "06/11/2003 20:43:47" UPTO_LINK_DATE= "06/11/2003 20:43:47" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "user32.dll" SIZE= "560128" CHECKSUM= "0xA1CBF84" BIN_FILE_VERSION= "5.1.2600.1255" BIN_PRODUCT_VERSION= "5.1.2600.1255" PRODUCT_VERSION= "5.1.2600.1255" FILE_DESCRIPTION= "Windows XP USER API Client DLL" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "5.1.2600.1255 (xpsp2.030804-1745)" ORIGINAL_FILENAME= "user32" INTERNAL_NAME= "user32" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x8AFFF" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "5.1.2600.1255" UPTO_BIN_PRODUCT_VERSION= "5.1.2600.1255" LINK_DATE= "09/25/2003 16:49:01" UPTO_LINK_DATE= "09/25/2003 16:49:01" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "WININET.DLL" SIZE= "588288" CHECKSUM= "0x8E2417C3" BIN_FILE_VERSION= "6.0.2800.1405" BIN_PRODUCT_VERSION= "6.0.2800.1405" PRODUCT_VERSION= "6.00.2800.1405" FILE_DESCRIPTION= "Internet Extensions for Win32" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "6.00.2800.1405" ORIGINAL_FILENAME= "wininet.dll" INTERNAL_NAME= "wininet.dll" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x974A2" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "6.0.2800.1405" UPTO_BIN_PRODUCT_VERSION= "6.0.2800.1405" LINK_DATE= "02/07/2004 02:05:03" UPTO_LINK_DATE= "02/07/2004 02:05:03" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "WINSOCK.DLL" SIZE= "2864" CHECKSUM= "0x73AE8088" BIN_FILE_VERSION= "3.10.0.103" BIN_PRODUCT_VERSION= "3.10.0.103" PRODUCT_VERSION= "3.10" FILE_DESCRIPTION= "Windows Socket 16-Bit DLL" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows(TM) Operating System" FILE_VERSION= "3.10" ORIGINAL_FILENAME= "WINSOCK.DLL" INTERNAL_NAME= "WINSOCK" LEGAL_COPYRIGHT= "Copyright © Microsoft Corp. 1981-1996" VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x10001" VERFILETYPE= "0x2" MODULE_TYPE= "WIN16" S16BIT_DESCRIPTION= "BSD Socket API for Windows" S16BIT_MODULE_NAME= "WINSOCK" UPTO_BIN_FILE_VERSION= "3.10.0.103" UPTO_BIN_PRODUCT_VERSION= "3.10.0.103" VER_LANGUAGE= "English (United States) [0x409]" />
    </EXE>
    <EXE NAME= "nvcpl.dll" FILTER= "GRABMI_FILTER_THISFILEONLY ">
    <MATCHING_FILE NAME= "nvcpl.dll" SIZE= "3309568" CHECKSUM= "0xE3E285C9" BIN_FILE_VERSION= "6.14.10.5672" BIN_PRODUCT_VERSION= "6.14.10.5672" PRODUCT_VERSION= "6.14.10.5672" FILE_DESCRIPTION= "NVIDIA Display Properties Extension" COMPANY_NAME= "NVIDIA Corporation" PRODUCT_NAME= "NVIDIA Compatible Windows 2000 Display driver, Version 56.72 " FILE_VERSION= "6.14.10.5672" ORIGINAL_FILENAME= "NVCPL.DLL" INTERNAL_NAME= "NvCpl" LEGAL_COPYRIGHT= "(C) NVIDIA Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x4" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x0" LINKER_VERSION= "0x0" UPTO_BIN_FILE_VERSION= "6.14.10.5672" UPTO_BIN_PRODUCT_VERSION= "6.14.10.5672" LINK_DATE= "03/24/2004 19:15:59" UPTO_LINK_DATE= "03/24/2004 19:15:59" VER_LANGUAGE= "English (United States) [0x409]" />
    </EXE>
    </DATABASE>
     
  6. 2004/07/06
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,890
    Likes Received:
    387
    I suggest you run System File Checker ....

    Start > Run > type in sfc /scannow - note the space and have your XP install CD handy.

    SFC will run and exit without any message - to see what, if anything was replaced, look in Event Viewer - System.
     
  7. 2004/07/06
    JoeHobart

    JoeHobart Inactive Alumni

    Joined:
    2004/05/19
    Messages:
    919
    Likes Received:
    1
    You are crashing inside of the nvidia display control panel applet, ala nvcpl.dll

    I'd update your NVIDIA software from http://www.nvidia.com/content/drivers/drivers.asp

    If you are running the latest already, you should consider going back a rev, or switching to the WindowsUpdate version.
     
  8. 2004/07/07
    kenlanderson

    kenlanderson Inactive Thread Starter

    Joined:
    2003/12/16
    Messages:
    60
    Likes Received:
    0
    Thank you for your help.
    First Nvida. I had a recent driver (3/24/04 v. 5.6.7.2) so I took your suggestion and got the Windows driver (10/6/2004, v. 5.2.1.6). And that seems to work - I have made more Explorer functions than I have before and it has not crashed! I will keep this open a few more days.

    As to what happened when I did the sfc /scannow. I ran it right after a WE crash. I found over 30 information messages but there was a message at the end that it had completed successfully. The messages seemed to be in pairs.

    Following is the first one:
    Event Type: Information
    Event Source: Windows File Protection
    Event Category: None
    Event ID: 64020
    Date: 7/6/2004
    Time: 9:25:07 PM
    User: N/A
    Computer: KEN-DELL
    Description:
    Windows File Protection scan found that the system file c:\windows\system32\oembios.bin has a bad signature. This file was restored to the original version to maintain system stability. The file version of the system file is 0.0.0.1.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Immediately followed by 2nd one:
    Event Type: Information
    Event Source: Windows File Protection
    Event Category: None
    Event ID: 64004
    Date: 7/6/2004
    Time: 9:25:11 PM
    User: N/A
    Computer: KEN-DELL
    Description:
    The protected system file c:\windows\system32\oembios.bin could not be restored to its original, valid version. The file version of the bad file is 0.0.0.1 The specific error code is 0x800b0100 [No signature was present in the subject.
    ].

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    There was more than one pair of informational message for this file and then it switched to another file. However, there was this successful end of job also.

    Should I be concerned about this?

    Thanks so much for you most helpful advice. I will be making another donation because I don't know where else I could get such help.

    Thanks much,
    Ken :) :)
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.