New build with a BSOD every hour.

I think I finally managed to get the dmp readable. Who knows if I did it properly, but it appears to my uneducated eyes to be what I need.

I get a blue screen of death ever hour or so, more frequent if I am clicking fast or using programs....but it will blue screen just sitting around doing nothing.

The most common by far is MEMORY_MANAGEMENT. But SYSTEM_SERVICE_EXCEPTION and BAD_POOL_HEADER are not far behind. Plus I have had a couple that mention the NTFS file system and even IRQL_NOT_LESS_OR_EQUAL and PAGE_FAULT_IN_NON_PAGED_AREA.

I have run memtest86+ multiple times. It ran all night for about 6 hours with zero errors, but then every once in a while it will give 100,000+ errors after 1 pass...which makes me think maybe its the mobo?

Here is my build:

Windows 7 64bit
ASUS P7P55D-E
Intel 860 i7 quad core
8 gigs DDR3 1600mhz G.Skill
BFG GTX 260 Maxcore 55 OC
2 HDs currently, but the OS has been on 3 now trying to get this to work.
EchoAudio AudioFire4

I think that is all the important stuff.

I just randomly made text files of 4 dmp readouts. But I have like 20 of them from the last couple days since doing my last clean install.

My opinion...the harddrives are not it IMO, I have had the OS on 3 drives now. The AudioFire is firewire, but I removed the driver and it still gave BSODs.

Please help me, I dumped almost all my savings into this thing. Its my 4th build (2nd for me) and first time I have ever ran into the BSOD.

 

I forgot to mention that Firefox seems to quit a lot, and also the transparent Windows bars and Taskbar will occasionally cease to be transparent.

 

Hmm, have you tried a similar approach with one stick of memory installed at a time and testing other slots too if all the sticks passed the test?

 

No I haven't. I guess I probably wrongfully assume that Ram would fail all the time if it was bad and if it passes 6 hours with all of them that random failures would be something else causing it like the Mobo...can a graphics card cause that? I will try that a bit later.

 

Well, the last time I had errors like that was bad RAM as it was writing garbage onto the hard drive and eventually the OS totally failed. Perhaps someone else has a better idea. Sorry.

 

Thank you for your thoughts. I need all the help I can get.
I just pulled 2 sticks of ram and my computer can barely load the desktop. I think 4 gigs shouldn't have a problem with this simple task. :confused Things seem to have sped up now though. We will see if the blue screens persist.

 

That ain't right at all sir! You should have no difference in boot up time between 4 and 8GB, possibly even two! Are your hard disks thrashing about when booting?

 

My comp has been running non stop since my post. Not long enough to feel confident, but long enough to wonder.

Just rebooted took forever to get going again. By "thrashing about" I assume you mean the typical seeking data sound...except all that data needed during boot should probably be kind of close together so it shouldn't have to seek much? Yes, then it is thrashing around during boot up...and it still is right now. Kind of weird. I have an Antec P193 so I honestly haven't noticed how noisy is has/was been, but this doesn't seem normal.

Please don't say it would be my hard drive because I have been getting BSOD on this build with the OS installed on 3 separate drives, all brand spanking new.

I should also mention I ran Uniblue RegistryBooster, its from a company BFG told me to get a drive sweeper from even though this is a new system. On a fresh install of Windows 7 I had 30+ registry errors. All but 3 of them were "system related errors". After installing software and massive amounts of BSODs I am currently at 150 system related errors, and 7 user related errors specific to the windows account. 0 are considered 3rd party.

 

Can't edit posts on this forum?

Anyways.....after pulling one of the two remaining sticks of RAM, the computer loads the desktop as normal. Thought I was closer to solving the problem but I put the other stick from B1 in place of the last one in A1 and it still booted good. Took it out and put it back over in B1 with nothing in A1 (manual says ok) and it booted good. So neither my RAM or mobo was causing the slow down. I should mention that prior to all this I did a reboot and a checkdisk ran. it looked like it repaired some stuff and then after booting the desktop took forever like it had been. This is when I started pulling and moving RAM as stated above and haven't had the issue during boot thus far. I assume at some point my HD took a hit from all this and now it seems to be okay..... Still haven't had a bluescreen. I will probably run it with the two sticks again now just to see what happens.

 

So I have been running my computer basically without blue screens for almost 24 hours. I hope this is coincidence, I don't like when problems just disappear because they usually come back.

Here is the thing....I am only running two sticks of RAM. Half the time has been with one pair and the other half with the other pair.

Does this mean my mobo has some bad slots or something?

What kind of reasons would 8 gigs crash a 64bit system but 4 wouldn't?

And I say basically without blue screens because when I first swapped the two sticks for another two sticks it bluescreened once as soon as I hit the desktop from booting. But its been running fine ever since.

I would run Memtest86+ on these two sticks but my BluRay drive coincidentally broke...won't read my disk, sounds like a noisy mess inside it.

 

I had switch back to the original two sticks of RAM. Last night I went to the other two sticks that had previously blue screened that one time during the initial boot....computer boots fine and then as soon as I open firefox I am presented with another BSOD.

It goes to show that even Memtest cannot find all the bad ram out there. But at this point I am fairly confident it is my Ram causing this.

thanks so much for the help.