BSOD irql not less or equal

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
L

Luds_1234

Commendable
Aug 10, 2016
39
0
1,530
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.
Click to expand...

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

Thanks for the help :)
 
Solution
Sohom
Ok, now it seems its the processor. Did you bend any motherboard pins while installing the processor, if so that could cause problems.
There's also another logic, i.e, you may be unlucky to receive bad ram sticks twice; but again thats a shot too far.
I think its your cpu.
Sort by date Sort by votes
I am not certain its not hardware related still as it shouldn't bsod as much loading drivers. You might need to contact Asus as its their board and it seems their drivers causing it?

you can't install most drivers in safe mode, that is normal. not all windows services are running then either.

did anyone ever respond on tenforums?

where did you get steps for edits 1 & 2? (I would remember if i pointed you at registry)
 
Upvote 0 Downvote
Hi,
I noticed that I ran an old version of Memtest.
So I ran Memtest with V7 and now I keep having errors.
I tried each stick in every slots, I always get errors.
I think I can conclude the motherboard is broken right?
 
Upvote 0 Downvote
Not all ram is tested for the motherboards, list doesn't include everything.

how did you choose parts? right now, if i were making a PC up I would use a site like PC partpicker that once you choose certain parts won't offer things that won't work with them. those parts are usually motherboard and CPU, as they most obvious.

Ask Asus since it seems you need to talk to them anyway. I doubt both sticks would have errors on them, but you never know.
 
Upvote 0 Downvote
Thanks.
I choose the parts based on advise of a former colleague.

I just tried with a new Ram stick, I still get errors on Memtest.

If I understand correctly, I should now try another motherboard but it could be the PSU or CPU as well?
 
Upvote 0 Downvote
i would expect that it is the motherboard itself. though I have been wrong before and have seen the other two parts you mention cause errors, the fact you keep getting errors from ram slots on a consistent basis would make me think replacing motherboard should stop them all.

The other parts are more likely to make PC turn off randomly (PSU) or cause other BSOD that you haven't seen (CPU) so the best place to start is motherboard. I have read that of the two parts that arse more likely to fail between CPU & motherboard, its more common for it to be motherboard

All of the errors were related to parts on motherboard itself... i just read through the thread again, come a long way. Hope I am right about motherboard...
 
Upvote 0 Downvote
Hi,
So I changed the motherboard (MSI
Z170A KRAIT GAMING 3x).

I no longer have Memtest errors but... When I boot from the usb windows 10 installer I have BSOD with 0x000021a error.

Is there something I have done wrong? Could it be the CPU?
I have updated the bios with last version. Tried without gpu. Tried with different ssd/hdd.
 
Upvote 0 Downvote
that is a windows error, it doesn't point at any hardware, but windows itself. Normally when you get it, its on an installed copy of windows, not when you are trying to install.
Reasons Behind the Error 0Xc000021A:
This issue arises when Windows is updated. So, after the update, it doesn’t boot to Windows and displays this blue screen of death along with error. There are two files that are the major cause of this error to appear. These files are listed below.

winlogon.exe: As the name of the file represents, this file is responsible for the login and logout operations inside Windows. This file can be damaged due to mismatch of System Files or 3rd party softwares. If this file gets damaged, then this error causes the PC to boot to the Windows Login.
csrss.exe: The second file causing this error is Csrss.exe. This .exe file belongs to Microsoft server or client. So, this file can also be damaged resulting this error.
Click to expand...

https://appuals.com/how-to-fix-error-0xc000021a-in-windows-8-and-10/

so as you got it on 2 different drives, I would get you to make a new ISO on another drive, and remove the USB itself from possible causes.
 
Upvote 0 Downvote


what i meant was use the media creation tool to make a new installer on another USB.

Not sure it will help, believe its likely it is something like the CPU. Did we ever run Intel Processor Diagnostic Tool? (this will only work if windows installed. Did you get bsod during or after install?

 
Upvote 0 Downvote
The motherboard should had fixed such problems, coz most of the times its RAM or the RAM slots... Just check whether the RAM sticks are inserted properly... Have you checked the hard diskdrives... Try downloading HDDSentinel (https://www.hdsentinel.com/download.php) and check the SMART attributes...
And another thing, try changing the SATA cables, though i guess you are using the new ones that came with the new mobo, but doesn't hurt to check once.
Also, try using the motherboard USB ports while installing windows and not your front panel USB.
If you have a DVD writer/ROM, unplug that for the time being, Run using only the bare minimum requirements with one stick ram and one SSD. Even unplug your GPU for the time being.
 
Upvote 0 Downvote
So, new RAM, clean SSD (clean on another computer), new boot USB => BSOD system thread exception not handled.

It restart then I was able to choose Language and Windows version. It's been 15min now and still stuck at first screen "Setup is starting". Not sure if I should restart and reclean the disk
 
Upvote 0 Downvote
I manage to launch the installation of windows, I got BSOD system service exception.

Now when restarting => The computer restarted unexpectedly or encoutered an unexepected error. Windows instrallation cannot proceed.
 
Upvote 0 Downvote
too many errors for an install. Something is just not right here.

New motherboard,
ram sticks should be fine, as you used 2 lots.
It has to be CPU or PSU at this point, All the intel errors are a clue, intel management engine interface is there to let hardware to talk to windows, so it crashing could be a sign of CPU being cause. There are ways to run Intel Processor Diagnostic Tool outside windows but you have to use linux. Loading linux on PC might tell you if its working - http://www.tcsscreening.com/files/users/IPDT_LiveUSB/index.html

there are only so many parts that effect install
CPU (if its overclocked it can cause bsod, if its bad it will as well)
Motherboard - you have a new one
RAM - you tested 2 types
PSU - I haven't seen PSU do this much, its more likely to corrupt drivers or cause freezes/restarts. Not stop installs from being done. Always a 1st time though.
Storage - you have tried a few.

nothing else effects data
 
Upvote 0 Downvote
Ok, now it seems its the processor. Did you bend any motherboard pins while installing the processor, if so that could cause problems.
There's also another logic, i.e, you may be unlucky to receive bad ram sticks twice; but again thats a shot too far.
I think its your cpu.
 
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