XP may be end-of-life — but your business isn't. Dave's Computers has provided hands-on Windows XP repair in New Jersey since 2011. Manufacturers, medical offices, laboratories, and small businesses across NJ rely on us when chain shops won't touch XP anymore. Search any XP error code below — we cover the 50 most common ones, with a quick tip and a clear path to a real fix.
Nine focused service areas — the work we do every week on legacy XP machines for New Jersey customers.
Failing IDE and PATA drives, bad sectors, clicking drives. We clone aging XP drives to new hardware while preserving the OS installation, activation state, and all software.
From $75 diagnosticWe read XP minidump files to pinpoint the exact driver or hardware causing crashes — not guesswork. Common culprits include driver conflicts, failing RAM, and overheating CPUs.
From $75 diagnosticXP is a prime target because it no longer receives security patches. We remove infections, assess network exposure, and help implement isolation strategies for NJ businesses.
From $149Registry cleaning, startup management, driver updates, defragmentation, and RAM upgrades. We squeeze performance out of older hardware to extend its useful life.
Visit Us for Free EstimateNTLDR errors, corrupted boot sectors, missing HAL.dll, and system file failures. We recover XP without reinstalling — preserving your software configuration and data.
From $75 diagnosticCompatible RAM, IDE hard drive replacements, power supplies, and sourcing period-correct components for systems that must stay on XP-era hardware.
Visit Us for Free EstimateXP network stack repairs, TCP/IP resets, Wi-Fi driver issues, and printer sharing on aging LAN configurations. We still know the XP network stack cold.
From $75 diagnosticDevice Manager errors (Code 10, 39, 43), unknown devices, USB recognition failures. We track down the right XP-compatible driver — even for hardware the manufacturer abandoned.
From $75 diagnosticWhen an XP machine fails and won't boot, we recover your data — files, databases, proprietary application data — before any repair or migration work begins.
From $199If you've been searching "Windows XP repair near me" from anywhere in NJ, this is the most comprehensive XP error reference you'll find from an active repair shop. Try the quick tip first. If it doesn't work — or you'd rather not poke around in the Recovery Console — drop the machine off at our Somerville shop and we'll handle the rest. Diagnostic is $75, credited to your repair if you proceed.
NTLDR is the boot loader file Windows XP needs before the desktop loads. It goes missing when someone accidentally deletes it, when a CD or USB drive is set ahead of the hard drive in BIOS, or when the boot sector gets corrupted.
Quick tipEnter BIOS (F2 or Delete at power-on) and confirm the hard drive is the first boot device. Remove any CDs or USB drives. If that doesn't fix it, NTLDR itself is damaged.
Bring it to our Somerville shop — we restore NTLDR from XP installation media and rebuild the boot sector without reinstalling Windows.
HAL stands for Hardware Abstraction Layer — it's what lets XP talk to your specific hardware. This error appears after a failed Windows Update, a corrupted system partition, or a mismatched HAL install during repair attempts.
Quick tipBoot from your XP installation CD, choose Recovery Console, and run expand D:\i386\hal.dl_ C:\Windows\System32\hal.dll (substitute your CD drive letter).
If you don't have XP install media, drop it off — we have the original XP media on hand and can restore the correct HAL.dll for your hardware in under an hour.
BOOT.INI tells XP where the operating system lives on disk. When it's missing or points to the wrong partition, XP can't find itself. This often happens after disk cloning, dual-boot setups gone wrong, or partition changes.
Quick tipFrom Recovery Console: bootcfg /rebuild scans your drives and offers to rebuild BOOT.INI with the correct ARC paths.
If bootcfg /rebuild finds no Windows installations, the partition table is likely damaged — bring it in for our full boot recovery.
The Master Boot Record's partition table has been damaged or zeroed out. Causes include malware (boot sector viruses), failed cloning operations, or a sudden power loss during disk write.
Quick tipDo not run partition recovery tools blindly — wrong moves here destroy data permanently. Power the machine off and leave it off.
This is a shop-only repair. We image the drive first (so your data is safe), then rebuild the partition table from the backup or filesystem signatures.
BIOS can't find a bootable drive at all. Either the hard drive has failed completely, the boot order is wrong, or the drive's cable connection has come loose.
Quick tipOpen the case (if you're comfortable) and reseat both the SATA/IDE data cable and power connector. Listen — does the drive spin up at power-on?
If the drive doesn't spin or BIOS doesn't detect it, the drive itself has likely failed. We recover data from dead XP drives every week here in NJ — drop it off before trying anything else.
NTOSKRNL is the XP kernel itself. If XP can't load it, you'll see "Windows could not start because the following file is missing or corrupt: \windows\system32\ntoskrnl.exe." Usually caused by a corrupted BOOT.INI pointing to the wrong partition, not the file actually missing.
Quick tipFrom Recovery Console: bootcfg /rebuild often fixes this because BOOT.INI is the real culprit 80% of the time.
If it's a true file corruption issue, we restore NTOSKRNL.EXE from installation media — same-day turnaround at our Somerville shop.
This is the XP registry hive that stores hardware configuration. When it's corrupted, XP can't load any drivers and won't boot. Power failures during shutdown are the most common cause.
Quick tipFrom Recovery Console, you can copy the System Restore backup hive — but this involves typing six precise copy commands without typos, and one mistake locks the machine permanently.
This repair is high-risk to attempt yourself. Drop it off at our Somerville shop — we restore the hive from System Volume Information snapshots without risking your data.
XP gets to the startup screen, then reboots automatically before you can see the actual error. XP is set by default to auto-restart on system failure, hiding the real blue screen.
Quick tipPress F8 at boot, choose "Disable automatic restart on system failure." Now the next reboot will pause on the actual BSOD so you can read it.
Once we see the real error, we know exactly what to fix. Bring it in — we identify the underlying crash cause and repair without reinstalling Windows.
Severe XP startup slowdowns are usually a failing hard drive with bad sectors, a bloated startup program list, a fragmented and corrupted registry, or a hidden malware infection. Often it's two or three of those at once.
Quick tipRun msconfig and disable non-essential startup items. Then check Event Viewer (Administrative Tools) for repeated disk errors — those mean the drive is dying.
If the drive is failing, time matters. We clone failing XP drives at our NJ shop before they die completely — much cheaper than data recovery after the fact.
If you installed Windows 7, 10, or 11 alongside XP and now XP won't boot, the newer Windows replaced the boot loader. XP's NTLDR-style boot files were overwritten by the newer BCD boot manager.
Quick tipThis is fixable but requires editing the BCD store from the newer Windows. EasyBCD is a common tool for this — but be very careful with dual-boot manipulations.
Dual-boot recoveries are routine for us. Bring both drives if possible — we'll preserve both operating systems without reinstalling either.
BIOS hands off boot to the drive, but the drive can't read its own boot sector. Causes range from a loose SATA cable to a failing drive to a corrupted boot record after a botched cloning operation.
Quick tipPower off, reseat the drive cables, try again. If it still fails, boot from XP install CD → Recovery Console → run chkdsk /r on C:.
If CHKDSK reports unrecoverable bad sectors, your drive is dying. We image dying drives first, then either repair or replace — your data stays safe either way.
XP can't read the disk it boots from. The most common cause on XP is a SATA controller mode mismatch — BIOS got switched to AHCI mode after a CMOS battery reset, and XP has no AHCI driver. Other causes: a moved hard drive, file system corruption, or a failing drive.
Quick tipEnter BIOS and check SATA mode. If it's AHCI, switch it to IDE or Compatibility/Legacy mode. Save and reboot.
If BIOS doesn't have an IDE option (common on newer boards), we inject the AHCI driver into XP's registry. Drop it off in Somerville — this is a 1-hour fix.
A system thread crashed and XP couldn't recover. Usually points to a driver problem (the parameters identify which driver), incompatible hardware, or sometimes a BIOS issue.
Quick tipNote the filename listed in the blue screen (e.g., "atapi.sys"). That's the driver that crashed. Boot into Safe Mode (F8) and roll back that driver.
If you can't reach Safe Mode, we extract the minidump from outside XP and identify the exact driver. Bring it in.
XP tried to access a memory page that shouldn't be pageable — usually bad RAM, a driver bug, or corrupted system files. XP's memory management is more rigid than modern Windows.
Quick tipRun MemTest86 from a bootable USB for at least 4 hours. Any errors = bad RAM. Replace the stick that fails (test them one at a time).
If MemTest passes, the cause is a driver or system file. We extract the minidump and trace it to the exact driver — every time.
A driver tried to access memory at an inappropriate interrupt level — almost always a driver conflict, often after a Windows Update pushed an incompatible driver, or after installing third-party software with a kernel-mode component.
Quick tipIf this started recently, use System Restore (F8 → Safe Mode → System Restore) to roll back to a known-good point.
Persistent IRQL crashes need minidump analysis. We use WinDbg at our Somerville shop to identify the exact culprit driver and replace it with a compatible version.
Similar to error 15, but specifically a driver caused the IRQL violation (the parameter 4 in the BSOD names the driver). Network adapter drivers and antivirus filter drivers are the most common offenders on XP.
Quick tipIf the BSOD names a specific .sys file, search for that driver online to identify the device. Uninstall and reinstall that device's driver.
XP-compatible driver hunting is what we do. We maintain a library of legacy drivers for hardware manufacturers don't support anymore.
XP can't read its own boot volume — caused by file system corruption, bad sectors in the boot partition, or a damaged partition table.
Quick tipBoot from XP CD → Recovery Console → run chkdsk /r on C:. This often repairs the file system and lets XP boot normally.
If CHKDSK finds extensive bad sectors, the drive is dying. We clone first, then repair the OS on the clone — your data stays intact.
The NTFS file system driver hit an error it couldn't recover from. Usually means file system corruption, but can also indicate a failing drive or, less commonly, a buggy disk driver.
Quick tipBoot to Recovery Console and run chkdsk /r. Let it run to completion even if it takes hours — interrupting it makes things worse.
Repeated NTFS errors after CHKDSK = the drive is failing. Stop using it. We recover data from failing NTFS volumes routinely at our NJ shop.
The kernel detected an illegal instruction from a kernel-mode component. Common causes: incompatible drivers, faulty RAM, or system file corruption.
Quick tipIf this started after installing new hardware or software, undo the change. Otherwise, run MemTest86 and check the drive with manufacturer diagnostics.
When the BSOD doesn't name a clear driver, we use minidump analysis to find it. That's a $75 diagnostic that usually solves the case same-day.
A critical XP system process (like csrss.exe or winlogon.exe) terminated unexpectedly. Sometimes malware, sometimes hardware-induced corruption, sometimes a failing drive.
Quick tipBoot to Safe Mode and run a thorough virus scan. If you can't reach Safe Mode, scan the drive from another machine.
This BSOD often points to deeper issues. Bring it to our Somerville shop — we boot the drive in WinPE for offline scanning and recovery.
XP couldn't read kernel data from the paging file. Almost always indicates a failing hard drive — bad sectors specifically in the swap file area. RAM errors can also cause it.
Quick tipRun manufacturer drive diagnostics (Seagate SeaTools, WD Data Lifeguard, etc.) immediately. If errors appear, back up critical data before anything else.
This is a "back up now, repair later" situation. Drop the drive at our shop — we image it first, then run repairs on the clone.
A kernel component made an illegal pool request — usually a buggy driver, sometimes faulty hardware. The parameters identify what type of pool violation occurred.
Quick tipUpdate or roll back recently changed drivers. Run MemTest86 to rule out RAM. Check for overheating — XP machines from the 2000s often have failing CPU fans.
If the cause isn't obvious, our diagnostic dives into the minidump. We've seen this one hundreds of times on XP — usually it's a specific driver we can identify quickly.
A driver didn't complete a power state transition correctly — common when XP machines come out of standby or hibernate. Network and USB drivers are frequent culprits.
Quick tipDisable hibernation as a workaround: powercfg /hibernate off (or via Power Options control panel on older XP). Update network and chipset drivers.
Power-state BSODs on industrial XP machines can be hard to track down. We isolate the offending driver through systematic disable-and-test at our Somerville shop.
A kernel-mode program caused an exception XP couldn't catch. Causes are wide-ranging: memory issues, driver bugs, malware, even failing motherboard components.
Quick tipThis BSOD has too many possible causes for a single fix. Start with MemTest86 and a malware scan from a bootable rescue disk.
For 0x8E, our diagnostic process eliminates causes systematically. Bring it in — we'll identify whether it's memory, driver, or hardware.
The Windows Logon Process or Client/Server Runtime Subsystem (csrss.exe) terminated unexpectedly. Often the result of a corrupted system file or recent system change.
Quick tipBoot to Last Known Good Configuration (F8 → arrow up to that option). If it boots, the issue was a recent registry change.
If LKGC doesn't work, this needs Recovery Console work to restore system files. We do this regularly — drop it off and skip the hassle.
A generic XP driver error meaning the device failed to initialize. Could be a driver problem, a hardware problem, or a resource conflict. Most common on USB devices, sound cards, and network adapters.
Quick tipUninstall the device in Device Manager, then reboot — XP often re-detects and reinstalls drivers correctly. If that fails, find the manufacturer's XP-specific driver (not the latest, the XP-compatible one).
For specialty hardware (lab equipment, industrial controllers), XP drivers are often hard to find. We have a library of legacy drivers and can usually source the right one.
XP can't load the driver because it's damaged in the system32\drivers folder. Sometimes malware deletes drivers; sometimes a failed update corrupts them.
Quick tipUninstall the device and let XP reinstall it. If the device is critical (storage, network), boot to Safe Mode first so XP can repair without conflicting access.
If you can't reach Safe Mode or the device is essential to boot, bring it to us. We repair drivers offline from the XP installation media.
The hardware itself reported a failure to XP. Often this means the device is actually dying — USB ports, GPU chips, and network adapters give Code 43 when they fail.
Quick tipTry the device in a different XP machine if possible. If it fails there too, the device itself is bad.
For critical hardware (lab/medical devices, industrial controllers), we can often source replacement parts even for obsolete equipment. Call us — we serve NJ businesses with hard-to-replace gear.
This isn't a malfunction — it's a 32-bit XP limitation. The 4 GB address space is shared between RAM and device memory mapping (PCI, video card, BIOS), leaving roughly 3.25–3.5 GB usable for system RAM.
Quick tipTo use more than ~3.5 GB on XP, you'd need 64-bit XP — which has serious compatibility issues with older hardware and software, and is rarely worth the trade-off.
If you need more memory for an XP workload, often the right answer is virtualizing XP inside a modern host. We design these setups for NJ businesses that can't migrate off XP applications.
Original XP couldn't address drives larger than 137 GB due to a 28-bit LBA limitation. Service Pack 1 and later added 48-bit LBA support — but only if the BIOS supports it and the registry key is enabled.
Quick tipVerify Service Pack 3 is installed. Check that the registry value HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters\EnableBigLba is set to 1.
Older XP machines sometimes have BIOS issues that need flashing. We do that at the shop — never recommended to flash BIOS yourself on a working production system.
XP knows there's hardware present, but has no driver to make sense of it. Common on motherboards built for newer Windows where XP has no native support for chipset features.
Quick tipRight-click the unknown device → Properties → Details tab → "Hardware Ids." The VEN_ and DEV_ codes identify the manufacturer and device — Google those exact codes with "XP driver" appended.
If the device isn't critical, you can usually ignore it. If it's required (often the case with industrial gear), we can usually find or extract the XP driver. Bring the machine in.
XP installs a hardware-specific HAL and storage controller driver during Setup. When you replace the motherboard, those don't match the new chipset and XP throws STOP 0x7B on boot.
Quick tipThe fix is a repair install — boot from XP CD, choose "R" to repair an existing installation. This redetects hardware while preserving installed software.
Repair installs on legacy XP machines are tricky — older CDs often need updated mass storage drivers slipstreamed in. We do this every week at our Somerville shop for NJ industrial customers.
A Windows Update pushed an incompatible driver and broke your hardware. This still happens occasionally on machines with automatic updates enabled or that get manually patched.
Quick tipDevice Manager → right-click the device → Properties → Driver tab → "Roll Back Driver." If that's grayed out, use System Restore to a point before the update.
We can also hide problematic updates so they don't reinstall. If you're running critical XP hardware, bring it in — we'll lock down updates properly.
XP can't assign a drive letter to the USB device because of a conflict with mapped network drives or removed devices that left orphaned mount points in the registry.
Quick tipDisk Management (Computer Management → Storage) → right-click the unlettered drive → "Change Drive Letter and Paths" → assign a letter that's not in use.
If Disk Management can't even see the drive, the USB stack itself may be corrupted. We've fixed XP USB issues hundreds of times — drop it off if it's not cooperating.
XP's network stack is more fragile than modern Windows. Common causes: corrupted Winsock catalog, a statically assigned IP that doesn't match the new network, or a driver that went unresponsive when the adapter didn't detect a link during boot.
Quick tipOpen Command Prompt as administrator and run netsh winsock reset followed by netsh int ip reset. Reboot. This resets the IP stack to defaults.
If the reset doesn't help, the driver or hardware itself may be failing. Bring it to our NJ shop — we diagnose XP networking issues without a reimage.
XP's Remote Access Service depends on several other services running in the right order. If permissions on certain folders are wrong, or if a service is disabled, you get Error 711 when trying to dial up or connect to a VPN.
Quick tipOpen Services (services.msc) and verify Telephony, Remote Access Connection Manager, and Secure Socket Tunneling Protocol Service are all set to Manual or Automatic and started.
If it's permissions on the LogFiles folder (a common cause), the fix involves command-line permission resets. We do this routinely.
Classic SMB protocol mismatch. Modern Windows 10/11 defaults to SMB2 and SMB3 with SMB1 disabled by default — but XP only speaks SMB1. Without SMB1 on the modern side, XP can't see the shares.
Quick tipOn the Windows 10/11 machine, enable SMB1 client (Control Panel → Programs and Features → Turn Windows features on/off → "SMB 1.0/CIFS File Sharing Support"). Warning: SMB1 has security implications.
For NJ businesses with XP machines that must share files, we design isolated network segments — XP keeps working, but stays sandboxed from the broader network.
IE8 is the last IE version for XP, and it doesn't support TLS 1.2 or 1.3 — required by virtually all modern HTTPS sites. So websites return SSL errors or just won't load.
Quick tipInstall Mypal or a legacy Firefox build with TLS 1.2 backported for XP. These work for most modern websites that IE8 can't reach.
For XP machines that need controlled web access (industrial monitoring, vendor portals), we configure secure browser setups. Visit our shop for the full setup.
XP's dial-up or VPN connection can't complete — either the remote endpoint is unreachable, authentication failed, or your network adapter has lost its configuration.
Quick tipVerify the remote server address. For VPN, confirm the VPN client supports XP-era protocols (many modern VPNs have dropped PPTP and older L2TP).
If your NJ business has XP machines that need VPN access, we can design a bridge — modern VPN endpoints with XP-compatible tunnels behind them.
Two devices on your network were assigned the same IP. Common on networks with mixed static and DHCP addresses, or after restoring a backup that included old network settings.
Quick tipOpen Command Prompt: ipconfig /release then ipconfig /renew to grab a new DHCP address. If the XP machine needs a static IP, set it to one outside the DHCP range.
For XP machines controlling NJ industrial equipment, IP changes break operations. We configure DHCP reservations and document the network setup so this doesn't happen again.
XP's Remote Procedure Call service is essential for many system operations — printing, file sharing, group policy. When you get Error 1722, RPC is either stopped, blocked by a firewall rule, or the network path to the target machine is broken.
Quick tipOpen Services and verify Remote Procedure Call (RPC) is started and set to Automatic. Check Windows Firewall isn't blocking it.
Recurring RPC errors often point to deeper service or registry issues. Drop it off — our $75 diagnostic identifies whether it's services, network, or registry.
XP's registry grows with every software install but shrinks very slowly when things are uninstalled. Unlike modern Windows, XP's registry hive files have a maximum size limit — hitting it causes severe instability and slowdowns.
Quick tipDo not use random "registry cleaner" tools — most do more harm than good. Stick to verified tools like CCleaner and create a backup before any registry operation.
For seriously bloated XP registries, we use specialized tools to compact the hive safely. This often dramatically improves boot time and application launch speed.
When XP's paging file (pagefile.sys) is set to a system-managed variable size, it grows and shrinks over time, becoming fragmented. A fragmented page file means more disk seeks per memory access — visibly slower performance.
Quick tipRight-click My Computer → Properties → Advanced → Performance Settings → Advanced → Virtual Memory. Set the page file to a fixed size (typically 1.5–2x your physical RAM).
We optimize XP page file placement (often moving it to the fastest sector of the drive) as part of our tune-up service. Visit us for a free estimate.
XP's System Restore defaults are often too generous for older, smaller hard drives. By default, it can use up to 12% of each drive — on a 40 GB drive that's nearly 5 GB just for restore points.
Quick tipSystem Properties → System Restore tab → Settings → reduce disk space usage to 3–5% per drive. Then delete old restore points by running Disk Cleanup → More Options.
For machines low on disk space, we often migrate to a larger drive while preserving the XP installation. Clone job — same-day at our Somerville shop.
The Prefetch folder is actually beneficial — XP uses it to cache frequently-used application launch data to speed startup. However, it accumulates stale entries for programs that no longer exist.
Quick tipDon't blindly delete Prefetch. Use a tool like CCleaner's "Old Prefetch Data" option to clear only entries for uninstalled programs. Leave the rest alone.
As part of our XP tune-up, we evaluate Prefetch in context, clear stale entries, and configure the Prefetching mode appropriately for your usage pattern.
svchost.exe is a host process for many XP services. When it spikes to 99% CPU, one of the services running inside it is the culprit. Most common cause: Windows Update Service searching for updates from offline servers — endlessly retrying.
Quick tipDisable Automatic Updates (Control Panel → Automatic Updates → "Turn off Automatic Updates"). This prevents the endless update search that pegs the CPU on most XP machines today.
For machines that need controlled updating (rare but it happens), we configure XP to use WSUS or manual update sources. Drop it off and we'll set it up properly.
Modern malware on XP often uses rootkit techniques that hide from the OS itself — meaning antivirus running inside XP can't see what it's trying to clean. The malware reinstalls itself the moment the AV stops scanning.
Quick tipBoot from a Linux live USB or a Windows PE rescue disk and scan the XP drive from outside the OS. Tools like Kaspersky Rescue Disk or ESET SysRescue work well.
If you don't have rescue media or the malware persists after offline scanning, bring it to our Somerville shop. We boot the XP drive in a clean environment and remove the infection at its source.
"Generic Host Process for Win32 Services has encountered a problem and needs to close." Common XP error after a malware infection that damaged the LSP (Layered Service Provider) chain or after a botched antivirus removal.
Quick tipRun netsh winsock reset from an admin command prompt and reboot. This rebuilds the LSP chain and often fixes the Generic Host Process error.
If the error persists, deeper system file corruption is involved. We use SFC /scannow and registry repair to fix this without reinstalling Windows.
Old XP machines connected to the internet are prime targets for browser hijackers. Symptoms: searches redirect to unfamiliar engines, new toolbars appear, ads inject into every page.
Quick tipCheck the hosts file (C:\Windows\System32\drivers\etc\hosts) for suspicious entries. Reset browser settings. Run AdwCleaner from a clean source.
XP machines should rarely be on the open internet anymore. We help NJ businesses isolate XP systems behind firewalls so they keep working without getting reinfected.
XP gets no security patches. Any internet-connected XP machine is vulnerable to ransomware that exploits unpatched flaws. Once encrypted, files are usually unrecoverable without the key.
Quick tipDisconnect the machine from the network immediately. Do not pay the ransom — there's no guarantee of recovery, and it funds more attacks. Identify the ransomware strain (ID Ransomware website helps).
We handle ransomware cases for NJ businesses. Sometimes shadow copies or backups can rescue you; sometimes we extract unencrypted fragments. Either way, we'll be honest about what's recoverable — bring it in.
If your Windows XP machine is throwing an error we haven't covered — or you've tried the quick tips and you're still stuck — give us a call or bring it by. We've worked on hundreds of XP systems across NJ since 2011, and we've probably seen yours before.
📞 Call (908) 428-9558Chain stores stopped training technicians on Windows XP over a decade ago. We never stopped. Dave's has been the go-to XP shop in NJ since 2011.
Continuously repairing Windows XP through end-of-support and beyond. We've serviced XP machines for 14+ years — long after most shops gave up.
From CNC factory floor workstations to dental X-ray controllers to embroidery machine PCs — we've kept legacy XP gear running for NJ businesses.
Transparent, upfront pricing. We tell you what's wrong before you spend a dollar on repairs. The $75 is credited toward your repair if you proceed.
Featured in Angie's List Magazine for honest, quality repair work. Received the Mayor of Hillsborough Certificate of Recognition for community service.
Not a franchise, not a chain. When you bring in your XP machine, you deal directly with the owner who actually understands the OS — every time.
Nothing gets shipped to a warehouse. XP data — often holding decades of business records — never leaves our Somerville location.
Drop-off repair shop located at 75 N Bridge St, Somerville, NJ 08876. Customers drive to us from across New Jersey for Windows XP service they can't find anywhere else. Street parking on N Bridge St plus a municipal lot nearby. Walk-ins welcome — no appointment needed.
From Bridgewater (~10 min): Head east on US-22, take the Somerville/NJ-28 exit, turn left onto W Main St, right onto N Bridge St. We're at 75 N Bridge St on your left.
From Bound Brook (~10 min): Head west on NJ-28 through Raritan, turn right onto N Bridge St at the Somerville circle.
From Flemington (~25 min): Head north on US-202 through Raritan, turn left onto N Bridge St at the Somerville traffic circle.
From Edison (~30 min): Take NJ-27 to NJ-28 W toward Bound Brook, continue on NJ-28 W into Somerville, turn right onto N Bridge St.
One location, easy to find, easy to park. Bring your Windows XP system in and we'll diagnose it the same day in most cases.
75 N Bridge St, Somerville NJ 08876
Behind Bank of America
Mon–Fri 10am–5pm
Saturday 9am–2pm
No appointment needed — walk in anytime
Drop-off service for all of New Jersey. Most customers come from Somerset, Hunterdon, Middlesex, and Mercer counties.
Drop your XP machine off at our Somerville shop and mention this coupon at the counter.
Bring this page in or show it on your phone when you drop off your XP machine. Mention "XPNJ25" at the counter.
We're a drop-off shop in Somerville, NJ. Customers regularly drive in from these Central New Jersey cities for XP service they can't find locally.
One location, drop-off only. Dave's Computers has one shop at 75 N Bridge St, Somerville NJ. We do not offer on-site or in-home service for Windows XP systems. Customers from as far as Flemington, Princeton, and Phillipsburg regularly make the trip for XP service they can't find elsewhere in NJ.
Drop it off at our Somerville shop. No shipping. No strangers. No surprises. Diagnostics are $75 — credited to your repair if you proceed.
📞 (908) 428-9558
We'll be back
Tues, May 27
10 AM – 5 PM
Need help or an estimate?
Text us at 908-428-9558