Windows 7 crash on copying files from D:\ to C:\

Page 1 of 2 12 LastLast

  1. Posts : 33
    Windows 7
       #1

    Windows 7 crash on copying files from D:\ to C:\


    I'm running fresh install of Windows 7 build 7068. When I try to copy ANY file from anywhere in D:\ to anywhere in C:\ I am getting "Windows Explorer has stopped working" error - it drives me mad. I've uninstalled all software, stopped all running programs - nothing helped. This is the crash report from Event Viewer:
    Code:
    Faulting application name: Explorer.EXE, version: 6.1.7068.0, time stamp: 0x49c590ff
    Faulting module name: SHELL32.dll, version: 6.1.7068.0, time stamp: 0x49c5ab1a
    Exception code: 0xc0000005
    Fault offset: 0x00000000002d5661
    Faulting process id: 0x784
    Faulting application start time: 0x01c9b32375d0f418
    Faulting application path: C:\Windows\Explorer.EXE
    Faulting module path: C:\Windows\system32\SHELL32.dll
    Report Id: c003dc89-1f16-11de-a237-001a4d55b9c7
    Can anyone help?
      My Computer


  2. Posts : 4,364
    Windows 11 21H2 Current build
       #2

    It would help to know what D: is - and that can be accomplished if you clcik the link under your username to the left, where it says System Specs - and edit your system specs to fill in your hardware....
      My Computer


  3. Posts : 33
    Windows 7
    Thread Starter
       #3

    I've updated them - D:\ is the second partition of my local hard drive. Both partitions are formatted in NTFS, if it matters.
      My Computer


  4. Posts : 4,364
    Windows 11 21H2 Current build
       #4

    The HD *type* matters big time.

    There was a recent flap about Seagate 7200.11 HDs having issues with firmware and the drives all of a sudden being unreadable.

    See Seagate Knowledge Base to get your latest Firmware, and make *sure* that you have a good working backup of your C ***on a different HD**** and that you use the detect tool to verify your Drive needs the firmware upgrade or not.
      My Computer


  5. Posts : 33
    Windows 7
    Thread Starter
       #5

    Actually my hard drive is ST3320620AS, 7200.10 version. Also I've reinstalled my windows 2 times, ran on safe mode and everything else. I've also deleted my previous partition, assigned new one for the OS, still the same. I think that I've figured out what's wrong - I am not getting "Destination Folder Access Denied" error message when I am copying files to my system drive, that's why Windows Explorer is crashing - it probably can't show the dialog because shell32.dll is corrupted for some reason.
      My Computer


  6. Posts : 4,364
    Windows 11 21H2 Current build
       #6

    That would explain why the BCCheck pointed to the fault in explorer.exe but listed shell32.dll as the pointer....

    Sorry about the HD confusion - I apparently didn't copy the *full* model number, so it found the 7200.11 and since I have a pair of the 500 GB 'Cudas, I assumed you were running into the same issue.

    For the Shell32.dll, you *should* be able to fix that using SFC....

    See SFC /SCANNOW Command - System File Checker for more details.
    Last edited by johngalt; 15 Apr 2009 at 00:34. Reason: spell checked - finally!
      My Computer


  7. Posts : 33
    Windows 7
    Thread Starter
       #7

    I'm getting twice this error message after I ran SFC:
    Code:
    2009-04-03 02:50:19, Info                  CSI    000002d6 [SR] Cannot repair member file [l:22{11}]"shell32.dll" of Microsoft-Windows-shell32, Version = 6.1.7068.0, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2009-04-03 02:50:21, Info                  CSI    000002d8 [SR] Cannot repair member file [l:22{11}]"shell32.dll" of Microsoft-Windows-shell32, Version = 6.1.7068.0, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2009-04-03 02:50:21, Info                  CSI    000002d9 [SR] This component was referenced by [l:194{97}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7068.0.WindowsFoundationDelivery"
    2009-04-03 02:50:22, Info                  CSI    000002dc [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"shell32.dll"; source file in store is also corrupted
    The rest is fine, that's the only corrupted file. Maybe if I could somehow replace my shell32 with a working non-corrupt one (guess the one on my DVD is corrupted) the problem will be fixed. My win is Ultimate x64 if it matters :)
      My Computer


  8. Posts : 4,364
    Windows 11 21H2 Current build
       #8

    Hmmm - somehow your shell32.dll is corrupted in both the currently used location *and* the backup store. weird.

    I'd get to running a couple of Virus scans on your machine before anything else.

    Also, did you use any sort of crack / unlocker / etc on your machine?
      My Computer


  9. Posts : 33
    Windows 7
    Thread Starter
       #9

    No. I am doing fresh install from my DVD, no cracks, unlockers and stuff - windows activates itself. My machine shouldn't be infected by a virus - I had 24/7 resident Kaspersky AV. If you want me to I will run online virus scan - it might show something but I seriously doubt it.
    I am using -Link Removed by dmex- release.
    Last edited by dmex; 05 Apr 2009 at 01:13.
      My Computer


  10. Posts : 4,364
    Windows 11 21H2 Current build
       #10

    I'll be at home in about an hour, and I am using 7068 x86-64 on my desktop as well. PM me.
      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 11:19.
Find Us