RJARRRPCGP

Looks like that would be QFT, for the Asus P6T Deluxe with an earlier Killer ethernet card! My upload speed at testmy.net, on FTTH, never looked as good as this before!

Check the event log for storahci issues! That's a known Windows 10 issue!

Looks like I busted Microsoft, with Windows10S, basically the new RT, instead for the x86 arch! Received word that the Microsoft Store bans third party browser engines, like iOS! Ironically, MacOS might be much better!

Their new player is problematic! It likes to stick, even with a high-end system! I don't even have the Core 2 Duo E4500 nor the Asus P5QL Pro motherboard anymore, because it's wimpy for current standards, L.O.L. My main rig is a socket 1366 monster with an Asus P6T Deluxe, a Core i7 "Bloomfield" Extreme 965 and 6 GB of triple channel DDR3 SDRAM. The video card is a GeForce GTX 960...

Reports I saw on the internet so far: 1 reported getting that error message or a similar error message on an X58 platform! Another reported the same or similar error message with an Athlon II! And now a report from one with an Ivy Bridge! This thread is related to this thread:

Ban Windows Update!!!!!!!!!!

It's an artificial black list. Ironically, I never seen anything like this before, even with XP. And this is long before 7 goes EOL! It's easy to get around, this processor ban just sends the message to folks to disable Windows Update and there could be a lot of worms again... I guess it's going to be the hard way again, with some folks disabling the BITS service...

MSI Afterburner, because XP's supported!

OK, here's what happened: The first try, everytime I un-checked the fast download option, I get redirected to a page with a message telling me that my PC is suspicious and to notify technical support. Obvious malicious web page. And with it checked, the download response looks normal, but it got transformed into an .exe that opens Internet Explorer. The host needs to be changed, pronto! I tried and all attempts failed with a compromise.

The XP post-SP3 QFE package over at Ryan VM has been compromised by an attack at the hoster of the file!

Sounds like a faulty optical drive or a bad CD burn...

Sounds like a faulty USB drive...

Not like 2000s CPUs! Starting in the early-2000s, heatsinks had to exponentially be bigger to cool down CPUs at factory clocks! 1990s CPUs usually required nothing more than a tiny heatsink and fan!

The 6 GB capacity is typical of triple channel. Coming across 6 GB almost always means a triple channel system, which I'm only aware of socket 1366 using and maybe some other Intel high-end platforms... And it looks like nForce 2 may only support 3 RAM slots and thus 3 GB at max...

Check "DMA" on the drive entry in Device Manager. DMA is stubbornly disabled by default and that's probably why the OS lags.

It's also very likely the motherboard requires a recap...

At least in the past, the Windows 7-Windows Update has seemed to have a bug where it screws up if you select more than some at a time and not in chronological order.

I/O error=Looks like a failing drive, a SATA cable problem or a SATA port problem.

I only heard of such a glitch with processors that have an integrated memory controller. I only heard of that with socket 1366, socket 1156, socket AM3 and later platforms. It seems to be the most common with Core i-series processors. It was believed to be a problem with the CPU pin contact. I saw one report of an insane problem of this type, such as "8 GB 2 GB usable". This kind of thing is reported over at overclockers.com, IIRC. It wasn't common on pre-Core-i-series-era platforms.

The seemingly odd "3 GB" RAM standard was apparently from the socket-462-and-socket-478-era, where motherboards commonly had 3 slots instead of 4.

That kind of stuff will encourage people running old browsers with vulnerabilities! That's absurd!

Perhaps this is why browsers should be blocked from the registry! (I believe this kind of thing can be used as an exploit.)

Looks like possibly a faulty USB port, if not the USB controller as well.

Sounds like it could have been lag because of throttling. (From dirty heatsink, CPU fan not working or CPU fan too slow.)

That phenomenon seems to occur the most with YouTube.