Page Fault in Non-Paged Area BSOD, Now (Almost) Everything "Has Stopped Working"

Haven't tried just the command prompt from safe mode, will give that a shot. Knoppix isn't letting me rename or delete that file; I seem to recall Knoppix can't write to NTFS formatted drives?

EDIT: Safe mode with command prompt blue screens as well, with "Loading Windows/System32/CLASSPNP.sys" as the last step displayed. Last known good configuration loads for a bit then goes to a black screen and stays there; does not accept keyboard input (numlock key does not toggle numlock).

EDIT2: While I was typing the previous edit, it automatically rebooted and went into Startup Repair. That ran for a while then produced the following error message: "The instruction at 0xfac345b5 referenced memory at 0x02d7c7e8. The memory could not be written." I have four 2GB sticks of memory so I'm going to try removing half of them and swapping them out to see if one of the sticks is bad.

Still blue screens no matter which memory sticks are in there, so it's not the RAM. Was really hoping it would be, since that would be the easiest to replace.

Any thoughts on how to proceed? Is it worth re-installing OS or is this definitely a hardware issue?

You may want to follow up your current memory diagnostic process by running MemTest86.
Download and burn the bootable ISO (near middle of page) and run it, testing memory individually 5 to 7 passes, find a good stick and use it to also test individual slots

Good idea, Trouble, I had forgotten it could be an issue with the slot rather than the sticks.

Very good idea, actually. Thanks, Trouble!

MemTest immediately found corruption on one of the sticks, others seem to be OK. I still get BSOD when booting up, however, even if I try Last Known Good Configuration or Safe Mode. I guess messing with that .dll file may have messed it up somehow? I'll probably re-install Win7 when I have some time (Thursday most likely), unless somebody else has some ideas. Can't go back and fix the .dll since Knoppix can't modify files on an NTFS drive.

Were you able to boot into the command prompt without networking?

If you did not succeed in changing the name of the network driver, it should not be involved, unless it was involved in the original problem.

Also, the video card has memory.

Maybe another dump file when not using the bad memory would help, if you can get one.

Saltgrass, I don't see an option to get just a command prompt; I can pick Safe Mode with Command Prompt, but that apparently just launches Safe Mode then tries to pull up a command prompt once it's up.

Will check for a new dump file tomorrow.

The dumpfile in Windows/Minidump has the same name and is the same size as the one I posted before. Is it probably the same one I posted before or would a new dumplog likely have the same size and name?

Re-installing Win7 fixed it once I removed the bad RAM; pretty sure I messed something up when I replaced that .dll file. Thanks all for your help, especially Trouble for the MemTest suggestion!

First on behalf of everyone involved, your welcome.
And second, thank you for the follow ups and keeping us apprised of your progress. Sorry to hear that a Re-install was required but sometimes you're stuck with playing the cards you're dealt.
Anyhow, thanks for joining our community and we hope to continue to see you around the forums.
Regards
Randy