Frequent/intermittent BSOD after Windows 7 upgrade

#1
I upgraded my mom's computer to Windows 7, and after loading all the latest drivers, I'm getting random BSODs that say "Page Fault in a Non-Paged Area."

Minidumps linked below:
Minidump 1
Minidump 2
Minidump 3
Minidump 4
Minidump 5
Minidump 6

Can anyone decipher these and tell me what the problem may be?

System Specs:
Operating system and whether it is 32bit (x86) or 64bit (x64),
Which Service Pack: Windows 7 64-bit Service Pack 1
Motherboard Mfr. and model number: ASRock G31M-S
CPU Type and Speed: Intel Core Duo Q6600 @ 2.4Ghz
Memory (RAM) Mfr. and model number: Crucial DDR2 800 4GB
Video Card Type and Speed: NVidia GFORCE 8600GT w/512MB DDR2, Driver version 275.33 (latest driver according to NVidia website)
Power Supply Unit (PSU) Mfr. and Wattage: Sparkle 550W

Memory Tab.JPG

SPD Tab.JPG

Thanks!
Cam
 


Last edited:
#2
Bueller? Bueller?
 


zigzag3143

Honorable Member
Microsoft MVP
#3
About half of these logs were inconclusive. I would run these to tests to define what the true cause/s are.

Memory corruption probably caused by a driver. please run these two tests



1-Memtest.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



2-Driver verifier


I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
 


#4
zigzag- thanks so much.

I'll give that a shot.

Cam
 


nmsuk

Windows Forum Admin
Staff member
Premium Supporter
#6
Looking at the memory timings, they're completely out. Can you set you memory speed to 800mhz with timings of 4-4-4-12-24 2T with a ddr voltage of 2.0V
 


#7
Ran Memtest86 for 5 passes using the extended test. Nothing. Thought I had the problem nailed down to a bad display driver, but the computer started BSOD'ing again. Same thing. Back to square one.

More DMPs here

nmsuk- I'll try adjusting the RAM through the BIOS utility. Thanks for pointing that out. Would be nice if it turns out to be that simple.
 


#8
Here's new SPD and Memory tab screen caps. Do my memory settings look correct now? Is the tRFC supposed to be 24? I couldn't find a place to set that, and it looks like it's at 52 with the CL, tRCD, tRP, and tRAS set to 4-4-4-12 and the voltage @ 2.0V.

Memory2.JPG

spd1.JPG

spd2.JPG
 


Last edited:
This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.