RJARRRPCGP

STOP: 0x0000009C is a processor error. It's usually seen by people that OC their processors too much, insufficient Vcore or wrong Vcore. If not overclocking you processor, please check the voltages anyway. Some motherboards may not be giving the right Vcore! A BIOS upgrade may be required. Also, bad caps and a power supply problem can cause this problem. Please look for the hardware monitor section in the BIOS or use Motherboard Monitor 5 and report the voltage readings back to us. But ignore the "-5V", "-12V" and "-3.3V" values. Please, report the "+12V", "+5V" and "+3.3V" values only. It's also possible that a processor overheat can cause this problem. Please clean out all of the dust bunnies from the heatsink!

That video card definitely is better. In fact, the Radeon 9600 SE has crappy VRAM.

I dunno why that would occur all of a sudden.

FAT32 should be able to handle up to 4 GB per file.

DirectX 3?! That's NT 4ese! Makes me suspect that Microsoft got lazy by slipping in some NT 4 code!

Now, that's strange. I thought that it would just give you a DLL error or just refuse to let you play. I never heard of Vista having so many changes that you're required to have a version for Vista and a version for earlier, except for DirectX. The only major change that I heard of is with DirectX. I didn't think that XP would reject the file as "corrupted". I would have instead expect XP to just have a DirectX DLL error instead. Because of DirectX 10. Heard that DirectX 10 won't be backported to Windows XP and earlier! OK, done ranting, LOL. Sounds like Microsoft changed the .exe structures for Vista. Likely so that people cough up money for Vista.

Unfortunately, Outpost is known to give a hard time about svchost.exe. I can be browsing the internet then the web browser suddenly can't find the web site. Because when I want to limit the svchost.exe traffic, it wants to block svchost.exe from all traffic!

HFCLEANUP is buggy with Windows XP, but I didn't get a BSOD under VMWare Player. Instead, I gotten at least some annoying problems: 1. Windows XP Setup thinks that even the drivers that came with Windows XP didn't pass the Windows Logo tests! I literally get a prompt of if I want to install the driver or not for drivers that come with Windows XP! 2. Then a pre-Windows XP style file prompt box for probably mplayer2.exe or mplayer.exe. 3. Then later on, I get a post-Windows installation style error message pop up, like when you type in the wrong file name in the "Run" box. The following error message pops up: Windows cannot find "mshta.exe" Make sure you typed the name correctly (or similar) The file collection I used was at least roughly the equivalent of the Windows 2000 FDV fileset. (Remove Internet Explorer, COM+, DTC, Remote Registry, Web Folders and etc.) Update: I was hoping that HFCLEANUP could make the commit change as low as Windows 2000 with Windows XP. Why isn't the commit charge going lower. With the Nvidia video driver installed, it probably won't be lower than 60 MB.

Probably the dreaded thermal throttling! Pentium 4s are known to underclock if overheating.

You sound even worse than Link21!

That's usually because of the CMOS getting erased. Just enter the BIOS setup and then choose the option to save and exit.

UDMA may not be enabled.

You shan't have any problem with Nvidia.

56k with SoverNet (sover.net) The usual download bandwidth is 40 kbps. I wish I can get it up to at least 48 kbps.

Sounds like possibly junkware or that an application has a memory leak.

That looks like a CPU and/or RAM malfunction. Did you check with Prime95? This may be symptoms of the voltages being messed up. Did you check with Motherboard Monitor 5? Did you check the processor temperature with Motherboard Monitor 5 or in the BIOS setup? The processor fan may be clogged with dust bunnies or bad. Also, bad caps can cause the same symptoms.

I don't blame everything on software. I first off said that the Perfect Disk issue seems to be under Windows XP only. I dunno why. I also thoroughly test my PC hardware. I put my PCs through boot camp! If Prime95 fails, they're DQ'ed! I also checked the SMART. The SMART was fine.

This was strange. When I tried Perfect Disk 5x I believe back in 2002, I had it analyze the HDD then I wanted to check something on the menus. Then when I clicked on the menu bar, Windows hung then rebooted. It would always go through if I didn't click on the menu bar when it was "analyzing". I never had anything like this occur with Diskeeper. Also, fast forward to 2004 with not the same hardware, with I believe Perfect Disk 6x, I was defragmenting files with the Perfect Disk boot-time defragmentation utility. It usually does a good job. But all of a sudden when it was complete then rebooted, explorer.exe would keep on crashing. I couldn't even access the desktop. It appears that under certain file placement conditions that it ends up misplacing files. Jeremy, BTW, I can't recall Perfect Disk having problems under Windows 2000. It worked properly everytime, AFAIK. Also, I can't recall having problems with Page Defrag under Windows XP.

Nope. I discovered my HDD suddenly being corrupted after it was done defragmenting! It failed to defragment properly! My HDDs were never bad. And my other hardware was fine. I also noticed that Page Defrag can be buggy, (seems to occur with Windows 2000 only) but not as major as with Perfect Disk a while ago. If you defragment the pagefile with Page Defrag, then right after you log in, you may get an error message pop up saying that there's not being enough virtual memory and the pagefile gets disabled! Windows 2000 may reject the pagefile as "corrupted"! I didn't mean the hardware. I meant Windows! Explorer.exe was repeatedly crashing after I defragmented! I was forced to reformat the HDD then reinstall Windows!

I had bad luck before with Perfect Disk in the past. My I believe 5x back in 2002, when I clicked on one of the menus when it was analyzing the HDD, Windows gave me a BSOD! I believe it was STOP: 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA, because of the event log entry. Windows rebooted on me when I clicked on one of the menus! Now fast foward to 2004, with a different PC, with I believe Perfect Disk 6x, after I defragmented with the Perfect Disk boot time defragmentation utility, after it was done and rebooted, the following error message popped up: Windows Explorer has encountered a problem and needs to close. That error message would repeat. Thus means that the HDD got corrupted! That's uncalled for! Number one, my PC hardware and configuration was fine. Also, the power never went out. Has anyone had major problems with Perfect Disk before?

If it occurs randomly, then I'm pointing at the CPU or PSU. The processor may be overheating. The PSU may be bad.

That sounds like the dreaded W32.Pinfi virus, which I gotten back in probably 2003. That virus would corrupt files by appending junk to the end of any file that it can access! That virus would easily spread to at least almost 500 files, if not more! The first symptom I saw was an error message from the Sound Blaster driver installer about a file being corrupted. An installer gave me a file corrupted error message even when I downloaded it from the official web site, because the W32.Pinfi infected the file that I just downloaded! Thus, I dunno what to tell you.

I dunno. Let's not talk about that.

Is it possible for a faulty processor to cause that error message?

Windows 2000 is roughly as fast as Windows XP or faster when installing it for me. But, you are right about booting it.