• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Solved Bsod page fault in non paged area ivy bridge


IonR19

New Member
Posts
4
#1
this pc was built around 1 year ago

3570K @ 4.2gHZ stock volts max temps around 75c using a hyper 212 plus
P8Z77-V Bios 2104
Sapphire 7950 dual x fans running stock with AMD beta 14.4

2x4GB corsair memory they are rated at 1600mhz the motherboard set it to 1333hz as default but i switched to xmp 1600mhz

in the blue screen it says
page fault in nonpaged area portcls.sys

i did a refresh , chkdsk , memtest, and after i did a driver verifer i got another type of error

driver page fault beyond end of allocation

so i had to go back and to safe mode and disable the verifier

the 1st one it occurs sometimes from 1h to 6h randomly usually while browsing or just steam chat


edit: if any one needs any other info about the hardware im using, please ask :)
 
Last edited:

My Computer

System One

  • OS
    Windows 8.1 Pro x64

lifetec

New Member
Power User
Posts
660
#2
All your dumpfiles points to vrtaucbl fffff801`9c113000 fffff801`9c127080 Sun Apr 01 11:08:53 2012 (4f781b25) 000252b0 None vrtaucbl.sys.
This is the driver for Virtual Audio Cable (WDM)
It seems there are no windows 8.1 compatible drivers , please uninstall and/or remove this program/device.
Driver Update Site: Ventrilo - Download

Info:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffe000168a9008, 0, fffff8019c12bdd9, 0}
*** WARNING: Unable to verify timestamp for vrtaucbl.sys
*** [COLOR=#ff0000]ERROR: Module load completed but symbols could not be loaded for vrtaucbl.sys[/COLOR]
Could not read faulting driver name
Probably caused by : portcls.sys ( portcls!GetMaxMapRegisters+5 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffe000168a9008, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8019c12bdd9, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------

Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff802543e1138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffe000168a9008 
FAULTING_IP: 
portcls!GetMaxMapRegisters+5
fffff801`9c12bdd9 8b4150          mov     eax,dword ptr [rcx+50h]
MM_INTERNAL_CODE:  0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  AV
PROCESS_NAME:  audiodg.exe
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
TRAP_FRAME:  ffffd00026f55f30 -- (.trap 0xffffd00026f55f30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe000168a8fb8
rdx=ffffe0001b0e4b88 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8019c12bdd9 rsp=ffffd00026f560c8 rbp=ffffe00019f0a150
 r8=0000000000000000  r9=ffffd001a6715180 r10=fffff780000003b0
r11=ffffd00026f560c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
portcls!GetMaxMapRegisters+0x5:
fffff801`9c12bdd9 8b4150          mov     eax,dword ptr [rcx+50h] ds:ffffe000`168a9008=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff802542120e7 to fffff802541e0fa0
STACK_TEXT:  
ffffd000`26f55d48 fffff802`542120e7 : 00000000`00000050 ffffe000`168a9008 00000000`00000000 ffffd000`26f55f30 : nt!KeBugCheckEx
ffffd000`26f55d50 fffff802`540f49c9 : 00000000`00000000 ffffe000`1b0e4880 ffffd000`26f55f30 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x20c37
ffffd000`26f55df0 fffff802`541eb22f : 00000000`00000000 00000000`00000000 fffff801`72006f00 ffffd000`26f55f30 : nt!MmAccessFault+0x7a9
ffffd000`26f55f30 fffff801`9c12bdd9 : fffff801`9c162d4d 00000000`00000000 ffffe000`19f0a150 ffffe000`4bd4d010 : nt!KiPageFault+0x12f
ffffd000`26f560c8 fffff801`9c162d4d : 00000000`00000000 ffffe000`19f0a150 ffffe000`4bd4d010 ffffe000`4bd4d100 : portcls!GetMaxMapRegisters+0x5
ffffd000`26f560d0 fffff801`9c161f20 : 00000000`00000000 ffffe000`1aff2210 00000000`00000000 ffffe000`1aff2210 : portcls!CPortPinWavePci::Init+0x21d
ffffd000`26f56160 fffff801`9c14c640 : ffffe000`4bd4d010 00000000`00000000 ffffe000`18471ca0 00000000`000007ff : portcls!CPortFilterWavePci::NewIrpTarget+0x184
ffffd000`26f561e0 fffff801`9c0d8327 : 00000000`00000000 ffffe000`18471ca0 ffffe000`1a3829e0 fffff801`00000082 : portcls!xDispatchCreate+0xd0
ffffd000`26f56260 fffff801`9c149226 : ffffe000`18471ca0 ffffe000`18471d00 ffffe000`18471df0 ffffe000`00000000 : ks!KsDispatchIrp+0x316
ffffd000`26f56320 fffff801`9c1190a1 : ffffe000`18471ca0 ffffe000`1a3829e0 00000000`00000000 ffffe000`1aad4010 : portcls!PcDispatchIrp+0x227
ffffd000`26f56390 ffffe000`18471ca0 : ffffe000`1a3829e0 00000000`00000000 ffffe000`1aad4010 00000000`00000000 : [COLOR=#ff0000]vrtaucbl+0x60a1[/COLOR]
ffffd000`26f56398 ffffe000`1a3829e0 : 00000000`00000000 ffffe000`1aad4010 00000000`00000000 00000000`00000000 : 0xffffe000`18471ca0
ffffd000`26f563a0 00000000`00000000 : ffffe000`1aad4010 00000000`00000000 00000000`00000000 ffffe000`1b0e4880 : 0xffffe000`1a3829e0

STACK_COMMAND:  kb
FOLLOWUP_IP: 
portcls!GetMaxMapRegisters+5
fffff801`9c12bdd9 8b4150          mov     eax,dword ptr [rcx+50h]
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  portcls!GetMaxMapRegisters+5
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: portcls
IMAGE_NAME:  portcls.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  530893ed
IMAGE_VERSION:  6.3.9600.17031
BUCKET_ID_FUNC_OFFSET:  5
FAILURE_BUCKET_ID:  AV_portcls!GetMaxMapRegisters
BUCKET_ID:  AV_portcls!GetMaxMapRegisters
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:av_portcls!getmaxmapregisters
FAILURE_ID_HASH:  {5ed50cb9-aab0-3dda-e0a4-0c00d74813c9}
Followup: MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D6, {ffffcf807158f008, 0, fffff80116bb7dd9, 0}
*** WARNING: Unable to verify timestamp for vrtaucbl.sys
*** [COLOR=#ff0000]ERROR: Module load completed but symbols could not be loaded for vrtaucbl.sys[/COLOR]
Could not read faulting driver name
Probably caused by : portcls.sys ( portcls!GetMaxMapRegisters+5 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (d6)
N bytes of memory was allocated and more than N bytes are being referenced.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffcf807158f008, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff80116bb7dd9, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------

Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80327562138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffcf807158f008 
FAULTING_IP: 
portcls!GetMaxMapRegisters+5
fffff801`16bb7dd9 8b4150          mov     eax,dword ptr [rcx+50h]
MM_INTERNAL_CODE:  0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD6
PROCESS_NAME:  audiodg.exe
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
TRAP_FRAME:  ffffd000c0dd4da0 -- (.trap 0xffffd000c0dd4da0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffcf807158efb8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80116bb7dd9 rsp=ffffd000c0dd4f38 rbp=ffffe000f80d19f0
 r8=fffff8011434516c  r9=0000000000000001 r10=fffff80114344960
r11=ffffd000c0dd4f30 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
portcls!GetMaxMapRegisters+0x5:
fffff801`16bb7dd9 8b4150          mov     eax,dword ptr [rcx+50h] ds:ffffcf80`7158f008=????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff803273930e7 to fffff80327361fa0
STACK_TEXT:  
ffffd000`c0dd4bb8 fffff803`273930e7 : 00000000`00000050 ffffcf80`7158f008 00000000`00000000 ffffd000`c0dd4da0 : nt!KeBugCheckEx
ffffd000`c0dd4bc0 fffff803`272759c9 : 00000000`00000000 ffffe000`f83161c0 ffffd000`c0dd4da0 ffffd000`c0dd4cc0 : nt! ?? ::FNODOBFM::`string'+0x20c37
ffffd000`c0dd4c60 fffff803`2736c22f : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd000`c0dd4da0 : nt!MmAccessFault+0x7a9
ffffd000`c0dd4da0 fffff801`16bb7dd9 : fffff801`16beed4d 00000000`00000000 ffffe000`f80d19f0 ffffe000`f7849ca0 : nt!KiPageFault+0x12f
ffffd000`c0dd4f38 fffff801`16beed4d : 00000000`00000000 ffffe000`f80d19f0 ffffe000`f7849ca0 ffffe000`f7849d90 : portcls!GetMaxMapRegisters+0x5
ffffd000`c0dd4f40 fffff801`16bedf20 : 00000000`00000000 ffffe000`f81576d0 00000000`00000000 ffffe000`f81576d0 : portcls!CPortPinWavePci::Init+0x21d
ffffd000`c0dd4fd0 fffff801`16bd8640 : ffffe000`f7849ca0 00000000`00000000 ffffe000`f70da810 00000000`000007ff : portcls!CPortFilterWavePci::NewIrpTarget+0x184
ffffd000`c0dd5050 fffff801`16b64327 : 00000000`00000000 ffffe000`f70da810 ffffcf80`74a66cf0 00000000`00000082 : portcls!xDispatchCreate+0xd0
ffffd000`c0dd50d0 fffff801`16bd5226 : ffffe000`f70da810 ffffe000`f70da900 ffffe000`f70da960 ffffe000`00000000 : ks!KsDispatchIrp+0x316
ffffd000`c0dd5190 fffff801`16ba50a1 : ffffe000`f70da810 ffffcf80`74a66cf0 00000000`00020000 fffff803`27893ec9 : portcls!PcDispatchIrp+0x227
ffffd000`c0dd5200 ffffe000`f70da810 : ffffcf80`74a66cf0 00000000`00020000 fffff803`27893ec9 00000000`00000000 : [COLOR=#ff0000]vrtaucbl+0x60a1[/COLOR]
ffffd000`c0dd5208 ffffcf80`74a66cf0 : 00000000`00020000 fffff803`27893ec9 00000000`00000000 00000000`00000000 : 0xffffe000`f70da810
ffffd000`c0dd5210 00000000`00020000 : fffff803`27893ec9 00000000`00000000 00000000`00000000 ffffe000`f83161c0 : 0xffffcf80`74a66cf0
ffffd000`c0dd5218 fffff803`27893ec9 : 00000000`00000000 00000000`00000000 ffffe000`f83161c0 ffffcf80`74a66cf0 : 0x20000
ffffd000`c0dd5220 fffff801`14305af7 : ffffe000`f70da810 ffffd000`c0dd5290 ffffcf80`74a66cf0 fffff801`16ba4fb0 : nt!ViFilterDispatchGeneric+0xd1
ffffd000`c0dd5260 fffff803`27877911 : ffffcf80`74a66cf0 00000000`00000002 00000000`00000000 ffffe000`f70db010 : VerifierExt!xdv_IRP_MJ_CREATE_wrapper+0xfb
ffffd000`c0dd52c0 fffff803`27893ec9 : ffffcf80`74a66cf0 ffffe000`f70d8040 00000000`00000002 ffffe000`f7b3cda0 : nt!IovCallDriver+0x3cd
ffffd000`c0dd5310 fffff803`27877911 : ffffe000`f70d8190 ffffcf80`74a66cf0 ffffe000`f5147680 00000000`00000000 : nt!ViFilterDispatchGeneric+0xd1
ffffd000`c0dd5350 fffff801`16ffa7d7 : ffffcf80`74a66cf0 ffffd000`c0dd53f0 ffffcf80`74a66f70 ffffe000`f7b3ce70 : nt!IovCallDriver+0x3cd
ffffd000`c0dd53a0 fffff803`27877911 : ffffcf80`74a66cf0 00000000`00000002 ffffe000`00000000 ffffe000`f6a4cbb0 : ksthunk!CKernelFilterDevice::DispatchIrp+0x10f
ffffd000`c0dd5400 fffff803`27601593 : 00000000`00000004 ffffd000`c0dd5701 00000000`00000000 ffffe000`f6a4cbb0 : nt!IovCallDriver+0x3cd
ffffd000`c0dd5450 fffff803`276a041e : 00000000`00000001 ffffe000`f702da20 00007ff9`cb745000 ffffe000`f7849090 : nt!IopParseDevice+0x7b3
ffffd000`c0dd5650 fffff803`276074f8 : 00000000`00000001 ffffd000`c0dd57b0 ffffe000`f7849060 fffff803`276a0364 : nt!IopParseFile+0xba
ffffd000`c0dd56b0 fffff803`27604e53 : 00000000`00000264 ffffd000`c0dd58a8 00000000`00000040 ffffe000`f50f1c60 : nt!ObpLookupObjectName+0x6d8
ffffd000`c0dd5830 fffff803`275d39a2 : ffffe000`00000001 ffffe000`f702dab8 000000a6`4f64ca20 00000000`00000020 : nt!ObOpenObjectByName+0x1e3
ffffd000`c0dd5960 fffff803`275d3628 : 000000a6`4f64cb28 000000a6`c0000000 000000a6`4f64ca30 00000008`00040004 : nt!IopCreateFile+0x372
ffffd000`c0dd5a00 fffff803`2736d7b3 : ffffe000`f831e568 00000000`001f0003 fffff6fb`7dbed7f8 fffff6fb`7dafff38 : nt!NtCreateFile+0x78
ffffd000`c0dd5a90 00007ff9`cd94b0da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000a6`4f64c9a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`cd94b0da

STACK_COMMAND:  kb
FOLLOWUP_IP: 
portcls!GetMaxMapRegisters+5
fffff801`16bb7dd9 8b4150          mov     eax,dword ptr [rcx+50h]
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  portcls!GetMaxMapRegisters+5
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: portcls
IMAGE_NAME:  portcls.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  530893ed
IMAGE_VERSION:  6.3.9600.17031
BUCKET_ID_FUNC_OFFSET:  5
FAILURE_BUCKET_ID:  0xD6_VRF_portcls!GetMaxMapRegisters
BUCKET_ID:  0xD6_VRF_portcls!GetMaxMapRegisters
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0xd6_vrf_portcls!getmaxmapregisters
FAILURE_ID_HASH:  {77152618-4fc3-2ce4-f278-2c763f14b69e}
Followup: MachineOwner
---------
It is known that many networkdevices with windows 7/8 driver have problems with windows 8.1
Please updateall your network related drivers to the latest windows 8.1 compatible drivers


Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update,please consider it could be a possible BSOD cause or remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driveras it may make the system unbootable! :

Note:firstcheck the support/driver downloadsite of your OEM model or system(mainboard) for the latest windows 8.1 drivers. from here Motherboards - P8Z77-V

ISODrv64 fffff801`9aba6000 fffff801`9abc4000 Fri Jan 29 04:39:02 2010 (4b625856) 0002768f ISODrv64.sys
Driver Description: ISO CD-ROM Device Driver - ISODrive
Driver Update Site: Create a MultiBoot CD, an ISO image file or a virtual CD - download FREE evaluation copies of our software!

athw8x fffff801`9bc98000 fffff801`9c021000 Thu Jan 17 10:15:39 2013 (50f7c13b) 00386204 athw8x.sys
Driver Description: Atheros Wireless LAN Driver
Driver Update Site: ATHEROS drivers for Microsoft Windows (Atheros?????)

tapSF0901 fffff801`9aa17000 fffff801`9aa24000 Mon Feb 11 13:51:36 2013 (5118e958) 0000b8d9 tapSF0901.sys
Driver Description: Spotflux Inc. TAP Device Driver
Spotflux Virtual Network Device Driver (VPN)
Driver Update Site: Spotflux Free VPN
Removing a spotflux Network Adapter if the Uninstall failed to remove it -
https://spotflux.zendesk.com/entrie...-Adapter-if-the-Uninstall-failed-to-remove-it

e1i63x64 fffff801`9bb3b000 fffff801`9bbaf000 Wed Mar 20 08:37:29 2013 (51496739) 0007ff34 e1i63x64.sys
Driver Description: Intel(R) Gigabit Adapter
Driver Update Site: Network Connectivity — Drivers and software for Gigabit Intel® Ethernet Adapters

TeeDriverx64 fffff801`9bb1f000 fffff801`9bb3b000 Tue Jul 02 20:38:08 2013 (51d31e10) 0002324b TeeDriverx64.sys
Driver Description: Intel Management Engine Interface driver
Driver Update Site: http://downloadcenter.intel.com
 

My Computer

System One

  • OS
    windows 8.1
    Computer type
    PC/Desktop
    System Manufacturer/Model Number
    self build
    CPU
    Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
    Motherboard
    Asrock P55 Pro
    Memory
    DDR3 Team--Elite-1333 8 gb
    Graphics Card(s)
    Sapphire R9 280x
    Sound Card
    Realtek Alc 855
    Monitor(s) Displays
    Acer V233H
    Screen Resolution
    1920 x 1020
    Hard Drives
    Samsung evo 850 SSd
    Seagate ST 320 gb
    Samsung HD 750 gb
    Seagate ST 3000gb
    PSU
    OCZ Stealth 600 watt
    Case
    Antec 300
    Mouse
    Speedlink Ledos and Nexus