BSOD - crashing once or more a day

[sduarte79]

Need some expertise and guidance on how to fix the BSOD errors I keep getting. I have an HP Pavillion with 2GB Ram, 32 bit with Windows 7 Ultimate Premium. This is not the OEM OS that came with the laptop. I installed this on a new hard drive over a year ago when it crashed and have not had any issues until about a week ago. I think the issue is due to possibly a driver but not my area of expertise and really some help. I followed the BSOD instructions and have attached the files required. Any help fixing this is greatly appreciated!!

Latest error received today below:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: 7a
BCP1: C04A4D88
BCP2: C0000185
BCP3: 20DAF820
BCP4: 949B1A3E
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\040712-228525-01.dmp
C:\Users\Shandis\AppData\Local\Temp\WER-2131784-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[Vir Gnarus]

They are just about all reporting I/O failure from your hard drive. If no configuration changes (drivers, BIOS, etc.) have been made recently then why can bet most of our money on the drive itself being dead. Hopefully you are still under warranty for it. If you can, try to backup the data on your drive using a livecd environment like Parted Magic.

 

[sduarte79]

Hi Vir Gnarus,

Thanks for the quick response! I have not made any conguraitons changes to those items unless they update automatically somehow. I'm certainly no guru there. I don't think its under warranty still but will have to check my documentation. Would there be a way to see if any config changes were made to those types of things?

 

[Vir Gnarus]

If you personally have not installed updates for them recently, then we can assume HD failure. Note that the motherboard's HD controller may also be at fault here, though more likely it's caused by a bad hard drive.