Random BSOD's on new Windows 7 install, even when left overnight

[alucardleashed]

New computer, I had just re-installed Windows 7 Ultimate x64, and I'm receiving random BSOD's (both Page_Fault_in_nonpaged_area & Memory_management) errors, which requires me to restart. Was having BSOD's previously, which prompted me to try re-installing Windows from scratch. It seems to happen without much warning or provocation.

Can you please help me determine if this is a hardware issue, driver issue, or a software issue? I've attached the zip from the SF_Diagnostics program.

Thanks!

 

[Arc]

Welcome aboard.

► You need to run Disc Check, as there is NTFS corruption.

1. Reseat the sata and power.
2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
3. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

► There is filmgr.sys corruption too, usually caused by Antivirus programs.
Uninstall AVG, and install Microsoft Security Essentials - Free Antivirus for Windows


► Uninstall the following things:

Start Menu\Programs\ASUS    Public:Start Menu\Programs\ASUS    Public
Start Menu\Programs\ASUS\ASUSUpdate    Public:Start Menu\Programs\ASUS\ASUSUpdate    Public
Start Menu\Programs\ASUS\EPU-4 Engine    Public:Start Menu\Programs\ASUS\EPU-4 Engine    Public
Start Menu\Programs\ASUS\GPU NOS    Public:Start Menu\Programs\ASUS\GPU NOS    Public
Start Menu\Programs\ASUS\PC Probe II    Public:Start Menu\Programs\ASUS\PC Probe II    Public
Start Menu\Programs\ASUS\TurboV    Public:Start Menu\Programs\ASUS\TurboV    Public
Start Menu\Programs\Catalyst Control Center    Public:Start Menu\Programs\Catalyst Control Center    Public

► Update ATI display driver:

Driver    c:\windows\system32\drivers\atikmpag.sys (8.14.1.6099, 184.00 KB (188,416 bytes), [COLOR=Red]2/10/2010[/COLOR] 9:11 PM)

Let us know the results.

 

[alucardleashed]

Thanks for your help. We've went through your list of items, and followed all your instructions. However, none of the tests turned up positive for any type of disk or NTFS corruption. I ran the Seagate and Chkdsk /f/r again yesterday, and still they came up without finding any corruption or bad sectors.

I've attached an updated copy of our SF Diagonostic logs, as well as screenshots of the Seagate Tools for Dos' findings.

Do you have any other suggestions that might help? Thanks again for your help; we'd really like to get to the bottom of what's causing these seemingly random BSOD's. It seems to happen more frequently when we try to restart the computer from Windows 7.

 

[koolkat77]

Did you make sure all the hardware is compatible with each other? Are the RAM voltages same? If any overclocking is done, please revert to defaults. Did you uninstall AVG and use MSE as Arc suggested?

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA 
Usual causes:  Defective hardware (particularly memory - but not just RAM), 
Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
BugCheck 50, {fffff80808858bcc, 0, fffff880012f3a91, 5}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefix+121 )
------------------
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA 
Usual causes:  Defective hardware (particularly memory - but not just RAM), 
Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
BugCheck 50, {fffffa2708c5e018, 1, fffff8800427a756, 7}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::ReleaseReference+16 )

Suggest taking memtest after you've checked the voltages of your RAM.
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

→ http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
→ Guide to using Memtest86+ - Geeks to Go Forums

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

 

[alucardleashed]

Thanks for the suggestion. The computer is not overclocked, and the two RAM sticks are the same brand and speed, with the voltage properly configured in the BIOS. As per suggestion, AVG was removed, and MSE installed instead.

We ran Memtest for 7+ runs, as suggested, and found one of the our two 4GB memory sticks to be faulty after testing it in several memory slots. After replacing the faulty stick (with one of the same brand and model), and testing with Memtest to make sure the new stick wasn't faulty, we find the system to be more stable than before.

However, when playing games (such as League of Legends), we are met with yet another BSOD, this time a "IRQL NOT LESS THAN EQUAL" error that we had not seen before.

I've attached our latest SF Diagnostics logs, for your further investigation.

Thanks again, and hopefully with your help, we'll be able to resolve the cause of this latest error.

 

[koolkat77]

Latest BSoD was caused by some old drivers of the ATI card.

4: kd> lmvm atikmdag
start             end                 module name
fffff880`04845000 fffff880`053f8000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Wed Jul 04 11:16:13 2012 (4FF3D19D)
    CheckSum:         00B618E2
    ImageSize:        00BB3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

fffff880`009fd578  fffff880`04af89ecUnable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0x2b39ec

Download and install the latest, but first uninstall the older ones first.
Click on the Start rb: ► Control Panel ► Programs ► Uninstall a program ► Uninstall all the ATI stuff.
During installation of the latest drivers, avoid "CCC - Catalyst Control Center". If you feel there are remnants of older drivers of the card, use Driver Sweeper to get rid of them. Reboot as many times required during this process.

After installing the latest drivers take the Furmark Test
Video Card - Stress Test with Furmark

• http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Monitor your temps with Speccy during these tests

• Speccy - System Information - Free Download

Keep us posted, good luck

 

[beret21]

Clear the page file once and see if that helps ! ! !

 

[alucardleashed]

Just an update, now that holidays are over. We're still getting BSOD errors, even after adding a dedicated nVidia graphics card to the system. All display drivers are updated, straight from nVidia. I'm starting to suspect that maybe the motherboard could be the cause of all these errors.

Please see attached the latest SF Diagnostics logs. Further assistance would be much appreciated.

 

[Arc]

Install Service pack 1.
Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

Apply a different version of display driver.

• Download and install Driver Fusion.
• Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.

Let us know the results.