PAGE_FAULT_IN_NONPAGED_AREA... dammit

[backfire]

Yea, that's the nice message I get when I start up my computer. It's been this way since last thursday. I start up the computer, log in, a few programs load, gets to about the point where skype starts, then just turns to that. What's weird about it is that I can seem to temporarily fix it by running a disk check. It takes about 3 or 4 hours, but after it reboots from that, everything works fine. It's only when I shut down the computer and start it up again does it do this on log in.

After I figured this out, I just decided to leave it on until I can figure out how to solve it permanently. Can't bluescreen on startup if I don't startup. Although, nature seems to want to screw me over. The storms here got so bad the power went off for a good 30 seconds. Just long enough for me to start up the system again and get that same damn error.


So anyways, I'm thinking it's not hardware related since everything works fine after the disk check and safemode starts up fine... so... any ideas? :-\


If that error code below is of any use, it's

*** STOP: 0x00000050 (0xFFFFF880068C08E8, 0x0000000000000000, 0xFFFFFA8004F67058, 0X0000000000000000)

Oh, and running Windows 7 64bit

Update
Also it seems I don't have to run a diskcheck across bad sectors, so it only takes me about 20 minutes. I still want to figure out how to fix the problem completely though.

[Mission Difficult]

You might try using something like SpinRite to make sure your drive isn't failing.

[DragonEkarus]

If this happens after Skype starts maybe Skype needs re-installed, have you tried not starting skype?

[backfire]

Skype wouldn't cause a blue screen. Plus it works fine when starting up directly after a disk check. It's not even "right" when it starts up skype, that's just around the time of the login process where it fails.

[Kirby]

It's Windows.


Saying "Skype wouldn't cause bsod" is a really dumb assumption to make.

[Ianki]

This was happening to me a lot, and it's a pretty non-specific error.  It's most likely either a hard disc, driver, or memory issue.  For me it was a memory issue.

You might want to run prime 95, just to see if it's a memory/cpu/motherboard issue and you can zero in from there.

you can also check the rated specs of your ram and make sure the bios is running it correctly.  my problem all came down to running my ramm at the right voltage.

[WaR1761]

Majority of blue screens are memory errors in my past experiences. Once you run checkdisk and or other windows hdd checking tools it normally flags bad sectors so they then aren't used again.

[Geoff]

was a memory error for me as well

[HeK]

http://www.memtest.org/

Also, I cannot stress it enough, double check your ram voltage and timings!!