BSOD:s again..

[baarod]

Wow.. Ran SFC /scannow and it found corrupted files but was unable to fix them, uploading report cause it looks pretty bad :/

Oh, and noticed it ain't "first boot of the day".. If I leave computer without power for about 2 or more hours it crashes after next startup.

Very troubling. Any idea what happened? Please list all system related software you have used that is not published by Microsoft. We can likely repair whats occurred but you are reaching a point of diminishing returns rapidly -- persistent crashes, a verifiably corrupted system, etc. It may be a better course of action at this point to backup the files you need and reinstall 7.

 

[Nippe]

Hum.. This is a link to very first thread I started after I set up my new PC, it should give most of information you need.

http://www.sevenforums.com/crashes-debugging/124087-computer-bsods-frequently.html

 

[CarlTR6]

Nippe, run SFC at least three times. From my experience, if SFC find multiple problems, it only corrects them one at a time. Let us know the results after three or four runs with SFC. If this does not do the trick, I concur with baarod, it is time to do a clean reinstall.

 

[Nippe]

And programs I got running:

 

[Nippe]

Ok.. Ran SFC like 5 times now.. Don't think it managed to fix anything but heres report anyways:

 

[Nippe]

So only solution is to do clean install? What about if problems come back?

 

[CarlTR6]

You can try a repair install: http://www.sevenforums.com/tutorials/3413-repair-install.html. If this does not work, it's time for a clean install: http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html.

 

[Nippe]

OK, today I decided to reinstall Windows. When computer started installing it crashed after 10% and bluescreened (BAD_POOL_HEADER). That was first startup ofc, after that I tried again and it installed just fine. Seems like its hardware issue?

 

[Nippe]

Ran SFC with clean install now and it didn't find any problems. Will see does if bluescreen tomorrow (hope not)

 

[Nippe]

Might have found a cause for bluescreens! Had a chat with some guy in WoW about those lags and he said that uninstalling some ASUS programs removed them from him.. So I did so and my lags were gone. He also said that program called "SmartDoctor" which has to do something with graphic card fan speeds caused bluescreens for him while playing. So I googled about that thing and found this site:
ASUSTeK Computer Inc.-Forum- Blue Screen Crashes, ASUS Drivers and Smart Doctor

Ok, I really hope someone from ASUS reads this aswell
If not, at least some information regarding windows crashes with ASUS Drivers:
I have experienced *random* blue screens on PC Startup after buying the 8600 nVidia from ASUS - and as I tend to tune everything to the owner settings I installed the whole software suite that comes with it (including Smart Doctor) - and upgraded all to the latest version from the ASUS download site - still blue screens.
Soooo... I went into digging through the stack dumps of windows to check what is actually happening.
Here is what I found:
If you have the Blue Screen Crash just on windows starting - when it starts to load your software uninstall Smart Doctor and it will go away. The problem with Smart Doctor is, that it is trying to acces the driver features to read the Video Card state and data, before the Video Card Driver finishes to initialize / load fully itself. It accesses so, an uninitialized part of the driver and / or card which does lead to a Page Fault in an Unpaged Area (Driver Memory) -> Blue Screen + Reset.

That looks excactly whats been happening for me.. Trying to uninstall those programs and see if that does the trick.

 

[CarlTR6]

Yes, it does seem like a hardware issue. I suggest that you run Memtest86 from a cold boot after your computer has been off for a while. Run it for at least 7 passes. This will take 6-8 hours. Follow the instructions in this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[Nippe]

Seems like computer is still crashing even without any programs installed and SFC don't find any problems.. Going to run Memtest86+ tomorrow (hope it can test 8gb of RAM) and post back results when done.

 

[CarlTR6]

Very good. We will be waiting for the results.

 

[Nippe]

Okay, I left Memtest86+ running for 6 hours and it seems to have found pretty many problems.. I have no clue how to read those error outputs but seems like errors are between 2gb and 4gb. Guess I just have to start going thru memory sticks 1-by-1 like in http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html and see if I can identify bad sticks and then go to shop..

 

[baarod]

Okay, I left Memtest86+ running for 6 hours and it seems to have found pretty many problems.. I have no clue how to read those error outputs but seems like errors are between 2gb and 4gb. Guess I just have to start going thru memory sticks 1-by-1 like in http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html and see if I can identify bad sticks and then go to shop..

95% of all persistent bugchecks here come down to
1) bad drivers. Only use signed drivers that have passed Microsoft Windows Hardware Compatibility Labs Logo certification. Not only will you get better quality but the driver software has to implement the latest features for the OS it's written for.
2) bad memory. Nobody ever believes this at first. When removing the offending DIMM also removes the bugcheck they usually come around.
3) third party anti-malware and *ahem* "utilities". Nobody knows Windows better than Microsoft. Be suspect of anyone who tells you otherwise. Sure there are exceptions, like Marc Russinovich who started Winternals before Microsoft bought them.
4) malware. It shouldn't surprise you that software whose only aim is to do evil things might not be written with the greatest attention to quality. Techniques such as rootkit injection, polymorphism and obfuscation might cloak this malware so well as to evade detection by even the best scanners but, when it crashes, it gives itself away.

 

[CarlTR6]

Okay, I left Memtest86+ running for 6 hours and it seems to have found pretty many problems.. I have no clue how to read those error outputs but seems like errors are between 2gb and 4gb. Guess I just have to start going thru memory sticks 1-by-1 like in http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html and see if I can identify bad sticks and then go to shop..

Good job with Memtest. You are correct to now test each stick in one slot. Let Memtest make at least seven passes on each stick. Once you have completed testing each stick, take a known good stick and test each motherboard slot.

 

[Nippe]

Tested each individual RAM stick with every of them passing (1 hour testing, 3 passes) and then started reading motherboard manual..
It says that my motherboard (P7H55-M PRO without integrated GPU) doesn't support more than 2 sticks of RAM type I have (CORSAIR CM3X2048-1333C9DHX ver3.3), 4 sticks are only supported with same model but with integrated GPU.
My motherboard seems to support "CORSAIR CM3X1024-1333C9 ver1.1" with 2x1gb sticks. And that manual also says my motherboard won't support any combinations with 4 sticks (why is there even 4 slots then..)

What should I do in this case?

 

[Nippe]

Oh, and I cannot test each slot because computer only boots when I have 1 stick in A1 or 2 sticks in A1 and B1 or 4 sticks in all slots.

 

[Nippe]

Ran Memtest86+ with 4 sticks again with no errors.. Seems like problems come only after computer has been powered down for more than 2 hours..?

 

[CarlTR6]

A cold boot puts more stress on the RAM. You need to run at least 7 passes when testing; 3 is not enough. Some experts recommend 12 or more passes.