BSOD after the machine idles for a while, error 0x00000050

hello,

PAGE_FAULT_IN_NONPAGED_AREA this is a verry hard one to troubleshoot as it's not sure it's being caused by the driver the reports mentions.This can be caused by harddisks who have errors (run chkdsk tocheck this) or some antivirus software or faulty memory (check with windows memory diagnostics) Diagnosing memory problems on your computer

Also is your computer setup to show hidden devices ? sometimes when you uninstall software traces (drivers etc) from that software are not removed right click computer and choose properties then advanced system settings then envirementvariables under systemvariables add

name = devmgr_show_nonpresent_devices
value = 1

in the devices manager you now should have a new menuitem under view "show nopresent devices" or something like that those that are grayed out have a problem

Caution

do not remove anything unless you know what it is ......

Code:

BIOS Version/Date	Phoenix Technologies, LTD ASUS P5N-D ACPI BIOS Revision 0402, 3/5/2008

The first thing I would recommend is updating your BIOS; there have been eight updates since your current version: ASUS - Motherboards- ASUS P5N-D


Antivirus Software:

Code:

ccsvchst.exe	c:\program files (x86)\norton 360 premier edition\engine\5.2.0.13\ccsvchst.exe	2976	8	1024	10240	3/9/2012 3:34 AM	10.1.1.16	126.96 KB (130,008 bytes)	1/30/2012 11:23 PM
ccsvchst.exe	c:\program files (x86)\norton 360 premier edition\engine\5.2.0.13\ccsvchst.exe	3596	8	1024	10240	3/9/2012 3:35 AM	10.1.1.16	126.96 KB (130,008 bytes)	1/30/2012 11:23 PM

Possible out of date drivers:

Code:

ASACPI	fffff880`05985000	fffff880`0598d000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys
pcouffin	fffff880`055e7000	fffff880`055fb380	Tue Dec 05 07:39:30 2006 (457584a2)	00019954		pcouffin.sys
nvm62x64	fffff880`058dc000	fffff880`0593fd80	Fri Oct 17 15:01:06 2008 (48f8fd12)	0006f977		nvm62x64.sys

Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Update the driver by:

1. Going to the Asus motherboard support site
   When you reach the website:
2. Scroll down the page and click Utilities
3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
4. Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
5. Download and install the driver.
6. After installation is complete, verify that it installed correctly.
   
   • Click Start Menu
   • Click My Computer
   • Go to C:\WIndows\System32\drivers\
   • Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)

Thanks to JMH and zigzag3143 for the above information.


pcouffin.sys

Update the chipset drivers for your motherboard through ASUS - Motherboards- ASUS P5N-D to update the nvm62x64.sys driver.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\bjones220\Windows_NT6_BSOD_jcgriff2\030912-114738-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0301b000 PsLoadedModuleList = 0xfffff800`03260670
Debug session time: Fri Mar  9 03:19:37.794 2012 (UTC - 6:00)
System Uptime: 8 days 11:29:06.660
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff87fffccba53, 8, fffff87fffccba53, 5}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+44791 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff87fffccba53, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff87fffccba53, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032ca100
 fffff87fffccba53 

FAULTING_IP: 
+3331313838643233
fffff87f`ffccba53 ??              ???

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800cec5a60 -- (.trap 0xfffff8800cec5a60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff87fffccba53 rsp=fffff8800cec5bf0 rbp=fffffa800af91b38
 r8=0000000000000001  r9=fffff8000301b000 r10=fffff88003564be0
r11=fffffa800c3eec50 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff87f`ffccba53 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030423bf to fffff80003097c40

STACK_TEXT:  
fffff880`0cec58f8 fffff800`030423bf : 00000000`00000050 fffff87f`ffccba53 00000000`00000008 fffff880`0cec5a60 : nt!KeBugCheckEx
fffff880`0cec5900 fffff800`03095d6e : 00000000`00000008 fffff87f`ffccba53 fffffa80`0c3e0000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`0cec5a60 fffff87f`ffccba53 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`000000b4 : nt!KiPageFault+0x16e
fffff880`0cec5bf0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`000000b4 fffff880`0cec5c49 : 0xfffff87f`ffccba53


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+44791
fffff800`030423bf cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+44791

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+44791

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+44791

Followup: MachineOwner
---------

Loading Dump File [D:\Kingston\BSODDmpFiles\bjones220\Windows_NT6_BSOD_jcgriff2\022912-78905-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0301c000 PsLoadedModuleList = 0xfffff800`03261670
Debug session time: Wed Feb 29 14:25:42.802 2012 (UTC - 6:00)
System Uptime: 4 days 8:38:17.257
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa804e02eb70, 2, 0, fffff80003143f9f}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa804e02eb70, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003143f9f, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032cb100
 fffffa804e02eb70 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiIdentifyPfn+23f
fffff800`03143f9f 4c8b7500        mov     r14,qword ptr [rbp]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff880082254e0 -- (.trap 0xfffff880082254e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0400000000000020
rdx=00000000000c40a4 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003143f9f rsp=fffff88008225670 rbp=fffffa804e02eb70
 r8=00000000000c40a6  r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!MiIdentifyPfn+0x23f:
fffff800`03143f9f 4c8b7500        mov     r14,qword ptr [rbp] ss:0018:fffffa80`4e02eb70=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030981e9 to fffff80003098c40

STACK_TEXT:  
fffff880`08225398 fffff800`030981e9 : 00000000`0000000a fffffa80`4e02eb70 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`082253a0 fffff800`03096e60 : 00000000`42506650 00000000`00000000 00000000`00000000 02000000`00009c50 : nt!KiBugCheckDispatch+0x69
fffff880`082254e0 fffff800`03143f9f : 00000000`00000000 02000000`00009c50 00000000`42506600 fffff800`0338473f : nt!KiPageFault+0x260
fffff880`08225670 fffff800`03144c7b : 00000000`00000000 00000000`00000004 fffffa80`1060b6e8 fffffa80`1060b000 : nt!MiIdentifyPfn+0x23f
fffff880`08225710 fffff800`034a97e5 : fffffa80`1060b000 fffff880`08225ca0 fffff880`082257e8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`08225750 fffff800`033ec4c8 : 00000000`00000006 00000000`00000000 fffffa80`1060b000 00000000`00000001 : nt!PfpPfnPrioRequest+0x115
fffff880`082257a0 fffff800`033a2bd3 : 00000000`00000000 00000000`00000000 fffffa80`090de000 fffffa80`0a577001 : nt! ?? ::NNGAKEGL::`string'+0x4810d
fffff880`08225830 fffff800`033a3449 : 00000000`00debb28 00000000`00debb48 00000000`00debb80 00000000`00000000 : nt!ExpQuerySystemInformation+0x1193
fffff880`08225be0 fffff800`03097ed3 : 00000000`00000000 00000000`113bdb08 00000000`01787e01 00000000`00000002 : nt!NtQuerySystemInformation+0x4d
fffff880`08225c20 00000000`779c167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00deba58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779c167a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiIdentifyPfn+23f
fffff800`03143f9f 4c8b7500        mov     r14,qword ptr [rbp]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiIdentifyPfn+23f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+23f

BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+23f

Followup: MachineOwner
---------

1. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Drivers...
2. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...

Thanks to Dave76 for help understanding possible causes.

• If you are overclocking any hardware, please stop.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Thanks for the help guys and sorry I am just now replying back. I was going thru all these instructions you gave me. So far I have updated all my drivers listed here. After updating my drivers I received yet another BSOD but only this time it said "IRQL_NOT_LESS_OR_EQUAL".

Afterwards I proceeded to scan the memory for errors. I conducted 10 passes on Memtest86 and 5 passes with Windows Memory Diagnostic. I never once received any errors, so I guess it's safe to say that this isn't a memory issue?

Also something else I forgot to mention that may be important to know. On one occasion when going into BSOD and turning the PC off. At first the computer would not turn itself back on. I pressed the power button several times and nothing. Finally I unplugged the power cable, re-plugged it, and suddenly the power button worked. Additionally, instead of booting up fresh, Windows resumed exactly where it was before the BSOD. Could this be a power supply issue?

Also I recently installed some security patches for Windows. I read in an article that these security patches were pretty important. Could they help prevent future BSOD's??

Thanks in advance

If you continue to have problems, I would suspect either the power supply or motherboard. You may also want to make sure all power sockets are securely fastened within the machine.

Windows updates can provide more stability, so there is a chance it will help your system stop crashing. See how the system responds for a few days and report back.