BSOD playing BattleField3 Beta, Error IRQL_NOT_LESS_OR_EQUAL

[sandrodago]

Hello, so i've been getting BSOD's constantly when I play any graphically intense games. I have a pretty good video card and it never over heats so I know it's not that it get's too hot.

I am running the nVidia Beta driver 285.38 (needed for Battlefield 3 beta).

Running:
Win7 64-bit Professional
Full retail version.
Recently re-installed. (a month ago)
Hardware is a month old. Recently upgraded everything.
GPU: MSI GTX560 TI Twin Frozr II .

This only happens in game, and I'm uncertain as to why. the video card is brand-new, i just got it 2 weeks ago and it's worked with every other game up till now.

I'm going to be running MEMTEST 4.2 tonight and post my results tomorrow.

attached are my reports and DUMP files.

Please help sevenforums, you're my only hope.

 

[zigzag3143]

Hello, so i've been getting BSOD's constantly when I play any graphically intense games. I have a pretty good video card and it never over heats so I know it's not that it get's too hot.

I am running the nVidia Beta driver 285.38 (needed for Battlefield 3 beta).

Running:
Win7 64-bit Professional
Full retail version.
Recently re-installed. (a month ago)
Hardware is a month old. Recently upgraded everything.
GPU: MSI GTX560 TI Twin Frozr II .

This only happens in game, and I'm uncertain as to why. the video card is brand-new, i just got it 2 weeks ago and it's worked with every other game up till now.

I'm going to be running MEMTEST 4.2 tonight and post my results tomorrow.

attached are my reports and DUMP files.

Please help sevenforums, you're my only hope.

Combination of things

1-You obviously upgraded because you have drivers from as far back as 2005. They need to be updated.

RTCore64.sys    5/25/2005 2:39:12 AM        fffff880`08881000    fffff880`08887000    0x00006000    0x42941d90                        
Razerlow.sys    11/7/2005 2:33:11 AM        fffff880`0653e000    fffff880`06543280    0x00005280    0x436ef527                        
SaiH8000.sys    4/4/2008 7:26:34 AM        fffff880`05e5b000    fffff880`05e85480    0x0002a480    0x47f6106a                        
spldr.sys    5/11/2009 12:56:27 PM        fffff880`01b84000    fffff880`01b8c000    0x00008000    0x4a0858bb                        
GEARAspiWDM.sys    5/18/2009 8:17:04 AM        fffff880`05462000    fffff880`0546f000    0x0000d000    0x4a1151c0

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

2-Your crashes appear to be caused by several things but I cant be sure till you update the drivers. The most recent one was caused by DirectX (your video driver). I would start by re-installing the driver with the newest available using this method.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using

Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

After the above I would run these two tests


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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[sandrodago]

wow, I had no idea, that my previous drivers were still there even after i did a fresh install of the new drivers. I;; try the driver wipe and then move on to memory test tonight.

Thanks for the help, if all that fails ill move on to the Driver Verifier and post back here most probably tomorrow with my results. Thank You Very Much!

 

[sandrodago]

I ran Driver Sweeper and sweeped all nVidia drivers and software from my pc, and then installed the 285.38 Beta driver again. if it BSOD's then I'll go back to the official Released version which is 280.XX.

After running MemTest for 9 passes, there were no errors, so we can rule out anything MOBO and RAM related.

As for the out of date druvers, there's a problem. One of the drivers, that is out of date is for my mouse "razerlow.sys". The problem is that there arent any newer drivers, as the mouse itself is old. Should I get a new Mouse? aswell the "SaiH8000.sys" is for my keyboard, would you recommend me getting new input devices all together?

I simply uninstalled the "RTCore64.sys" driver, it was for the MSI Afterburner program. and both "spldr.sys" & "GEARAspiWDM.sys" are Windows 7 components drivers so it shouldn't be those nor do i want to touch those.

I'm going to try and play again, and if it still goes BSOD then I'll run the Driver Verifier and post back here.

Thanks for all the help!

 

[zigzag3143]

I ran Driver Sweeper and sweeped all nVidia drivers and software from my pc, and then installed the 285.38 Beta driver again. if it BSOD's then I'll go back to the official Released version which is 280.XX.

After running MemTest for 9 passes, there were no errors, so we can rule out anything MOBO and RAM related. Good news

As for the out of date druvers, there's a problem. One of the drivers, that is out of date is for my mouse "razerlow.sys". The problem is that there arent any newer drivers, as the mouse itself is old. Should I get a new Mouse? aswell the "SaiH8000.sys" is for my keyboard, would you recommend me getting new input devices all together? Re-install in compatibility mode.

I simply uninstalled the "RTCore64.sys" driver, it was for the MSI Afterburner program. and both "spldr.sys" & "GEARAspiWDM.sys" are Windows 7 components drivers so it shouldn't be those nor do i want to touch those. Leave them be

I'm going to try and play again, and if it still goes BSOD then I'll run the Driver Verifier and post back here.

Thanks for all the help!

Good to see you are making progress. Hopefully the changes will fix the BSOD's but if not verifier will tell you which driver is causing it.