BSOD with Lenovo x200s

nursegladys · 02 Mar 2013

Dear experts,

I have a periodic BSOD problem on my beloved Lenovo x200s. I bought it with 2GB RAM and Vista x32 installed. About a year ago I added 2GB RAM, installed Windows 7 x64 and changed the hard disk for a Crucial M4 256GB. Since then I had periodic BSOD which I think was linked to the graphics driver (one reason I like this x200s is it has the 1440x900 screen: don't know if this has anything to do with the problem).

The problem got worse and a few days ago I did a clean install of Windows 7. I have had two further BSOD since then. I think they are recorded in the attached files made with the SF Diagnostic Tool.

I am quite competent with computers, but trying to ID the problem from the event logs etc is beyond me. Any help from you good folks on Windows 7 Support Forums would be much appreciated.

Thanks,

James

koolkat77 · 02 Mar 2013

Welcome to Seven Forums.

Code:

Model	M4-CT256M4SSD2 ATA Device

Code:

STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR 

Usual causes:  Memory, Paging file corruption, File system, Hard drive, Cabling, 
Virus infection, Improperly seated cards, BIOS, Bad motherboard, 
Missing Service Pack

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc4000bb68, ffffffffc000000e, 8b8f860, fffff8800176dba0}

GetPointerFromAddress: unable to read from fffff80002b13278
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc4000bb68, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000008b8f860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8800176dba0, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031b09b0 -- (.trap 0xfffff880031b09b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a0112c5fc8 rbx=0000000000000000 rcx=fffff8a0112c5fb8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800176dba0 rsp=fffff880031b0b48 rbp=fffff8a0112c5f80
 r8=0000000000000000  r9=0000000000000000 r10=fffff8800176dba0
r11=fffff8a0112c5fc8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
rdyboost!SmdEtwEnableCallback:
fffff880`0176dba0 0000            add     byte ptr [rax],al ds:fffff8a0`112c5fc8=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000294d812 to fffff800028dac40

STACK_TEXT:  
fffff880`031b0698 fffff800`0294d812 : 00000000`0000007a fffff6fc`4000bb68 ffffffff`c000000e 00000000`08b8f860 : nt!KeBugCheckEx
fffff880`031b06a0 fffff800`02901a0f : fffffa80`0f883520 fffff880`031b0810 fffff800`02b16540 fffffa80`0f883520 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`031b0780 fffff800`028e82a9 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff880`031b0950 : nt!MiIssueHardFault+0x28b
fffff880`031b0850 fffff800`028d8d6e : 00000000`00000000 fffff880`0176dba0 4beb857f`2e35aa00 00000000`00000000 : nt!MmAccessFault+0x1399
fffff880`031b09b0 fffff880`0176dba0 : fffff800`02b33d2b fffffa80`03ba0580 fffff8a0`0b606d10 fffffa80`0625ed70 : nt!KiPageFault+0x16e
fffff880`031b0b48 fffff800`02b33d2b : fffffa80`03ba0580 fffff8a0`0b606d10 fffffa80`0625ed70 00000000`00000700 : rdyboost!SmdEtwEnableCallback
fffff880`031b0b50 fffff800`02c890b6 : fffffa80`03cd6c90 fffffa80`03cd6cb8 fffffa80`042a6c70 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1283d
fffff880`031b0c00 fffff800`02d279a8 : fffffa80`03cc4c80 fffff8a0`112c5f80 00000000`00000000 00000000`00000000 : nt!EtwpDisableTraceProviders+0x1a6
fffff880`031b0c80 fffff800`02c33dfb : fffffa80`03cc0000 00000000`00000000 00000000`c0000001 fffffa80`285e3020 : nt!EtwpStopLoggerInstance+0x58
fffff880`031b0cc0 fffff800`02b7b34a : 73634946`030c0104 fffffa80`03cc4790 00000000`00000080 fffffa80`03c10740 : nt! ?? ::NNGAKEGL::`string'+0x44ab3
fffff880`031b0d40 fffff800`028cb946 : fffff800`02a56e80 fffffa80`03cc4790 fffffa80`03cc4040 00000000`00010001 : nt!PspSystemThreadStartup+0x5a
fffff880`031b0d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb
MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
---------

Please update the firmware of your SSD.

writhziden said:

If you have an SSD, make sure the following are up to date:

SSD firmware
BIOS Version
Chipset Drivers
Hard disk controller drivers/SATA drivers
If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Perform a System File Check to check the integrity of all protected Windows 7 :

Click on the start
Type CMD on Search
Left click and Run as Administrator
Type
Code:
```
SFC /scannow
```

Full tutorial here:

SFC /Scannow Command - System File Checker

Disk Check on your hard drive for file system errors and bad sectors on it.

How to run Disk Check on Windows 7

Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

Note

Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial:

Memory Diagnostics Tool

Code:

ACPI thermal zone ACPI\ThermalZone\THM0 has been enumerated.             
_PSV = 0K             
_TC1 = 0             
_TC2 = 0             
_TSP = 0ms             
_AC0 = 0K             
_AC1 = 0K             
_AC2 = 0K             
_AC3 = 0K             
_AC4 = 0K             
_AC5 = 0K             
_AC6 = 0K             
_AC7 = 0K             
_AC8 = 0K             
_AC9 = 0K             
_CRT = 400K             
_HOT = 0K             
_PSL - see event data.

Please keep a check on the temperature of the system.

For monitoring the heat/celsius of the system, use Speccy or HWMonitor:

Code:

Event[3084]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2013-03-01T12:27:07.225
  Event ID: 37
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: James-PC
  Description: 
The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

Event[3085]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2013-03-01T12:27:07.260
  Event ID: 37
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: James-PC
  Description: 
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

These errors are not good to have, here are some links you could go through:

Take your time and Let us know the results.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Debug session time: Sat Mar  2 21:50:46.037 2013 (UTC + 6:00)
System Uptime: 1 days 13:16:35.801
GetPointerFromAddress: unable to read from fffff80002ac1278
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
KERNEL_DATA_INPAGE_ERROR (7a)
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR:  0x7a_c000000e
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
CPUID:        "Intel(R) Core(TM)2 Duo CPU     L9400  @ 1.86GHz"
MaxSpeed:     1860
CurrentSpeed: 1862
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Debug session time: Fri Mar  1 08:33:14.116 2013 (UTC + 6:00)
System Uptime: 0 days 22:53:26.755
GetPointerFromAddress: unable to read from fffff80002b13278
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
KERNEL_DATA_INPAGE_ERROR (7a)
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000000e
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_4096
CPUID:        "Intel(R) Core(TM)2 Duo CPU     L9400  @ 1.86GHz"
MaxSpeed:     1860
CurrentSpeed: 1862
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

nursegladys · 05 Mar 2013

Thanks Koolkat77.

It has taken quite a while to work through the instructions. Here are the results:

1. The firmware for the Crucial M4 SSD was 0309. I have updated it to the latest (040H).

2. I checked the BIOS. It was already the latest version (3.22)

3. Updating chipset drivers. I was a bit confused as to where I could find the current chipset driver version. In Device Manager I found "Mobile Intel® 4 Series Chipset Processor to DRAM Contoller – 2A40" which had the following details:
Driver Provider: Microsoft
Driver Date: 21/06/2006
Driver Version: 6.1.7601.17514

I then applied all optional Windows updates, but there was nothing that appeared to be to do with the chipset drivers. There was no change in Device Manager under "Mobile Intel® 4 Series Chipset Processor to DRAM Contoller – 2A40".

I then used the Lenovo System Update software, which gave no option to update the chipset drivers.

I then visited the Lenovo Support website and downloaded and ran "Intel Chipset Support for Windows 8 (32-bit, 64-bit), 7 (32-bet, 64-bit), Vista (32-bit, 64-bit), XP (32-bit, 64-bit) - ThinkPad Version 9.3.0.1021". This has a release date of 19.10.12. This seemed to run OK. Afterwards I could again see no change in Device Manager under "Mobile Intel® 4 Series Chipset Processor to DRAM Contoller – 2A40". So I still have the driver version 6.1.7601.17514 which was released in June 2006. I guess this is the most up to date chipset driver?

While on the Lenovo Support website I also found "Intel AMT 4.2 Management Engine Interface for Windows 7 (32-bit, 64-bit), Vista (32-bit, 64-bit) and XP (32-bit) - ThinkPad Version 4.2.0.1008". This is shown as having a release date of 15.4.10. I downloaded this and tried to run it. It would not run, giving "Error - This computer does not meet the minimum requirements for installing the software - Setup will exit" I don't really understand what the Intel AMT Management Engine is. I guess my laptop does not need it?

4. Updating hard disk controller drivers/SATA drivers. In Device Manager under "Standard AHCI 1.0 Serial ATA Controller" and "ATA Channel 0" I had the same driver listed:
Driver Provider: Microsoft
Driver Date: 21/06/2006
Driver Version: 6.1.7601.17514

I used the Lenovo System Update to install Intel Matrix Storage Manager driver for Windows 64bit, version 8.9.2.1002. This ran successfully. In Device Manager I now no longer have the 2 devices "Standard AHCI 1.0 Serial ATA Controller" and "ATA Channel 0". Instead I have "Intel® ICH9M-E/M SATA AHCI Controller". The driver details are now:
Driver Provider: Intel
Driver Date: 07/08/2009
Driver Version: 8.9.2.1002

I have also noticed another device in Device Manager, "M4-CT256M4SSD2", i.e. the Crucial SSD. The driver details are:
Driver Provider: Microsoft
Driver Date: 21/06/2006
Driver Version: 6.1.7600.16385
I cannot see any more recent driver available from Windows Update, the Lenovo System Update tool nor from the Lenovo website.

5. Perform a System File Check. Did this and it reported that "Windows Resource Protection did not find any integrity violations".

6. Run Disk Check. I ran the check only and no problems were found. I also did the "check and automatically fix file system errors" and the "scan for and attempt recovery of bad sectors". I don't think either showed any problems.

7. Number down items at start-up. I only have one application in the start up folder: Windows Home Server.

8. Memtest86 v 4.20. I did 9 passes (it took 12 hours!) with no errors.

9. Windows Memory Diagnostics. Ran it, no errors.

10. Temperatures. I used CPUID Hardware Monitor to record temperatures and ran Prime95 and FurMark to stress the CPU/GPU. The results (in degrees centigrade):
Min Max
THM0 42 105
THM1 38 98
Core#0 33 93
Core#1 33 93

You can see it is getting pretty hot. The temperatures rise to the maximums shown above, and then fall sharply. After a few minutes the temperatures would rise as before. I figured that the CPU/GPU is throttling because of the heat. I can see in CPU-Z that the CPU speed is normally 1.8GHz (multiplier of 7) but that it throttles back to either 798MHz (multiplier 3) or sometimes 399MHz (multiplier 1.5).

I think this throttling causes the Event ID 37 warning ("The speed of processor x in group x is being limited by system firmware..."). I don't know if this is anything to worry about. Under normal usage I don't think I am likely to be pushing the CPU/GPU hard enough to cause throttling.

Since updating the Crucial M4 firmware I have had no more BSOD. I did have an unexpected shutdown, which occurred when I had closed the laptop lid (which should put it into Sleep). When I opened it again in the morning Windows 7 restarted, saying that it had unexpectedly shut down. I had a look in Event Viewer to try to see what might have been the cause, but I couldn't see anything.

I have attached a new file created with the SF Diagnostic Tool.

I have made this post rather detailed just in case it helps anyone else with similar problems. Sorry if it is longwinded and boring.

Thanks again Koolkat77 and thanks in advance to everyone for any comments on the above and the attached.

Britton30 · 06 Mar 2013

Welcome to Seven Forums nursegladys.
Have you had any more BSODs since preforming that big list of thing? Your CPU temp should not be over 80C even during stressing it. If you haven't, blow or vacuum all the laptop's vents free of dust. Since I think you are comfortable, you can also remove the bottom covers, SSD, and DVD drive to help with the cleaning.

I may have read too fast, did you install the graphics driver from the Lenovo support site?

Dsprague · 06 Mar 2013

You may want to update your wireless driver, one of your BSODs points to it as a problem:

Code:

 kd> !IRP fffffa8004088230
Irp is active with 4 stacks 2 is current (= 0xfffffa8004088348)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0  0 fffffa80052ee050 00000000 00000000-00000000    
          Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
 \Driver\NETw5s64
            Args: 00014400 00000000 00000004 00000002
 [ 16, 2]   0 e1 fffffa8004699e10 00000000 fffff80002ace200-fffffa8007f2e120 Success Error Cancel pending
           \Driver\vwifibus    nt!PopSystemIrpCompletion
            Args: 00014400 00000000 00000004 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8007f2e120    

            Args: 00000000 00000000 00000000 00000000

Driver Reference Table - NETw5s64.sys

updates can be found here: Intel Download Center

Vir Gnarus · 06 Mar 2013

Ouch, in two crashdumps the readyboost driver - which is used for prefetching as well as the readyboost feature - has mysteriously been zeroed, entirely:

Code:

0: kd> !chkimg -lo 50 -d -db !rdyboost
    fffff8800176d000-fffff8800176d03c  61 bytes - rdyboost!SmdContentsUpdateRequestPrepare+a8
    [ 85 ff 74 09 48 8b cf ff:00 00 00 00 00 00 00 00 ]
    fffff8800176d03f-fffff8800176d055  23 bytes - rdyboost!SmdContentsUpdateRangeConvert+f (+0x3f)
    [ 23 42 0c 44 0f b6 d8 45:00 00 00 00 00 00 00 00 ]
    fffff8800176d058-fffff8800176d061  10 bytes - rdyboost!SmdContentsUpdateRangeConvert+28 (+0x19)
    [ 49 c1 e9 0c 4c 8d 94 08:00 00 00 00 00 00 00 00 ]
    fffff8800176d064-fffff8800176d076  19 bytes - rdyboost!SmdContentsUpdateRangeConvert+34 (+0x0c)
    [ 49 c1 ea 0c 41 8b c2 c1:00 00 00 00 00 00 00 00 ]
    fffff8800176d07b - rdyboost!SmdContentsUpdateRangeConvert+4b (+0x17)
    [ 01:00 ]
    fffff8800176d07f-fffff8800176d09f  33 bytes - rdyboost!SmdContentsUpdateRangeConvert+4f (+0x04)
    [ 49 03 c1 48 3b c1 76 0b:00 00 00 00 00 00 00 00 ]
    fffff8800176d0a3-fffff8800176d0de  60 bytes - rdyboost!SmdContentsUpdateRangeConvert+73 (+0x24)
    [ 41 8b c0 c3 cc cc cc cc:00 00 00 00 00 00 00 00 ]
    fffff8800176d0e2-fffff8800176d0ef  14 bytes - rdyboost!SmdPopulationStoresSpaceCheck+32 (+0x3f)
    [ 41 d3 e1 41 8b c1 f7 d0:00 00 00 00 00 00 00 00 ]
    fffff8800176d0f2 - rdyboost!SmdPopulationStoresSpaceCheck+42 (+0x10)
    [ 10:00 ]
    fffff8800176d0f4-fffff8800176d0f8  5 bytes - rdyboost!SmdPopulationStoresSpaceCheck+44 (+0x02)
    [ 72 0b 83 24 8f:00 00 00 00 00 ]
    fffff8800176d0fa-fffff8800176d10b  18 bytes - rdyboost!SmdPopulationStoresSpaceCheck+4a (+0x06)
    [ ff 44 8f 20 41 0b f1 45:00 00 00 00 00 00 00 00 ]
    fffff8800176d10e-fffff8800176d124  23 bytes - rdyboost!SmdPopulationStoresSpaceCheck+5e (+0x14)
    [ 8b 47 44 8b d6 49 8b ce:00 00 00 00 00 00 00 00 ]
    fffff8800176d128-fffff8800176d135  14 bytes - rdyboost!SmdPopulationStoresSpaceCheck+78 (+0x1a)
    [ e8 ff ee fe ff 44 8b d8:00 00 00 00 00 00 00 00 ]
    fffff8800176d138-fffff8800176d13a  3 bytes - rdyboost!SmdPopulationStoresSpaceCheck+88 (+0x10)
    [ bb 02 01:00 00 00 ]
    fffff8800176d13d-fffff8800176d14d  17 bytes - rdyboost!SmdPopulationStoresSpaceCheck+8d (+0x05)
    [ 45 8b e3 45 0f bc d4 41:00 00 00 00 00 00 00 00 ]
    fffff8800176d151-fffff8800176d161  17 bytes - rdyboost!SmdPopulationStoresSpaceCheck+a1 (+0x14)
    [ 42 f6 44 97 20 0f 4a 8b:00 00 00 00 00 00 00 00 ]
    fffff8800176d165-fffff8800176d167  3 bytes - rdyboost!SmdPopulationStoresSpaceCheck+b5 (+0x14)
    [ 0f 84 95:00 00 00 ]
    fffff8800176d16b-fffff8800176d16f  5 bytes - rdyboost!SmdPopulationStoresSpaceCheck+bb (+0x06)
    [ 4c 8b 8a 80 01:00 00 00 00 00 ]
    fffff8800176d172-fffff8800176d176  5 bytes - rdyboost!SmdPopulationStoresSpaceCheck+c2 (+0x07)
    [ 48 81 c2 a0 01:00 00 00 00 00 ]
    fffff8800176d179-fffff8800176d17c  4 bytes - rdyboost!SmdPopulationStoresSpaceCheck+c9 (+0x07)
    [ 4c 8d 82 90:00 00 00 00 ]
    fffff8800176d180-fffff8800176d18c  13 bytes - rdyboost!SmdPopulationStoresSpaceCheck+d0 (+0x07)
    [ 49 3b d0 73 7b 8b 02 83:00 00 00 00 00 00 00 00 ]
    fffff8800176d18e - rdyboost!SmdPopulationStoresSpaceCheck+de (+0x0e)
    [ 80:00 ]
    fffff8800176d191-fffff8800176d1ab  27 bytes - rdyboost!SmdPopulationStoresSpaceCheck+e1 (+0x03)
    [ 66 41 85 2c 41 74 02 ff:00 00 00 00 00 00 00 00 ]
    fffff8800176d1b0-fffff8800176d1b5  6 bytes - rdyboost!SmdPopulationStoresSpaceCheck+100 (+0x1f)
    [ 74 4e 83 ba 30 02:00 00 00 00 00 00 ]
    fffff8800176d1b8-fffff8800176d1c2  11 bytes - rdyboost!SmdPopulationStoresSpaceCheck+108 (+0x08)
    [ ff 75 04 33 c9 eb 11 8b:00 00 00 00 00 00 00 00 ]
    fffff8800176d1c5-fffff8800176d1c7  3 bytes - rdyboost!SmdPopulationStoresSpaceCheck+115 (+0x0d)
    [ 8b 8a f8:00 00 00 ]
    fffff8800176d1cb-fffff8800176d1d3  9 bytes - rdyboost!SmdPopulationStoresSpaceCheck+11b (+0x06)
    [ c1 e0 07 2b c8 44 8b 82:00 00 00 00 00 00 00 00 ]
    fffff8800176d1d7-fffff8800176d1db  5 bytes - rdyboost!SmdPopulationStoresSpaceCheck+127 (+0x0c)
    [ 48 81 c2 a0 01:00 00 00 00 00 ]
    fffff8800176d1de-fffff8800176d1e1  4 bytes - rdyboost!SmdPopulationStoresSpaceCheck+12e (+0x07)
    [ 48 8d 82 90:00 00 00 00 ]
    fffff8800176d1e5-fffff8800176d1f9  21 bytes - rdyboost!SmdPopulationStoresSpaceCheck+135 (+0x07)
    [ eb 0c 83 3a ff 75 03 41:00 00 00 00 00 00 00 00 ]
    fffff8800176d1fc - rdyboost!SmdPopulationStoresSpaceCheck+14c (+0x17)
    [ 20:00 ]
    fffff8800176d1fe-fffff8800176d204  7 bytes - rdyboost!SmdPopulationStoresSpaceCheck+14e (+0x02)
    [ 72 15 41 8b ca b8 01:00 00 00 00 00 00 00 ]
    fffff8800176d208-fffff8800176d229  34 bytes - rdyboost!SmdPopulationStoresSpaceCheck+158 (+0x0a)
    [ d3 e0 f7 d0 44 23 e0 0f:00 00 00 00 00 00 00 00 ]
    fffff8800176d22d-fffff8800176d234  8 bytes - rdyboost!SmdPopulationStoresSpaceCheck+17d (+0x25)
    [ 45 33 c9 48 8d 84 24 88:00 00 00 00 00 00 00 00 ]
    fffff8800176d238-fffff8800176d272  59 bytes - rdyboost!SmdPopulationStoresSpaceCheck+188 (+0x0b)
    [ 45 33 c0 41 8d 51 07 49:00 00 00 00 00 00 00 00 ]
    fffff8800176d274-fffff8800176d279  6 bytes - rdyboost!SmdPopulationStoresSpaceCheck+1c4 (+0x3c)
    [ c0 44 8b 84 24 90:00 00 00 00 00 00 ]
    fffff8800176d27d-fffff8800176d281  5 bytes - rdyboost!SmdPopulationStoresSpaceCheck+1cd (+0x09)
    [ 0f bc cd ba 01:00 00 00 00 00 ]
    fffff8800176d285-fffff8800176d2aa  38 bytes - rdyboost!SmdPopulationStoresSpaceCheck+1d5 (+0x08)
    [ 44 01 04 8f d3 e2 f7 d2:00 00 00 00 00 00 00 00 ]
    fffff8800176d2ac-fffff8800176d2db  48 bytes - rdyboost!SmdPopulationStoresSpaceCheck+1fc (+0x27)
    [ c0 eb c6 33 db eb c2 cc:00 00 00 00 00 00 00 00 ]
    fffff8800176d2de-fffff8800176d2e2  5 bytes - rdyboost!SmdPopulationPerform+22 (+0x32)
    [ 8b ac 24 f8 01:00 00 00 00 00 ]
    fffff8800176d2e5-fffff8800176d315  49 bytes - rdyboost!SmdPopulationPerform+29 (+0x07)
    [ 41 8b f9 4d 8b f0 48 8b:00 00 00 00 00 00 00 00 ]
    fffff8800176d318-fffff8800176d31e  7 bytes - rdyboost!SmdPopulationPerform+5c (+0x33)
    [ 33 d2 48 8d 8c 24 80:00 00 00 00 00 00 00 ]
    fffff8800176d322-fffff8800176d326  5 bytes - rdyboost!SmdPopulationPerform+66 (+0x0a)
    [ c7 84 24 f8 01:00 00 00 00 00 ]
    fffff8800176d329 - rdyboost!SmdPopulationPerform+6d (+0x07)
    [ 10:00 ]
    fffff8800176d32d-fffff8800176d33b  15 bytes - rdyboost!SmdPopulationPerform+71 (+0x04)
    [ 44 8d 42 48 e8 ca 3c ff:00 00 00 00 00 00 00 00 ]
    fffff8800176d33e-fffff8800176d33f  2 bytes - rdyboost!SmdPopulationPerform+82 (+0x11)
    [ 49 bb:00 00 ]
    fffff8800176d342 - rdyboost!SmdPopulationPerform+86 (+0x04)
    [ 10:00 ]
    fffff8800176d346 - rdyboost!SmdPopulationPerform+8a (+0x04)
    [ 10:00 ]
    fffff8800176d348-fffff8800176d34c  5 bytes - rdyboost!SmdPopulationPerform+8c (+0x02)
    [ 4c 89 9c 24 80:00 00 00 00 00 ]
    fffff8800176d350-fffff8800176d354  5 bytes - rdyboost!SmdPopulationPerform+94 (+0x08)
    [ 4c 89 9c 24 88:00 00 00 00 00 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3591 errors : !rdyboost (fffff8800176d000-fffff8800176dfff)
fffff8800176d000 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d010 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d020 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d030 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00  00 *00 ................
fffff8800176d040 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d050 *00 *00 *00 *00 *00 *00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d060 *00 *00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d070 *00 *00 *00 *00 *00 *00 *00  00  00  00  00 *00  00  00  00 *00 ................
fffff8800176d080 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d090 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d0a0  00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d0b0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d0c0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d0d0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00 ................
fffff8800176d0e0  00  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d0f0  00  00 *00  00 *00 *00 *00 *00 *00  00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d100 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00  00 *00 *00 ................
fffff8800176d110 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d120 *00 *00 *00 *00 *00  00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d130 *00 *00 *00 *00 *00 *00  00  00 *00 *00 *00  00  00 *00 *00 *00 ................
fffff8800176d140 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00  00 ................
fffff8800176d150  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d160 *00 *00  00  00  00 *00 *00 *00  00  00  00 *00 *00 *00 *00 *00 ................
fffff8800176d170  00  00 *00 *00 *00 *00 *00  00  00 *00 *00 *00 *00  00  00  00 ................
fffff8800176d180 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00 *00  00 ................
fffff8800176d190  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d1a0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00  00  00  00 ................
fffff8800176d1b0 *00 *00 *00 *00 *00 *00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d1c0 *00 *00 *00  00  00 *00 *00 *00  00  00  00 *00 *00 *00 *00 *00 ................
fffff8800176d1d0 *00 *00 *00 *00  00  00  00 *00 *00 *00 *00 *00  00  00 *00 *00 ................
fffff8800176d1e0 *00 *00  00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d1f0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00  00 *00  00 *00 *00 ................
fffff8800176d200 *00 *00 *00 *00 *00  00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d210 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d220 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00  00  00 *00 *00 *00 ................
fffff8800176d230 *00 *00 *00 *00 *00  00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d240 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d250 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d260 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d270 *00 *00 *00  00 *00 *00 *00 *00 *00 *00  00  00  00 *00 *00 *00 ................
fffff8800176d280 *00 *00  00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d290 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d2a0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00 *00 *00 *00 *00 ................
fffff8800176d2b0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d2c0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d2d0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00  00  00 *00 *00 ................
fffff8800176d2e0 *00 *00 *00  00  00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d2f0 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d300 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 *00 ................
fffff8800176d310 *00 *00 *00 *00 *00 *00  00  00 *00 *00 *00 *00 *00 *00 *00  00 ................

The whole thing wiped clean. I don't know what happened, be it from something incidentally zeroing that portion of memory or some hardware failure of some sort, but it's pretty big. I think the c000000e error (device does not exist) showing up in the thread stack for each scenario seems to reflect this. I'm with koolkat leaning on this being some drive failure of some kind. We'll have to see if the new firmware does the trick.

nursegladys · 11 Mar 2013

Britton30, thanks for your reply. No more BSODs, but I do have occasional unexpected shutdown when the laptop is in sleep. I start windows normally and all seems OK. I have used canned air to clean the fan/vents, but the temps are the same. Under normal use the maximum I get is between 60 and 70 degrees. The very high temperatures I only see if I use Prime/Furmark. I did install the latest graphics driver available from Lenovo (using the Lenovo System Update software). It was version 8.15.10.2555 (date 13/10/2011). After reading Dsprague’s post I have installed a more recent driver.

Thanks Dsprague. I followed the link you gave for Intel Download Center and ran the Driver Update Utility. Although I installed all Windows Updates and all driver updates given by the Lenovo System Update software, I found that there are newer drivers for graphics, chipset INF, WIFI and Ethernet. I have now installed all of these. If of any use/interest to anyone who reads this, the drivers:
Graphics was 8.15.10.2555 (date 13/10/2011): now 8.15.10.2869 (date 04/10/2012)
Intel WiFi Link 5100 AGN was 13.0.0.107 (date 15/09/2009): now 14.3.2.1 (date 22/01/2012)
Intel 82567LM Gigabit was 10.1.9.0 (date 07/04/2010): now 10.1.17.0 (date 20/10.2011)

Thanks Vir Gnarus. This doesn't sound good. I updated the firmware of the Crucial M4 SSD after my first post but before my second post (both attached the files produced by SF Diagnostic Tool). I don't know which files showed the mystery zeroing of the readyboost driver, so I am not sure whether the firmware update has solved the problem.

I'm really impressed by this forum and grateful for all the replies. I have attached another set of files from the SF Diagnostics Tool. If anyone has any bright ideas how to get to the bottom of what is going on I would love to hear.

Thanks.

Vir Gnarus · 12 Mar 2013

Ok, I see two crashdumps, one from Sunday and one from Monday. Both show up the Intel wifi driver (NETw5s64.sys). You mentioned you updated it, but I'm still seeing the original old date on this on both crashdumps. I'm not sure if they happened before you updated or not but you may need to download the update, uninstall the wifi driver completely, then reinstall the new one to make sure the new one sticks.

Also, I'm seeing a very curious and ugly item, and that's the Lenovo Doze Mode driver. Look in your Programs & Features and try to find it and uninstall it. In fact, see if you can't find any other Lenovo bloatware that came with your system and uninstall those too. I wouldn't doubt that this fella had something to do with the odd complete removal of the readyboost driver in memory.

nursegladys · 17 Mar 2013

Thanks to all I think problems are solved (except I now have developed an unhealthy interest in error/warning messages in Event Viewer!).

I wanted to post what I discovered in case this helps others with similar problems.

As noted above I did install the latest Wifi driver (Intel WiFi Link 5100 AGN 14.3.2.1 (date 22/01/2012)) and this is not causing any more problems.

There was nothing like Lenovo Doze Mode driver in your Programs & Features. A google search suggested that it was part of the Lenovo Thinkpad Power Management software, so I uninstalled it.

No more BSOD, no performance problems (though possibly slightly slow resume from sleep/booting up). I found a few errors in Event Viewer.

Event 7016, Service Control Manager reported "The Data Transfer Service service has reported an invalid current state 0." This appears to be used by the Lenovo fingerprint reader software. So I uninstalled the Lenovo driver and software and instead installed the Autentec driver and TrueSuite software. No more problems and the fingerprint reader is very noticeably faster.

Event 10, WMI reported "Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected." This turned out not to be a problem (see http://support.microsoft.com/default...;en-US;2545227) but I ran the Fix It anyway and the error is no longer reported.

Event 12348, VSS reported "Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{e3388938-8b8a-11e2-9a15-001f16111232}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly. Check security on the volume, and try the operation again." After a lot of searching I found that this was caused by the F:/ volume created by Microsoft Office One Click installation. I am not sure that this really created any problems (although I did have a number of seemingly related errors with VSS, System Restore and volsnap) and the system did seem to be able to create restore points. I did a lot of google searching and others with similar problems did have some real functionality problems. In any event the solution turned out to be simply uninstalling Microsoft Office and reinstalling it using a MSI installation. No more inaccessible F:/ disk and no more errors.

I also have a persistent warning, Event 1530, User Profile Service reports "Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards." The details nearly always refer to "5 user registry handles leaked from \Registry\User\S-1-5-21-2246975502-3360084185-2704206490-1001:" and the culprit in each case is lsass.exe. I have done lots of searching about this and it does not seem to be a real problem, it is "by design" according to Microsoft (Event ID: 1530 may be logged in the Application log on a Windows Vista or newer computer). So I guess I will just have to ignore the warnings and take less interest in events reported in Event Viewer.

I will post if I discover anything over the next week or so, otherwise I guess I will happily post to simply to mark as solved.

Thanks again for all the help!

nursegladys · 10 Apr 2013

A quick update,

Everything seemed sorted, but I couldn't do without the Lenovo Thinkpad Power Management software. This was I think associated with the ugly Lenovo Doze Mode driver noted by Vir Gnarus. So I reinstalled it. At the same time I noticed that Lenovo have "Patch module for Power Manager for Windows 7", the notes say

"The patch module for Power Manager enables you to fix the application error related to VC++ 2005 components on the Windows Vista, and Windows 7 operating systems. After applying this patch, the following files will be copied to the following folder on your computer. <For 32-bit operating systems> C:\Program Files\ThinkPad\Utilities. PWMTR32V.dll <For 64-bit operating systems> C:\Program Files (x86) \ThinkPad\Utilities. PWMTR32V.dll, PWMTR64V.dll"

I wanted to see if this was really the fix to the problem so I did not install the patch and used the laptop for a week or so. Sure enough I have had a recurrence of the BSOD when the laptop is in sleep. The SF Diagnostic Tool log is attached if anyone would care to take a look.

I am now going to install the patch module and let the laptop run for a while to see if it solves the BSOD problems. I will report back on the results.

I hope this helps anyone else having similar problems.

Thanks to all!