Moved: Misc tasks, screen freezes, video driver unloads, BSOD atikmpag

Well, moving the video card did not produce a result that was different than the original PCI-E location. The game still crashed. I have attached the minidump zip to the post, though I already know it will tell us the same thing that the rest of the minidumps tell us, atikmpag.sys.

I am going to shutdown and move my video card back to the original location. I don't believe moving the card to the 8x PCI-E slot is going to improve the stability, and it will only slow down the card.

Also, when I moved my video card to this bottom PCI-E slot, I used my Antec LCD Power Supply Tester (Amazon.com: Easy Accurate Pc Power Tester for Atx 20/24PIN Power…) to verify that the power supply was at least providing proper volts. I know this doesn't test the amperage, but I don't have an ampmeter, so this is all I have to work with. The tester showed that everything was within nominal limits, including that both 6-pin connectors that feed the video card were putting out the exact same voltage.

At this point, I am waiting for FedEx to deliver my new copy of RCT3 Platinum. When that arrives, I will install from those disks and see what happens. I will also remove all traces of Daemon Tools prior to that install. If this results in the same exact issue, I am going to run into my local computer shop, and buy a new 250GB Hard Drive to install a fresh copy of Windows 7 onto. I don't want to format/reinstall over the current installation if I don't have to.

BSOD analysis is an art form - and not a science (at least at the level we do here).
The system blaming the ATI drivers is just it's best guess as to what caused the problem - it's not necessarily correct.

I have a very difficult time believing that 5 completely separate driver versions have the same exact error and that ATI has not done anything about them yet.

If there's 5 separate versions that cause the same error - then it's most likely that that isn't the cause.

In particular, this error is a difficult one to troubleshoot - and I'm fascinated by it.
Our best guess is that Daemon Tools is to blame - but that's not a sure thing, it's just a guess.
As for video card tests - the only one that I know is replacing the video card with one that's known to be good (or a new one if you don't have access to a known good card).

I have recently read about this free bootable diagnostic utility - but haven't had time to try it: Home | Inquisitor hardware testing platform

Nothing different in the memory dumps - both are STOP 0x116's as usual.
I can't recall if I've stated this before, but when I see video errors with dxgkrnl.sys in the stack text, I wonder about hardware problems.

Have you uninstalled DirectX and then reinstalled it? I'm not familiar with this, so you'll have to Google for the methods.
Have you run the System File Checker?:

SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

From this link ( http://forums.amd.com/game/messagevi...&enterthread=y ):

The following hardware issues are examples that can cause a TDR event:
- Failing overclock on CPU or GPU (stop overclocking)
- Bad sector in memory resulting in corrupt data being communicated between GPU and the system (either video or system memory) ( MemTest and a video memory stress test: |MG| Video Memory Stress Test 1.7.116 Download )
- Corrupt hard drive/windows install resulting in corruption to the system registry or the page file (Hard drive diagnostics ( HD Diagnostic ), reset your pagefile

Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.

and run the System File Checker

SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

)
- Over heating of GPU or CPU again resulting in corrupt data being communicated. (Point a house fan at the video card, take temperature readings from the card with an IR detector (or your finger - but be very, very careful!!!)
- GPU failure due to any sort of issue from insufficient power(VERY common) to heat. (check the power leads, use a multimeter to check the power output, try another, more powerful PSU)

The following software issues are examples that can cause a TDR event:
-Incompatible drivers of any sort (either GPU, sound, etc) ( http://www.microsoft.com/windows/com...s/default.aspx )
-Messy registry (I doubt this and don't approve of registry cleaners)
-Known vista issues resounding around multiple displays, aero, dreamscape, and various display drivers. (none known for this OS)
-Known vista issues that sometimes cause corrupt information to be sent to the video card from system memory (will be addressed completely in SP2, has had various fixes applied since vista's release) (none known for this OS)
-Bad direct x files (uninstall, then reinstall DirectX)
-bad system files (System File Checker - was run above)
-Bad driver (some drivers will cause an event due to internal bugs, however these are not nearly as common as many think due to all of the previous things causing the same symptom) - (remove all 3rd party programs and check to be sure drivers aren't loading. Then install only the necessary 3rd party stuff, and ensure it's the latest version and that it's compatible with Win7)

Okay, there is a lot of information there, thank you!

I have uninstalled Daemon Tools.
I have uninstalled my "archived copy" of Rollercoaster Tycoon 3, and the FedEx driver just dropped off my brand new copy that I ordered from Amazon less than 20 hours ago.

I have put my video card back in the original spot as well. There was no real difference in the system in the other slot.

I have downloaded the Inquisitor LiveCD x86_x64 and I will give that a try after this post. I will let you know as soon as I am back in Windows.

I have gone ahead and re-executed SFC. Windows Resource Protection did not find any integrity violations.

The following hardware issues are examples that can cause a TDR event:
- Failing overclock on CPU or GPU
----- there is no overclocking on my system
- Bad sector in memory resulting in corrupt data being communicated between GPU and the system (either video or system memory)
----- MemTest ran for 9 hours and completed almost 8 full sets of tests. There were no RAM errors. I will execute the video memory stress test next.
- Corrupt hard drive/windows install resulting in corruption to the system registry or the page file
----- I have reset my page file, and we shall see if that makes a difference. If not, I will get the Seagate SATA test and run that.
- Over heating of GPU or CPU again resulting in corrupt data being communicated.
----- I think we have been over this piece of the puzzle, as the system runs fine for multiple hours playing really intense games like Starcraft 2 but it can't seem to play RCT3 for more than 30 minutes.
- GPU failure due to any sort of issue from insufficient power(VERY common) to heat.
----- I have used my power supply tester to make certain that the proper volts are going both to the video card and to the motherboard. I did not bother testing other power leads, such as hard drive and CD rom, at this time.

The following software issues are examples that can cause a TDR event:
-Incompatible drivers of any sort (either GPU, sound, etc)
----- Having used Verifier, I don't know if I have any incompatibility issues
-Messy registry
----- I went ahead and scanned the registry a day ago, and used a cleaner (sorry)
-Bad direct x files
----- I will uninstall and reinstall Direct X
-bad system files
----- Reviewed above in this post, all good
-Bad driver (some drivers will cause an event due to internal bugs, however these are not nearly as common as many think due to all of the previous things causing the same symptom)
----- If it comes to this, I am going to purchase a new hard drive to install Windows 7 on and see what happens. I don't want to format and install on this copy only to realize that it didn't help at all, as I have done 3 fresh installs of Windows 7 with a format during installation each time already.

Do not buy any more stuff until we've finished all the tests unless you've got the money to spare and don't mind experimenting. I'm able to do that and I've got a ton of spare parts laying around the house because of it!!!

Anyhow, I'm just about certain that there's a hardware failure here (although it could be an incompatibility). I can't recall, have you tried another video card?

Yes, I have already replaced my Radeon 5870 once. I went back to the local computer store that I purchased the card from, and they gave me a different card (they even said that the new card was a newer revision/bios on the card). I don't have any other cards, my other systems are laptops or have on-board video ... but I can go back to that local computer store and have them put a brand new 5870 (if they have one in stock) in the system and test the system.

I don't know what hardware pieces in my system could be incompatible. I don't have a lot in my system, and all the components have been listed as compatible with Windows 7.

I used a website linked from somewhere in the SevenForums that helps you ensure you have a large enough power supply. The listing of all my components recommended a 650W power supply, and I have a 750W. I know that is a "little" on the close side, and I kind of wish I had purchased a 1000W, but the system can deal with high-stress without any real problems.

I have run into a slight issue with Inquisitor. Make certain that you put a floppy disk in your drive (if you have one), otherwise it will fail the set of tests and you have to start again. Also, the first step in the "non-destructive test" is a full 30-minute CPU Burn-In, so that really adds to the time that it will take to test the system. So far, though, other than the floopy drive, I have not come across any errors with the test.

No need for another video card unless you thing you need to try one.
Can you purchase a higher wattage PSU from a store that will allow you to return it?

Another way to "test" the PSU is to remove some unneeded devices. That will draw less power from the PSU - and should lessen the frequency of problems (if that is the cause). The more that you're able to remove, the more noticeable the change should be.

Or, you could add more stuff and see if it makes the system die faster (I'm just sorta thinking out loud here)?

I just finished the Inquisitor tests, and everything turned out successfully using that tool.

I should be able to goto my local computer shop and get a different power supply. I did just have a new development. I ran the Inquisitor program in the primary CD drive in my computer, and now the button the front of the drive refuses to function. I know power is getting to the drive, as the light functions and I can hear the drive spin up. This started as I was getting ready to reboot my system following the Inquisitor Tests. When I hit reboot, the disk refused to eject from the system. I had to use the pinhole to get the disk out of the drive.

I am running the Video Card Memory Stress Test now, and it will take about another 2 hours. I will let you konw the results of that when I am finished.

I will head downtown and pickup a 1KW power supply this afternoon in order to test that possibility.

Video Memory Stress Test v1.7.116

WARNING: Your card can be not compatible with this test! If multiple errors will found, try test with onscreen buffer usage or wthout of ignoring colors bit mask.
Changing video mode to 640x480x16...OK
[6/12/2010 1:15:56 PM] Test started for "Primary Display Driver (ATI Radeon HD 5800 Series)"...
Trying 16bpp RGB:565 mode...OK
Trying 16bpp RGB:555 mode...OK
Trying 16bpp BGR:565 mode...NOT SUPPORTED (Code: 80004001)
Trying 32bpp RGB:888 mode...OK
Trying 32bpp BGR:888 mode...NOT SUPPORTED (Code: 80004001)
[6/12/2010 2:44:56 PM] Pass completed (0 errors found).

I guess this means that the Video Card is fine. I am going to head to town and get a power supply, based on your previous recommendations.

Also, that CD Rom Drive still will not open. It will not even open during the initial BIOS load/boot process. I think that might just be a separate issue. From Windows, when I right click the drive and click Eject, I get an error message. I think that might just be something with that drive specifically. Wierd. I probably will not replace it at this time though, I will wait until after replacing the power supply.

Disconnect the drive (both the power and the data cabled) and see if you still have issues.
Everything inside the system is interconnected - so a problem with the CD/DVD drive can reveal itself as freezing, etc.

The drive started working again. I powered the computer off for 15 minutes and I came back to install RCT3 off the new media that I got. I thought to myself, why not test one last time before going to town to purchase a new power supply. So I booted up, the drive opened, and I am installing off that same drive that was non-functional just half an hour ago. I will let you know how this test goes.