Fault in Non paged Area Error (Solved - Sort of)

Ok - life was great and right in the middle of my session I get a "Fault in Non Paged Area Error" error and BSOD. After windows restarted I relaunched X1, opened the same session and as it's loading - same error. I've restarted X1 in safe mode without any plugins and it opens. I can also open other sessions with plugins and no problems. So do I just have a corrupted VST? When I get home I'll try to shut down one plugin at a time. But each time I'm wrong the computer will crash again. Ugh!

Has anyone else had this problem? A quick internet search indicates it may be more of a driver or memory problem than a software problem. So I'm wondering if my approach will not fix the problem. I'm just curious if anyone has any suggestions before I get home and start troubleshooting????

Thanks!

wineshop

When I get home I'll try to shut down one plugin at a time. But each time I'm wrong the computer will crash again. Ugh!

less crashy: better to disable them all down to start with, then re-introduce one at a time, the first one to cause a crash is likely the culprit(s)

Ok. Now I'm really confused. I opened my session in safe mode, and one at a time started it with each plugin. Each time it opened fine. All the way to the end. Every plugin opened and the session worked fine. Then I saved it again. Then closed it again and opened the session in normal mode. Crash!!! Same error.

I don't get it. I had every plugin open and working. One other thing - all of a sudden it asks me where my Waves 8.0 folder is every time. I only own CLA. But every time I open my session (safe mode or regular mode) it pops up and asks where that Waves 8.0 folder is. It's never done that before. May have nothing to do with my problem, but still ...

Update. I've narrowed one thing down - the crash only happens when I load a large session (25 tracks or so) into Sonar X1 with my Focusrite Saffire pluged in. That's when it craches. If I have my Line6 DI connected as the interface, everything loads up fine and plays. So - I'm thinking, "dead interface or dead FW card". However, all windows sounds, youtube, home videos, even smaller Sonar X1 sessions - all open and close fine with the Focusrite as the interface. But when I open one of my large sessions - boom.

So I found about 5 common pluggins between the problem sessions. I started X1 in safe mode without those common plugs. It still crashed. I tried a different (TI Chipset) FW card. Same problem. Updated Focusrite firmware - no help. Windows, drivers and Sonar are all up to date.

Is my Focusrite the problem here, or is it still a software issue? Please help!!! Should I uninstall and reinstall Sonar X1? What to do??

IMHO the best way to test for bad RAM is to pull out one stick at a time and run your test project with each stick out. If it stops crashing with a particular stick out, there's the culprit. 

Thanks y'all. And yes, I'll try one chip at a time. I built this computer - so perfectly comfortable opening her up.



Are you sure the error wasn't "fault in non paged area"?.
You are exactly right. Sorry - typo on my part! Thanks for catching that (I've now corrected it).



My specs:
Win 7 64bit Home Premium
i7 2600K (not overclocked)
Gigabyte GA-P67-UD3-B3 MB
Mushkin blackline RAM 8GB (2x4GB)
MSI GTS 450 video card
Corsair 600W PS
3x1 TB hard dives - none are close to full.

You may be on to something about the Ram. I've actually already replaced the RAM. When I first built the computer (back in June) it would randomly freeze. I figured out it was the memory. Mushkin RMA'd it so this is my 2nd set. However, memtest86 shows no problems. I'll try it with one chip at a time. Freezing did stop, by the way with the new Ram.

Thank you.

Funny, I had the same error today but nothing to do with SONAR.  I was running Win Media Player. 

wineshop


Update - I tried it with each Ram chip pulled, one at a time and it crashed both times. So - I think it's safe to say memory is fine.

Get this - I set up Sonar to use my Line6 DI as its interface. It works with it, as I stated before. But here's the interesting part - while my session was open I changed devices in "preferences" (unchecked the Line6 DI and checked the Focusrite) and as soon as I did it crashed with the same error.

But if my Focusrite is bad, why does it work with some sessions and why does it work with Windows files, iTunes, etc? I don't get this. And I don't have another FW interface to try out.

Any more ideas????

I don't see where you mentioned the actual "STOP ERROR" number ... do you know it?

You might want to try turning OFF the windows swap (paging) file if you're using one;  reboot, see if things load normally without issue.

If they do, you probably have a funky drive, or cable, or section of the drive, or windows setting for the swap file.

I've seen swapfile's bite people in the arse a few times (though I DO use one myself).

It could be still the RAM. I did a fast checkup for Mushkin blackline RAM, and from the specs it seems to need 1.65 V. Most newer motherboards give standard 1.5 V, because the i7 2600K is advised to have memory voltages below 1.65V. The 1.65 V can damage the processor at the long term...

It can be you have a RAM version that works well below 1.65 V, but without knowing the exact part number it is impossible to say. If not - then it is possible the RAM just cant get enough power to work within specifications, leading to strange errors...

Anyway - take a look in the BIOS of your motherboard and look what Voltage your memory is getting, and compare that to the specifications of the RAM...

It might be useful if you said which version of Windows you are running :-)

"Fault in Non Paged Area" with stop code 0x0000005 and ntoskrnl.exe the culprit can point to an application looking for something in RAM and failing to find it. So Windows (correctly) looks to see if it's in swap. If the data's not found in swap, that BSOD error can be generated. In other words, it indicates a possible failure to write to the swap file/read the data from swap once written.

I suggest checking the Windows logs for errors (or lots of retries) paging/reading/writing to the hard drive(s) - especially the one holding the swap file. Run checkdisk on all drives, with both the "automatically fix file system errors" and "scan for and attempt recovery of bad sectors" boxes ticked and see if that turns up anything. It may also be an idea to download a copy of Speedfan (free) and use its ability to read the drive's SMART data and then provide a detailed report (via the web) on what it's found. Also check the drives aren't running too hot.

Also check the drive cables are propely connected, data and power.

Or it may be something else entirely (RAM, dodgy driver or hardware - audio or video...), such is the nature of the cryptic 0x000etc....

It's worth searching Microsoft's website with the error code and version of Windows you have as search terms. Most BSOD error codes are documented there somewhere or other.

PS-  if you're overclocking anything, cease doing so and see if that improves things (some BIOS's overclock by default, so you may be overclocked without realising it - watch out for things like "TURBO" settings).

Has X1 ever worked properly using the Focusrite with a large project loaded?

From the sounds of it, if X1 is the only software causing a problem it's possible there's some kind of conflict going on between the Focusrite drivers/FW drivers and X1. Or some link in the hardware chain is flakey - but not yet flakey enough to show an easily identifiable fault.

However, if it all worked OK once, then something must have changed to break things. An X1 update maybe? The latest hotfix is useless to me as it won't recognise the WASAPI drivers for my Cakewalk(!) UA-101 at all.

Maybe it's time to raise this with technical support if you haven't already done so?

My problem is with the ASIO drivers. I have no idea why I didn't try that sooner, but when I switched to WDM - no problems. Now, I'm not sure why all of a sudden that would happen when I've always used ASIO. But, for now, I'm making music again. I just wanted to post this in case someone has the same issue in the future. Maybe they'll try to switch drivers before puling their hair out.

Thanks

No need to uninstall and reinstall SONAR when switching audio interfaces.

BTW, did you have your Focusrite connected to a Texas Instruments Firewire chipset?

SP



Thanks for chiming in. My apologies, I think my comment a few posts up sounded confusing. I actually never uninstalled Sonar. But what I was implying was that as a troubleshooting method I should attempt a reinstall in hopes that would fix my problem before I resorted to purchasing a new interface.

And yes - I do have a TI FW chipset.

Thanks again