Sudden Death

ruskle

ruskle

ruskle

Associate
Joined
17 Aug 2011
Posts
81
Location
London
I have been happily using my PC for the last couple of months now after a few problems with the build (rma'd faulty ram). Absolutely no problems playing lots of Skyrim and BF3, temps all ok when gaming. Then all of a sudden, last night in the middle of a BF3 session with my mates on skype, BSOD!!!!

Happened to quick to read any of the messages. After this it simply won't post. It's shown a variety of debug errors on the mobo but the most consistent one is F2 (recovery process started). I've unplugged everything, all SATA devices and the GPU. I'm gonna leave it on with this F2 and hope it magically heals itself but if that doesn't happen I'd be gratefull for any ideas as to the cause and the solution.

Ta
 
Either the Motherboard has gone kaput, or it doesnt like Corsair ram methinks.

Tried memtest on it?
 
ruskle said:
Happened to quick to read any of the messages.
Click to expand...

Look in the 'Event Viewer' for the error message related to the BSOD.

Right click 'My Computer' and select manage.

Select Event Viewer and then Applications - and then look up the error associated with your BSOD.
 
Karateyid said:
Don't think he can get that far... System won't post at all afaik.
Click to expand...

D'oh, you're right, I miss read the part of not being able to post.

OK...

Have you reset the CMOS? If not reset and if it posts load optimised defaults save and exit and then go from there.

Also, remove all the memory bar 1 stick - and alternate sticks and memory slots if neccessary.

Check that the MB is securley fitted.

Also check the kettle lead is securley fitted - often overlooked.

Other than that reseat all components and cables that are still connected and cross all opposable appendages.
 
Last edited:
F2 is for the automated recovery. If you have unplugged the HDD i can't see how it will work :/

I would suggest you download ultimatebootcd or a similar boot disk and burn it to disk. Set the BIOS to boot from the DVD drive. These bootdisks have tools for testing the RAM and HDDs as well as other useful bits and pieces.

I would start with resetting the CMOS as suggested. If that doesnt work try and boot from the bootdisk and test the memory and HDD. I'm unsure if you have confused "Post" with "Boot". You have enough suggestions to get you started. Post back what you find with more detail and we can go from there.
 
Last edited:
Thanks a heap everyone for getting back to me, it's much appreciated.

Right I cleared CMOS, took the battery out, and based on the comment from honosuseri plugged the boot drive back in. I'm now getting debug code 78 (ACPI module initialization). I've done a google search on that and I'm still non the wiser as to what it actually means.

Tbh I'm pretty clueless, its my first PC build and I may well have confused post with boot. Just to be clear though, LEDs are on, fans spinning but no signal to the monitor, no bios, nada. I'm going to download ultimatebootcd but will I be able to do anything if I'm not even getting to bios?

One last thing, the board has ROG connect feature, which I've installed on my laptop. I've connected it up since it failed but apart from allowing me to switch it on and off through my lappy I've got no further with it. Can that be used to help me at all?
 
I just started it up again and the debug code has gone back to F2. I've got the ROG connect hooked up and the RC Poster is stuck on detect memory.

I would flash the BIOS put I can't find my damn usb drive. However, my main suspicion is that as Grimley said it probably doesn't like the vengence RAM, which isn't actually on the compatible RAM list in the manual. Why it's worked for the last 2 months and then packed in I don't know.
 
Yeah, ran it with just board, cpu, ram and boot drive, also without the boot drive.

Whats strange is that I keep getting different debug codes. Tried it this morning having cleared CMOS again and this time its on 62 (Installation of PCH runtime services). I'm sure that's what I had before when it was the memory. Wish I knew someone round my way that I could swap the RAM with.
 
Update: Its alive!!! It was the RAM.

Dunno why I didn't think to do this earlier but I experimented with taking out one of the sticks and using different slots. One of the sticks is faulty.

Asus Maximus Gene Z definitely doesn't like Corsair Vengeance, either that or its just **** memory cos its the second time its gone **** up. Works alright with one 4gb stick but I'm gonna return and get something else.
 
You must log in or register to reply here.
Back
Top Bottom