BSOD causing intermittent power to monitor on boot

Hi,

Firstly, thanks for all the experts here, i have found some very valuable information!

OS: Windows 7 Home Premium x64
i7-2600K CPU @ 3.40 Ghz
OEM
8Gb RAM
Asus P8P67Pro
Harware & software build around 6 months old
BIOS, Windows updates and Driver updates applied regularly.

A couple of weeks ago i had a BSOD. Since, when trying to boot, most of the time my monitor turns ON, OFF, ON, OFF, etc...for some time, very rarely leading to a successful boot. No problem accessing Recovery options or BIOS.

Sometimes (very rarely), it does boot up normally.
I have tried everything i can think of (with my limited knowledge).

I hope the logs will be meaningful to someone and will allow you to identify the problems and help me fix them!

Thanks in advance!

Nightfrogs

The first half of your syslog shows nothing but the same thing: that the Server service failed to start, and therefore the Computer Browser service it depends on is failing. It is smothering your syslog with this.

Anyways, that's not the problem. The problem is that you have several unexpected system shutdown events in your syslog, but only one mentions it being caused by a BSOD, which is a single 0x124 WHEA error. There was no crashdump produced so I cannot tell exactly what the fault was, but WHEA errors are most commonly hardware-based failure.

Given the symptoms you're experiencing, I'd chalk this up to either a failed mobo, power supply, or video card/controller (if it's video controller, then it's a bad mobo). CPU can also cause it if it is overheating or there's serious instability issues due to drastic overclocking. Check to make sure that's not the case.

Since this system is 6 months old, and it's an OEM, it's best to simply put the warranty to use and have the vendor take care of it, since you will end up needing to do that in the first place anyways. If you speculate it may be the video card (that could explain the monitor flipping out), then try switching to onboard video (provided it exists) and removing your video card from the motherboard and see if things stabilize using that. If not, it's evidently not the video card.

Hi Vir Gnarus, thanks for looking into this so quickly. I suspect the numerous 'unexpected system shutdown' events are forced (manual) reboots when the pc was running but the monitor going from ON to OFF repeatidly.
Whilst i have overclocked it (automatically) using the build in Asus AI OC tool from Bios, it is not currnetly OC'd.
I will try changing the video card to an older one to see if it makes a difference.
Any other suggestions would be more than welcome! :)

Cheers!

Nothing at the moment. If you wish, you can run some hardware tests as mentioned below, but I believe it's just wasting time. It doesn't really matter what hardware it is, since most likely it's going to be whatever came with the OEM computer. Changing stuff around will either void warranty or just waste time (and possibly money) when it can be sent to them to have them put up with it by replacing the bad part for free. Still, it's yer choice.

RAM: Memtest86+ - 7+ passes
CPU: Prime95 - Torture Test; Large FFTs; overnight (9+ hours)
GPU: MemtestCL - Run twice (if any of the tests work on your GPU; ATI cards will need to install the ATI APP SDK as it requires OpenCL)
Drives: Seatools - All basic tests aside from the Fix all or the advanced ones.

Be aware that some of these run in Windows while others are in their own livecd environments.

Hi, after sending support emails to Asus and to the shop i bought my system from, getting ready to have to RMA it or to pay the shop to troubleshoot, i dug a bit more today and found a way of (apparently) resetting my services to what they should be by default.
I also noticed an issue with the Atheros Bootrom (some Bluetooth thing i don't use), which i managed to reinstall.
It seems, of of these 2 actions could have solved my problem as i've done numerous reboots today without problems.Strange maybe, but i don't care it's now working again! :)
Thanks for your help Vir!

That's the oddest thing I've ever heard. Nothing present here indicates anything that your problem would remotely be software-based. This may very well be an edge case.

Anyways, glad to hear it works now. Hope it continues. If you find everything's ok for sure, you can mark this thread as solved.