New baffling problems!!!

[legacy-{eZs}Woody]

OK....I installed this game about a month and a half ago and have been playing it heavily on the same system ever since. I developed the infamous stuttering/pausing problem and solved it last week with fixing RAM timings and adding more RAM. The game was running perfectly with lightning fast load times and no pausing for several days straight until yesterday!

I go to start the game and get the following message:

UT2004 Build UT2004_Build_[2004-03-03_02.42]

OS: Windows XP 5.1 (Build: 2600)
CPU: AuthenticAMD PentiumPro-class processor @ 2186 MHz with 1023MB RAM
Video: ALL-IN-WONDER 9700 SERIES (6436)

ReadFile beyond EOF 4834590+2/4834590

History: ULinkerLoad::Serialize <- FString<< <- FNameEntry<< <- LoadNames <- ULinkerLoad::ULinkerLoad <- UObject::GetPackageLinker <- UObject::StaticLoadObject <- (Engine.LevelSummary CTF-BadNeighborsUTa.LevelSummary NULL) <- UCacheManager::ExportCacheMaps <- NewMaps <- UCacheManager::SaveNewPackages <- UCacheManager::InitCache <- UCacheManager::execInitCache <- (UT2K4GUIController Package.UT2K4GUIController @ Function XInterface.GUIController.InitializeController : 0165) <- UObject::execClassContext <- (UT2K4GUIController Package.UT2K4GUIController @ Function XInterface.GUIController.InitializeController : 0165) <- UObject::ProcessEvent <- (UT2K4GUIController Package.UT2K4GUIController, Function XInterface.GUIController.InitializeController) <- UGameEngine::Init <- InitEngine

Can't figure this out....All I did with the computer that day was play with some photoshop files and install a new printer driver. So I did a system restore to two days prior when I knew the game was functioning fine...no help. same error message....tried the usual stuff, deleting the .ini files, etc. Nothing....same above error message each time I tried to run the game.

I uninstalled, trashed the UT2004 folder (after backing up my .ini files) and defragged/ reinstalled/ defragged. Now I get a new error message when I try to launch the game:

UT2004 Build UT2004_Build_[2004-03-03_02.42]

OS: Windows XP 5.1 (Build: 2600)
CPU: AuthenticAMD PentiumPro-class processor @ 2196 MHz with 1023MB RAM
Video: ALL-IN-WONDER 9700 SERIES (6436)

Ran out of virtual memory. To prevent this condition, you must free up more space on your primary hard disk.

History: FMallocWindows::Malloc <- FMallocWindows::Realloc <- 00000000 996626868 FArray <- FArray::Realloc <- 498313434*2 <- FString<< <- FNameEntry<< <- UMasterMD5Commandlet:oQuickMD5 <- GameEngine:efaultMD5 <- UGameEngine::Init <- InitEngine

WTF!? I have 1GB RAM, a 2GB static page file, and loads of free drive space on a freshly defragged drive. So I do the usual....turn off page file/ defrag/ turn back on/ defrag/ set "auto" page file/ defrag....etc. Same error message.

Well I figure I'm making progress because at least it's a different error message than last time so I roll the dice and uninstall/ reinstall again. The time the game flashes me the following message immediately:


Jees!!! Keep in mind that all other games including 2k3 and UT99 are fine and my computer is behaving normally the whole time (no I don't have any of those nasty worms or viruses in the news).

So this time I can't even uninstall because every single app in the UT2004 folder isn't launching....so I figure sounds like a problem in the registry. To play it safe I back up my registry then go through it and delete every reference to "UT4" and "UT2004" I can find and all associated registry entries for this game. Then I manually trash the UT2004 folder and it's contents. I reboot and check again just to be sure that Windows has no idea 2k4 ever once graced my hard drives.

Now I do the six CD dance again while eating chocolate brownies and raising my blood pressure even higher.

I get a little farther into the launch and it's looking good until I get this line of crap:


I click the OK button about ten times and the message keeps popping up until finally it goes away and gives me the following error message:

UT2004 Build UT2004_Build_[2004-03-03_02.42]

OS: Windows XP 5.1 (Build: 2600)
CPU: AuthenticAMD PentiumPro-class processor @ 2196 MHz with 1023MB RAM
Video: ALL-IN-WONDER 9700 SERIES (6436)

Can't bind to native class XInterface.GUI

History: UClass::Bind <- (Class XInterface.GUI) <- ULinkerLoad::CreateExport <- (GUI 1992363) <- IndexToObject <- ULinkerLoad::CreateExport <- (GUIComponent 1992363) <- IndexToObject <- ULinkerLoad::CreateExport <- (GUIMultiComponent 1992363) <- IndexToObject <- ULinkerLoad::CreateExport <- (GUIPage 1992363) <- IndexToObject <- ULinkerLoad::CreateExport <- (UT2K4GUIPage 1992363) <- ULinkerLoad::CreateImport <- IndexToObject <- ULinkerLoad::CreateExport <- (PopupPageBase 2343952) <- IndexToObject <- ULinkerLoad::CreateExport <- (FloatingWindow 2343952) <- IndexToObject <- ULinkerLoad::CreateExport <- (LargeWindow 2343952) <- ULinkerLoad::CreateImport <- IndexToObject <- ULinkerLoad::CreateExport <- (KickInfoPage 263372) <- IndexToObject <- ULinkerLoad<<UObject <- (LinkerLoad Package.LinkerLoad 263372)) <- SerializeExpr <- (2E) <- SerializeExpr <- (0F) <- UStruct::Serialize <- (Function xVoting.VotingReplicationInfo.SendPlayerID) <- UFunction::Serialize <- LoadObject <- (Function xVoting.VotingReplicationInfo.SendPlayerID 263372==263372/396104 263339 125) <- ULinkerLoad::Preload <- LinkProperties <- UStruct::Link <- UState::Link <- UClass::Link <- UStruct::Serialize <- (Class xVoting.VotingReplicationInfo) <- UState::Serialize <- UClass::Serialize <- (Class xVoting.VotingReplicationInfo) <- LoadObject <- (Class xVoting.VotingReplicationInfo 263372==263372/396104 26031 1729) <- ULinkerLoad::Preload <- PreLoadObjects <- UObject::EndLoad <- UObject::StaticLoadObject <- (Core.Class xVoting.xVotingHandler NULL) <- UObject::ProcessEvent <- (GameInfo Entry.GameInfo, Function Engine.GameInfo.InitGame) <- BeginPlay <- UGameEngine::LoadMap <- UGameEngine::Init <- InitEngine

That's it!!!!! Obviously I need professional help! The really frustrating thing is that this game worked perfectly just the day before and I didn't do a damn thing that would have porked it. I even did a lengthy drive scan to check for errors on that.

If anyone has any ideas I am very eager to listen. I'll try just about anything short of indecent proposals (except maybe from women).

[legacy-Karmanator]

If you didn't mistype you may have a bad RAM since it should be 1024mb RAM, not 1023! You should check into this if not a mistype...sorry =(

[legacy-{eZs}Woody]

That's a good catch. I didn't notice that. I'll look into it. On the other hand, I did try various configurations of my three sticks of RAM without all of them in there at the same time and I still had the problem.

[legacy-ThePerfectCore]

Originally posted by Karmanator
If you didn't mistype you may have a bad RAM since it should be 1024mb RAM, not 1023! You should check into this if not a mistype...sorry =(

No...

That "1023" is what happens when the program only counts extended system RAM, which is everything above 640kb. It rounds down to 1023.

Although I wouldn't rule out the possibility of failing hardware.

[legacy-Karmanator]

Also if you've got a dual RAM setup and you're running different RAM's not made for dual setup or using an extra stick it could cause these problems.

[legacy-Ms Black]

You could try reinstalling windows, or possibly just reinstalling Direct X9b. Do you have all the latest updates and SP1 installed for XP? Seems weird that it'd suddenly die like that.

Also, you might want to try uninstalling your graphics drivers, rebooting, and reinstalling the latest ones.

[legacy-{eZs}Woody]

Originally posted by Karmanator
Also if you've got a dual RAM setup and you're running different RAM's not made for dual setup or using an extra stick it could cause these problems.

This is interesting. I'm running three sticks of Corsair 3200DDR on an ASUS A7N8X in this configuration: slot 1-256MB, slot 2-512MB, slot 3-256MB.

After underclocking the RAM down to 333MHz on a 166MHz FSB with timings at 2.5,3,3,8 I ran memtest86+ on all three sticks individually (one at a time in their respective slots while the others were removed) and they all tested OK. When I test them all simultaneously in the same speed settings I get a series of errors on test #5.

So this is a problem of running the RAM together that doesn't occur on each stick individually. In other words they play fine on their own but don't get along with each other.

Now even though all the cards are Corsair XMS the pair of matching 256MB cards are CMX256-3200C2 certified to 2.5,3,3,6 while the 512MB card is just a CMX-512-3200 certified to 3,3,3,8. The problem is that with the C2s in the box the thing won't boot (I get a POST "memory failed" error) but it boots fine at the current 2.5,3,3,8 with all cards. And like I said they all test fine individually at those latency settings at 333MHz.

My overall 2k4 problems occurred several days after installing the new RAM but I had been playing for many hours on and off before it decided to quit on me.

Ms Black's idea of reinstalling the vid drivers (Catalyst 4.4) may be a good one but I think I am likely on to the problem with this memory thing. All my other games were running fine.

I'm going to try testing the RAM in different slots to see if it makes a difference.

[legacy-{eZs}Woody]

Straight out of the manual for memtest86+

There have been numerous reports of errors with only tests 5 and 8 on Athlon systems. Often the memory works in a different system or the vendor insists that it is good. In these cases the memory is not necessarily bad but is not able to operate reliably at Athlon speeds. Sometimes more conservative memory timings on the motherboard will correct these errors. In other cases the only option is to replace the memory with better quality, higher speed memory. Don't buy cheap memory and expect it to work with an Athlon! On occasion test 5/8 errors will occur even with name brand memory and a quality motherboard. These errors are legitimate and should be corrected.

[legacy-Ms Black]

Are you running the latest bios revision for your motherboard?

[legacy-{eZs}Woody]

Originally posted by Ms Black
Are you running the latest bios revision for your motherboard?

Unfortunately, the last time I tried to update the BIOS it wouldn't work. I think I'm stuck with what I have (1003).

I managed to get memtest86+ to run through several loops with all three cards by forcing them to not utilize dual channel. By placing them in the following order slot 1-256MB, slot 2-256MB, and slot 3-512MB all metest86 tests came back positive all the way up to 400MHz on a 200MHz FSB and with the CPU running at x11 (2.2GHz). I also ran prime95 for 90 minutes with no errors like this. So I'm pretty sure there is nothing wrong with my memory but it wasn't working well in the slot configuration I had.

I was hoping this would solve my problems but it didn't work after reinstalling 2k4 I get the same load errors. Now I'm thinking that some files are messed up so I'll proceed the old fashioned way and start reinstalling drivers and won't stop until I'm forced to format C and reinstall Windows again!

[legacy-Ms Black]

Hmm, It might be an idea to have another crack at updating the bios. It can solve quite a few issues. Hard to give advice on it tho, best way is to just follow the instructions on the manufacturers website I guess.

Sorry, i've not got any other suggestions

Will let you know if I think of anything else!

[legacy-mluckey]

If you are running the RAM in SPD mode, then don't. Set the RAM timing manually to the default speed of the slowest module in the setup. The motherboard reads the SPD of the first module installed in most cases, and if that one isn't the fast one, you are OK, but otherwise, you ask for issues.

Mixing different RAM speeds isn't always a good practice for gamers, but if you set the RAM to the slowest module you are usually good to go..

[legacy-{eZs}Woody]

Thanks for the replies. I do set my timings manually. The RAM is all the same speed rating (DDR3200) if that's what you mean. The certified lowest latency timings are a little different. The matched pair is "C2" or CAS 2 while the single larger stick is CAS3 but for some reason the C2 sticks won't run at CAS3 (can't figure that one out) so I am running them at 2.5 (2.5,3,3,11). This shouldn't be a problem since the RAM is basically identical but just certified for different latency settings from Corsair. But since they all run fine at the current settings and test good under stress this should no longer be an issue. Even Corsair recommends running this RAM at C2.5 in the forums even though it's not guaranteed.

In fact the bandwidth tests of three sticks in single channel at the new settings of 2.5,3,3,11 are yeilding almost the same results as my original settings of 2,2,2,5 in dual channel mode without the third stick (just a hair under 3000kB/s). I'll run some 3DMark tests also when I get the opportunity.

I've come to theorize here that adding an extra stick of RAM last week caused my system to encounter memory errors with what are otherwise good sticks of RAM. These memory errors caused permanent corruption of essential Windows or drivers files for UT2k4 to load that don't seem to affect other games or applications or Windows itself. I will attempt to uninstall/reinstall some of the critical drivers such as graphics and sound and system to see if I can repair the problem short of having to reinstall Windows.

I'm worried that if I reformat and reinstall WinXP and the problem persists with a clean install of UT2k4 that I may have encountered a new problem in 2k4 that I cannot resolve without building a new machine but I think that is a stretch.

[legacy-mluckey]

You seem to be knowledgeable about troubleshooting, hardware and such, so perhaps this will help.

It is not uncommon for a motherboard to require either more voltage, or increased RAM signal strength to run mre than 2 RAM modules. If your motherboard allows increasing the signal strength, try raising it a notch. Otherwise, it's a virtual guarantee that if you raise the voltage a notch or two, that you will stabilize the RAM. Most all RAM on the market can handle up to 2.85 volts without any issues. Some RAM prefers extra voltages (WinBond chipped RAM in particular). You could always try a 2.65 - 2.75v RAM setting to see if that stabilizes things.

I have four different setups, and motherboards fro two different Manufacturers (Asus, and Abit) and three of them required more voltage to run three RAM modules.

[legacy-Rectal Prolapse]

Did you scan your system for viruses/spyware? It sounds like your UT2K4 install is corrupted (although bad memory would do that too!).

Are your hard drives working properly? Maybe DMA is disabled, which can happen if Windows detects that the data CRCs from the data transfers are incorrect, and it will automagically disable DMA...which may indicated an IDE problem.

[legacy-Ms Black]

Good advice, mluckey.

My RAM (Corsair 1GB DDR XMS3200LL Pro TwinX (2x512MB) CAS2) Doesn't like running on the default of 2.6v. It throws a few errors in Memtest+ I just upped the voltage to 2.75 and it runs absolutely fine now. Apparently my RAM is actually rated at 2.7v, according to corsair. Corsair say that you may run the modules up to 2.8v, but any higher will void the warranty.

[legacy-{eZs}Woody]

Yes that is good advice. I'm running my RAM at 2.7 but haven't upped it since adding the third stick. It's possible that if I do I could go back to utilizing dual channel with the first two sticks. Right now the RAM seems to be running smooth and error free under load in it's current configuration. I will probably experiment with the voltage also.

Looks like I'll get the chance to reformat and reinstall after all. I uninstalled and reinstalled virtually every hardware driver I had! I figured I was probably wasting my time but I wanted to at least attempt to isolate the problem. I used the "drivercleaner" software to eradicate all traces of drivers first.

Been so busy lately I just haven't had the time to get this done once and for all. But I'm missing out on my game time and am just going to go ahead and reformat.

I'll post my final results when I finish. It's almost as frustrating to solve a problem and never understand what went wrong in the first place.

[legacy-mluckey]

Glad to be of some sort of help............

[legacy-bugnodz]

I was getting ram errors with my Corsair 3200LL until I read (granted on an Abit site) that 11-3-3-2.5 or 10-3-3-2.5 (or 2) gave great bandwidth and stability and it was true. 11-3-3-2.5 in dual channel had no error with memtest or Prime 95. For some reason I tried different timings but the 11 seemed to be the magic number as far as stability and bandwidth. I also bumped vcore and ram voltages up a tad too. Dont know if the non-Abit boards will get the same results but its worth a try. Dont let the 11's scare ya.

[legacy-mluckey]

bugnodz,

You are dead-on with those timings. It's an nVidia dual-channel thing, not an Abit thing. The Via chipsets respond waaaaay different than the nVidia chipsets because of the basic architectural differences. Via chipsets like tight timings, and nVidia likes more relaxed timing as a rule of humb for RAM.

[legacy-bugnodz]

Its nice to hav a board that has so many features too. Hows that 5700 workin for you?

[legacy-{eZs}Woody]

Time to drag this topic up from the dead. Been busy at work all last week but over the weekend I finally had the chance to sit down and solve this problem once and for all...sort of:

Hopefully my experience can help some others who have suffered.
___________________________________________
AMD Athlon 2500+
ASUS A7N8X Deluxe rev 2.0 BIOS 1007
2x 256MB Corsair 3200c2 and 1x 512MB Corsair 3200
ATi Radeon 9700Pro AIW
Drives: C: WD800JB
D: SATA RAID0 240GB (pair of Seagate Barracuda 120GB)
On board audio: NVidia Soundstorm
____________________________________________

Initially a reinstallation of WinXP on an underclocked system using ATi Catalyst v4.5 failed to run a clean install of 2k4 (even after patching) to my complete horror. I almost gave up.
Here's what I did.....

- I disconnected my RAID0 on the mobo and unplugged it.
- I clocked back to default speeds for a 2500+ of 166x11
- I used only a single stick of 512MB RAM (the new one) in slot 1 set to 3,3,3,9 and synced to the FSB (166MHz).
- I set my CPU voltage (Vcore) up a notch to 1.675 Volts (indicates 1.7) and my RAM voltage from 2.7 Volts to 2.8 Volts.
- I unistalled catalyst 4.5 and installed 3.9 (I was previously running fine with 4.4 for a couple weeks when the problems started but had initially installed 2k4 under 3.9). I used Driver cleaner to completely rid the old catalyst stuff after uninstalling.
- I uninstalled and reinstalled UT on the C drive. ( this is what I had tried before when it worked for a few times yesterday then quit again)

A successful install and tested working so I replaced the ini files with my own custom and tested again thoroughly...all good.

I then started working forward to reinstall all my hardware one step at a time and testing 2k4 after each miniscule change.

- first changed the RAM card to slot 3...tested ok
- changed the RAM timings back to 2.5,3,3,9....tested ok
- added the other two 256MB sticks to slots 1 and 2. This enabled dual channel with the following configuration: slot1-256, slot2-256, slot3-512. 2k4 still tested OK even after running several maps online.
- next I enabled and plugged in the SATA RAID0 and ran 2k4 off C drive....tested ok
- next I copied the entire 2k4 directory over to D drive (RAID) and changed the drive location in the registry....test failed.

2k4 wouldn't run off D drive, wouldn't even load. So without uninstalling the C drive folder I reinstalled 2k4 again on to D drive from the CDs. Still failed even after rebooting. Now with dual installs of 2k4 I was still able to run the C drive installation...all I had to do was change the location setting in the registry. So I conclude that 2k4 is unstable on my system when run on a different drive. The RAID volume seems stable with other apps and with the 1GB of RAM I don't think the load times are a whole lot slower on C drive so I guess I'll just live with running 2k4 off C. It's still a good drive; WD ATA100 80GBJB drive with 8MB cache. When I first installed 2k4 it was running fine of the RAID for over a month so I don't get it but I'm not messing with it anymore, it's a {edited for content ) so I'm lucky it's running at all.

I have not attempted to install the patch. I have left my voltages alone at the slightly higher settings.

I reclocked my system back to 11x200MHz (default settings for a 32bit 3200+) and tested 2k4 for several more maps online with no problems. In fact it's running very smooth now.

My conclusion is that a combination of running it on the boot drive and rolling back to ATi Catalyst 3.9 is what fixed me. Turns out there is nothing wrong with my RAM, my Windows installation, or any of my hardware as far as I can tell. I guess I will never understand why it ran fine under Cat 4.4 and on the RAID for a long time before deciding not too for some arbitrary reason.

Oh yeah! My final conclusion is that it's a {edited for content ) so I'm lucky it's running at all.

See you all online soon.

[legacy-Ms Black]

Interesting. I suppose you have the latest driver your RAID controller?

I myself run UT2k4 off a RAID system, and it runs fine here. I can't imagine why it doesn't like running on yours! Very odd.

[legacy-Karmanator]

Probably Spyware or a lingering virus thats hiding out...or registry changes made by the spyware...that always messes with my UT...glad youre runnin good bro!

[legacy-{eZs}Woody]

Well it used to work fine....just stopped for some reason.

No spyware or viruses since the problem was the same both before and after a reformat/reinstall of XP.

I do have the latest SATA drivers but that could also be the problem. Often upgrading drivers can cause more problems than it fixes.

Any other games don't even need to be properly installed. If I just copy the specific game's registry file and the game folder it will work after reinstalling Windows without reinstalling the game. 2k4 is the only game I have that won't accept this kind of shortcutting....It must be installed clean off the CD to work for some reason. I'm thinking it's because I installed on the boot drive first that it won't run on a different volume now unless I were to reinstall Windows again. Doesn't make any sense but it's the only thing I can think of. I did notice that 2k4 puts all kinds of stuff all over the registry where most games don't. It may be some kind of extra anti-piracy scheme.

[legacy-Karmanator]

UT adds to the registry? GODAMMIT!!!! No wonder everyone is having all these problems....that was really ****ing stupid Epic/Atari. REAL STUPID! Try Registry Mechanic as a last resort bro...good luck.

[legacy-Ms Black]

All games pretty much add stuff to the registry! Some games don't rely on it as much as others though.

Nearly every program uses the registry one way or another these days.

[legacy-wisealma]

This is exactly what happened to me! Thank YOU SO much for the details. How did you edit the registry? I had it running on my D: drive just fine, and then it stopped working. I have tried it on my C: drive, but it didn't work. If you could explain what you edited in the registry, and how to do it, I just might be playing again today! Please and thank you!

Wise



Time to drag this topic up from the dead. Been busy at work all last week but over the weekend I finally had the chance to sit down and solve this problem once and for all...sort of:

Hopefully my experience can help some others who have suffered.
___________________________________________
AMD Athlon 2500+
ASUS A7N8X Deluxe rev 2.0 BIOS 1007
2x 256MB Corsair 3200c2 and 1x 512MB Corsair 3200
ATi Radeon 9700Pro AIW
Drives: C: WD800JB
D: SATA RAID0 240GB (pair of Seagate Barracuda 120GB)
On board audio: NVidia Soundstorm
____________________________________________

Initially a reinstallation of WinXP on an underclocked system using ATi Catalyst v4.5 failed to run a clean install of 2k4 (even after patching) to my complete horror. I almost gave up.
Here's what I did.....

- I disconnected my RAID0 on the mobo and unplugged it.
- I clocked back to default speeds for a 2500+ of 166x11
- I used only a single stick of 512MB RAM (the new one) in slot 1 set to 3,3,3,9 and synced to the FSB (166MHz).
- I set my CPU voltage (Vcore) up a notch to 1.675 Volts (indicates 1.7) and my RAM voltage from 2.7 Volts to 2.8 Volts.
- I unistalled catalyst 4.5 and installed 3.9 (I was previously running fine with 4.4 for a couple weeks when the problems started but had initially installed 2k4 under 3.9). I used Driver cleaner to completely rid the old catalyst stuff after uninstalling.
- I uninstalled and reinstalled UT on the C drive. ( this is what I had tried before when it worked for a few times yesterday then quit again)

A successful install and tested working so I replaced the ini files with my own custom and tested again thoroughly...all good.

I then started working forward to reinstall all my hardware one step at a time and testing 2k4 after each miniscule change.

- first changed the RAM card to slot 3...tested ok
- changed the RAM timings back to 2.5,3,3,9....tested ok
- added the other two 256MB sticks to slots 1 and 2. This enabled dual channel with the following configuration: slot1-256, slot2-256, slot3-512. 2k4 still tested OK even after running several maps online.
- next I enabled and plugged in the SATA RAID0 and ran 2k4 off C drive....tested ok
- next I copied the entire 2k4 directory over to D drive (RAID) and changed the drive location in the registry....test failed.

2k4 wouldn't run off D drive, wouldn't even load. So without uninstalling the C drive folder I reinstalled 2k4 again on to D drive from the CDs. Still failed even after rebooting. Now with dual installs of 2k4 I was still able to run the C drive installation...all I had to do was change the location setting in the registry. So I conclude that 2k4 is unstable on my system when run on a different drive. The RAID volume seems stable with other apps and with the 1GB of RAM I don't think the load times are a whole lot slower on C drive so I guess I'll just live with running 2k4 off C. It's still a good drive; WD ATA100 80GBJB drive with 8MB cache. When I first installed 2k4 it was running fine of the RAID for over a month so I don't get it but I'm not messing with it anymore, it's a {edited for content ) so I'm lucky it's running at all.

I have not attempted to install the patch. I have left my voltages alone at the slightly higher settings.

I reclocked my system back to 11x200MHz (default settings for a 32bit 3200+) and tested 2k4 for several more maps online with no problems. In fact it's running very smooth now.

My conclusion is that a combination of running it on the boot drive and rolling back to ATi Catalyst 3.9 is what fixed me. Turns out there is nothing wrong with my RAM, my Windows installation, or any of my hardware as far as I can tell. I guess I will never understand why it ran fine under Cat 4.4 and on the RAID for a long time before deciding not too for some arbitrary reason.

Oh yeah! My final conclusion is that it's a {edited for content ) so I'm lucky it's running at all.

See you all online soon.