Solved BSOD on New Computer

[tuggumkee]

Hello,

I'm building a new computer, and i've been getting BSOD anywhere from login to 2 hours of useage. I have looked around trying to figure out the problem, and had NIS2011 trial installed and removed it and the BSOD still occurs, so here i am.

Here's my computer specs.

Windows 7 Ultimate x64
AMD Phenom II X4 955 (OC) to 3.2GHz
Mobo - MSI 870U-G55
EVGA Nvidia GeForce GTX 560
Kingston HyperX RAM 1600Mhz 4GB(2x2GB) DDR3 KHX1600C9D3K2/4GX
Hitachi 1TB 7200RPM SATA HDD
PSU - Corsair GS600
CoolMaster 430 GLite Case

I've also attached the Zip File

Hope you guys can figure out the problem!

 

[zigzag3143]

Hello,

I'm building a new computer, and i've been getting BSOD anywhere from login to 2 hours of useage. I have looked around trying to figure out the problem, and had NIS2011 trial installed and removed it and the BSOD still occurs, so here i am.

Here's my computer specs.

Windows 7 Ultimate x64
AMD Phenom II X4 955 (OC) to 3.2GHz
Mobo - MSI 870U-G55
EVGA Nvidia GeForce GTX 560
Kingston HyperX RAM 1600Mhz 4GB(2x2GB) DDR3 KHX1600C9D3K2/4GX
Hitachi 1TB 7200RPM SATA HDD
PSU - Corsair GS600
CoolMaster 430 GLite Case

I've also attached the Zip File

Hope you guys can figure out the problem!

Six different causes. Makes me think hardware please run these two tests.


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.



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.

 

[tuggumkee]

Ok, I have run memtest86 for 6 passes earlier before posting with zero errors, should I still run the test for the sticks individually? I will do the driver test when I get home!

 

[tuggumkee]

Ok, the computer has been in Verify mode for a while, and has now crashed at least twice during this mode. I've uploaded the updated minidump file Zip.

 

[tuggumkee]

Another ATTEMPTED_WRITE_TO_READONLY_MEMORY occured after the last post.

0x000000be (fffff8a0`01f422c8,80300000`5849b802,fffff880`09463500,00000000`0000000e)
ntoskrnl.exe+7fd00

 

[tuggumkee]

Another Update on the BSOD dump. New error types include PAGE_FAULT_IN_NONPAGED_AREA, PFN_LIST_CORRUPT, IRQL_NOT_LESS_OR_EQUAL.

 

[zigzag3143]

Another Update on the BSOD dump. New error types include PAGE_FAULT_IN_NONPAGED_AREA, PFN_LIST_CORRUPT, IRQL_NOT_LESS_OR_EQUAL.

None of these are driver verified. please go start>cmd>verifier /query. Which drivers are listed as being verified?

 

[tuggumkee]

I went and did that, but it opens another prompt that flashes to quickly for me to see(it self closes).

 

[zigzag3143]

I went and did that, but it opens another prompt that flashes to quickly for me to see(it self closes).

If you open a cmd window, then in that type verifer /query it will stay on screen. If it is off it will say no drivers are being verifed.

 

[tuggumkee]

Ok (forgot to run cmd as Admin)

So verified drivers are :

amdxata.sys
serial.sys
nvlddmkm.sys
nvbridge.kmd
rt64win7.sys
ndis.sys
nvhda64v.sys
dump_dumpata.sys
dump_atapi.sys
dump_dumpfve.sys
secdrv.sys

 

[tuggumkee]

Another BSOD, this time PFN_LIST_CORRUPT with USBD.SYS as the driver cause.

 

[tuggumkee]

Quick Question,

Is it possibly any of the hardware? I'm coming up on the return deadline for the hardware, and i'm wondering if i should be worried about returning any of it.

 

[tuggumkee]

Current Update,

I have re-installed Windows, still recieved the BSOD. At that point i had yet to install SP1, so i just did a repair install. During this it said i needed to uninstall ATI manager to do repair install. Looked it up and seems like it was the chipset drivers for my mobo onboard graphics. Uninstalled and left uninstalled, and yet to have a BSOD.

TLR BSOD problems might be fixed, seems like GPU and mobo onboard graphics drivers were fighting, uninstalled mobo graphics. Will update if BSOD shows its ugly head.

 

[tuggumkee]

So i came back from a 10 day vacation, to more BSOD =(. I have 1 day left on my return policy on hardware, so if someone could respond before then it would be great.

So this is from a fresh Win 7 Ultimate install, there are 3 BSOD. The most recent one, (BAD POOL HEADER), occurred only after I updated DirectX (Download Details - Microsoft Download Center - DirectX End-User Runtime).

The Bsod are not as frequent as before, but since there is only one day left in my return policy on all the hardware i figured i should post ASAP. (plus never having bsod is better than having it infrequently).

Those 3 BSOD did not occur while running driver verifier, i'm currently running in it now and will post when more BSOD occurs.

 

[tuggumkee]

Still having Bsod, ran memtest on ram again, and currently running hard drive test. can anyone tell me if its more likely hardware or software problem?

 

[tuggumkee]

Discovered it was a motherboard / 1600mhz ram incompatibility.