IRQL NOT LESS OR EQUAL crash after Windows 10 upgrade, dump file attached

[Slizzl]

Hi.
I keep getting IRQL NOT LESS OR EQUAL crashes about 1-3 times a day after upgrading to 10, I've tried a clean install of OS, resetting BIOS settings and driver updates, so I'll just ask here.
I'll just copy paste some info and hopefully it makes more sense to you than me, if you need more please tell me.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000003994482379, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000070, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8034c902239, address which referenced memory

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000003994482379

CURRENT_IRQL: 0

FAULTING_IP:
nt!PpmIdlePrepare+289
fffff803`4c902239 488bce mov rcx,rsi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

TRAP_FRAME: ffffd001969f17a0 -- (.trap 0xffffd001969f17a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000003984b834a6 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8034c902239 rsp=ffffd001969f1930 rbp=ffffffffffffffff
r8=0000000000000000 r9=ffffd001969f1b60 r10=000000130dd4bd8d
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
nt!PpmIdlePrepare+0x289:
fffff803`4c902239 488bce mov rcx,rsi
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8034c9c14e9 to fffff8034c9b6940

STACK_TEXT:
ffffd001`969f1658 fffff803`4c9c14e9 : 00000000`0000000a 00000039`94482379 00000000`000000ff 00000000`00000070 : nt!KeBugCheckEx
ffffd001`969f1660 fffff803`4c9bfcc7 : ffffd001`969c7180 fffff803`4c803fa9 00000000`00003505 00000013`0dd4ab1a : nt!KiBugCheckDispatch+0x69
ffffd001`969f17a0 fffff803`4c902239 : 00000000`05309702 00000000`00328c15 00000000`00000001 ffffe000`ab86a010 : nt!KiPageFault+0x247
ffffd001`969f1930 fffff803`4c901228 : 00000000`00000000 00000000`00000002 ffffe000`ab86a0f0 00000000`00000000 : nt!PpmIdlePrepare+0x289
ffffd001`969f1b00 fffff803`4c9b96cc : ffffffff`00000000 ffffd001`969c7180 ffffd001`969d3cc0 ffffe000`aac5b840 : nt!PoIdle+0x1b8
ffffd001`969f1c60 00000000`00000000 : ffffd001`969f2000 ffffd001`969ec000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!PpmIdlePrepare+289
fffff803`4c902239 488bce mov rcx,rsi

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!PpmIdlePrepare+289

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5775e2f5

FAILURE_BUCKET_ID: X64_AV_nt!PpmIdlePrepare+289

BUCKET_ID: X64_AV_nt!PpmIdlePrepare+289

Followup: MachineOwner

 

[MeanMachine41]

Go to your Device Manager and check all drivers for any yellow triangles.
It appears a W8.1 driver is installed and could be the fault.

 

[azaran]

Thats typically a memory issue. Have you done any RAM or HDD diagnostics?

 

[Slizzl]

Go to your Device Manager and check all drivers for any yellow triangles.
It appears a W8.1 driver is installed and could be the fault.

I just did a check and there's no yellow triangles.

Thats typically a memory issue. Have you done any RAM or HDD diagnostics?

I did a test using Memtest86+ a couple of days ago and got 7 passes and no errors.

 

[smorizio]

make sure the mb has updated bios to rule out a bios bug. download hardware info 64 bit set it tto sensor and logging see if any of the power supply rails are not holding. run intel cpu test make sure it not a cache error.

 

[MeanMachine41]

Have you tried looking in Event viewer for any clues as to why the Kernel error is occurring.?
Run "SFC /SCANNOW" without the quotation marks in an elevated prompt to see if any windows files have been corrupted.

 

[Slizzl]

Have you tried looking in Event viewer for any clues as to why the Kernel error is occurring.?
Run "SFC /SCANNOW" without the quotation marks in an elevated prompt to see if any windows files have been corrupted.

Did SFC /SCANNOW and it detected nothing. I'm not really sure what I'm supposed to be looking for with Event Viewer.

make sure the mb has updated bios to rule out a bios bug. download hardware info 64 bit set it tto sensor and logging see if any of the power supply rails are not holding. run intel cpu test make sure it not a cache error.

I've done a Intel CPU test earlier and it passed. Tried hwinfo64 and there doesn't seem to be anything wrong with the power supply rails. I'm not really sure how to update BIOS, but I guess I can try. BIOS Version says American Megatrends Inc. P11-A2, 02.07.2013, how can I update it?

 

[MeanMachine41]

That critical event in event viewer was generated because your system did not shut down correctly. So no help there.
It is best now to have your complete BSOD dump file analyzed.

The guys at Windows 10 Forum: http://www.tenforums.com/ will do this for you and are experts at it. There is a product called Bluescreenview by Nirsoft if you want to try Analyze yourself.

This is a link to show you what your dealing with: https://blogs.technet.microsoft.com/askcore/2008/10/31/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners/

 

[Slizzl]

That critical event in event viewer was generated because your system did not shut down correctly. So no help there.
It is best now to have your complete BSOD dump file analyzed.

The guys at Windows 10 Forum: http://www.tenforums.com/ will do this for you and are experts at it. There is a product called Bluescreenview by Nirsoft if you want to try Analyze yourself.

This is a link to show you what your dealing with: https://blogs.technet.microsoft.com/askcore/2008/10/31/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners/

Thanks for the info, I'll give it a shot.