BSOD PAGE_FAULT_IN_NONPAGED_AREA caused by an unknown driver

As the title says, I encountered the first BSOD after I clean installed my PC for the last 6 days. The BSOD error code is also in the title, with the reason for the fail is from an unknown driver called "kinonivd.sys".

I have attached the log file from the collector as requested.

Attachment 268282

Hi Rin3105,

Welcome to the BSOD forum.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

13) Make sure that there is no over clocking while troubleshooting

14) Update: kinonivd.sys
EpocCam

Code:

kinonivd	EpocCam	c:\windows\system32\drivers\kinonivd.sys	Kernel Driver	Yes	Manual	Running	OK	Normal	No	Yes

Code:

kinonivd     EpocCam                EpocCam                Kernel        Manual     Running    OK         TRUE        FALSE        98,304            122,880     0          2/1/2019 2:36:28 AM    C:\WINDOWS\system32\drivers\kinonivd.sys         4,096

15) Approximately when were each of the RAM modules installed?

Code:

kinonivd.sys Thu Jan 31 13:36:28 2019 (5C534E3C)

zbook said:

Hi Rin3105,

Welcome to the BSOD forum.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

13) Make sure that there is no over clocking while troubleshooting

14) Update: kinonivd.sys
EpocCam

Code:

kinonivd	EpocCam	c:\windows\system32\drivers\kinonivd.sys	Kernel Driver	Yes	Manual	Running	OK	Normal	No	Yes

Code:

kinonivd     EpocCam                EpocCam                Kernel        Manual     Running    OK         TRUE        FALSE        98,304            122,880     0          2/1/2019 2:36:28 AM    C:\WINDOWS\system32\drivers\kinonivd.sys         4,096

15) Approximately when were each of the RAM modules installed?

Code:

kinonivd.sys Thu Jan 31 13:36:28 2019 (5C534E3C)

Hi zbook,

Thank you for hearing me out.

I have ran all those commands in administrative Command Prompt after making sure that there is no over clocking before doing that. I have attached the results as a log file below this.

If I remember correctly, the first RAM module I use is from around 2015, and the second RAM module is from just last year, 2019.

UPDATE: I uninstalled EpocCam yesterday, so my PC is running fine again, but I still wanna diagnose my PC fully to see if there's any unwanted drivers or programs that still can trigger BSOD later on.

I am looking forward for your respond soon.

Attachment 268387

All of the reports were good.

Observe for any BSOD or unexpected shutdowns and / or restarts.

If there are BSOD then upload a new V2.

zbook said:

All of the reports were good.

Observe for any BSOD or unexpected shutdowns and / or restarts.

If there are BSOD then upload a new V2.

Hi zbook,

Thank you for the quick response,

I will keep an eye on further errors and will report to you as soon as one occurs again.

Cheers,
Rin

Hello,

So it has been more than a month ever since I got this issue, and I haven't had anymore BSODs, which is really a good thing to know.

I would like to thank everyone who had helped me in this thread. It means a lot to me. I will close this thread and mark this as solved.

Cheers.
Rin

That's great news.

You're welcome.