RJARRRPCGP

Can also occur if you jump to different places in a video file being played on the PC. I don't have crash info right now, waiting for it to occur again, because the most recent one is unbelievably incomplete.

Sounds like you don't have the boot order configured correctly in the BIOS.

Looks like the driver isn't even compatible with the no-execute-memory protocol. How can that be? It has existed since XP 2002 SP2!

From my experience with 7, it looks like a common issue on anything Vista and later. I dunno what it is. x64 seemed to be the worst. On 7 x64, I would suddenly get a real long boot routine, even with 5+ GB of RAM.

Seems to be a disorder laptop HDDs develop that requires wiping the HDD and repartitioning. I dunno what to say if removing the extras don't fix that! (My sister's laptop with an HDD had an issue like this, wiped the HDD and voila! It's back to normal HDD speeds!) Seems to be some kind of bit rot that I never seen on a desktop HDD. :/ I wasn't telling you to wipe the HDD, so please don't panic, lol. Just something I noticed.

Was this problem solved? If it wasn't, a registry entry may have too restrictive of permissions.

Looks like it supports virtualization technology, which AMD didn't give people a hard time with, unlike Intel, where lots of them don't! (In fact, Intel made me P-ed, I had to change my processor just to have VT, because when AMD made it standard, Intel decided to make it available only on some.) In this case, you should be real happy you have an AMD. http://products.amd.com/en-US/DesktopCPUDetail.aspx?id=654&f1=&f2=&f3=&f4=&f5=&f6=&f7=&f8=&f9=&f10=&f11=&f12=True Looks more like Windows blocked the driver from loading.

It may mean a hardware failure. Or CPU overheating. The OP-listed symptoms could be disk errors.

If that was on reboot, it usually means a corrupted MBR on your HDD. Probably a bad optical drive or corrupted MBR.

Sounds like the driver failed to load and thus Windows 2000 went to the usual dreaded fallback graphics driver.

That's not caused by ATA mode.

That's an old bug that IIRC only occurs with GeForce 2 (maybe GeForce 1 too) video cards. It's also possible that it only occurs with the Via KT133 chipset. This bug was the SNAFU of the GeForce 2 and Via KT133 combo. Back in 2002, I had to remove my GeForce 2 MX 200 and pop my Voodoo 3 3000 back in to install XP on my Via KT133-based motherboard.

This: Does Microsoft want me to be a bubble boy? lol

Real bizarre stuff for a post-1994 board. Remove the CR2032 battery, clear the CMOS, get a new CR2032 battery, then when prompted to load defaults, load the defaults, save, reboot, re-enter the BIOS setup and make your needed changes and save.

10 minutes sounds more like Windows went to PIO mode because of ATA errors! I would replace your SATA cable and clear the CMOS.

PIO would make almost everything use 100 percent of CPU! If Windows goes to PIO mode, it means you need to replace your ATA cable or you have a bad ATA controller. Also may be caused by too high of PCI-E clock!

I dunno why your skin would hog them up. That's not common with NT-based Windows. It was common with non-NT-based versions.

I'm having a problem here: A list I made attached:Missing Windows 7 SP1 Updates.txt This list is based on what I got after Windows Update scanned the installation. Actually, ignore the Net Framework section. That's not as concerning. The KB2532531 update failed and I dunno why ATM..

DISM claims there's no image inside of install.wim. Error: 0xc1510113. -> Hmm. Looks like my Ultimate image is not using index 5..... It's index 4. Oh well. I fixed it, even though I right afterwards got an error about not even having permission! (That's despite being ran as administrator and proper ACLs.) Turns out DISM still goes by the "read-only attribute" like DOS-based Windows. I getting ready to learn Windows 7 hotfix integration, because I got 5 GB of RAM now.

Actually, this reminds me of Windows 95! Remember OSR2? Microsoft refused to offer OSR2 as an update to retail variants! This caused me to get P-ed back in 1999.

Failure at the same clusters sounds like a real old school problem, was usually seen with 386s and 486s! Back in the 1990s, it means the BIOS has the HDD capacity-related parameters set wrong. (Back in the days where the number of cylinders, heads and sectors per track had to be manually entered.) But with your PC, it should be fine at 100 and 120 GB. That's within the early 2000s LBA 28-bit limit.

lol

To the OP: May be a faulty or overheating GPU.

Looks like the PC is loosing power for a split second and then coming back on. Just like when there's a power co. issue.

But why do I have to do this with a fresh install? Even Vista didn't have this bug! It seriously looks like hotfix time! TBH, something's broken in Windows Update. Not happy, because 7 SP0 didn't have any Windows Update failures! Guys, it looks like I have to apply fewer updates at a time and then run that.