RJARRRPCGP

Why. Does it require SSE? I do know that T-birds don't support SSE, even SSE 1! T-birds don't support SSE at all! Only Athlon XP Palominos and later support SSE! It may be because your processor is malfunctioning. Did you test it with a 24-hour run of Prime95? Um...No. If that was the case, then the machine would be crashing all the time...or at least all the programs would start going squirlly at the very least. I haven't seen a blue screen in quite some time now. Also, Prime95 is demanding. You can think that your processor is working properly, but Prime95 still fails. If Prime95 keeps on failing, you have a faulty processor, motherboard malfunction or your require a power supply with more watts.

If that is it then why is XP able to boot up and work under safety mode? Because it's not under a higher work load. It probably is fine until it's being put under a higher work load then it crashes.

I have gotten wording about the following: Intel made it's complier so that it's slower on purpose if a non-Intel processor is detected. Even if the processor supports the functions required.

This is why I always use a firewall with most Windows installations, because of internet viruses doing that. (Or at least probably) Sasser was a suspect of that behavior. Sasser was the suspect of the following behavior: Repeatedly port scanning, usually port 135 and port 445. When I was using Sygate Personal Firewall, it was logging port scans within every hour at one point back in 2004. When I was being port scanned, according to the firewall, many of them were from an IP address that's owned by the ISP I'm with! Probably zombie PCs with the same ISP I have port scanning my PC.

Actually FAT16 also has a second partition table. FAT32 has a second (spare) bootsector in sector #6, just like NTFS (depending on which version), has one in the middle (NT4.00) or at the end of the partition (Win2k/XP/2003). jaclaz NT4 don't support FAT32! Anybody that uses FAT on anything larger than 20gigs is a sick little monkey that doesn't understand the differences between FAT and NTFS (or they just need cross OS readability which is forgivable). Windows didn't set the limit to push an agenda, they did it for sanity. Actually, I have always been installing Windows 2000 and Windows XP on a FAT32 partition, but then convert it to NTFS, because that's my own workaround I have for preventing Windows from dorking around with the drive letters! If you install it to a NTFS partition, then it's known to dork around with the drive letters. It's known to make drive C become drive D and drive D drive C or it assigns a random drive letter, for example, it may make my primary master HDD drive F! By installing on to a FAT32 partition and then convert it later after the Windows installation has been complete by typing convert c: /fs:ntfs your able to make sure that the primary master HDD is drive C. When you install Windows on to a FAT32 partition, the primary master HDD always is drive C. Windows won't change any drive letters when you run the convert command.

It's probably because Windows 98 don't include a driver for it, probably because the hardware is newer than Windows 98, thus required to download the driver from the hardware manufacturer's (or chipset manufacturer) web site!

Service Pack 2 is actually 266 MB!

Hi there! My first post in this topic (at least I think so:) but I've been monitoring it since page 2 :> My desktop after activating doubledpi.reg 3200x2400 - now I can have even a bigger mess on mz desktop then before! PS: After changing the resolution to 3200x2400 i couldn't use atitray anymore and I had to kill it because it was using 90% of CPU Power. My monitor is Nec MultiSync FE750+ running on 9600XT in 85 Hz. Cat 6.1 And Now for Something Completely Different My obligatory contribution: "Wow! This project is great!" Please use a different host, because they have a traffic limit!

Did you get and run Memtest86? Run Memtest86 for 24 hours. (or up until you see an error)

Did you disable the automatic reboot option in the control panel?

Did you take the heatsink back off and checked the thermal paste. Make sure that the thermal paste isn't on any of the bridges!

I agree, because if it's a licensing issue, then Windows probably would display an explicit error message. It's probably not a licensing issue if you got a generic error message.

Actually, you can have a FAT32 partition bigger than 32 GB if you use a third party partitioning utility. There's nothing in FAT32 that prohibits you from creating partitions bigger than 32 GB! The 32 GB partition limitation in Windows XP Setup is arbitrary! That's because Microsoft want everybody to use NTFS.

Sorry, I'm with Andromeda43 on this one, because most of the HDDs that I experienced having bad sectors and the click of death were Western Digital. But I haven't had as bad luck as Andromeda43. Luckly, I never was required to replace it three times!

The Raptors are the only HDDs I want from Western Digital. Had bad luck with Western Digital. A Western Digital 13 GB 5,400 RPM HDD that I still have does that. I can't recall having that issue with my Maxtor HDDs. But they're PATA.

Sounds like it's unstable. I suggest that you run Memtest86 for 24 hours. Memtest86 is available at: http://memtest86.com

Athlon XP Barton 3000+ OC'ed to 2.39 Ghz (184x13.0) 1.75V

With the automatic reboot, the crashes are probably still being logged. Look for a "Save Dump" entry in the System event log. Windows can still boot if there's not enough power. But then crash randomly.

It appears to likely not be accepted anymore. It forces me to create an account and enter billing information!

That reminds me of when I accidently forced Windows to install the wrong IDE driver by using Device Manager. After I did that, after I rebooted, gotten the the following BSOD: ***STOP: 0x0000007B INACCESSABLE_BOOT_DEVICE Thus I rebooted again. Then that's when Chkdsk scrolled file system errors and decided to say that there's "orphaned" files! Chkdsk also deleted random files on my non-OS HDD! Thus I lost some AVI files and JPG files permanently! D*** Nvidia! Didn't warn me that the IDE driver didn't support nForce 1! That was when I had an Asus A7N266-VM/AA motherboard back in July, 2003. Was my first Athlon XP system I built. LOL.

On the 7th screenshot, Iexplore.exe is the one using the most RAM. Sidebar.exe isn't nearly at 400 MB. Sidebar.exe appears to be fine there.

Bad memories of the K6 processors? The K6 processors, which were before the Athlon, didn't do very well. AMD has came a long way! Even the Athlon XPs rocked! I still have an Athlon XP, because I'm not ready to build an Athlon 64 system yet. Definitely won't be until at least spring! Even then, I dunno. Thus required to make do with an Athlon XP.

The colored lines and blocks problem can also be caused by a GPU problem. The GPU heatsink may be loose! Also, the GPU may not have enough thermal compound.

That's retarded! It actually punishes you just because the video card don't support pixel shader 2?! When it don't even use pixel shader 2!

This isn't an attempt to circumvent anti-copy protection!