bsod detail

[win2]

OS - windows 7 home premium x64 - OEM
CPU- Intel Core 2 Quad Q8300 @ 2.50GHz Yorkfield 45nm Tech ]#
Motherboard - ASUSTeK Computer INC. P5P43TD (LGA775)
Memory - 4.00 GB Dual-Channel DDR3 @ 666MHz (9-9-9-24)
Graphics Card - ATI Radeon HD 5700 Series
What is the age of system (hardware)? 1 year half
re-installed the OS - 3 months ago

 

[zigzag3143]

OS - windows 7 home premium x64 - OEM
CPU- Intel Core 2 Quad Q8300 @ 2.50GHz Yorkfield 45nm Tech ]#
Motherboard - ASUSTeK Computer INC. P5P43TD (LGA775)
Memory - 4.00 GB Dual-Channel DDR3 @ 666MHz (9-9-9-24)
Graphics Card - ATI Radeon HD 5700 Series
What is the age of system (hardware)? 1 year half
re-installed the OS - 3 months ago

Several problems


1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).


2- Multiple malware apps. Not a good idea. I would remove Avast and ESET and replace with Microsoft security essentials.


http://files.avast.com/files/eng/aswclear5.exe

http://download.eset.com/special/ESETUninstaller.exe


Virus, Spyware & Malware Protection | Microsoft Security Essentials



3-Hardware possible RAM. If the above dos not fix th problem please read here.


Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html