BSOD Blue Screen of Death with windows 7 and Lenovo Thinkpad E531!!

Hi,

In order to assist you, we will need the DMP files to analyze what exactly occurred at the time of the crash, etc.

If you don't know where DMP files are located, here's how to get to them:

 1.    Navigate to the %systemroot%\Minidump folder.
 2.    Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
 3.    Upload the zip containing the DMP files to Skydrive or a hosting site of your choice and paste in your reply.

If you are going to use Skydrive but don't know how to upload to it, please visit the following:

http://www.wikihow.com/Use-SkyDrive

Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete DMP files upon use.

If your computer is not generating DMP files, please do the following:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

If you cannot get into normal mode to do any of this, please do this via Safe Mode.

Regards,

Patrick

Hello,

Great, I look forward to your reply.

Regards,

Patrick

below is the Skydrive link for my Dymp file:

Thanks!

We have two DMP files, both are 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 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800a63b0a8
Section       @ fffffa800a63b180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Data Read
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000306a9
Processor ID  : 0x0000000000000007

^^ Cache data read error.

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800a63b138
Section       @ fffffa800a63b2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL2_DRD_ERR (Proc 7 Bank 6)
  Status      : 0xfe20000000041136
  Address     : 0x00000000ab800000
  Misc.       : 0x00000030e6000086

^^ Specifically, the error is DCACHEL2_DRD_ERR. This indicates that your L2 Cache suffered a data read error on Processor 7 and Cache Bank 6. On the other dump, it's Processor 1 and Cache Bank 6.... leaving us with a consistency in Cache Bank.

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. Run Memtest for NO LESS than ~8 passes (several hours) to test your RAM:

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

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

Regards,

Patrick

Dear Patrick,

My pleasure, I look forward to your update.

Regards,

Patrick

Dear Patrick,

We have the same exact bug check, yes. Is this the same laptop? I don't mean model, I mean is this the same exact laptop you sent them? Unless they sent you the same exact laptop in return, there's essentially no way we'd be getting *124's. I've taken a look at your modules list, and the only thing you have installed that I would normally consider potentially problematic is Kaspersky, but in my years as an analyst I have never seen Kaspersky cause a hardware bug check such as *124.

I would contact Lenovo again and tell them you're still getting the hardware based bug check you were getting before, and would like a brand new laptop or a repair at the very least. Did they even run diagnostics? What the....

Regards,

Patrick

No, it's not the same exact laptop, I switch it myself from the company I work with, the previous one is still with the IT department and they think I made different updates that leads me to BSOD.