BSOD - PAGE_FAULT_IN_NONPAGED_AREA - issues after new pc parts.

ArtoSimonyan

Reputable
Feb 2, 2015
5
0
4,510
Hey, so recently I purchased a new PC parts and the troubles began.

The only thing which I'm sure it was working is my video card (AMD Radeon r9 280x) which I've been using in my previous build.

I've been getting quite a lot and different BSOD messages and I'm not quite sure what exactly is causing them.

Things I've tried to resolve the issue:

> Installed all drivers from the official vendors.
> Updated BIOS to latest available version.
> Reinstalled my OS to be sure everything is correctly installed.
> Took out ram sticks one by one to see if there is an issue with either of my 2 sticks ( did not find any).

My hardware & Setup is as follows:

OS: Win 8.1 Pro 64 bit
SSD: ADATA Premier Pro SP920, SSD 256G
Motherboard: ASRock Z94 Anniversary
CPU: Intel I5-4460
Video Card: Sapphire Vapor-X R9 280x
RAM: GEIL ENHANCE VELOCE 16GB(2X8GB), DDR3, 1600MHz

Here are the most recent memory dumps:

Code:
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 2/2/2015 9:39:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020215-4390-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8000CC42198) 
Bugcheck code: 0xD1 (0x2E, 0x6, 0x0, 0xFFFFF8000CC42198)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.


On Mon 2/2/2015 9:39:08 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x3A783) 
Bugcheck code: 0xD1 (0x2E, 0x6, 0x0, 0xFFFFF8000CC42198)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport 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. 


On Mon 2/2/2015 9:38:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020215-4625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0) 
Bugcheck code: 0x1A (0x5003, 0xFFFFF79940000000, 0x1D07B, 0x1D079002A0F6)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Mon 2/2/2015 9:19:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020215-5343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0) 
Bugcheck code: 0x50 (0xFFFFD00033A4D940, 0x0, 0xFFFFF802025E36CC, 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 Mon 2/2/2015 8:37:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020215-4265-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x170720) 
Bugcheck code: 0x50 (0xFFFFF8001F7F0720, 0x8, 0xFFFFF8001F7F0720, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 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. 



On Mon 2/2/2015 8:36:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020215-4750-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF80055A591CB) 
Bugcheck code: 0x50 (0xFFFFC0007109D200, 0x0, 0xFFFFF80055A591CB, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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. 



On Mon 2/2/2015 8:04:46 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020215-5062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0) 
Bugcheck code: 0xA (0xFFFFC00014EEAB88, 0x2, 0x1, 0xFFFFF80130AFD1B7)
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.

As far as I can tell its related to my video card driver but it's the latest stable driver and the card was working perfectly with previous setup so I'm a bit confused about all this. Additionally, those errors occur even without any driver(s) installed on my system (fresh windows install).

Any tips, suggestions or resolutions will be greatly appreciated.
 

ArtoSimonyan

Reputable
Feb 2, 2015
5
0
4,510
Not every time when I power on my pc but quite frequently. Normally I do get other errors but so far with the limited testing time I had since I reinstalled my OS, those are all the dumps and BSOD information I can provide.

Other common ones are:
SYSTEM_SERVICE_EXCEPTION
IRQL_DRIVER_LESS_THAN_OR_EQUAL_TO

Those are on the top of my head the most I've seen. As I said, I tried the memory and swapping the ram sticks and it doesn't seem like either one is the actual issue but can't be quite sure.

Will keep testing and providing memory dumps.