Tech Support Forum banner

Problems after power outtage

925 Views 15 Replies 3 Participants Last post by  ch00beh
So a couple days ago, I was in the middle of playing Team Fortress 2 when the lights flicker for a bit then the power goes out. I curse a bit, unplug the computer, and find a book. A couple hours later, once the power kicks back in, I plug the computer back in, boot it up, and let it idle while I take care of some stuff on my laptop. I look up a couple minutes later to find a lovely BSOD. So of course, restart, then several minutes later, another BSOD. More cursing.

Anyway, third boot up, I start quickly looking around and notice that some apps aren't starting up at start up like they should (steam... the internet once) and I can't make Avast Antivirus do anything. Figuring it wouldn't hurt to try, I reset the CMOS and find out that it takes about forever long to change the date and time at the next start up. I tried a system restore and it threw an error a minute into the restoration. I just started running a memory diagnostics thingy, and it's now reporting that I have some kind of hardware problem that i'll need to contact the computer manufacturer about, except that I built the PC, so that's kind of redundant.

So long story short, my computer is bugging out after a power outage. Everything I read on google about power outages have people completely unable to boot, so I'm just kind of confused. I figure if I have a legit hardware problem, my computer wouldn't even turn on, so I'm thinking either hard drive or OS issue? I'm probably wrong. Anyway, specs:

OS: Windows 7 Pro 64bit, though for whatever reason, the corner says it's an RC when I got it legally from MSDN
CPU: Intel Core i5-750 Lynnfield 2.66GHz
Mobo: GIGABYTE GA-P55-UD3L
RAM: CORSAIR XMS3 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)
Video Card: EVGA 512-P3-N871-AR GeForce 9800 GTX+ 512MB
Sound Card: Audigy Soundblaster 2? I can't remember, scrapped it from my older PC and lost all the paperwork that went with it
Power Supply: See above.

Sorry, I'm new here, so I don't know if I missed anything that anyone needs to know. If it's really pressing that the unknown hardware stuff is needed, then I can look for my screw driver and muck around. I'm also not very intensely versed in technical stuff, if you couldn't tell, despite having built my PC. I just like hammering square blocks into square holes.
See less See more
Status
Not open for further replies.
1 - 16 of 16 Posts
sorry about that. The reports are attached.

Other missing info that I can find
Age of System:
-CPU, motherboard, RAM, and main HD are ~1.5 years old
-second HD is about 7? years old (inherited it) and the third is 5-6
-power supply is 3.5 years old
-video card is 2 years old; sound card is ~5 years old
-case is ~7? years old (not sure, I inherited the case, as well as that second drive, but since then I've replaced everything)

I obtained Windows 7 from MSDN through school, so I guess that counts as retail. It's been installed since I installed the new CPU, so about ~1.5 years old, and I haven't reformatted since. Originally the comp was an XP, but that's kind of moot seeing as how everything in it has been replaced.

From what I remember, the power supply was made by Thermaltake. Don't remember the wattage and lost all the paperwork.

I appreciate the help.

Attachments

See less See more
Hi,

First thing, get rid of Avast. While I do not think it is the cause in this case it is on my list of things that have been known to cause BSODs and also if you "can't make Avast Antivirus do anything" it is not exactly doing you much good.

Download the Avast Removal Tool (ART) from here -> save to desktop.

Boot into SAFEMODE - NO Networking. Then go to desktop, RIGHT-click on the ART icon and select Run as Administrator.

When complete - re-boot.

Install MS Security Essentials --> http://www.microsoft.com/Security_Essentials/

Then reset the Windows Firewall to its default settings -
START -> type cmd.exe -> right-click -> run as administrator -> type netsh advfirewall reset press enter
Here is the details of the 3 BSOD.
Code:
[font=lucida console]
BugCheck 109, {a3a039d895dfa524, b3b7465ee85dcde6, fffff88000d07058, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 109, {a3a039d895a698ad, b3b7465ee824c16f, fffff88000c6d058, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 109, {a3a039d895f9f586, b3b7465ee8781e48, fffff88000d40058, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]
From Microsoft's listing on BugCheck 109:
Cause

There are generally three different causes for this bug check:

1. A driver has inadvertently, or deliberately, modified critical kernel code or data. Microsoft Windows Server 2003 with Service Pack 1 (SP1) and later versions of Windows for x64-based computers do not allow the kernel to be patched except through authorized Microsoft-originated hot patches. For more information, see Patching Policy for x64-based Systems.

2. A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was started. Normal breakpoints (bp) can only be set if the debugger is attached at start time. Processor breakpoints (ba) can be set at any time.

3. A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.
1. Avast has been known to do this, hence the request for removal

2. If you do not even know what that means then it does not apply to you

3. This is the most likely possibility in my opinion; especially as the BSODs appeared after a power outage.

So, start testing your hardware with a memtest:
Memtest - Instructions:

Download the ISO (or the .exe for USB drives) from here http://www.memtest.org/#downiso

Then (if you have chosen the ISO) burn the ISO using IsoRecorder: http://isorecorder.alexfeinman.com/W7.htm

Boot from the CD/USB and run the test (at least 7 passes per test) with only one stick of RAM in place at a time.

It is a time consuming process but it is the only way to be sure it isn't a RAM fault.

For your final test, run the test with all the RAM in place.
Regards,
Reventon

BUGCHECK SUMMARY
Code:
[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 14 12:52:58.945 2010 (GMT+12)
System Uptime: 0 days 2:07:30.959
BugCheck 109, {a3a039d895dfa524, b3b7465ee85dcde6, fffff88000d07058, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 14 10:44:02.855 2010 (GMT+12)
System Uptime: 0 days 0:37:52.870
BugCheck 109, {a3a039d895a698ad, b3b7465ee824c16f, fffff88000c6d058, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun 14 10:04:45.507 2010 (GMT+12)
System Uptime: 0 days 4:03:08.912
BugCheck 109, {a3a039d895f9f586, b3b7465ee8781e48, fffff88000d40058, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ 
[/font]
See less See more
Much appreciated! I'll get to doing this as soon as I get a couple hours free time and I'll be sure to get back to you with the results.

Though what would you recommend in replacement of Avast for my antivirus?

EDIT: Oh, Microsoft security essentials. Didn't know that even existed, and would it be cynical of me to say I don't really trust Microsoft with their security systems? But I suppose I'll try it anyway. Better than a nonfunctional BSOD generator.
Didn't know that even existed, though would it be cynical of me to say I don't really trust Microsoft with their security systems? But I suppose I'll try it anyway. Better than a nonfunctional BSOD generator.
Gotcha. Will definitely try this out then. Thanks.
Sorry for the double post, but I just finished doing the memtests with the individual sticks and then both in. No errors came up. I guess this is a good thing? But that brings me no closer to knowing what's up with my computer, though the symptoms aren't as egregious as before, but I may just not be noticing them.

So basically, Microsoft Security Essentials can't update its definitions, and Chrome keeps saying it can't understand the security definitions of various sites. I'm sure other stuff must be wonky somewhere that I haven't looked yet because I haven't tried using the computer for anything since it crashed. I did find my W7 disc, so I'm thinking of giving it a reformat since all my important stuff is saved.
Hi I suggest you run chkdsk and sfc /scannow this will check both the hdd and the system files for any errors once done post back with any info,I do not use chrome so cannot be of help there and for mse do you recieve any error code
Alright. Chkdsk found some errors, but it fixed them, according to it. Sfc /scannow, on the other hand, found errors, but said it could not fix some of them. I can't open up the .log file it's telling me about, though, saying "Access Denied."

For MSE, I get the error code 0x80072f8f, and the message tells me it couldn't connect to the internet, though I know I am. If I ignore the security message in Chrome, I can load sites still. And my forum loads without question, and it's not a cached copy.
That error code is a Windows Update error - it has been known to occur because the computer was not set to the correct date/time. Check this now.

Same thing with the Security Message in Chrome.
Alright. So I was pretty excited when I realized that it wasn't 2009 and fixed that, and then MSE started updating and Chrome wasn't throwing errors anymore. But then I noticed that my computer was lagging ridiculously after a few minutes. I looked at my little CPU monitor desktop widget, and lo and behold, all of my RAM was being used, but as soon as I closed Chrome, only 3GB of it was in use while Steam and MSE were updating. Kind of ridiculous.

Anyway, after several more minutes, both MSE and Steam are unable to download. I decide a nice restart might help, so I shut down, noticing that there are updates that need to be applied to the system. Halfway through the installation, a blue screen pops up mentioning something along the lines of "memory management error." It was pretty quick, so I couldn't write it down. After that, I restart, and in the middle of starting up, I get another blue screen that only says:
stop: c0000221 Unknown Hard Error
\SystemRoot\System32\ntdll.dll
Another restart. This time Windows asks if I want to repair the start up, which I would very much like, but it randomly restarts soon after I accept. And now I am trying again, and it seems to be stuck at "Attempting repairs" after I said it could try rolling back to a restore point.

Man, this is ridiculous.

EDIT: Update - running Memtest86 after a second blue screen and I am getting loads of errors. Nice!
See less See more
EDIT: Update - running Memtest86 after a second blue screen and I am getting loads of errors. Nice!
That would explain a fair bit. On the basis of that return your RAM.
Okay, I isolated the RAM again to do the memory test stuff again, and no errors came up. Then I put both back in and no errors came up. Started up windows, and no blue screens - yet.

This is really embarrassing but I think I didn't put the second stick of RAM in properly. >_>

Anyway, I will see how this goes for now. It seems to be working properly... RAM looks stable, updates are all happening smoothly... So, yeah. Thank you very much, Reventon and Joeten, for all your help. Really, thanks. I'd continue gushing, but I think it would be better if I just wrote a poem for you guys.

Unexpectedly, with great rapidity
Ch00beh's system was cursed by electricity.
But Joeten came to aid
And with Reventon, they'd
Help Ch00beh's computer avoid morbidity.
1 - 16 of 16 Posts
Status
Not open for further replies.
Top