Avast WEBforum
Other => Viruses and worms => Topic started by: aceschborn on May 08, 2014, 05:55:57 PM
-
I found the avast forums after googling my boot problems and safe mode boot failing at aswrvrt.sys. Based on what I've read I'm making my own thread and hoping I can get some valuable input.
PC: Windows 7 Ultimate x64 (herein HTPC)
OS drive: Intel X-25M 80gb
Other drives: 3 spinners
Ram: 2x4gb
Problem: media center extender couldn't connect to my HTPC. Used KVM to switch from work PC to HTPC. Monitor would not switch over (went to standby mode) but with TV on it was apparent the mouse and keyboard had. The desktop had been switched over to the TV. I took the mouse to the family room and was able to select 'shut down' from the start menu. After a longer than usual period the computer shut down. Upon restart the computer BSOD at the beginning of the 'Starting Windows' screen (photo in link). Restarted and start up repair could not fix the problem. System restore failed (photo in link). Boot to safe mode resulted in failure at loading aswrvrt.sys (video in link). Went to command prompt and ran chkdsk /r (photo in link).
Troubleshooting: removed RAM and replaced with single stick of 2gb from work PC - no change. Unplugged all HDD except OS drive - no change.
Other notes: I'm not sure if it's related or not, but the computer has encountered random freezes and BSODs over the course of, say, the last year and a half.
Some screenshots in my photo album: https://plus.google.com/photos/101860571453932856357/albums/6011078305520626241?authkey=CM_8_tiTn-yvTg
Based on the other threads I have read, I downloaded and ran FRST; the log file is attached.
Thanks for any and all help!
-ace
-
I suspect it has something to do with the 3 other drives on your system. I'll get you help.
-
Hi Michael, thanks for the quick reply. Wouldn't unplugging all the HDDs except the OS drive preclude that from being a problem?
-
Oh, sorry, didn't see that. Sometimes that's the cause. I've asked someone to help you.
-
This behavior indicates that the Windows registry is unable to allocate the memory pool needed to contain the registry files. This may be caused by a defective random access memory (RAM) module. If the problem persists, disable caching on the motherboard.
Initially I will try a reg back, this may not work
Download the attached Fixlist.txt to the same location as FRST
Run FRST and press Fix
On completion a log will be generated please post that
Then try a normal boot
-
Well I'll be. Performed your procedure from command prompt of start up repair. Closed FRST and selected restart. Given option of system repair or launch normally and selected launch normally. Booted up into Windows! Such a pleasant sight!
I've attached the log. How do I go about determining what went wrong and ensuring it doesn't happen again?
-
It was based on the BSOD error code, this basically states that as the registry was written, due to memory problems, it may have corrupted. So I just restored a known good copy :)
If you have now changed the RAM then it should be OK .. Unless there is a motherboard problem but, that is less likely
-
First and foremost, THANK YOU for your help!
Hmm. I actually reverted back to the existing memory when memory from my other PC did not fix the problem. I don't have any spare memory around. Can you say with certainty it is a bad memory module(s) or MoBo? How might I rule out the motherboard? What's the best way to test the memory? Presumably I could replace only one of two modules if bad, right?
-ace
-
You could run the windows memory test to see if there is an evident problem http://windows.microsoft.com/en-gb/windows7/diagnosing-memory-problems-on-your-computer
-
The Windows Memory Diagnostic Utility did not detect any errors. I vaguely recall running this in the past in order to try and troubleshoot the random freezing and BSOD issues, which, at this point, I'm guessing are all related to last nights failure. What else can I do to troubleshoot?
The reg back seems to have brought back a couple Windows updates that I thought I had previously installed. Any reason to hold off on re-installing them now?
-
Nope, install the updates.. Also the RAM should now be securely seated so that may have been part of the problem
-
I will install the updates on next boot.
Based on what I've read elsewhere, I'm running MemTest86+ for the next few hours. Is there anyway the video card or video card memory could be causing problems? What else can I troubleshoot or rule out?
Thanks again!
-
I will need to have a look around for that as I am mainly software orientated
-
Okay, thanks for any further help you can offer!
BTW, safe to rule out that this was not software/Avast related?
Best regards!
-ace
-
Yes from the BSOD code it points to hardware. Did Memtest reveal anything ?
-
I ran MemTest86+ for ~12 hours and it didn't find a single error or problem, however, just this morning I got a BSOD. This was a more 'typical' BSOD that I have been having and Windows was able to start normally afterwards.
I took another couple photos posted here: https://plus.google.com/photos/101860571453932856357/albums/6011078305520626241?authkey=CM_8_tiTn-yvTg
Any insight?
-
Hmm 01e comes back again at memory, could you zip and upload the last two or three minidumps to a file sharing site please
c:\windows\minidump
-
The minidump folder is empty! Blue Screen View also shows nothing as well (reading the minidumps that don't exist?)
The BSOD mentions the graphics adapter, so I went ahead and used Display Driver Uninstaller to remove the NVidia drivers (dated 2014-03-04), restarted, and then installed the latest drivers (dated 2014-03-10).
-
May have been memory manipulation within the video drivers. Let me know how that goes