BSOD playing WoW and Skyrim, IRQL_NOT_LESS_OR_EQUAL

Hello,

some times, when I play at World of Warcraft or Skyrim I get an IRQL_NOT_LESS_OR_EQUAL BSOD.
I have:

• Windows 7 Professional 32bit
• Intel(R) Core(TM)2 Quad CPU @ 2.40GHz
• Gigabyte GA-P35-DS3 motherboard
• 4GB Micron 16HTF12864AY-667B3 RAM
• ATI Radeon HD 5770
• Realtek ALC885/889A/890 @ Intel 82801IB ICH9

I already tried to:

1. Update all available motherboard drivers;
2. Update graphic card and sound card drivers;
3. Run a memtest.

The problem is still here. I attach the last minidump file I got this morning.

Could someone help me to solve this problem?




Regards,


Lorenzo


Attachment 190606

LorenzoC said:

Hello,

some times, when I play at World of Warcraft or Skyrim I get an IRQL_NOT_LESS_OR_EQUAL BSOD.
I have:

• Windows 7 Professional 32bit
• Intel(R) Core(TM)2 Quad CPU @ 2.40GHz
• Gigabyte GA-P35-DS3 motherboard
• 4GB Micron 16HTF12864AY-667B3 RAM
• ATI Radeon HD 5770
• Realtek ALC885/889A/890 @ Intel 82801IB ICH9

I already tried to:

1. Update all available motherboard drivers;
2. Update graphic card and sound card drivers;
3. Run a memtest.

The problem is still here. I attach the last minidump file I got this morning.

Could someone help me to solve this problem?




Regards,


Lorenzo


Attachment 190606

Old drivers

Code:

SSPORT.sys    11/21/2006 11:41:42 PM        0x95000000    0x95007000        0x00007000    0x4563d506                    
npf.sys    11/6/2007 3:09:15 PM        0xa0d57000    0xa0d5db00        0x00006b00    0x4730c9eb                    
WinRing0.sys    7/26/2008 8:25:10 AM        0xa5938000    0xa5939980        0x00001980    0x488b25b6                    
a5mmlyj9.SYS    3/21/2009 9:47:30 AM        0x94d0e000    0x94d46000        0x00038000    0x49c4fe02                    
ssmdrv.sys    5/5/2009 5:05:18 AM        0x9335f000    0x93364a00        0x00005a00    0x4a000f5e                    
L8042Kbd.sys    6/17/2009 11:50:16 AM        0x94cd4000    0x94cd7500        0x00003500    0x4a391ec8

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


Please run verifier to find which one is causing this



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

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