BSOD (IRQL_NOT_LESS_OR_EQUAL – 0x0000000A)

Toggle sidebar Toggle sidebar
C

Chopstixzz

Honorable
Mar 27, 2013
7
0
10,510
Hello,

About a month ago this screen turns up every few days.

http://i.imgur.com/YTsFHTz.jpg

I've already removed all the USB devices for a while, my windows is up to date and it's still happening. After this screen I'm also forced to do a startup repair.

Is there anything else I can do or try?
 
Solution
J
the info provided is not enough to determine the cause of this failure.
the bugcheck just indicated that the program located in memory at memory address 0xffff800034B19A1 (param 4) tried to read (param 3) from address
0xffffa908000001b (param 1) and the interrupt was set to 2 (param 2)
when the interrupt is set to 2 it means the data you want to access must all ready copied into memory. The problem was that the data was not in memory and the memory manager is not allowed to get it because the driver had priority over the memory manager. It just causes the driver to wait for the memory manager but the memory manager can not run because of the driver interrupt level was 2. The system just shut down because it would never...
Sort by date Sort by votes
BigBadBeef

BigBadBeef

Admirable
May 30, 2014
2,076
0
6,460
Your RAM is most likely dying, do a memory diagnostic, google your operating system and the keyword "memory diagnostic" to learn how to do that.

And I used to have a monitor just like yours... with 21:9 movies coming out, it really outlived its usefulness... "brick aspect ratio screens" we call them. ;)
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
the info provided is not enough to determine the cause of this failure.
the bugcheck just indicated that the program located in memory at memory address 0xffff800034B19A1 (param 4) tried to read (param 3) from address
0xffffa908000001b (param 1) and the interrupt was set to 2 (param 2)
when the interrupt is set to 2 it means the data you want to access must all ready copied into memory. The problem was that the data was not in memory and the memory manager is not allowed to get it because the driver had priority over the memory manager. It just causes the driver to wait for the memory manager but the memory manager can not run because of the driver interrupt level was 2. The system just shut down because it would never finish.

Now you need to find out what the driver was (most likely a bug in the driver or a corruption in the data the driver is trying to access).

generally, you can guess and update motherboard drivers or you can look at the memory .dmp file for the driver name.
often you will have to provide a kernel memory dump rather than a minidump, often you have to turn on verifier debugging flags to figure out which driver is causing the problem or is corrupting another drivers data.

ie start cmd.exe as an admin, run
verifier.exe /standard /all
reboot and see if you get another bugcheck, if verifier catches a error it will name the driver in the memory dump file.

 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom