Solved Regular BSOD - 0x50 - Page fault in nonpaged area

[nick95610]

Understood. I'll test them in that manner and report back.

Thanks for all the help and patience. It's greatly appreciated.

 

[richc46]

Your welcome,

 

[nick95610]

Update:

After I ran Memtest the last time (with both chips in) the computer booted up and didn't crash. After it passed the 10 minute threshold, I got curious and wanted to see how long it would last. I didn't switch it off, and as it turns out, it lasted a couple of days without crashing. It probably would have lasted to the end of its hardware life, but the geniuses that run the electrical company here decided to turn the power off for a day. When it came back on and I booted the computer back up, it was back to its own schedule of BSODs every 5 minutes.

I didn't really have many options, so I took out a RAM chip, put in my Memtest disc, and rebooted. Sadly, as with before, I could not enter the boot menu, even after many, many attempts. I hear it has something to do with having a USB keyboard. I also hear the way to fix that is to get into the BIOS and enable the USB setting. Now, see, I'd do that, but to get into the BIOS, I actually need the keyboard to work in the first place, so that's probably not gonna happen.

After getting bored of rebooting to get the keyboard to work, and it never doing so, I loaded up into safe mode to see if I could at least get internet access to get some of my work done. Surprisingly, it's not crashing here. So until I figure out how to load up the boot menu, I have a few questions:

-What would cause a problem such as this to, once every hundred startups, not produce BSODs until shut down?

-Can it still be a memory problem if safe mode works fine? If not, should I focus my attention on maybe some leftover drivers from the old hardware that may be causing issues?

Thanks in advance.

 

[richc46]

Might be best not to guess. Give me the BSOD report

 

[nick95610]

Here you go. There will be a few crashes since after the power outage. I went back to normal mode to check a few things. You should recognize them by the date (080612-...).

 

[nick95610]

New update:

I stopped trying to access the boot menu and instead started going for the bios. I eventually got in, and from there, I changed the boot order to DVD first. This way keyboard unresponsiveness shouldn't be an issue anymore.

These are my results:

It's been tough getting my actual work in between BSODs, power outages and loss of internet - of which one or two are occurring at any given time - so I didn't have the time to run Memtest for 6 passes on each chip, but I ran one chip in one slot - the same configuration under which the BSODs occur - for 2 passes and it showed no errors.

I know that's not conclusive, but what might be more telling is this: I installed a fresh copy of Windows on a reserve partition of my hard disk. I let it run for 15 minutes after the installation was complete to see if it would crash. After it did not do so, I installed the audio drivers for the motherboard (and no other MB drivers) and the video card drivers. A few hours later and still no crash on the new installation.

I even booted back up into the main Windows, and it resumed crashing as normal. Right now I'm back again in the fresh Windows, and it's still not crashing.

Is it safe to rule out a hardware problem at this point? I'm not really good with computers, and I don't know how to read crash reports, but from, I guess, a mechanical perspective, I don't see how it could be hardware if it only crashes under such tight conditions.

What could we be looking at? Old drivers clashing with the new? New drivers bad off the CD? Something else entirely? I have no idea, and I don't even know what else I can do to troubleshoot, let alone fix the problem.

Is there anything else than can be gleaned from the crash reports that might solve this?

 

[richc46]

Sorry for the delay. I was not home and did not have the software needed to read your dump files.
The last 3 reports, all indicate memory. Take a memory test.
Run for 8 passes.
Run memtest for 8 passes
Then test each individual stick in a good slot for 6 passes.
If you have dual channel, the results may be incorrect, if shows pass.
Guide to using Memtest86+ - Geeks to Go Forums

 

[nick95610]

No problem. Thanks for sticking with me this long.

I'll run the memory tests overnight and post the results tomorrow.

In the meantime, I was comparing system drivers between the two installations of Windows, and there seems to be only one discrepancy - a management engine interface driver. I'm gonna see what happens if I scrap it.

EDIT: Better course of action - I found out which driver it is on the motherboard's disc. I've installed it on the fresh OS to see if it affects it at all.

 

[nick95610]

First Memtest is done. Chip 1 in slot 1 for 12 passes (yeah, I overslept), and no errors.

I'll test the the same chip in the other slot tonight, then test the other chip the following nights.

 

[nick95610]

Figured I should update this thread in case it ever comes up in search results for someone with the same problem.

The problem is resolved now... kinda.

Between the frequent power outages and all the work I missed while my computer was down, I didn't have the time to run Memtest for each chip in each slot for 6 passes, but in the meantime, I accidentally tripped over a solution.

The more I used the reserve partition's fresh Windows installation to catch up on work, the more drivers and programs I installed to make it more usable. I figured that at some point the BSODs would catch up with me, but they didn't. Since I installed it, it hasn't crashed once while running it.

I'm guessing my old OS just couldn't click with the new hardware. I'm not adept enough to understand why, so I won't try to guess, but it looks like that was it. In retrospect, it was naive of me to think I could replace every part of the computer and still run the old OS.

Anyway, many thanks, Rich, for the guidance and all the time you dedicated. I'm sorry this was such a frustrating problem, but thanks for sticking with it.