Page Fault in Non Paged Area.

Hi, I got this message "Page Fault in Non Paged Area." with a BSOD.

I have changed the destination of my Page File (From my OS disk to another). Because I have an SSD and it took some place, I moved it to another HDD.


What caused this?

Help Appreciated!


I know I havent installed all drivers for my motherboard, but that's on purpose because I dont want the ATI catalyst drivers on my computer, also, that shouldnt have anything to do with pagefile should it?

Thanks in advance.

FredeGail said:

Hello Nikkoelite & Welcome to SevenForums!

BSOD Summary

Code:

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


Loading Dump File [C:\Users\Frederik\AppData\Local\Temp\Rar$DI00.722\073111-13244-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 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`03097e50
Debug session time: Sun Jul 31 19:38:16.236 2011 (UTC + 2:00)
System Uptime: 0 days 7:06:59.500
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - Handlingen er gennemf rt.

FAULTING_IP: 
+67522faf0160dde8
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff800043c4328 -- (.exr 0xfffff800043c4328)
ExceptionAddress: fffff80002ed42a1 (nt!KiTimerWaitTest+0x0000000000000171)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: ffffffffffffffff
   Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000

TRAP_FRAME:  fffff800043c43d0 -- (.trap 0xfffff800043c43d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa800827baf8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ed42a1 rsp=fffff800043c4560 rbp=f7fff88004104cc0
 r8=fffff88004104cd8  r9=0000000000000039 r10=fffff80003044e80
r11=fffffa8007f78f00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!KiTimerWaitTest+0x171:
fffff800`02ed42a1 488b6d00        mov     rbp,qword ptr [rbp] ss:0018:f7fff880`04104cc0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ec242e to fffff80002eca6d0

STACK_TEXT:  
fffff800`043c3418 fffff800`02ec242e : 00000000`00000000 00000000`00000000 fffff800`043c3b90 fffff800`02ef76ec : nt!KeBugCheck
fffff800`043c3420 fffff800`02ef049d : fffff800`030d8b7c fffff800`03012e3c fffff800`02e5a000 fffff800`043c4328 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`043c3450 fffff800`02ef7b10 : fffff800`03019b0c fffff800`043c34c8 fffff800`043c4328 fffff800`02e5a000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`043c3480 fffff800`02f04a6f : fffff800`043c4328 fffff800`043c3b90 fffff800`00000000 fffff880`04104cb8 : nt!RtlDispatchException+0x410
fffff800`043c3b60 fffff800`02ec9d42 : fffff800`043c4328 fffff880`04104cc0 fffff800`043c43d0 fffff880`04104cf8 : nt!KiDispatchException+0x16f
fffff800`043c41f0 fffff800`02ec8512 : 00000000`0000000a fffff880`04112d7b fffff800`03044e80 fffff800`02ed6de0 : nt!KiExceptionDispatch+0xc2
fffff800`043c43d0 fffff800`02ed42a1 : ffffffff`ffb3b4c0 fffffa80`09e46b60 00000000`00000000 fffffa80`00000000 : nt!KiStackFault+0x112
fffff800`043c4560 fffff800`02ed5d8d : fffff880`04104cb8 fffffa80`096bcc68 fffffa80`096bcc68 00000000`00000000 : nt!KiTimerWaitTest+0x171
fffff800`043c45e0 fffff800`02ed64ce : 0000003b`a6698d60 fffff800`043c4c58 00000000`00190f19 fffff800`030475a8 : nt!KiProcessExpiredTimerList+0x6d
fffff800`043c4c30 fffff800`02ed5cc7 : 00000016`2ea39ac5 00000016`00190f19 00000016`2ea39a36 00000000`00000019 : nt!KiTimerExpiration+0x1be
fffff800`043c4cd0 fffff800`02ed2eea : fffff800`03044e80 fffff800`03052c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`043c4d80 00000000`00000000 : fffff800`043c5000 fffff800`043bf000 fffff800`043c4d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02ec242e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

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

Let's start off by doing a SFC /SCANNOW

Upload any incoming BSOD.
FredeGail

I did that and minimized the window while it worked and then it closed itself

Also, could you not read anything from the dumps I've attached?

thanks

FredeGail said:

Nikkoelite said:

FredeGail said:

Hello Nikkoelite & Welcome to SevenForums!

BSOD Summary

Code:

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


Loading Dump File [C:\Users\Frederik\AppData\Local\Temp\Rar$DI00.722\073111-13244-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 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`03097e50
Debug session time: Sun Jul 31 19:38:16.236 2011 (UTC + 2:00)
System Uptime: 0 days 7:06:59.500
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - Handlingen er gennemf rt.

FAULTING_IP: 
+67522faf0160dde8
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff800043c4328 -- (.exr 0xfffff800043c4328)
ExceptionAddress: fffff80002ed42a1 (nt!KiTimerWaitTest+0x0000000000000171)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: ffffffffffffffff
   Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000

TRAP_FRAME:  fffff800043c43d0 -- (.trap 0xfffff800043c43d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa800827baf8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ed42a1 rsp=fffff800043c4560 rbp=f7fff88004104cc0
 r8=fffff88004104cd8  r9=0000000000000039 r10=fffff80003044e80
r11=fffffa8007f78f00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!KiTimerWaitTest+0x171:
fffff800`02ed42a1 488b6d00        mov     rbp,qword ptr [rbp] ss:0018:f7fff880`04104cc0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ec242e to fffff80002eca6d0

STACK_TEXT:  
fffff800`043c3418 fffff800`02ec242e : 00000000`00000000 00000000`00000000 fffff800`043c3b90 fffff800`02ef76ec : nt!KeBugCheck
fffff800`043c3420 fffff800`02ef049d : fffff800`030d8b7c fffff800`03012e3c fffff800`02e5a000 fffff800`043c4328 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`043c3450 fffff800`02ef7b10 : fffff800`03019b0c fffff800`043c34c8 fffff800`043c4328 fffff800`02e5a000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`043c3480 fffff800`02f04a6f : fffff800`043c4328 fffff800`043c3b90 fffff800`00000000 fffff880`04104cb8 : nt!RtlDispatchException+0x410
fffff800`043c3b60 fffff800`02ec9d42 : fffff800`043c4328 fffff880`04104cc0 fffff800`043c43d0 fffff880`04104cf8 : nt!KiDispatchException+0x16f
fffff800`043c41f0 fffff800`02ec8512 : 00000000`0000000a fffff880`04112d7b fffff800`03044e80 fffff800`02ed6de0 : nt!KiExceptionDispatch+0xc2
fffff800`043c43d0 fffff800`02ed42a1 : ffffffff`ffb3b4c0 fffffa80`09e46b60 00000000`00000000 fffffa80`00000000 : nt!KiStackFault+0x112
fffff800`043c4560 fffff800`02ed5d8d : fffff880`04104cb8 fffffa80`096bcc68 fffffa80`096bcc68 00000000`00000000 : nt!KiTimerWaitTest+0x171
fffff800`043c45e0 fffff800`02ed64ce : 0000003b`a6698d60 fffff800`043c4c58 00000000`00190f19 fffff800`030475a8 : nt!KiProcessExpiredTimerList+0x6d
fffff800`043c4c30 fffff800`02ed5cc7 : 00000016`2ea39ac5 00000016`00190f19 00000016`2ea39a36 00000000`00000019 : nt!KiTimerExpiration+0x1be
fffff800`043c4cd0 fffff800`02ed2eea : fffff800`03044e80 fffff800`03052c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`043c4d80 00000000`00000000 : fffff800`043c5000 fffff800`043bf000 fffff800`043c4d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02ec242e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

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

Let's start off by doing a SFC /SCANNOW

Upload any incoming BSOD.
FredeGail

I did that and minimized the window while it worked and then it closed itself

Also, could you not read anything from the dumps I've attached?

thanks

Closed itself? Strange, could you do one more and just leave it?

Your .dmp was quite hard to analyse, so we'll just do some known steps first. Just post any incoming .dmp as you did.

Best Regards,
FredeGail

Tried once again. I had it opened this time all the time, I saw it reach 99%, then it ticked to 100% a message apperad (window closed too fast for me to read the message).