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

Another suggestion from the ATI Forums was to download CCleaner (Registry Cleaner). So I completed that as well. It did clear out some items that were unrequired. I will see if there is any difference when I get home.

I went through Verifier ... I did find a single driver that caused the BSOD on boot up. FSProLabs mprifl.sys This was for a program that I used called MyLockbox, a basic folder hiding/encryption software. I have uninstalled this software.

However, this did not resolve my issue. After removing the MyLockbox software, I deleted the Verifier settings, checked all non-microsoft Verifier drivers, and the system rebooted successfully. I then removed the verifier settings and restarted. I then opened Roller Coaster Tycoon 3, played for about 15 minutes, and then the game froze, the screen went black, the video card driver unloaded, then reloaded, and then BSOD atikmpag.sys.

I have attached the files that were listed in the three problems. Two problems with files occured first, then the ShutDownUnexpected Minidump. I have also uploaded these new files to my SkyDrive linked in the first post.

You've done most everything that I would do.
This is definitely a video issue - but it I don't recall if you've tried any other cooling solutions (pointing a house fan - on high - into the case at the video card).

Also, when it crashes, unplug it from the wall, grab hold of the metal of the case with one hand, and then CAREFULLY poke around inside the case looking for hot stuff (you may burn yourself if not careful!).

Have you scanned the Prime95 screen output when the test runs to see if there were any errors/failures listed in the output (it won't always crash the system)?

Will check back this afternoon with any more suggestions I might think of.
Good Luck!

I believe the system has plenty of airflow, as this is a CM Storm Sniper case. There are 4 120mm fans, and one of them points directly at the video card. Yesterday afternoon, I sat down and tried to "tune" my fan settings to reduce the heat signature a little bit, so my video card does not surpass 75 degrees C.

Immediately following making this change is when I started up Roller Coaster Tycoon 3, and it crashed on me. Also, last night happened to be raid night for my guild, and I was able to play WoW for 3 1/2 hours solid without anything bad happening at all. We downed 5 bosses and made attempts on Lich King, so if something was going to stress out my machine a little, that would have been it.

When I ran Prime95, I did not notice any errors within that application. Everything appeared to be normal within the output files. It has been a few weeks since I tested the RAM, today I am going to setup my system to run memtest while I am at work ... it should be able to make about 10 passes during the day. Maybe that will result in something different.

Thanks for the help!

Hmm ... I just read something that really made me think. When I am playing RCT3, there is one major difference between doing much of anything else ... I am using Daemon Tools to run the game without the disk. I bought this game years ago, and, like most games I purchase, I make an archival backup just in case something happens to the original ... well guess what ... something happened to the original disk. So, I am using the image running on my hard drive loaded through Daemon Tools. I read another post that some people have experienced many unusual issues with Daemon Tools, and I am starting to think that this might be my issue. At this time, I think I am going to head out and purchase a new Platinum Edition to replace my RCT3 set. Then I will completely uninstall Daemon Tools and try playing off the new game disk. If I don't crash, then I will know that the issue has been Daemon Tools this whole time. *sigh*

Y'know, most BSOD's are solved by the owners - not by us analyzing things.
This may be the clue that we need.

If you've already uninstalled Daemon Tools - try running a copy of RCT3 from the CD/DVD to see if that'll cause a BSOD. Try this both with and without Driver Verifier running (using the settings outlined below)

If you haven't uninstalled Daemon Tools, run Driver Verifier and then run RCT3 to generate a crash (unless the 061010-23197-01.dmp file was caused by doing that). FYI - that dump file is a Verifier Enabled Minidump and it blames the ATI driver again.

Also, if it's still crashing on you, let's try looking at your MSINFO32 report:

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

And the Event Viewer log files:

Event Viewer Log Files
Please provide us with copies of these 2 logfiles:
- Go to Start and type in "eventvwr.msc" (without the quotes and press Enter
- Expand the Windows Logs category by clicking on the arrow/+ sign to it's left
- Right click on the Application log and select "Save all events as" and name it Application
- Then, right click on the System log and select "Save all events as" and name it System
- Zip up the log files and upload/attach them with your next post.

NOTE: If the log files are too big to upload to the forums, please upload them to a free file hosting service and provide us with the link to the files.

In the end, it's usually the sptd.sys file (located in C:\Windows\System32\drivers) that causes the BSOD's.

I'd suggest running Driver Verifier again using these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Looking at the memory dump files I found this driver:

Code:

a4d8cipw.SYS Tue Jul 14 17:12:55 2009

A google search revealed nothing about it. This is either a suspicious entry (malware) - or it's related to something that a program like Daemon Tools does (makes a driver to mount the file(s))

Thank you for the great recommendations!

I just got home, and after running MemTestx86 for 9 hours, it made 7 complete passes over the RAM and it was 88% complete through an 8th pass with no errors whatsoever. I rebooted into Windows and came here first to read.

I have completed creating my restore point.

I have the System Info, Application Log, and System Logs all zipped up, but I am getting a failure to upload message from the forums. Instead, I have uploaded to my skydrive.

SystemInfo_AppLog_SysLog.zip - 2.75MB - Public - Windows Live

I have NOT removed Daemon Tools yet, as I thought about another test while I was at work. I am about to enable Verifier again, per your instructions, and when the system crashes, I will upload those log files. Also, I plan to load an ISO DVD movie file and play that in Windows Media Player. If I get a crash from that as well, then we know that the issue stems from Daemon Tools.

Daemon Tools version 4.35.5.0068
SPTD Version 1.62 (was listed on the DT About Screen as well)

I will message back after the Verifier tests ...

I turned on Verifier. I played the RCT3 for a little bit, and the computer did freeze, but I did not have the crash that I usually have.

This time, the screen just went black. The video driver did not unload, and I did not get a BSOD. I did not get any issues listed in the Action Center / Problems area, nor did I get any minidump. There was also nothing in the System or Application Logs of note. I know the system locked up completely, but I have no idea what caused it, and I don't appear to have any logs that help me in this case.

Should I proceed with uninstalling Daemon Tools? I ordered a brand new copy of RCT3 from Amazon today, and it should arrive at my house tomorrow. That should replace my "archival backup" and I won't need Daemon Tools in order to play (only sucks because I have paid for the game twice now LOL).

Anyway, I also ran a DVD movie from Daemon Tools for about 3 hours, and nothing bad happened. No crashes, but for some reason Windows Media Player wouldn't play the audio ... played video just fine, but no audio. I switched over to VLC Media Player, and the movie ran perfectly.

I also found one other item that was causing a little trouble.

Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 6/11/2010 6:08:45 PM
Event ID: 219
Task Category: (212)
Level: Warning
Keywords:
User: SYSTEM
Computer: XavierSysWin7
Description:
The driver \Driver\WUDFRd failed to load for the device Root\SIDESHOW\0000.

I periodically got two of these Warnings in my System Event Log. This was apparently from my Logitech G15 Keyboard and an incompatibility with Windows SideShow (Monochrome) and Windows SideShow (Color) programs within the G15 LCD Manager. I have disabled these programs (uncheck BOTH boxes on either side).

Well, I tried something unconventional ... Before any of this, I disabled Verifier, as when the game crashes, it only freezes and never goes to a BSOD, nor does it log anything in any log that I am able to locate. So, I downloaded a NO CD executable in order to by-pass Daemon Tools. I have not yet uninstalled DT, but I was not using it with the game or in any other capacity. The game still crashed after about 15-20 minutes of gameplay with the normal driver unload/BSOD. I have attached this dump to the post in a zip file - 061110-20623-01.dmp

I also right clicked the game file, and I asked it to troubleshoot compatibility. This requested that I execute the game, which I did, and it crashed with the usual driver unload/BSOD but this time was faster than the other attempts, probably within 3 minutes of starting the scenario. This dump is also in the zip file - 061110-19656-01.dmp

Both list atikmpag.sys as the likely issue, but I just don't understand how can this be the issue when Driver Verifier doesn't state it as being the issue, or having any issue with much more complex games and stress test/benchmarks!

Is there something other than a stress test for video cards? Something like MemTestx86 that will verify components on the physical card and test them directly? 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.

You know ... something else just came into my head. Maybe it is the PCI-E slot on the motherboard. Maybe it is having an issue. I have three separate PCI-E slots, and there are two that are x16 ... I am going to shut down and move my card to the other slot on the motherboard (that is, if there is enough airflow and space between that slot and the power supply). I will try that really quickly.