RJARRRPCGP

I never heard of that bug with XP x64! OTOH, XP x32 had a bug with a GeForce 2 and Via KT133 where text mode XP setup will lock up at "Setup is starting Windows" and had to pop my Voodoo 3 back in to get past that! (That was back in 2001, LOL) With a driver problem, the kernel should throw "0x000000D1". "0x0000000A" is usually unstable CPU core/corruption. (Usually means you need to turn down your core clock speed or raise Vcore)

Just like with good ol' Windows 98 SE, LOL.Actually, XP's been working fine with my Sabertooth 990 FX R 2.0! If you keep getting the dreaded STOP: 0x0000007B BSOD, even with "IDE mode" in the BIOS on the Sabertooth 990 FX R 2.0, it means you're probably using the beige SATA ports. *** Don't use the beige SATA ports! *** They don't support PATA emulation! You must use the brown SATA ports. I believe the brown SATA ports are the native AMD ones.

The dreaded BGW error message is because of the oddball setup of the hosting provider... Not typical...

1979? I was thinking that you would be lucky to get a 4 MB HDD for less than $20,000!

Yep, this reeks of a coup d'etat!

Sounds like "laptop-HDD-degradation-disease". Where the laptop HDD access is slow for some absurd cause and wiping the HDD restores performance, at least temporarily. If the laptop HDD is a Seagate, it's a definite suspect. And I still suspect the HDD, even if it's a WD. If disabling extra services, or programs don't solve the problem, I'm afraid it's the HDD.

I noticed this bug, but that was before I wiped the HDD and reinstalled Windows XP x32 SP3: (for Halo CE) Close Skype with the "X" and Skype.exe is always a zombie process! (Must be terminated with Task Manager)

I have a GeForce GT 640 and happy with it.

Just in case you weren't aware: http://techreport.com/review/27727/some-840-evos-still-vulnerable-to-read-speed-slowdowns After ~3 months read speeds begin going south, ultimately reaching good ole UDMA-33 levels : Wow! I would replace the ATA cable!

FSB termination voltage likely higher than required on a 45 nm dual core! I doubt you need more than 1.25 V. An FSB termination voltage bump is usually only required on Quads, because of an architecture limitation that causes interference with 4 cores. A bus error (appears as a "STOP: 0x00000124" BSOD with "bus/interconnect error" reported in the event log) is likely when multitasking on a Quad which OTOH, is usually non-existent on a dual core. A 65nm Quad likely requires 1.3 V for the minimum FSB termination voltage with a small FSB OC! Was being a pain at just 367 Mhz, which is nothing for my P45! My 3.3 Ghz Kentsfield OC required the FSB termination voltage raised to 1.3 V and the Vcore at 1.40 V. (367x9.0) On a P45, a Duo easily goes to 450 Mhz FSB without touching any bus or northbridge voltages. (On an E8400)

It's snappy, but updating Windows is super slow, like a 386 and 486! Seems to be deadlocks in Windows Update code. It's working well with a PNY Optima 120 GB SSD, which appears to have a Silicon Motion controller. It's doing well, despite a single 4 GB stick. (I lost fundamental stability with a 2x4GB RAM kit, had to return it)

FYI, if someone has tested on a Vostro 200, then it should be fine. To me, the Inspiron 530S looks like a renamed Vostro 200. Looks like the chipset is probably G33.

Actually, it may be anything higher than 768 MB.

Sounds like the wrong ATA driver.

OT, likely the worst was when Microsoft bought Rare! -> That right there makes me want the FTC to go harder on Microsoft!

Most of the problems are caused by folks browsing random web sites as administrator! That's a typical PEBKAC issue there..... When using a highly privileged account, all you have to do is click on an ad and then wham! Windows is compromised!

When I had "PFN_LIST_CORRUPT", it was with a RAM overclock, I think it was with my Kingston PC2100 DDR SDRAM at about 145 Mhz, even when it seemed that I couldn't make it occur again.....

Looks like it's time to chuck the CD drive or get CDs of another manufacturer.

QFT! Makes me miss the 1980s and 1990s! Even during most of the 1990s, it wasn't this bad! At least it wasn't a pandemic invasion... It's gotten to the point where I'm saying "enough!". A.K.A., gotten to the point where I'm putting my foot down!

Windows 95 OSR2 and later don't require a reboot to change the color palette nor the resolution.

I just got another BSOD a while ago, it was 0x000000BE again for kmixer.sys, when playing a video. And then after rebooting, there won't be a crash for a while, if not many hours!

I definitely understand about the ethernet. Because I have FTTH. That didn't matter with DSL, but, times have changed. And for the board manual that lists 1066 at max: 1066/4 is a paltry 266 Mhz FSB, that's why E8400 isn't supported. And that's just ridiculous for some CPUs, despite being within board design limits to not be listed... If a Wolfdale is supported, then for all of the 266 Mhz FSB or less variants, the board shouldn't even give a squeak. Especially, because Wolfdale uses less watts than Conroe per clock cycle.

No you don't. There's no 512 MiB RAM limitation (but there is a RAM limitation around twice that amount) nor any FSB frequency limitation whatsoever. Search the forum and read: all the info you need is here, in much detail. There's an issue where there appears to be a 768 MB limit. At least confirmed with the swap file. Setting the virtual memory to more than 768 MB results in a false "Insufficient memory to initialize Windows" (or similar) error message. Possibly applies to RAM amount, too.

ClearMem is so old school that it appears to have a compatibility issue with more than about 512 MB of RAM installed. It's from the Windows 3.1x period, LOL.

It said that it was kmixer.sys. Looks like late updates may have broke XP.