BSOD "Page fault in nonpaged area"

Androecian

Member
Joined
Aug 28, 2013
Posts
5
I have a stock Compaq CQ5600F with 4GB of DDR2 RAM instead of the original 2GB.

Original OS: Windows 7 64bit, preinstalled, unchanged
System is 5+ years old
CPU: AMD Athlon II 170
Video card: NVIDIA GeForce 6150SE nForce 430, motherboard-based (no separate card)
Motherboard: Pegatron NARRA5 (Socket AM2)
Manufacturer: Compaq
Model no.: CQ5600F

The Perfmon report is included in the ZIP folder.

Anything you can tell me will be helpful, and thank you very much! :)
 
Hi,

We have various different bugchecks attached:

PAGE_FAULT_IN_NONPAGED_AREA (50)

This indicates that invalid system memory has been referenced.

Usual causes are a bug in a device driver, hardware related memory issues, corrupt NTFS volume, anti-virus software.

memory_corruption mentioned throughout the dump, possible device or memory issues.

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

A system thread generated an exception that the error handler did not catch.

Usual causes are a bug in a device driver.

In the stack we can see:

Code:
kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0317b7e8 fffff880`012d609e : 00000000`00000000 00000000`00000000 fffffa80`0452cdf0 00000000`00000000 : fltmgr!TreeFindNodeOrParent+0x8
fffff880`0317b7f0 fffff880`012ddedb : 00000000`00000000 fffffa80`06f5fe00 00000000`00000000 fffff880`012d86d9 : fltmgr!TreeLookup+0xe
fffff880`0317b820 fffff880`013050f1 : fffffa80`06fd1e50 fffffa80`06fd1e50 fffffa80`00000000 fffffa80`06f5fe00 : fltmgr!DeleteContextFromStreamList+0x6b
fffff880`0317b890 fffff880`012f96ce : fffffa80`04865d70 00000000`00000001 fffffa80`04865d70 fffffa80`04812c80 : fltmgr!FltpRemoveAllFileObjectContextsForInstance+0x21
fffff880`0317b8c0 fffff880`012f5705 : 00000000`00000004 fffffa80`04865800 fffffa80`04812bc0 fffffa80`048ab010 : fltmgr! ?? ::NNGAKEGL::`string'+0x168f
fffff880`0317b8f0 fffff880`0130674a : fffffa80`04812c80 fffff880`012ec201 fffffa80`04812bc0 fffffa80`04785190 : fltmgr!FltpFreeInstance+0xd5
fffff880`0317b960 fffff880`017e10a2 : 00000000`00000000 fffffa80`04785190 fffffa80`04812bc0 00000000`00000001 : fltmgr!FltUnregisterFilter+0xaa
fffff880`0317ba00 00000000`00000000 : fffffa80`04785190 fffffa80`04812bc0 00000000`00000001 00000000`00000000 : [COLOR=#ff0000][U][B]Soluto+0xe0a2[/B][/U][/COLOR]

Probably caused by : Soluto.sys ( Soluto+e0a2 )

Soluto = Soluto.sys which is the Soluto driver (cloud-based PC management). I'd recommend for troubleshooting purposes removing this software. You can reinstall it later if it is not the cause, of course.

MEMORY_MANAGEMENT (1a)

A severe memory management error occurred.

BugCheck 1A, {3452, 2ff9000, fffff70001088ad8, 8ca000002549bc46}

The first parameter of the bugcheck is 0x3452 which falls under the category of: Other - An unknown memory management error occurred.

PFN_LIST_CORRUPT (4e)

The page frame number (PFN) list is corrupted, typically caused by passing a bad memory descriptor list.

Usual causes are a bug in a device driver, BIOS or hardware issue.

Various DirectX kernel and MMS calls in the stack:

Code:
kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`07dd5ed8 fffff800`02d11a0c : 00000000`0000004e 00000000`00000099 00000000`0007b119 00000000`00000002 : nt!KeBugCheckEx
fffff880`07dd5ee0 fffff800`02c2eb97 : 00000000`00000000 fffff680`00030068 00000000`00000000 fffffa80`05d16fb8 : nt!MiBadShareCount+0x4c
fffff880`07dd5f20 fffff800`02cb3e47 : 00000000`00000000 fffff680`00030bf8 fffffa80`0bbbfb30 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x320fd
fffff880`07dd60d0 fffff800`02c6f3cf : fffffa80`00000000 00000000`0617ffff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`07dd6290 fffff800`02c81e13 : ffffffff`ffffffff fffff8a0`11c90878 fffff8a0`11c908a0 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`07dd6390 fffff800`02c7e3d0 : fffff880`0416e62e fffff8a0`0358ce50 fffffa80`0bbbfb30 fffffa80`0ba94f00 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`07dd6390)
fffff880`07dd6528 fffff880`0416e62e : fffff8a0`0358ce50 fffffa80`0bbbfb30 fffffa80`0ba94f00 fffff8a0`11c90870 : nt!KiServiceLinkage
fffff880`07dd6530 fffff880`04159c93 : fffff8a0`00e4ec00 fffff8a0`03b5f4b0 00000000`00000001 00000000`00000000 : [COLOR=#ff0000][U][B]dxgmms1[/B][/U][/COLOR]!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`07dd6560 fffff880`04154637 : fffffa80`0b5d2620 00000000`00000001 fffff8a0`0358ce50 00000000`00000001 : [COLOR=#ff0000][U][B]dxgmms1[/B][/U][/COLOR]!VIDMM_GLOBAL::CloseLocalAllocation+0x11b
fffff880`07dd6610 fffff880`0413aecc : fffff8a0`00000000 fffffa80`00000000 fffffa80`061f8000 00000000`00000000 : [COLOR=#ff0000][U][B]dxgmms1[/B][/U][/COLOR]!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`07dd66e0 fffff880`0407cccc : 00000000`00000000 fffff8a0`03bb0000 fffff8a0`03bb0000 00000000`00000001 : [COLOR=#ff0000][U][B]dxgmms1[/B][/U][/COLOR]!VidMmCloseAllocation+0x44
fffff880`07dd6710 fffff880`0407c65f : fffff8a0`03bb0000 fffff8a0`03bb1300 fffff8a0`00000000 00000000`00000000 : [COLOR=#ff0000][U][B]dxgkrnl[/B][/U][/COLOR]!DXGDEVICE::DestroyAllocations+0x248
fffff880`07dd6800 fffff880`0407c8e1 : fffff8a0`03bb0000 fffff8a0`03bb0000 00000000`00000001 00000000`00000000 : [COLOR=#ff0000][U][B]dxgkrnl[/B][/U][/COLOR]!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`07dd6850 fffff880`04080ae8 : fffff8a0`0e150300 fffff880`07dd6ca0 fffffa80`0626c000 fffff880`040473af : [COLOR=#ff0000][U][B]dxgkrnl[/B][/U][/COLOR]!DXGDEVICE::TerminateAllocations+0xb9
fffff880`07dd68a0 fffff880`040831a3 : fffff8a0`03bb0000 fffff880`07dd69b0 00000000`03f72d01 fffff780`00000301 : [COLOR=#ff0000][U][B]dxgkrnl[/B][/U][/COLOR]!DXGDEVICE::DestroyAllocation+0x448
fffff880`07dd6930 fffff960`002411da : 00000000`00000000 fffffa80`0be38b50 00000000`00000020 00000000`00000000 : [COLOR=#ff0000][U][B]dxgkrnl[/B][/U][/COLOR]!DxgkDestroyAllocation+0x9bf
fffff880`07dd6bf0 fffff800`02c81e13 : fffffa80`0be38b50 00000000`ffffffff 00000000`00000000 fffffa80`0be12380 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`07dd6c20 000007fe`fe324a4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`07dd6c20)
00000000`04eefc38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe324a4a

Also seeing other DirectX calls being made in other *1A bugchecks, etc. Possible memory / video card issues.

Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

sptd.sys is listed and loaded in your modules list, this is the SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7). Please remove this driver ASAP: DuplexSecure - Downloads

If the above software recommendations do not help, let's run a Memtest for no less than ~8 passes (several hours):

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

Regards,

Patrick
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top