Question
Applies to
1567 views

Win7x64 HP Pavilion dv6 Blue Screen

johnnymcconny asked on

I received a pc from a friend that was blue screening like crazy. So much I couldn't copy data off of it. I then reformatted it. I was doing the windows updates and it blue screened again. Please help!

 

 

Here is the link to both the pc info file and the minidump: https://skydrive.live.com/redir?resid=227FA60180F17BE4!503&authkey=!AGclgmZ_QRHNirQ

1 person had this question

Abuse history


The answered status icon Answer
Patrick Barker replied on
Hi,

The attached DMP file is of the WHEA_UNCORRECTABLE_ERROR (124) bugcheck.

A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).


If we run an !errrec on the 2nd parameter of the bugcheck (address of the WER structure) we get the following:


===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8004e87138
Section       @ fffffa8004e87280
Offset        : 600
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Unknown (Proc 1 Bank 2)
  Status      : 0xb200000000030005

Unknown, therefore there's not much we can say about this and we'll have to go through troubleshooting steps.


There is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - http://www.piriform.com/speccy

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

3. Ensure your BIOS is up to date.

4. The only software conflict that can usually cause *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite. If you have something like this software-wise, remove it ASAP.

5. Given I cannot see what kind of error we're getting from this *124, run a Memtest for NO LESS than ~8 passes (several hours) to check the health of the RAM. If it passes, move on to Seatools to check the health of the hard disk:

Memtest86+:

Download Memtest86+ here:

http://www.memtest.org/

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

http://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting

-----------------------------------------------------------------------------------------

http://www.seagate.com/support/downloads/seatools/

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

6. If all of the above fail, the only left to do is replace your processor as it is faulty.

Regards,

Patrick
Debugger/Reverse Engineer.
1 person found this helpful

Abuse history


progress