Random BSOD's on cold start (PAGE FAULT IN NON PAGED AREA etc.)

[JACK7554]

Hello guys.
Recently my Windows 7 PC started to randomly BSOD on the desktop, after "cold" start. As I can remember, it was BSOD code 7F.
So I decided to reinstall and format my system to Win 10 (Clean install from usb flash drive) After a week random BSOD's showing up again. I reinstalled windows 10 again (thinking that was a bad drivers causing BSOD) and today I get more and more BSOD's.
I got SYSTEM SERVICE EXCEPTION win32base.sys and PAGE FAULT IN NON PAGED AREA luafv.sys. And other two without error codes.
The problem is:
1.I turn off my pc 2. Next morning I turn it on.3. After couple of minutes it crashed with BSOD, I push reset and then again bsod. 4. Then my pc works normally.

But today i got four BSOD's and this is feels really bad. I checked my HDD with crystal disk info (all green), run chkdsk (no errors), checked drivers, viruses, programs, all good.
My system is:
AMD Phenom II X4 955 3,2 Ghz
Motherboard GA-MA770T-UD3
GTX 1060 3GB
8GB RAM
600W

Any suggestions will be appreciated.

 

[Colif]

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[JACK7554]

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

Okay, here's my minidump link

 

[Colif]

since no one bit, and I can't read dumps, Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

you could try turning off fast boot, it might be one of your drivers that doesn't like the way it works - http://www.tenforums.com/tutorials/4189-fast-startup-turn-off-windows-10-a.html

 

[JACK7554]

I turned off fast boot long ago, since my PC can't shut down with this feature properly.
Yesterday i got this BSOD, reset my PC and then got blank blue screen at Windows 10 loading screen.


Okay then, here it is from who crashed:

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 06.05.2017 9:18:18 your computer crashed
crash dump file: C:\Windows\Minidump\050617-25781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80334894B42)
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.

 

[Colif]

ntoskrnl = windows kernel. it gets blamed for driver errors a lot but its just the victim

you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, run Who crashed and see what driver it reveals

Note: you might want a Win 10 installer as boot disc just in case this puts you into a boot loop and you need to boot into cmd and turn it off. download the Windows 10 media creation tool and use it to make a win 10 installer on USB (if you don't have it already)

 

[JACK7554]

I have win 10 USB, how do I boot into cmd?

 

[Colif]

change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
Choose Command prompt

 

[JACK7554]

I did driver verifier for ten minutes and got no BSOD's, so I think my drivers are good ?

 

[Colif]

irq errors are almost always driver errors. The rare times they something else is ram

download free version of memtest86 and use it to make a USB. It runs without windows so boot PC from it and check your ram, 1 stick at a time. Any errors are too many, stick is bad and needs replacing or to be removed. Do a few passes on each, I think 3 to 8 is about normal to find problems.

It might make sense as PAGE FAULT IN NON PAGED AREA refers to a error occurring in ram (non paged area is ram)

 

[JACK7554]

So, my PSU died recently and i bought brand new PSU for 650W and its fixed the problem completely! Turns out it was bad power supply after all. Anyway, thanks for help!