BSODs with different error codes, all of them include ntoskrnl.exe

Hello everyone!

One of the computers at work is crashing with BSODs. The error code is different in each crash. For the last three weeks I've been trying to figure out what is it that it's causing the BSODs, updating drivers and removing a memory module that was added.

I have yet to cicle the original memory module between the 2 memory slots, and then do the same with the other memory module, but due to the fact that each BSOD happens once every 5 days or so, that would take a lot of time.

So, following the instruccions, I've attached all the suggested info.
Here's some additional info that I hope will help.

OS related details:

• Current OS:Windows 7 Enterprise x64, all updates installed (includes SP1)
• Original OS: Windows XP
• Re-installed OS about 2 months ago (It had the same OS before, but this is a clean install)
• People told me the BSOD problem existed even when the computer had Windows XP running

HW related Details/Specs

• Dell Inspiron 1520 (Notebook)
• Cumputer is 3 or 4 years old
• CPU: Core2Duo T5250 1.5GHz
• Memory: 4GB DDR2 (2 modules, 2GB each). Last crash happened with computer running with only one module
• Graphics an everything else: Intel Mobile 965 chipset family.
• HDD: Western Digital 120GB WDC WD1200BEVS-75UST0

Error codes (in cronological order):

1. IRQL_NOT_LESS_OR_EQUAL 0x0000000a
2. BAD_POOL_CALLER 0x000000c2
3. MEMORY_MANAGEMENT 0x0000001a
4. IRQL_NOT_LESS_OR_EQUAL 0x0000000a

Well... I think that's all.

Thanks in advance.

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!!!

* If you have a Raid update its Driver.



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-7 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+






Driver Verifier

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.

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

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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

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

Driver Verifier

Using Driver Verifier (Windows Drivers)