Solved BSOD ntoskrnl.exe and ntkrnlmp.exe PAGE_FAULT_IN_NONPAGED_AREA

[unkka89]

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 24.6.2015 6:10:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062415-37877-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x50 (0xFFFFF6F7FFFFFF80, 0x0, 0xFFFFF80002E96D91, 0x5)
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 Wed 24.6.2015 6:10:59 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF6F7FFFFFF80, 0x0, 0xFFFFF80002E96D91, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.

i have already done that driver verifier thing. i have installed OS 4 times and still bsod comes.

 

[Boozad]

BugCheck 50, {fffff6f7ffffff80, 0, fffff80002e96d91, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDispatchFault+d1 )

Followup: MachineOwner

0x50 STOPs can be down to a faulty system service or NFTS corruption among other things, this will be impossible to tell though as you have an ACER PID on a retail ASUS motherboard meaning your Windows installation is counterfeit.

Is„nt„nimi:                     UNKKA-PC
K„ytt”j„rjestelm„:              Microsoft Windows 7 Home Premium 
K„ytt”j„rjestelm„n versio:      6.1.7601 Service Pack 1 koontiversio 7601
K„ytt”j„rjestelm„n valmistaja:  Microsoft Corporation
K„ytt”j„rjestelm„n asetukset:   Yksitt„inen ty”asema
K„ytt”j„rjestelm„n versio:      Multiprocessor Free
Rekister”ity omistaja:          Unkka
Rekister”ity organisaatio:      
Product ID -tunnus:             [COLOR=Red]00359-OEM-8992687-00006 ---> ACER PID[/COLOR]
Ensiasennusp„iv„:               11.6.2015, 13:11:15
J„rjestelm„n k„ynnistysaika:    24.6.2015, 9:25:59
J„rjestelm„n valmistaja:        System manufacturer
J„rjestelm„n malli:             System Product Name
J„rjestelm„laji:                x64-based PC
Suorittimet:                    1 suoritin(ta) asennettu.
                                [01]: AMD64 Family 16 Model 10 Stepping 0 AuthenticAMD ~2809 Mhz
BIOS-versio:                    American Megatrends Inc. 2001   , 8.3.2011

Counterfeit installations such as yours can contain heavily modified code that can cause the installation to behave it unexpected ways. Analysing BSODs and determining their causes on these sorts of installations is completely unreliable, and for this reason most analysts won't attempt it.

My recommendation is to install a genuine copy of Windows 7. This will minimise the problems you are experiencing and make subsequent diagnosis of BSODs far more reliable. Once you are running a genuine Windows 7 installation and are still experiencing BSODs, upload your new logs we will be happy to help you solve them.

 

[unkka89]

thanks for fast anwser! i try to install new version and post logs if something happens again.