Windows 7: BSOD 0x0000000A IRQL_NOT_LESS_OR_EQUAL

SirZ · 18 Mar 2012

Hello. Appeal to you for help, because I do not know what to do next. Sorry for my terrible english.

This BSOD starts after I upgrade my computer (I change MB, CPU, RAM). 1st under suspicion got the old system with many drivers from other old MB's. I reinstall it with fresh drivers from ASUS & Nvidia sites - but nothing happen. I still got BSOD on many different programs (mostly on games & GPU decoded videos, but few times system crashed in skype).
Ok, I reinstall system again with ASUS drivers from a CD. Few days system works fine - but today I have this BSOD again.

I scan my system with:
'SFC /scannow' - all good.
'MemTest86' - 10 test passed without errors.

Logs in attach. My system configuration in my forum profile.

zigzag3143 · 18 Mar 2012

MOST likely your 4 year old creative drivers
Related to ctac32k.sys Creative AC3 SW Decoder Device Driver (WDM) from Creative Technology.

These crashes were caused by memory corruption/exception (probably a driver).
Please run this test to find which driver is causing the problem.

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

* If you have raid update its Driver.

Driver verifier

Quote:

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/Windows 7 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 "Special Pool", "Force Pending I/O Requests" and "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.

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.

SirZ · 19 Mar 2012

Hello. I have done all that is written in last post. Logs in attach.
After reboot I have immediately BSOD with other error "DRIVER_VERIFIER_IOMANAGER_VIOLATION".
Driver in log 'SscRdCls.sys+12d4' - it's RAM disk driver. This is my PC problem? But why? In old configuration all works perfectly.

zigzag3143 · 19 Mar 2012

Quote: Originally Posted by SirZ

Hello. I have done all that is written in last post. Logs in attach.
After reboot I have immediately BSOD with other error "DRIVER_VERIFIER_IOMANAGER_VIOLATION".
Driver in log 'SscRdCls.sys+12d4' - it's RAM disk driver. This is my PC problem? But why? In old configuration all works perfectly.

Driver verified and related to your Ramdisk/ramdisk Plus. You need to disable it at least to test. Yours is from 2007

SirZ · 20 Mar 2012

Yesterday I delete RAM disk program with driver SscRdCls.sys.
Few minutes ago I have BSOD from 1st post again (logs in attach).

Now I start 'verifier' to debug again.

SirZ · 20 Mar 2012

Sorry for frequent posts, but new BSOD with active 'verifier' did not take long.
New error: KMODE_EXCEPTION_NOT_HANDLED 0x0000001e. Logs in attach.

zigzag3143 · 20 Mar 2012

Quote: Originally Posted by SirZ

Sorry for frequent posts, but new BSOD with active 'verifier' did not take long.
New error: KMODE_EXCEPTION_NOT_HANDLED 0x0000001e. Logs in attach.

Driver verified and related to memory corruption.

If you havent run memtest you need to, if you have run it for 6-8 passes then keep running verifier.

SirZ · 24 Mar 2012

I again tested my RAM with memtest (20 passes without errors) I run verifier - anyway I have BSOD.

Ok, if Windows said what problem in my RAM I need to dig in this way.

First I compared recommended RAM settings from Corsair and setting what I have in my BIOS. Everything was normal (I don't change anything in BIOS setting, all it be default).

Then I tried activate 'X.M.P.' in BIOS memory setting, and you know, BSOD's are gone! 3 days I can't get this BSOD's with my methods, I think problem is solved.

zigzag3143 many thanks for helping me!

Windows 7: BSOD 0x0000000A IRQL_NOT_LESS_OR_EQUAL

BSOD 0x0000000A IRQL_NOT_LESS_OR_EQUAL problems?