BSOD: irql_not_less_or_equal AND page_fault_in_nonpaged_area

Dan, you've asked for help finding the cause of your crashes, but you don't seem to want to do any of the tests recommended.

You should do the tests recommended or take your computer to a shop where they will charge you to do these tests.
You've had this problem since last August, if you would perform the suggested tests, it would be solved by now.

It's your computer and your choice.
Let us know if you want to continue.

What I'm trying to determine is if we have a software problem or a hardware problem. From what you have told me, you only get bsods when in Windows. That could be software or hardware. The hardware is used when in bios, but not the hard drive. You have said you never get bsods in bios. That could be anything from corrupted system files, drivers or the hard drive itself. You enter bios before the hard drive becomes involved. If you run the Seatools, it is Seagate's diagnostic program. It should tell us if the problem is the hard drive itself. If you can boot from and run a live Linux distro, which runs from ram with little to no involvement of the hard drive, and not BSOD it will tell us that most likely, the problem is the hard drive or something on it. If you can run a linux distro from ram for a long time and no bsods, and if the Seatools gives your hard drive a clean bill of health, we will know it is something on the hard drive. It could be a virus, a bad driver, corrupted system file or a multitude of things. But, you cannot take a hard drive with Windows installed from another system and not expect to get BSODs. It is set up for different hardware, different motherboard drivers, different software drivers and many other things. Diagnosing and testing things, can be a long tedious affair. But, if you are willing to do the work, I think we can get there. If everything I explained above checks out, I am going to want you to wipe the hard drive completely clean, get another known good hard drive or buy a new one. We will do a clean install of Windows only and start adding 1 program at a time slowly, giving each program and driver time to show if it is the problem or not. Eventually, one driver or program will start the BSODs and we will know exactly what program or driver is causing the problem. That is my thinking and my ideas. I hope that explains where I am going. But, the important thing is I am not there. You have to tell me exactly what is happening and what you are doing each step of the way. If you get an error message, I need to know what it is. If something odd is happening, I need to know. You have to be my eyes and ears, in other words. I hope that explains what I am thinking, if you have different thoughts, pease let me know. Also know that Windows system files will almost never ever cause a bsod unless they are corrupted, even if a mini dump blames them. Many cases the dump files have to blame it on something but cannot figure out what caused it, so it will blame a system file. In actuality, it was something else that caused it. Does that help you understand better?

Dan, first go to device manager, click start type device in the search box and click on devicee manager. What has yellow triangles or exclamation points on it? Also, try goig to your motherboard's web site and download and install the chipset drivers. If they are not listed as chipset drivers, they will be an .ini file also wownload and install Microsoft security essentials.

Dan you also need a good CPU temp program, and always keep tabs on the CPU temp, but especially while running Prime. Nothing will heat your CPU more than Prime. That's what it is designed to do...Stress tour CPU as much as possible. I use Core temp. How is your graphics card doing?

I hope my explanation of what I was looking at made sense. But, from what you just wrote blows holes in that theory. Also, please go to Windows Update and check for new updates until it can find no more.

Also download CPUz,. Run the program, It's very safe. Show screenshots of the main window, plus screenshots of the memory tab and the SPD rab. In the SPD tab the top left is 'slot number'. If no ram is installed in that slot, it will be blank. So, keep changing skllots until you find a;; your ram.Screenshots and Files - Upload and Post in Seven Forums

Dan, Please go to bios and go to ram timings and set the Command rate (CR) from 1T to 2T) @T is easier on the ram and causes less problems, also make sure the Dram voltage is set to 1.5V (or whatever is on your ram). See how that works for you. If you continue to bsod, we will increase the dram voltage and the CPU NB voltsge s little. Although I don't believe it makes a difference, the FSB is slightly elevated, but I wouldn't think enough to worry about. Also, how are your temps?

According to the BIOS, CPU Temperature hovers around 42 C and NB Temperature hovers around 40 C
I don't have the hard drive and GPU temps at the moment (they aren't in use at the moment), but they've never had any problems.

Perhaps my BIOS is weird, but I couldn't find the Command Rate.
EDIT: Confirmed. There is no way to set the Command Rate in the BIOS for my board... I tried searching for a BIOS mod which would allow me to (I heard rumors of one for ECS), but I couldn't find it.
In the BIOS "Memory Configuration" there are options to set the DRAM Timings for the following items (in CLK cycles): TRCD, TRP, tRTP, TRAS, TRC, tWR, TRRD, tWTR
For any of these, 4 CLK is the lowest they go.
I looked all through the BIOS and the Motherboard Manual but I couldn't find anything related to the Command Rate.

According to the CPU-Z screenshots I attached, the voltage for the RAM is set to 1.50 V.
Though, in the BIOS it says VDIMM voltage is 1.608 V... is that the same thing?


EDIT:
So, does that mean you've narrowed down the problem to the Motherboard?
The board is designed to work with DDR3 1333 RAM, so trying to mod the board settings so that the RAM works leads me to believe that the board is the problem.
It seems like the most likely candidate to me (especially considering the reviews).

Correct me if I'm wrong here....
We've eliminated the hard drive (by getting the same errors on two empty drives with fresh Win 7 installs).
We've eliminated software and drivers (by extension of eliminating the hard drive).
We've eliminated the RAM sticks (by swapping them out with a separate working machine, and running MemTest86+).
The CPU, while not eliminated, seems like an unlikely candidate (that, and the fact that it passes Prime 95 stress testing makes me think it is fine).
The voltages are ok (I think), so that eliminates the PSU (right?).
That leaves us with the Motherboard, correct?

I would settle for 95% confidence at this point.
I'm not concerned at all with Fixing the board... especially considering the board is not that high quality to begin with.
I would be fine simply buying a nice new ASUS board... if you think that will solve the problem.

Thanks,
Daniel

Daniel, to be perfectally honest, I have no idea what the problem is. The reason I wanted to set the CR to 2 is that it is easier on the IMC to run it at 2 rather than 1. It will not change the frequwncy at all. But, when you say it passes Prime... To pass Prime you need to run it for a minimum of 8 hourd. many here insist on 12 hours before calling it stable. Also, are you sure you ran Memtest for 7 Passes on each stick in each slot? I've never been able to run 7 passes in less than 6-8 hours. There is some reason you can be in bios and never bsod. When you start your computer the bios goes through POST (Pre operation self test) initalizing all hardware attached to it. When you boot it habds the process over to the hard drive and the OS. That is the only point you bsod. You say you ran memtest86 for a couple of hours. That runs from ram also and no BSOD. I read your manual too. There is a lot to be desired in that board. There are too many settings that are not available to you. Either I'm missing something here, or the problem resides in the hard drive, OS or something on it. That is when you BSOD. Yes, it could be the sata controller on the board or the IMC on the CPU or several other things on the board. The CPU being bad is possible, but highly unlikely. I have no idea of your finances, but if it were me, before spending money on anything, I would make sur of the memory bu running each stick for 87 full passes, I would run Disk Check on the hard drive. Like you, I would want a board I have some confidence in. But, if you have an excellent board and any of these things is the issue, you will have the same problems. If you buy a new board, you may consider upgrading your system. I don't know what you do with your computer, but the Phenom II is getting 'a little long in the tooth' right now.