BSOD While Gaming

BeKure said:

I get a lot of blue screen crashes happening while I play video games. It happened a lot when I played Rift and now that I'm playing Star Wars the Old Republic, it happens as well. It is very frustrating to say the least. I only really notice it while gaming. I have enclosed a DMP zip.
Any help would be appreciated.

Thank you.

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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).

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.

Driver Verifier - Enable and Disable


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users


Also


Old driver that need updating

Code:

Alpham264.sys        3/20/2007 4:51:03 AM        fffff880`02ab5000    fffff880`02aba500    0x00005500    0x45ffae87                    
regi.sys        4/16/2007 10:19:10 AM        fffff880`097e6000    fffff880`097ee000    0x00008000    0x462393ee                    
Alpham164.sys        7/23/2007 2:57:03 AM        fffff880`02aa8000    fffff880`02ab4f00    0x0000cf00    0x46a45f4f                    
Mo3Fltr.sys        9/17/2008 9:50:37 PM        fffff880`06d6d000    fffff880`06d70200    0x00003200    0x48d1c1fd                    
ALSysIO64.sys        4/19/2009 2:41:04 PM        fffff880`09fa5000    fffff880`09fad000    0x00008000    0x49eb7e50

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads


Finally Your Avast is complicit in many of these.


I notice your avast which is often at least a contributing cause of BSOD'S . Please remove and replace your Avast with Microsoft Security Essentials AT LEAST TO TEST


http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows

BeKure said:

regi.sys, and Mo3Fltr.sys, are not even installed on my PC. I deleted the software a while ago. Why would the drivers still be present? If they are in fact still present, how do I delete them completely?

Alpham164.sys and ALSysIO64.sys I did in fact just update though so thank you.

I got rid of avast and installed Microsoft Security Essentials like you suggested and I haven't blue screened in game since but...
I still am having trouble while gaming because I keep getting a error that says my game has "stop working". Although it is not blue screening it is still force closing during game sessions, which is not as bad as blue screening but still annoying.

They are indeed installed and Loading. I couldnt just pull their names out of a hat.

To prevent them from loading you can rename them from Alpham164.sys to Alpham164.bak, etc


That will at least keep them from loading.

Old drivers can easily cause freezing, and lagging.

BeKure said:

zigzag3143 said:

BeKure said:

regi.sys, and Mo3Fltr.sys, are not even installed on my PC. I deleted the software a while ago. Why would the drivers still be present? If they are in fact still present, how do I delete them completely?

Alpham164.sys and ALSysIO64.sys I did in fact just update though so thank you.

I got rid of avast and installed Microsoft Security Essentials like you suggested and I haven't blue screened in game since but...
I still am having trouble while gaming because I keep getting a error that says my game has "stop working". Although it is not blue screening it is still force closing during game sessions, which is not as bad as blue screening but still annoying.

They are indeed installed and Loading. I couldnt just pull their names out of a hat.

To prevent them from loading you can rename them from Alpham164.sys to Alpham164.bak, etc


That will at least keep them from loading.

Old drivers can easily cause freezing, and lagging.

Can't I just uninstall or delete them? Where would I find the drivers anyhow? The software that its associated with these drivers was deleted some time ago. I have searched for these drivers on my PC and can't find them anywhere.
I used Memtest86 and the test claims that there are no errors with my hardware so I assume it's a driver of some sort but like I said I cant find regi.sys, or Mo3Fltr.sys anywhere on my computer.
Please help.

Emitted from my Droid Bionic via Tapatalk

You can delete them if you can find them. So memtest passed but verifier? I havent seen any DMP files that are verifier enabled.

17 of 25 are caused by memory exceptions. The verified ones are Related to Mo3Fltr.sys WinDDK from Microsoft Windows Hardware Compatibility Publisher.

I would remove WinDDK and the old drivers which are still loading even in the newest crash

All the crashes involve the old drivers BTW.

Code:

Alpham264.sys    3/20/2007 4:51:03 AM            fffff880`06b12000    fffff880`06b17500    0x00005500    0x45ffae87                    
Alpham164.sys    7/23/2007 2:57:03 AM            fffff880`06b05000    fffff880`06b11f00    0x0000cf00    0x46a45f4f                    
Mo3Fltr.sys    9/17/2008 9:50:37 PM            fffff880`0a093000    fffff880`0a096200    0x00003200    0x48d1c1fd

BeKure said:

zigzag3143 said:

BeKure said:

Can't I just uninstall or delete them? Where would I find the drivers anyhow? The software that its associated with these drivers was deleted some time ago. I have searched for these drivers on my PC and can't find them anywhere.
I used Memtest86 and the test claims that there are no errors with my hardware so I assume it's a driver of some sort but like I said I cant find regi.sys, or Mo3Fltr.sys anywhere on my computer.
Please help.

Emitted from my Droid Bionic via Tapatalk

You can delete them if you can find them. So memtest passed but verifier? I havent seen any DMP files that are verifier enabled.

zigzag3143 said:

17 of 25 are caused by memory exceptions. The verified ones are Related to Mo3Fltr.sys WinDDK from Microsoft Windows Hardware Compatibility Publisher.

I would remove WinDDK and the old drivers which are still loading even in the newest crash

All the crashes involve the old drivers BTW.

Code:

Alpham264.sys    3/20/2007 4:51:03 AM            fffff880`06b12000    fffff880`06b17500    0x00005500    0x45ffae87                    
Alpham164.sys    7/23/2007 2:57:03 AM            fffff880`06b05000    fffff880`06b11f00    0x0000cf00    0x46a45f4f                    
Mo3Fltr.sys    9/17/2008 9:50:37 PM            fffff880`0a093000    fffff880`0a096200    0x00003200    0x48d1c1fd

Alpham164.sys and Alpham264.sys are drivers that are associated with a gaming keyboard. The manufacturers website (SteelSeries) states that the lastest drivers were posted 2011-02-22 and I installed these drivers yesterday. Should I uninstall them anyway?

Mo3Fltr.sys is a driver associated with a gaming mouse that I no longer own. I even uninstalled the software from my PC. I have no idea where these drivers are hiding. this is very frustrating to say the least.

I have no idea what WinDDK is or where to find it on my system. I tried searching for it using windows search tool. I don't even see WinDDK on the Driver Reference Table.

With all these mysterious drivers it might be faster (and easier) to do a clen install. Do you have the win 7 dvd?