• Creator
  • #4229502

    Windows closes down as I access network.

    by oneteam2nepal ·


    Whenever I tried to move the network files from one of the folders to another folder, the computer crashes and shows the blue screen.

You are posting a reply to: Windows closes down as I access network.

The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our Community FAQs for details. All submitted content is subject to our Terms of Use.

All Answers

  • Author
    • #4229503
      Avatar photo

      A very old problem with Windows File Manager.

      by rproffitt ·

      In reply to Windows closes down as I access network.

      I demonstrated this issue back in 1995 to Microsoft engineers and their reply to the issue was “don’t do that.”

      Workarounds are:
      1. Try another PC.
      2. Use the command line.
      3. Use other file managers.
      4. Use Linux.

      Fixing the PC in question is possible but unlikely as it involves tracking down which file causes WFE and Windows to fault. It took me a few days back then to track it down, isolate it and get ready for my trip to Redmond.

    • #4229515
      Avatar photo

      Re: access

      by kees_b ·

      In reply to Windows closes down as I access network.

      Accessing the network isn’t the same as moving files on a share to another folder on the same share (that is what I understand you’re doing).

      Does it happen also if you copy such a file first to your local PC, and than back to the new folder on the same or another share?

    • #4230344

      Reply To: Windows closes down as I access network.

      by pollygler ·

      In reply to Windows closes down as I access network.

      To troubleshoot, you could try updating network drivers or checking for any software conflicts.

    • #4230567

      Windows closes down as I access network.

      by thealightm ·

      In reply to Windows closes down as I access network.

      Experiencing a blue screen (BSOD) when moving network files could be due to various reasons, including hardware issues, driver conflicts, or software problems. Here are some troubleshooting steps you can follow to identify and fix the issue:

      1. Update Drivers:
      Ensure that your network adapter drivers are up-to-date. Outdated or incompatible drivers can cause stability issues.
      Visit the manufacturer’s website for your network adapter and download the latest drivers.

      2. Check for Windows Updates:
      Make sure your operating system is up-to-date with the latest Windows updates. Sometimes, Microsoft releases patches to fix bugs and improve system stability.

      3. Run System File Checker (SFC) and DISM:
      Open Command Prompt as an administrator.
      Run the following commands:
      bash Copy code [sfc /scannow]

      mathematica Copy code [DISM /Online /Cleanup-Image /RestoreHealth]
      Restart your computer after the scan and repair process completes.

      4. Check Disk for Errors:
      Open Command Prompt as an administrator.
      Run the following command to check and repair disk errors:

      bash Copy code [chkdsk C: /f]

      Replace C: with the appropriate drive letter if your system drive is different.
      Restart your computer and let the disk check complete.

      5. Disable Antivirus/Firewall:
      Sometimes, third-party antivirus or firewall software can interfere with network operations. Try disabling your antivirus/firewall temporarily to see if it resolves the issue.

      6. Check Network Settings:
      Ensure that your network settings are configured correctly. Incorrect network configurations can lead to connectivity issues and system instability.
      Resetting your network settings to default might help resolve the issue.

      7. Hardware Check:
      Check your network hardware (router, switches, cables) for any physical damage or issues.
      Test your network connection with another device to rule out hardware problems.

      8. Check Event Viewer for Errors:
      Open Event Viewer by searching for it in the Windows search bar.
      Look for any critical or error events under Windows Logs > System that occurred around the time of the BSOD.
      Note down any relevant error messages or codes for further troubleshooting.

      9. Perform a Clean Boot:
      Perform a clean boot to start Windows with minimal drivers and startup programs. This can help identify if a third-party application or service is causing the issue.
      Instructions on how to perform a clean boot can be found on Microsoft’s official website.

Viewing 3 reply threads