When This Error Pops Up
You're watching a video on Chrome or Edge, maybe a training video or a live stream. Then it freezes. You see a black screen or a spinner. The error says NS_S_REBUFFERING (0X000D0BC8). It means the player ran out of data and had to reload from the server. I've seen this happen with Netflix, YouTube, and even local network streams.
I had a client last month—small real estate office—their agent couldn't watch property walkthrough videos. Every 30 seconds, buffering. Took me 10 minutes to fix. Here's exactly what I did.
Root Cause: Broken Connection to the Source
The error code translates to: the source (the server) had to rebuffer because the client (your PC) wasn't getting data fast enough. That's not always your internet speed. Could be DNS cache, a firewall blocking partial packets, or IPv6 messing things up. Or your browser's cache is full of junk from old streams.
Real triggers: Switching Wi-Fi networks, using a VPN, or having a bad router cache. Also seen it after Windows updates that reset network settings.
Fix Steps (Do These in Order)
Step 1: Clear Your Browser's Cache and Cookies
This fixes 1 in 3 cases. Stale cached data confuses the player.
- Open Chrome or Edge.
- Press
Ctrl + Shift + Delete. - Choose "All time" for time range.
- Check "Cached images and files" and "Cookies and other site data".
- Click "Clear data".
- Restart the browser.
Step 2: Flush DNS and Reset Network Stack
Your PC's DNS cache can hold a bad record that causes rebuffering. Run this in Command Prompt as admin (right-click Start > Command Prompt Admin).
ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew
netsh winsock reset
netsh int ip reset
After that, restart your PC. This clears everything network-related.
Step 3: Disable IPv6 Temporarily
IPv6 is great for future stuff but sometimes Windows bungles it and causes buffering. I've seen this specifically on Windows 10 version 22H2.
- Open Control Panel > Network and Sharing Center > Change adapter settings.
- Right-click your active connection (Wi-Fi or Ethernet) > Properties.
- Uncheck "Internet Protocol Version 6 (TCP/IPv6)".
- Click OK.
- Restart browser.
Step 4: Turn Off Windows Defender Firewall for Testing
Skip this if you're worried about security—but it's a quick test. If the error goes away, you know the firewall was the problem. Then add an exception for your browser instead.
- Press
Win + R, typewf.msc, hit Enter. - Click "Turn Windows Defender Firewall on or off" on the left.
- Turn off for both private and public networks.
- Test the stream. If fixed, turn firewall back on and add an exception for the browser.
Step 5: Check Your Wi-Fi vs Ethernet
Had a client who had this error only on Wi-Fi but not Ethernet. Their Wi-Fi card was using an old driver. Update your network adapter driver from the manufacturer's site—Windows Update often gives generic ones that suck.
Step 6: Disable Hardware Acceleration in Browser
Sometimes the video decoding engine fights with your graphics driver.
- Chrome: Settings > System > Use hardware acceleration when available (turn off).
- Edge: Settings > System and performance > Use hardware acceleration (turn off).
- Restart browser.
If It Still Fails
Check your router's DNS server. Go to router admin page (usually 192.168.1.1), find DNS settings. Change from ISP default to Google DNS (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1). Save and reboot router.
Also, try a different device on the same network. If the other device streams fine, the problem is your PC. If all devices have the issue, it's your router or internet line. Call your ISP and ask them to check for packet loss—that's the most common cause of rebuffering that won't go away with local fixes.
One last thing: if you're using a VPN, disconnect it. VPNs add overhead and can cause exactly this error. I've seen it with NordVPN and ExpressVPN both. Not saying they're bad—just turn them off for streaming.