Search

Malfunctioning New PC

0 views

Understanding the Problem and Initial Observations

When a freshly assembled computer suddenly turns its screen black while you are copying files, it can feel like a mystery. The hardware in question is a mid‑late‑2000s build: an Intel Pentium 4 3.06 GHz processor, 1 GB of RAM, a 120 GB hard drive, an ATI Radeon 9700 Pro graphics card, and a standard LCD monitor. The operating system is Windows XP, which is still running in the background when the screen vanishes. You’ve already ruled out the most obvious culprit – the sleep or power‑save settings – because they are disabled. You’ve also considered that the monitor might be defective, but you’re not yet ready to replace it. The question remains: what other factors could trigger a black screen only during a file transfer?

File transfer is a resource‑intensive operation. The CPU must handle disk I/O, the memory controller manages data buffers, and the graphics subsystem must refresh the display continuously. When one of these subsystems is strained or misconfigured, the system may lose its ability to keep the screen alive. A few scenarios can produce exactly the symptom you’re seeing:

  • Video driver instability or corruption – Drivers translate Windows calls into hardware commands. If the driver for the Radeon 9700 Pro is damaged or incompatible with the version of Windows XP you’re running, the GPU may reset during heavy load, causing a blank screen.
  • Insufficient power delivery – The Radeon 9700 Pro draws significant current when the GPU is busy. A marginal power supply or a faulty connector can lead to a drop in voltage that forces the graphics card to power‑down temporarily. The monitor then shows black even though the CPU continues to operate.
  • Overheating – The Pentium 4 and the Radeon 9700 Pro both generate heat. If the case fans or heatsinks are not adequate, the components may throttle or shut down a portion of the system to protect themselves. Overheating can manifest as a sudden black screen.
  • Memory problems – When the file transfer process requires more memory than is available, Windows may start paging. Faulty RAM can corrupt the data stream or the driver stack, which may lead to a display crash.
  • Hard‑disk errors – A failing drive can stall during I/O operations. If the OS or the driver tries to recover, it may cause the GPU to lose its context, resulting in a blackout.
  • Cable or connector issues – A loose or defective VGA/DVI cable can lose the signal during high‑bandwidth activity.

    Because the system is still running, you can often see taskbar icons or a blinking cursor. That indicates that the OS has not crashed entirely; only the video subsystem has lost sync with the monitor. Understanding this separation helps focus the troubleshooting: keep the CPU and OS happy, but ensure the GPU, power, and cooling paths are stable.

    Before you start replacing parts, gather a few details that will guide the next phase:

    1. Note the exact moment the screen goes black – is it after a specific file size, after a few minutes, or during a particular transfer?
    2. Check the system event logs for any warnings or errors around the same time. Windows XP stores this information in the Event Viewer under Application and System logs.
    3. Record the current GPU and driver version. Use the dxdiag tool or the ATI Catalyst Control Center to view driver details.
    4. Make sure the monitor’s power LED stays on; if the LED shuts off, it may be a monitor fault rather than a GPU problem.

      Armed with these observations, you can now move on to a systematic diagnostic process that will uncover whether the problem lies in the monitor, the graphics card, the power supply, the memory, or the OS itself.

      Diagnostic Checklist and Resolution Steps

      Resolving a black screen that appears only during file transfer involves a blend of software checks and hardware tests. The goal is to isolate the component that fails under load. Below is a step‑by‑step guide that covers the most common culprits, using freely available tools and straightforward techniques. You do not need advanced soldering skills or expensive diagnostics; most problems can be ruled out with simple swaps and updates.

      1. Verify the Display Cable and Monitor Connection

      Start at the simplest point: the cable that carries the video signal from the GPU to the monitor. If you are using a VGA cable, examine it for bent pins or visible damage. If possible, replace the cable with a new one or a known‑good cable from another system. Try a different connector type – for example, swap a VGA cable for a DVI or HDMI cable if your monitor supports it and the GPU has the necessary port. After each swap, perform a file transfer to see if the problem persists. A persistent black screen after multiple cable changes points away from the cable itself.

      2. Test with a Second Monitor or TV

      Even if you have a spare monitor, connecting a second display can quickly indicate whether the issue is specific to the original monitor. Connect the second monitor to the same GPU and power it on. Run a file transfer on the primary screen. If the second monitor remains stable while the first one goes black, the original monitor is likely at fault. If both monitors exhibit the same behavior, the problem resides in the GPU or the system as a whole.

      3. Inspect the Power Supply Unit (PSU)

      Under heavy GPU load, the power draw spikes. Check the PSU’s specifications: a 300 W supply may suffice for a Pentium 4 and a single ATI Radeon 9700 Pro, but any marginal PSU can under‑deliver. Verify the connectors: the card should have a 6‑pin PCIe power plug. If the cable is loose or the plug is faulty, the GPU may lose power and reset. Swap the power cable or the PSU entirely if you have a spare or can borrow one. After changing the PSU, perform a file transfer to confirm whether the black screen still occurs.

      4. Update or Reinstall the Graphics Driver

      Drivers are a common source of display instability. Visit the AMD support page (

Suggest a Correction

Found an error or have a suggestion? Let us know and we'll review it.

Share this article

Comments (0)

Please sign in to leave a comment.

No comments yet. Be the first to comment!

Related Articles