Random BSOD and wont allow to boot from windows dvd

[MrAtheist]

Recently I started to get random bsods from the computer and it happened before once a few months back. It's got to do with the display driver, which I have uninstalled it and installed the latest from the AMD website. Now bsod is happening again and sometimes it just wont pass the post. Trying to boot off the windows dvd to repair and it wont let me. (after it finished loading the dvd content, it just went back to boot from hard drive, which failed miserably at the windows splash screen and led to a force restart. and the loop continues) Now I'm lucky that I got the computer running. Dont know when the next bsod is coming.

I have attached the rar file and if someone could look into it, it would be really appreciated.

 

[Arc]

Welcome aboard.

► Uninstall ESTE. It is one of the main problems.

fffff880`02dfb528  fffff880`02823ca2Unable to load image \SystemRoot\system32\DRIVERS\eamonm.sys, Win32 error 0n2
*** [COLOR=Red]WARNING: Unable to verify timestamp for eamonm.sys
*** ERROR: Module load completed but symbols could not be loaded for eamonm.sys[/COLOR]

Use Microsoft Security Essentials - Free Antivirus for Windows.

► Try to download and install the latest beta of ATI display driver.

► update the network driver.
First, download the network card driver from manufactuer's website.
Then reinstall the driver:

1. Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
2. Double click to expand "Network adaptors".
3. Right click your network card and click Uninstall.
4. Check "Delete driver software for this device" check box, click OK.
5. Restart the computer
6. If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.

► It is possible to disinfect a system infected with malware familyRootkit.Win32.TDSS using the utility TDSSKiller.

Disinfection of an infected system

• Download the TDSSKiller.exe file on the infected (or potentially infected) computer.
• Run the TDSSKiller.exe file.
• Wait for the scan and disinfection process to be over. It is necessary to reboot the PC after the disinfection is over.

Let us know the results. If the system is stable, some more things are to be done there.

 

[MrAtheist]

Thanks for the promptly reply.

I have removed ESET and installed MSE and the latest network driver. (not sure what you mean by the beta driver though) I already have the latest display driver installed.

Right now the system is running without problems. What are the next steps you are referring to?

 

[Arc]

Right now the system is running without problems. What are the next steps you are referring to?

Observe the situation. If the crashes occur within the normal time, inform us. If not, assume your issue is over, and let us know.

 

[MrAtheist]

Hi,

I need someone to take a look at the log files. But this time I dont think it's a software problem. 8 out of 10 times there will be no post + no beep upon powering on. When it posts/beep, it would freeze on the windows splash screen page. If somehow the OS is loaded by luck, the system would just go bsod or black screen in less than 10 minutes of use. And each time the bsod is caused by different sys file when I use BlueScreenView.

Im thinking that it is a mobo problem and have test different configurations on it (reset bios, take mobo out and boot it with 1 stick dimm and then 2 sticks, etc). Same thing would happen where 8/10 tries result in no post/no beep. I have uploaded the dmp file and if someone could look at it it would be appreciated.

 

[Arc]

First, you have not followed the instructions I have given earlier, but you said that you have followed. Here is the proof that you have not followed.

egui    "c:\program files\eset\eset smart security\egui.exe" /hide /waitservice    Public    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Eset was the crasher, and it is still there.

Second, it is a custom build PC,

System Manufacturer    System manufacturer
System Model    System Product Name

But it is using the OEM license.

BiosMajorRelease = 8
BiosMinorRelease = 15
BiosVendor = American Megatrends Inc.
BiosVersion = 1101   
BiosReleaseDate = 11/20/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
[COLOR=Red]SystemFamily = To Be Filled By O.E.M.[/COLOR]
SystemVersion = System Version
[COLOR=Red]SystemSKU = To Be Filled By O.E.M.[/COLOR]
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = [COLOR=Blue]M4A785-M[/COLOR] (= motherboard.)
BaseBoardVersion = Rev X.0x

Before anything else, we want to see the report. http://www.sevenforums.com/windows-...n-issue-posting-instructions.html#post1957831