IRQL Not Less or Equal/ Stop: 0x00000A (or 1E)

[Saintzer0]

More and more I am getting these BSOD's lately while I am playing resource heavy games (skyrim/swtor).

The Last known good configuration seemed to help for a few days, but the BSODs are back.

Video card is updated, Memtest86 shows nothing wrong, Video Stress test is good.

I am at a loss at this point and have no idea where to go from here. Hope the crash info can shed some light.

note: perfmon report shows no antivirus but I am indeed using microsoft security essentials.

 

[zigzag3143]

More and more I am getting these BSOD's lately while I am playing resource heavy games (skyrim/swtor).

The Last known good configuration seemed to help for a few days, but the BSODs are back.

Video card is updated, Memtest86 shows nothing wrong, Video Stress test is good.

I am at a loss at this point and have no idea where to go from here. Hope the crash info can shed some light.

note: perfmon report shows no antivirus but I am indeed using microsoft security essentials.

Memory corruption (probably a driver) please run driver verifier to find out which.

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

 

[Saintzer0]

I actually just tried the driver verifier procedure just before posting. Upon next reboot it crashed immediately. One of the crash dumps I uploaded is from that crash. Not sure what to next and wondering if driver verifier was to blame I disabled it after startup repair. System crashed again.

 

[zigzag3143]

I actually just tried the driver verifier procedure just before posting. Upon next reboot it crashed immediately. One of the crash dumps I uploaded is from that crash. Not sure what to next and wondering if driver verifier was to blame I disabled it after startup repair. System crashed again.

None of the previous DMPS were driver verified. It is supposed to make your system crash when it finds the offending driver. It is the best way to find the driver.

 

[Saintzer0]

So the object is to MAKE the system crash from Driver verifier to collect the necessary dump data which will tell which drivers are at fault? Sorry I'm not to knowledgeable on this stuff yet.

 

[zigzag3143]

So the object is to MAKE the system crash from Driver verifier to collect the necessary dump data which will tell which drivers are at fault? Sorry I'm not to knowledgeable on this stuff yet.

Yes. You see the only way verifier can write the name of the driver is by the DMP log created in the crash.

It doesnt always give you an answer the first time.

 

[Saintzer0]

It came up as Usbfilter.sys. Which I googled and ended up back on this site.
So i replaced the old with the new, tried the verifier reboot and so far no BSOD (3hours ago)
I have been doing the same things that crashed it before and its good so far.

Btw, is there a "legit" driver service that can let you know when ANY driver you have is out of date?

 

[mgorman87]

What kind of power supply do you have?

Can you also upload a full report
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[Saintzer0]

So it crashed again. This time getting the stop error 0x0000007F.

Not sure on the manufacturer of the power supply but it is 1000 watt.
I am NOT overclocking at all.
Not sure if bios update is needed.
Might try Memtest 86 again tomorrow when I get off work.

Latest perfmon report and dump file uploaded

 

[zigzag3143]

So it crashed again. This time getting the stop error 0x0000007F.

Not sure on the manufacturer of the power supply but it is 1000 watt.

I am NOT overclocking at all.
Not sure if bios update is needed.
Might try Memtest 86 again tomorrow when I get off work.

Latest perfmon report and dump file uploaded

Both were 7F

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:


Cause

Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.
A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows.



In your case a double vault caused by a driver. You obviously did not have driver verifier at the time of either of these crashes so we are inconclusive about which driver is at fault.

Run verifier.

Malware not detected in perfmon, UAC off

 

[Saintzer0]

I wonder if the usbfilter.sys driver I just updated is at fault. I'm certain I selected the best possible options from the drop downs on the asus site. Should I reinstall the driver as well?

 

[zigzag3143]

I wonder if the usbfilter.sys driver I just updated is at fault. I'm certain I selected the best possible options from the drop downs on the asus site. Should I reinstall the driver as well?

Probably not. It isnt a critical OS file so you could rename it just to check. Rename it usbfilter.bak

 

[Saintzer0]

Had no crashes for almost 24 hours then a new one. Computer was running slow in the meantime.

PAGE_FAULT_IN_NONPAGED_AREA
0x00000050

Not sure if verifier would be in the dump files as I shutdown the system after use just in case but here is the info as usual.
You guys are saints and I would be up **** creek without you. I really appreciate this.

 

[Saintzer0]

0x000007F BSOD
Maybe I should run memtest again? 1 stick at a time?

 

[Saintzer0]

and the latest dump - page fault in non paged area again

 

[zigzag3143]

and the latest dump - page fault in non paged area again

This one was Related to idmwfp.sys Internet Download Manager WFP Driver from Tonec Inc. I would remove it at least to test.

 

[Saintzer0]

I uninstalled Internet download manager. Stressed system again for about an hour and it crashed again
I wonder if my not be able to open the ati catalyst control center has anything to do with all this

 

[zigzag3143]

I uninstalled Internet download manager. Stressed system again for about an hour and it crashed again
I wonder if my not be able to open the ati catalyst control center has anything to do with all this

It might but we cant tell without the DMP files. Upload them.

 

[Saintzer0]

Still more and more frequent BSOD's Seems to be going longer before crashing than before. Dumps and report uploaded

 

[zigzag3143]

Still more and more frequent BSOD's Seems to be going longer before crashing than before. Dumps and report uploaded

This one is inconclusive. The only way we are going to get specific information is by running verifier (again)

Just to be sure can you run Malwarebytes.

Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!