Windows 8.1 IRQL_NOT_LESS_OR_EQUAL and SYSTEM_SERVICE_EXCEPTION

Chaze117

Commendable
Dec 18, 2016
10
0
1,510
Hello everybody!
So this two BSOD errors appeared with a fresh windows, the IQRL first appeared two or three weeks after installing a new RAM module I already tested both of my modules (overnight) no errors, as I searched over the internet I know you need my dump files so here is it. Dumps

Please somebody tell me what can cause this errors I don't know much how search in this dump files.

Thank you.
 
irq errors associated with ntfs.sys. that is part of windows file system.
other driver mentioned actually part of windows kernel. Downside of who crashed isn't it doesn't always tell me enough or points at windows.

I don't think they tied to the ram, more the hdd. Seems odd you get the errors out of the blue,

Is PC custom build or brand name? What have you got?

If custom, have you got latest drivers from the motherboard makers? I suspect its a sata driver
If its brand name, do you have its latest drivers of manufacturers web site for model?
 
Custom Built. On Gigabyte's site the Intel SATA Preinstall driver is 2 years old and I only find Intel® Rapid Storage Technology drivers on Intel website, but I installed that.

I downloaded WinSDK and analyzed the dump files with WinDbg. So at this point 3 files causes the BSOD
MsMpEng.exe -> Windows Defender, now it's turned off.
svchost.exe
csrss.exe
 
last 2 parts are parts of windows
svhost = service host
csrss.exe = Client/Server Runtime Subsystem in the Microsoft ® Windows operating system utilizes the process csrss.exe for managing the majority of the graphical instruction sets under the Microsoft Windows operating system.

so report may blame them but they not generally the cause. Do you have latest drivers for GPU?

who crashed just blamed ntkrnlmp which is also windows, for both the system service exception & irq errors. can you give us a screen shot of what the debugger outputted and I see if I can see anything else in there.
 
Here is the WinDbg log from the latest crash Link

Edit:
So I updated my Bios to F5a Beta because a strange thing appeared when I turned off my PC it turns back on and error message with boot failure (I'm not sure, it was too late sorry) and option with reset the system defaults. By the way turning off the WinDefender reduced the BSOD amount.

Update:
After running driver verifier for two days it crashed with DRIVER_VERIFIER_DETECTED_VIOLATION and blamed the mv91cons.sys driver so I updated the Marvell driver, the original driver from the MoBo DVD. I hope the best
 
Did we ever run memtest86 on the ram? the program creates a bootable USB so run it without windows, test 1 stick at a time, any errors are too many. If you get errors, stick needs to be removed/replaced but from what you say, it might not be the sticks themselves.

Maybe ram is fine and its the memory slot itself... cause if both work fine in 1 slot, it might be the one slot not in use when you only use the 1 stick. So when you run memtest, vary the slots too. If both sticks test fine in 1 slot, try the other with a stick you know works

6 months ago I didn't blame ram but have run into a few cases since that were ram, so I changed my mind.
 
I tested them with memtest86 separately and together too, all test ran about 4 hours, no error as I said my last post the BSOD only occur if the rams run in dual channel. Interesting thing I installed windows 7 for some old software and I got much less BSOD and what appeared not memory releated.

Yesterday one of my friend said maybe it's the PSU, luckily I have an other PC to thest this.

 
what were the bsod you get in win 7? it would be using different drivers so I be curious what they are?

what are actual parts in PC? How many memory slots on Motherboard? can you run both sticks in different channels?

are both sticks out of a set or are they just the same size?
 
I think you mentioned you added a stick of ram,this might give incompatibility issues. Can you give us the partnrs of the ram? Other thing you can do if no bsod occurs is the next,

download hwinfo32,
install and open it=click run,
close the top window which is the system summary,
at the left top click "save report",
at the bottom of the next window check "short text report",
after that you'll see what's in the pc,
copy by clicking "copy to clipboard" and rightclick+paste in your next respons

A artikel that says why it might cause this,
http://www.tomshardware.com/reviews/ddr-dram-myths,4155.html#p4
look at "Just Adding More Dram".
 
Computer: GIGABYTE Z87X-UD7 TH
CPU: Intel Core i5-4460 (Haswell-DT Refresh, C0)
3200 MHz (32.00x100.0) @ 3192 MHz (32.00x99.8)
Motherboard: GIGABYTE Z87X-UD7 TH-CF
Chipset: Intel Z87 (Lynx Point)
Memory: 16384 MBytes @ 798 MHz, 10-10-10-30
- 8192 MB PC12800 DDR3 SDRAM - Kingston KHX1600C10D3/8G
- 8192 MB PC12800 DDR3 SDRAM - Kingston KHX1600C10D3/8G
Graphics: GIGABYTE GeForce GTX 960 IX OC
NVIDIA GeForce GTX 960, 2048 MB GDDR5 SDRAM
Drive: ST1000DM003-1ER162, 976.8 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: SanDisk SD8SBBU240G1122, 234.4 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: Marvell Console, Processor
Sound: Intel Lynx Point PCH - High Definition Audio Controller [C2]
Sound: NVIDIA GM206 - High Definition Audio Controller
Network: Intel I217-V (ClarkvilleV) Network Adapter
Network: Intel I210AT Copper (Springville) Network Adapter
OS: Microsoft Windows 10 Professional (x64) Build 14393.1198 (RS1)


Sometimes my MoBo starts with C6 code sometimes with 51 code and that means BSOD
 
The sticks run at default at 1.5V which is about as low as these ones do.You could add some voltage and see if this will give some stability,like setting it to 1.55V in the bios.You can go up as high as 1.65V if necessary without issues.



Are you sure about the C6? Can't find that one in the manual. The other,51, seems to be a memory issue.
 
C0~CF Reserved.
A little more specific when I select the OS (doesn't matter 10 or 7) it changes 62, something (too fast I cant read it) then 51. It must be something with the dual channel I ran both ram stick about two weeks separately no BSOD.
I read other forums and who has 50-55 error code the PC didn't turn on or restarted after 2-3 secs.
I found one post from 2013 about this error the guy said Thunderbolt caused the 51 error code, I tried to turn it off but I don't find it anywhere in the bios.

Update: Today evening I started the PC with C6 (win10 autostarted no chance to select win 7) then swhitched into 51 (sadly I don't know when, I went to have some food) about after minute when I logged on it switched to A0
 
Yes I tried, same error code, I think the problem is the slot so next month when I got my salary I RMA the motherboard and if they say can't reprair and can't send me an other I can buy stuff from the mb price I buy a new mb with 1151 socket new CPU and new memory.