BSOD irql not less or equal

[Luds_1234]

Hello,

I have built a gaming PC last year and since day one I've been getting BSOD with typically this kind of messages:
irql not less or equal
page fault in nonpaged area

At that time, I handled that by disabling the automated page file.

But since today I keep having thoses message again. I tried to re-enable the default page size but it still crash more often.

Computer :
Asus Z170-A
i5-6600K
GTX 1070
2 x G Skill Ripjaws F4-2133C15-8GRR
CT250BX100SSD1 (250 GB, SATA-III) (Windows)
Crucial_CT525MX300SSD1 (525 GB, SATA-III) (Games)

Last whocrashed report:

On Wed 02-08-17 17:40:02 your computer crashed
crash dump file: C:\WINDOWS\Minidump\080217-5125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0xA (0xFFFFFA862A03ED48, 0x2, 0x0, 0xFFFFF8027EB0A794)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 02-08-17 17:40:02 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA862A03ED48, 0x2, 0x0, 0xFFFFF8027EB0A794)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 02-08-17 16:28:59 your computer crashed
crash dump file: C:\WINDOWS\Minidump\080217-5437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x50 (0xFFFFFD02A203D461, 0x10, 0xFFFFFD02A203D461, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 02-08-17 15:50:28 your computer crashed
crash dump file: C:\WINDOWS\Minidump\080217-5812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0xF7 (0x6692BFF56ECF, 0x6E92BFF56ECF, 0xFFFF916D400A9130, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 02-08-17 15:37:52 your computer crashed
crash dump file: C:\WINDOWS\Minidump\080217-5718-01.dmp
This was probably caused by the following module: hdaudbus.sys (HDAudBus+0x2EE8)
Bugcheck code: 0xD1 (0xFFFFA087C5DD04EC, 0x2, 0x1, 0xFFFFF80795632EE8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\hdaudbus.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: High Definition Audio Bus Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Mini dumps are here : https://drive.google.com/drive/folders/0B-Mr6iz5C17QQjFiQU5kSmxudkk

Thanks for the help

 

[Colif]

netio.sys is normally lan drivers, according to you we updated them earlier so lets see what I find... yep, you have latest version now.

AsIO.sys is still there - dated 2012... haunting us Program might be called Asus Probe 2, its also possible its a left over from something else but then it shouldn't be running

that is only old driver. Did you post on that other forum?

If you cannot get rid of asIO then I would suggest looking at a reset. It will wipe everything on C drive and force win 10 to reinstall new drivers. Its a hammer approach but if you can't get rid of driver, it should fix it.

just copy everything off C you want to keep. then go to settings/update & security/recovery
select reset this PC
choose keep files/settings (at least this keeps logins and contents of library folders (so documents, pictures, videos, music))
PC will restart and reinstall win 10

 

[Luds_1234]

I just follow your procedure and reset windows.

So far so good, let's see on longer period

Beside GeForce Experience and Realtek drivers, what drivers do you advise me to install ?

 

[Luds_1234]

Okay... So as some software were'nt running well after reset (missing dll's etc), I decided to do a clean install of windows from usb.
During windows installation I had 3 BOSD with similar errors.
I zipped the dumps here : https://drive.google.com/file/d/0B-Mr6iz5C17QMmdDRDBydjVyMTA/view?usp=sharing

 

[Colif]

As you know, I can't read dumps but errors during install are not normal and might lead us to look at checking ram for errors (it really depends on the errors you are getting). MOst common cause is Memory so we shall start there.

I would download memtest86 on another PC and run it, it will create a bootable USB you can use to test ram sticks in PC. Test 1 stick at a time, any errors are too many. Only score you want is 0. If you get any stick needs to be removed/replaced

Bad ram could explain why random programs kept crashing as well.

 

[gardenman]

I was going to mention that I viewed these earlier and didn't find anything interesting in them. I think it lists 1 driver and generic filenames and crashes.

Here's the info on the 3 new dumps: https://pastebin.com/cVsepD84

 

[Colif]

I was going to mention that I viewed these earlier and didn't find anything interesting in them. I think it lists 1 driver and generic filenames and crashes.

Here's the info on the 3 new dumps: https://pastebin.com/cVsepD84

IRQ errors, yep... looks like ram or something like that. If they had been WHEA errors or similar, I would have to look elsewhere.

Run memtest and see if it finds anything. run tests for up to 8 hours.

 

[Luds_1234]

As you know, I can't read dumps but errors during install are not normal and might lead us to look at checking ram for errors (it really depends on the errors you are getting). MOst common cause is Memory so we shall start there.

I would download memtest86 on another PC and run it, it will create a bootable USB you can use to test ram sticks in PC. Test 1 stick at a time, any errors are too many. Only score you want is 0. If you get any stick needs to be removed/replaced

Bad ram could explain why random programs kept crashing as well.

Thanks,
I just launch a new Memtest.

Is it possible to run games/windows with a deffected ram? A few days ago everything was OK. Then it started with random bosd.

 

[Colif]

I think programs can run fine with corrupted ram, as it depends on if the corrupted parts are being used or not. You have 16gb of ram so there is always the chance the corrupted parts had never been used until recently. I hardly ever use more than 4gb so there is a chance the other stick in my PC is corrupted but as I never use enough ram for PC to use the extra stick, I may never know.

conhost.exe is used by command prompt
msoobe.exe = MS out of box experience, used for registration and activation of licence.

oddly, the only driver mentioned is.... this seems familiar... e1d65x64.sys which as we all know, is Intel LAN drivers. How can that be causing any problems on a fresh install where it shouldn't even be there yet? were these errors during the install process or after it?

 

[Luds_1234]

Errors occurred after installation, during the last wizard and or after reboot.

I'll let Memtest for 8 passes for first stick then try a reinstall. If I encounter new bosd I ll conclude that it is not coming from the ram.

I'll keep you posted

 

[Colif]

try doing install and not be attached to internet, i can only guess windows might be grabbing drivers in the last stage and getting intel driver. that or its built into win 10 and then I have to start to think it might be hardware

that driver matches this Intel controller - Intel-Ethernet-Connection-I218-LM, i have worked out tonight there have been multiple different chips for each Intel board released in last few years. Driver version 22.4.0.1 is the latest version for it released 16th June 2017

figuring out if that is right driver for what you have is another question, I have to think microsoft can figure that out somehow?

 

[Luds_1234]

Ok I think it is dead now...

I tried to install without ethernet or other disk and only one stick. I had a BSOD.

I wanted to try the same with antother stick. No screen... no bios nothing.

There is a red light with 'Mem Ok' blinkg on the motherboard...
I hope I did brun my motherboard :/

I'm thinking to get it to a shop :/

 

[Colif]

it might be as simple as a memory stick not being in slot correctly, as motherboard won't start if ram isn't in right. Also depends on what slots you used, did you put them back in the same slots they were in before? Board has 4 slots, usually have to have 2 sticks in 1 & 3 to get them to work in dual channel, if you put them in 1 & 2 for instance it may not work. http://www.tomshardware.com/answers/id-2512824/dram-led-solid-red-video-output-asus-z97-mobo.html

This only started after you ran memtest after all.

You can take to store if you want, I wasn't expecting it to go this way after the way it started, looked like you just had software problems. Let us know how you get on

 

[Luds_1234]

Indeed the sticks were not deep enough in the slots :s
I'm trying a new window installation on another ssd.

I'll let you know

 

[Colif]

Indeed the sticks were not deep enough in the slots :s
I'm trying a new window installation on another ssd.

I'll let you know

that is a relief

 

[Luds_1234]

OK so I installed windows on other ssd => got bsod.

I removed one stick =>got bsod.
I removed stick and replace with the other one => got bsod.


Can I safely say that it's not related to ram or ssd?
What else then? :/
Did I made a mistake when building pc?
Is there something that I should change in the bios?

 

[Colif]

Now is when you take it to a shop and ask them to figure it out. It might be the board itself. not a lot left. At least it should still be under warranty
Store should at least have spares they can swap in that they know work.

you tested ram - no errors?
you used 2 SSD - both got bsod which seems unlikely so I think you could remove ssd from cause (unless you really unlucky) - could be sata cables maybe, depends on errors
only parts that might have anything to do with data that remain are motherboard and CPU and both hard to test really (You didn't get any errors that pointed at CPU)

what bsod are you getting? is it always the same or different? Anything new?

 

[Luds_1234]

Now is when you take it to a shop and ask them to figure it out. It might be the board itself. not a lot left. At least it should still be under warranty
Store should at least have spares they can swap in that they know work.

you tested ram - no errors?
you used 2 SSD - both got bsod which seems unlikely so I think you could remove ssd from cause (unless you really unlucky) - could be sata cables maybe, depends on errors
only parts that might have anything to do with data that remain are motherboard and CPU and both hard to test really (You didn't get any errors that pointed at CPU)

what bsod are you getting? is it always the same or different? Anything new?

Last Whocrashed


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-C1073IE
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., Z170-A
CPU: GenuineIntel Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17115959296 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 05-08-17 14:01:16 your computer crashed
crash dump file: C:\Windows\Minidump\080517-3656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0xD1 (0xFFFFFA0EA67210F0, 0xFF, 0x72, 0xFFFFFA0EA67210F0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 05-08-17 14:01:16 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0xFFFFFA0EA67210F0, 0xFF, 0x72, 0xFFFFFA0EA67210F0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 05-08-17 13:54:25 your computer crashed
crash dump file: C:\Windows\Minidump\080517-3421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x50 (0xFFFFCB65BEE1E730, 0x0, 0xFFFFF803DC26F40C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 05-08-17 13:42:13 your computer crashed
crash dump file: C:\Windows\Minidump\080517-4281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0xF7 (0xD1D9DC65EE66, 0xD1D1DC65EE66, 0xFFFF2E2E239A1199, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 05-08-17 13:37:39 your computer crashed
crash dump file: C:\Windows\Minidump\080517-4796-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF808BAA1E7CD)
Bugcheck code: 0xD1 (0xFFFFF80FD03D8440, 0x2, 0x0, 0xFFFFF808BAA1E7CD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

I have run memtest but not waited for 8 passes. I'll do that now.

Since I built it my self and bought parts online, I don't have a real shop to ask :s

 

[Luds_1234]

Latest minidump https://drive.google.com/drive/folders/0B-Mr6iz5C17QbV9qY202MmJkVEE?usp=sharing

 

[Colif]

oh, so windows works, its just giving errors? I thought it wasn't working at all...

where did you get drivers from? have you installed any?

tcpip is LAN so did you go to Asus web site and grab latest LAN drivers? Its probable that you are using generic drivers

how often does it crash?

 

[Luds_1234]

Yep now I have windows installed since I noticed the ram was not properly installed in their slots.

I did not reinstall drivers yet and ethernet was not plugged. Is it still possible it is not hardware so?

It crashes randomly, sometimes after 30min, sometimes after 2 min.

 

[Colif]

see if it crashes in safe mode.. if its just drivers, it shouldn't

go to settings/update & security/recovery
under advanced startup, click restart now button
choose troubleshoot
choose advanced
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
PC will restart and load safe mode

you can't so much in safe mode but it only uses windows drivers so shouldn't crash if the cause is other drivers installed. Windows update may have grabbed some for PC already if you didn't.

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://pastebin.com/ef6e7VtY

Spoiler

File: 080517-3656-01.dmp (Sat Aug 5 08:01:16 2017)
BugCheck: [DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)] {fffffa0ea67210f0, ff, 72, fffffa0ea67210f0}
Probably caused by: ntkrnlmp.exe (Process: System)

File: 080517-3671-01.dmp (Sat Aug 5 07:08:20 2017)
BugCheck: [DRIVER_OVERRAN_STACK_BUFFER (F7)] {67fad00a5be5, 675bd00a5be5, ffff98a42ff5a41a, 0}
Probably caused by: ntkrnlmp.exe (Process: svchost.exe)

File: 080517-3703-01.dmp (Sat Aug 5 07:00:45 2017)
BugCheck: [ATTEMPTED_WRITE_TO_READONLY_MEMORY (BE)] {ffff82d00cd84a88, 8000000000400121, ffffd501b45f7700, a}
Probably caused by: memory_corruption (Process: System)

File: 080517-4281-01.dmp (Sat Aug 5 07:42:13 2017)
BugCheck: [DRIVER_OVERRAN_STACK_BUFFER (F7)] {d1d9dc65ee66, d1d1dc65ee66, ffff2e2e239a1199, 0}
Probably caused by: ntkrnlmp.exe (Process: System)

File: 080517-4359-01.dmp (Sat Aug 5 06:58:30 2017)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)] {fffffe8c78556290, 2, 0, fffff803c01da22d}
Probably caused by: msrpc.sys (Process: System)

File: 080517-4796-01.dmp (Sat Aug 5 07:37:39 2017)
BugCheck: [DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)] {fffff80fd03d8440, 2, 0, fffff808baa1e7cd}
Warning: Unable to verify timestamp for: e1i63x64.sys
Probably caused by: e1i63x64.sys (Process: amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.1439_none_7efe016621f5)

File: 080517-3312-01.dmp (Sat Aug 5 07:07:06 2017)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)] {ffffffffc0000005, fffff802eacd4fd5, 0, ffffffffffffffff}
Probably caused by: memory_corruption (Process: consent.exe)

File: 080517-3421-01.dmp (Sat Aug 5 07:54:25 2017)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)] {ffffcb65bee1e730, 0, fffff803dc26f40c, 2}
Probably caused by: memory_corruption (Process: svchost.exe)

I can't help you with this. Wait for someone else to reply. Good luck.

 

[Colif]

only 3 drivers total

Intel management engine interface
Intel LAN driver (there isn't a newer version of this on intel site but if you look on Asus site for motherboard there is one from last month, under LAN
Steelseries engine

none are that old at all.

The only thing I have missed along the way is the fact there is a newer bios to one you are on. That could be the difference, it was released 21 July 2017.

Z170-A BIOS 3503
1. Improve System Performance and stability
2. Fix Plextor device issue
3. Fix some VGA card can't boot into OS or Setup when "Above 4G Decoding" is enabled.
4. Fix Logitech keyboard issue
5. Fix compatibility issue with some large size HDD

https://www.asus.com/au/Motherboards/Z170-A/HelpDesk_Download/

you update bios by downloading that file, unzipping it onto USB, start PC into BIOS, look on tools menu and run the updater. Instructions should be in the manual

updating bios could help the programs actually work. Otherwise, it looks like something is wrong with motherboard itself as the drivers loaded don't look that out of place, especially since you only had 3.

 

[Luds_1234]

Hello,
Last update.

I ran memetest and had 0 errors after 8 passes.
I ran windows in safemode for a few hours and had no crash (I did not do much in it but see it running without bsod's was satisfaying).

Does it mean it might no be hardware related?

I'll install the drivers you recommend me tonight.

 

[Luds_1234]

Hi,

When in safe mode, I try to install drivers (Intel Management Engine Interface), I have the following error :
The Windows Installer Service count not be accessed.

I can not update windows in safe mode neither, I thing this can be related.

When running windows normally, I have BSOD pretty quickly.

Edit: When checking in msconfig, the service Windows Installer is stopped

Edit2: I follow few steps to enablie msiserver but I keep getting the error:
system error 1084 has occurred this service cannot be started in safe mode

As suggested I remove the option subkey in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SafeBoot
but it does not change anything