[SOLVED] BSOD IRQL_NOT_LESS_OR_EQUAL || BSOD SYSTEM_SERVICE_EXCEPTION - Windows 7 x64

gisakux

Member
Joined
May 12, 2015
Posts
21
Here is the crash dumps

I will upload the MEMORY.DMP FILE too

https://www.dropbox.com/sh/n4uzop4vt...YjHz6GL0a?dl=0


I have tried to:

Update my bios to latest version
memtest86 14 passes without any errors ( because I also got BSOD MEMORY_MANAGEMENT before bios where updated,
but it seems to have been fixed)
reinstalled my video drivers


I can send you my computer specs if you want to, I build the computer myself and it works fine except I think there is a hardware problem with the drivers or so, really appreciate your help

PS: later that day I had no problem, played for 2-3 hours, the problems seems to occur randomly, sometimes after half hour, sometime it doesn't occur within the time I use the computer. It crashes mostly during when I play games or open launcher.

Regards Matteas
 
Code:
1: kd> .bugcheck
Bugcheck code 0000000A
Arguments fffffa80`0d998e50 00000000`00000002 00000000`00000001 fffff800`01eab5ce

Code:
1: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0de11818 fffff800`01e77e69 : 00000000`0000000a fffffa80`0d998e50 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0de11820 fffff800`01e76ae0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0de11960 fffff800`01eab5ce : 00000000`00000000 fffff680`001386f8 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x260 (TrapFrame @ fffff880`0de11960)
fffff880`0de11af0 fffff800`01eaa807 : 00000000`00000000 fffff680`00138b78 fffffa80`073747b0 fffff800`020327c0 : nt!MiDeletePteRun+0x504
fffff880`0de11ca0 fffff800`01e65daf : fffffa80`00000000 00000000`2716ffff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`0de11e60 fffff800`01e77b53 : ffffffff`ffffffff fffff8a0`0b994588 fffff8a0`0b9945b0 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0de11f60 fffff800`01e74110 : fffff880`0383562e fffff8a0`0b7338d0 fffffa80`073747b0 fffffa80`0730ff00 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0de11f60)
fffff880`0de120f8 fffff880`0383562e : fffff8a0`0b7338d0 fffffa80`073747b0 fffffa80`0730ff00 fffff8a0`0b994580 : nt!KiServiceLinkage
fffff880`0de12100 fffff880`03820c93 : fffff8a0`00000000 fffff8a0`09da8010 00000000`00000001 fffffa80`0a1cf000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`0de12130 fffff880`0381b637 : fffffa80`07720490 00000000`00000001 fffff8a0`0b7338d0 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11b
fffff880`0de121e0 fffff880`03801ecc : 00000000`00000000 fffff880`00000000 00000000`00000010 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0de122b0 fffff880`04300ccc : 00000000`00000000 fffff8a0`0b52f000 fffff8a0`0b52f000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0de122e0 fffff880`0430065f : fffff8a0`0b52f000 fffff8a0`0b530300 fffff8a0`00000000 fffff880`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0de123d0 fffff880`0432e883 : 00000000`00000008 fffff8a0`09d561d0 fffff8a0`0b392f10 fffff880`0de127f0 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`0de12420 fffff880`0432dfaf : fffff8a0`0b392f10 fffff8a0`0b392f10 fffff880`0de12780 fffff880`0de127b0 : dxgkrnl!DXGCONTEXT::Present+0x2cb
fffff880`0de12740 fffff960`001ea9f0 : fffffa80`07387b50 00000000`0c40e840 00000000`0bdf7010 00000000`00000001 : dxgkrnl!DxgkPresent+0x543
fffff880`0de12ab0 fffff800`01e77b53 : 00000000`06e805f0 fffff880`0de12b60 00000000`2d4b3014 00000000`0cf45f90 : win32k!NtGdiDdDDIPresent+0x18
fffff880`0de12ae0 000007fe`fd92145a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0de12ae0)
00000000`0c40e588 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fd92145a

Code:
1: kd> .trap fffff880`0de11960
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800de11a60 rbx=0000000000000000 rcx=fffff8800de11a60
rdx=000000000006afd9 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001eab5ce rsp=fffff8800de11af0 rbp=fffffa80014110b0
 r8=fffffa80073747b0  r9=0000000000000000 r10=0000000000000000
r11=fffff8800de11ac0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiDeletePteRun+0x504:
fffff800`01eab5ce f0410fba6e1000  lock bts dword ptr [r14+10h],0 ds:00000000`00000010=????????

Looking at the trapframe regarding the exception that caused the bug check, it was a LOCK prefix with BTS instruction, specifically to perform a read/write on r14+10.

Given the Direct X kernel calls and memory related functions throughout the stack and read/write failures generating exceptions, I'd say this is a bad video card.
 
Okey so the BSOD will keep poopin up random while I have this video card? Can I make it work somehow or should I just get a new video card?

It is a GTX 460 that I have used on another computer and it worked fine there.
 
Remove it for now and either use a secondary video card or onboard video. If you crash, it's not likely a GPU problem but maybe board related. I doubt it's graphics drivers related.
 
Okey I will do that if I get one more BSOD, because I clean the registry with some programs and some other cleanups and played today for 4-6 and have had the computer on for a longer time and I haven't got any problems so far, can I somehow trigger the BSOD to occur so I know if the problem still exist?
 
Yesterday I played for 6 hours and nothing happend, but today I started my computer again, went down for a half an hour and when I come back it said an error has occured (Bluescreen)

Capture.PNG

What do you think is the problem? , should I remove the video card for now or do you think it is something else according to this last error (picture)
 
Okey I will remove it for now, if I don't get any BSOD for X days does it mean it was the video card?

I will test at first with onboard video and if it seems to work fine for some days I will try with a different video card
 
Hi again Patrick, it seems no problem when the pc is running on the onboard video, I then tested one last time my video card (gtx 460, the one you called bad) in the pc and got BSOD. So then I switched video card with my other computer(main) to see if I still get BSOD with another video card (gtx 670). So far I have not got any problem with this other video card(gtx 670) on that computer.

But the thing is the video card you said were bad (gtx 460) don't get any BSOD on my other computer (main). Why is that so? Could it be that the video card does not work properly with the first computer I tried with and that is why it gets BSOD?

Really want to figure this out if the problem is with the video card, so I don't buy a video card and then get the same problem I got with this video card.
 
Test it extensively in the other computer, like for a few days to a week. If no crash in the other computer, it's either bad drivers for your video card which you'll need to experiment with a few versions until you find the right one, or possibly a bad power supply.

I say that, because it may not be providing enough power for it to run.
 
I see , my brother in law said the same thing, but I have the same power supply for both computers.

If you mean test the bad video card in my main computer, so have it been there before I bought my other video card (670). I have used it for about 3 years so it felt that it should worked on my second computer (the one Im trying to fix).

So should I put back my "bad video card" on my second computer, but downgrade some versions and experiment?
 
I see , my brother in law said the same thing, but I have the same power supply for both computers.

The same as in same manufacturer, or the exact same one (i.e you're unplugging it from computer #1 and using it for computer #2)? If the latter, then it's not the power supply. If the former, then it can still be the power supply. It's not the manufacturer that I imply is the problem, it's just the specific power supply itself on its own. It could be failing.

Also, what I mean is, use the video card that crashes your main computer in the secondary computer for awhile. At least a week. If still no crashes, it's not the video card itself, but either as I said a video driver issue on your main computer, or the main computer's power supply provided it's the same manufacturer, but actually a different one.
 
Ohh okey, it is the same as manufacturer. I think then that could be the issue cause I have used that video card for both computer, the one I used in first worked fine, but when I changed to the secondary then it's when I got the BSOD, which could be a video driver issue as you also said.

Let say it is a video driver issue, what do you suggest I should do? Cause I have used the video card in that computer before.

Also if it is the power supply that is failing do you mean that it is failing just for that specific video card?
 
Let say it is a video driver issue, what do you suggest I should do? Cause I have used the video card in that computer before.

You'll need to experiment with a few driver versions until you find the right one for your card/computer.

Also if it is the power supply that is failing do you mean that it is failing just for that specific video card?

No, it's damaged and should be replaced.
 
Okey I will try them out, thanks for all the help so far, do you want me to upload another MEMORY.DMP file or is it not helpful?
 
You're welcome.

do you want me to upload another MEMORY.DMP file or is it not helpful?

Not necessary at the moment, as we have enough info to prove either video card, power supply, or video drivers. Thanks though.
 
I got two BSOD when I was trying to update some launchers (battle.net and League of Legends). First I got PFN_LIST_CORRUPT and then SYSTEM_SERVICE_EXCEPTION

Should I now try a different version on my video driver?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top