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!
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?
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.
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...
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?
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"...
Regarding safe mode, I can get to the menu where you pick which version of safe mode you want. Picking normal safe mode (rather than safe mode with various other things turned on), it starts loading Windows but blue screens part way through.
There's a zip of the file from Windows/Minidump. I used Knoppix to get it so I would need Linux versions of the SF Diagnostic and CPU-Z tools to get their data. F8 for safe mode also results in a BSOD while loading Windows.
Now it gives me a BSOD every time I try to boot up, either that same PAGE_FAULT_IN_NONPAGED_AREA or a very brief (both in length and duration) ILLEGAL EXCEPTION one. That means I can't really get at all the dump files the BSOD forum needs, as well as furthering my suspicions that it's a hardware...
Was playing New Vegas earlier today and suddenly got a BSOD. Error type was Page Fault in Non-Paged Area. My general approach is to just leave the machine off for an hour or so after a BSOD. Booted it up again a short while ago and was pleased to see Windows load and give me a login prompt...