Windows 10: stop code page fault in nonpaged area

welp...this is a different problem from what I've been having...and THIS TIME I have a photo to go with it!

and what was I doing when the computer smacked me in the face as it were?

why, I had just loaded teamspeak, first item on my daily startup check list.

items included in post: one photo care of cellphone camera, and one log using tenforums supplied log tool.

:)

 

Blue screen error

Getting the following: Stop code: Page fault in nonpaged area

How to fix

 

STOP CODE Help?

Thanks, I've done that but now I'm getting a stop code saying : PAGE FAULT IN NONPAGED AREA What failed IOMap64.sys??

 

...yes the photo is upside down. just download and flip right side up. no idea WHY it did that..

 

There were a couple of drivers involved in the stack which was captured at the time of the crash. The one portcls.sys is a windows driver which is unlikely to be a problem. Immediately prior to this is a virtual audio cable driver vrtaucbl.sys which was also noted as having no symbols. I would strongly suspect this driver was the culprit. See if you can update it.

Code: # 0 TID:0001 kb kbn kbnL kn knL kpn kPn # Child-SP RetAddr Call Site 00 fffffe0f`428c2b28 fffff802`407be2d1 nt!KeBugCheckEx 01 fffffe0f`428c2b30 fffff802`4067cfad nt!MiSystemFault+0x142ce1 02 fffffe0f`428c2bd0 fffff802`4079754e nt!MmAccessFault+0x23d 03 fffffe0f`428c2da0 fffff805`9c7795c1 nt!KiPageFault+0x40e 04 fffffe0f`428c2f38 fffff805`9c7c1171 portcls!GetMaxMapRegisters+0x5 05 fffffe0f`428c2f40 fffff805`9c7c0065 portcls!CPortPinWavePci::Init+0x3b1 06 fffffe0f`428c2fe0 fffff805`9c7a4aa0 portcls!CPortFilterWavePci::NewIrpTarget+0x195 07 fffffe0f`428c3060 fffff805`9c7a3c6e portcls!xDispatchCreate+0x2b0 08 fffffe0f`428c3110 fffff805`98c24215 portcls!KsoDispatchCreateWithGenericFactory+0x2e 09 fffffe0f`428c3140 fffff805`9c7a4b99 ks!KsDispatchIrp+0x285 0a fffffe0f`428c3200 fffff805`9b2c38c2 portcls!PcDispatchIrp+0xd9 0b fffffe0f`428c3270 fffffe0f`428c3330 vrtaucbl+0x38c2 0c fffffe0f`428c3278 ffffd50e`fcbbd2d8 0xfffffe0f`428c3330 0d fffffe0f`428c3280 00000000`00000000 0xffffd50e`fcbbd2d8 *** WARNING: Unable to verify timestamp for vrtaucbl.sys *** ERROR: Module load completed but symbols could not be loaded for vrtaucbl.sys[/quote]
There was also a warning for the AVAST aswsnx.sys driver so that would be the other component I would suspect:

Code: Unable to load image \SystemRoot\system32\drivers\aswSnx.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for aswSnx.sys *** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys[/quote]

 

probably going to do a repair on my avast at some point anyways, a fresh install if that doesnt fix it..

the audio cables have been a known issue for some time, I'll need to get with a buddy of mine and see if he cant hook me up with updated cables, though its my understanding that windows 10 and virtual audio cables do not get along for some reason.

 

on the bright side, the fact I've gone almost 8 days without the other issue occurring tells me it was something to do with fast startup *Biggrin

 

That's good to know - I was hoping that was going to be the answer.

 

you and me both...I mean, for the headaches fast startup causes, a couple seconds longer on the boot time isnt too high a price in comparison.

by loading it all fresh...less headaches?

that said...first time I've ever seen this error.

 

and same EXACT error again.

logs attached.

is it still flagging on the two items you mentioned before?

 

Yes, same two drivers are picked out. Their dates have not changed so it does not look as if you were able to find any updates.

 

well if its avast, there's literally nothing I can do that isnt a straight up uninstall/reinstall, and then I'm stuck with that shtacko, as any av is better than just windows defender, as to the audio cables, I'm waiting on a buddy of mine to roll in on teamspeak, he did actually find updated virtual audio cables.

 

OK, change the audio cable drivers when you can and see if that fixes it. Then if you get another BSOD post another set of logs.

 

I did get another bsod, two of them back to back, and this time I was paying attention to what I was doing immediately before hand...

both times, I'd JUST loaded discord and it took a dump on me.

I'll get the next one's log and see if its related.

edit: as my friend has yet to get ahold of me, I went ahead and outright yanked the cables altogether..I need a stable system more than I need an internet radio broadcast ready system.

 

two weeks problem free....is there any way to verify it was the cables giving me such grief? or is the lack of a problem since their removal proof enough?