Running Windows XP Home Service Pack 2.
AMD Athlon 64 Processor
64+
797 Mhz
512 MB of RAM

Both IQRL_NOT_LESS_OR_EQUAL and PAGE_FAULT_IN_NONPAGED_AREA errors have occured.

Here's 2 CRASH DUMP analyses from WinDbg:

{{{{ FIRST DUMP }}}}}}

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: e1e5701a, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf9d56c0, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.


FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 417eb327

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
e1e5701a

FAULTING_IP:
nv4_disp+16c0
bf9d56c0 f642fe08 test byte ptr [edx-0x2],0x8

MM_INTERNAL_CODE: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 00000000 to bf9d56c0

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 nv4_disp+0x16c0


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nv4_disp+16c0
bf9d56c0 f642fe08 test byte ptr [edx-0x2],0x8

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nv4_disp+16c0

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

{{{END DUMP 1}}}


{{{START DUMP #2}}}}

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: 00000016, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804f8f58, address which referenced memory


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

Followup: MachineOwner


READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get MmPageSize (0x0) - probably bad symbols
00000016

CURRENT_IRQL: 2

FAULTING_IP:
+ffffffff804f8f58
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
804f8f58 ?? ???

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

STACK_TEXT:
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002

{{{END DUMP}}

Any help would be appreciated. Thanks. Please email a copy of fix to DarkDespair5 A.T. gmail (D0T) com

Well it most certainly is nVidia related, whether hardware or software (most like the software). One issue I also see is that you stated you are running at 797Mhz on an Athlon 64 processor. Either you have Cool'n'Quiet turned on (which is fine but you may want to try disabling it while you figure out your probable driver conflict) or your processor speed in the BIOS is messed up (which could also cause instability). Two things to consider. Anyway, if it is driver related you may want to find some older drivers (the newer the better but obviously not the ones you are using) and load them and see if that takes care of the problem. Also what video card are you running and is there a certain even that causes these errors (playing games, running GPU or CPU intensive programs, running demos, watching videos, etc.)? And I don't necessarily have a fix, just things you could try so you will have to read the post.

This is a problem for which there is actually no known solution. It has been variously called the "infinite Nvidia driver loop" to a host of other names. As was pointed out you can try to go to an earlier driver. This has sometimes fixed it. You can use a driver cleaner to take out all bits of the nvidia pieces and reinstall the driver. When memory is being called by several programs, this is the message you often get. One thing you might examine is bringing up your taskmanager and watching the size of programs, particularly when you are on the web. It can happen, that there is an entirely benign process that may suddenly demand a large amount of memory and this in turn bites into the addresses held by the Nvidia drivers.