BSODs just after windows start up

[bagri2]

I've recently put together my first new full build, and I need some help troubleshooting. I have been getting some bad_pool_header BSODs the first few times I start it up, and occasionally some artifacting when not running games (I thought I had this solved with a fix in CCC, but it came back).
As the PC was relatively stable after a few tries booting, I didn't put too much time in to fixing it.
The wireless card then went missing from device manager, and I decided to get to the bottom of it, as having no net is no fun.

I tried to run memtest, and it would reboot the computer a few seconds in to the test.
I tried again with 1 stick in slot 1, and it worked with no problems.
Other stick by itself in slot 1, no problems.
Running memtest with both sticks in any combination of slots 1-2, 1-3, 1-4, 2-1, 3-1, 4-1 etc, all cause a reboot. I haven't tried 2-3, 2-4, 3-4 etc.

Now I have just reformatted and reinstalled Windows, running with one stick in slot 1, and I have had no BSODs or artifacting just yet, and the wireless card is found and everything seems to be working.

I've attached all the minidumps of BSODs from before my reformat, any ideas on what is going on would be much appreciated.

Specs:
CPU: AMD Phenom II 550
M/B: Gigabyte GA-MA785GT-UD3H
RAM: 2x2Gb G Skill DDR3 1600Mhz
Video card: Sapphire ATI HD 5770 Vapor-X OC Ed 1Gb
Case: Antec 300
HDD: WD 1.5Tb Green
SSD: Patriot 64Gb
Optical: LiteON IHAS324 24x
PSU: Thermaltake Litepower 700W
CPU Cooler: Cooler Master Hyper TX3
O/S: MS Windows 7 HP 64bit
Wireless: D-Link DWA-510
Sound Card: Createive Sound Blaster X-Fi Xtreme

 

[zigzag3143]

I've recently put together my first new full build, and I need some help troubleshooting. I have been getting some bad_pool_header BSODs the first few times I start it up, and occasionally some artifacting when not running games (I thought I had this solved with a fix in CCC, but it came back).
As the PC was relatively stable after a few tries booting, I didn't put too much time in to fixing it.
The wireless card then went missing from device manager, and I decided to get to the bottom of it, as having no net is no fun.

I tried to run memtest, and it would reboot the computer a few seconds in to the test.
I tried again with 1 stick in slot 1, and it worked with no problems.
Other stick by itself in slot 1, no problems.
Running memtest with both sticks in any combination of slots 1-2, 1-3, 1-4, 2-1, 3-1, 4-1 etc, all cause a reboot. I haven't tried 2-3, 2-4, 3-4 etc.

Now I have just reformatted and reinstalled Windows, running with one stick in slot 1, and I have had no BSODs or artifacting just yet, and the wireless card is found and everything seems to be working.

I've attached all the minidumps of BSODs from before my reformat, any ideas on what is going on would be much appreciated.

Specs:
CPU: AMD Phenom II 550
M/B: Gigabyte GA-MA785GT-UD3H
RAM: 2x2Gb G Skill DDR3 1600Mhz
Video card: Sapphire ATI HD 5770 Vapor-X OC Ed 1Gb
Case: Antec 300
HDD: WD 1.5Tb Green
SSD: Patriot 64Gb
Optical: LiteON IHAS324 24x
PSU: Thermaltake Litepower 700W
CPU Cooler: Cooler Master Hyper TX3
O/S: MS Windows 7 HP 64bit
Wireless: D-Link DWA-510
Sound Card: Createive Sound Blaster X-Fi Xtreme

I have only run 5 of the 30 DMP's so far and though they seem to point to win 7 files I believe it iws still a memory problem.

You need to finish the memtest run in all configurations.

Ken

BugCheck 3B, {c0000005, fffff80002058e6d, fffff8800812f610, 0}
Probably caused by : memory_corruption ( nt!MiDeletePfnList+1bd )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {fffff8a0034531ec, 0, fffff8800125ec9c, 0}
Probably caused by : Ntfs.sys ( Ntfs!NtfsPrepareFcbForRemoval+38 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 19, {20, fffff8a00a222700, fffff8a00a222780, 5080113}
Probably caused by : ntkrnlmp.exe ( nt!CcDeleteSharedCacheMap+1bc )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 34, {50830, fffff88002f7e8e8, fffff88002f7e150, fffff880012c4f9d}
Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireScbForLazyWrite+25 )

 

[bagri2]

I have only run 5 of the 30 DMP's so far and though they seem to point to win 7 files I believe it iws still a memory problem.

You need to finish the memtest run in all configurations.

Ken

BugCheck 3B, {c0000005, fffff80002058e6d, fffff8800812f610, 0}
Probably caused by : memory_corruption ( nt!MiDeletePfnList+1bd )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {fffff8a0034531ec, 0, fffff8800125ec9c, 0}
Probably caused by : Ntfs.sys ( Ntfs!NtfsPrepareFcbForRemoval+38 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 19, {20, fffff8a00a222700, fffff8a00a222780, 5080113}
Probably caused by : ntkrnlmp.exe ( nt!CcDeleteSharedCacheMap+1bc )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 34, {50830, fffff88002f7e8e8, fffff88002f7e150, fffff880012c4f9d}
Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireScbForLazyWrite+25 )

Sorry, I'm not all that familiar with memtest.. When you say I need to finish the memtest run in all configurations, does that mean I need to run tests with the memory sticks in the other slot combinations, being slots 2-3, 2-4, 3-4 etc?

 

[Jonathan_King]

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run it for at least 5 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.

 

[bagri2]

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run it for at least 5 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.

Right, I have followed the above instructions and run memtest86 on my RAM. Both sticks report no errors if put in by themselves, in any slot.

However, if I put both sticks in together, in any combination of slots, and try to run memtest86 it causes the computer to reboot within a few seconds of the test starting.

Is there something I'm missing about memtest86? Can you only test one stick at a time?

---

An update on where I am up to now: I have reformatted and reinstalled Windows 7, and haven't recieved any BSODs since. I've experienced some artifacting, but I'm assuming its a video card issue at this stage. I'm running with both sticks in there, and waiting to see what goes wrong.

Apologies if I'm posting in the wrong section of the forum now.