BSOD Kernel_Data_Inpage_Error

badkenny · Dec 13, 2012

Hi, I just bought Thinkpad W530 and from very beginning I have BSOD almost every day

I'm getitng couple types of them (ie. DPC_WATCHDOG_VIOLATION), but most frequent one is KERNEL_DATA_INPAGE_ERROR. I Hope U will help me guys.

P.S. I have some problems with WiFi adapter - sometimes need to restart it to connect to my access point - so that may be some trace.

usasma · Dec 14, 2012

I had a quick look at the dumps and nothing stands out to me.
Please start with these free diagnostics: Hardware Diagnostics

I'll post back this afternoon (after work) with more details.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

smihlp.sys Mon May 30 12:21:37 2011 (4DE3C411)
SMI helper driver - Likely part of the UPEK Protector Suite
http://www.carrona.org/drivers/driver.php?id=smihlp.sys

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Thu Dec 13 09:16:30.161 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121312-13000-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16442.amd64fre.win8_gdr.121023-1503
System Uptime:[B]0 days 21:37:51.936[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+24028 )[/B]
BugCheck [B]7A, {4, 0, fffffa800e8f8e80, 4b0000}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000007A]KERNEL_DATA_INPAGE_ERROR (7a)[/url]
Arguments: 
Arg1: 0000000000000004, lock type that was held (value 1,2,3, or PTE address)
Arg2: 0000000000000000, error status (normally i/o status code)
Arg3: fffffa800e8f8e80, current process (virtual address for lock type 3, or PTE)
Arg4: 00000000004b0000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
BUGCHECK_STR:  0x7a_0
PROCESS_NAME: [B]netsh.exe[/B]
FAILURE_BUCKET_ID: [B]0x7a_0_nt!_??_::FNODOBFM::_string_[/B]
CPUID:        "Intel(R) Core(TM) i7-3820QM CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: [B]2694[/B]
  BIOS Version                  G5ET61WW (2.03 )
  BIOS Release Date             09/13/2012
  Manufacturer                  LENOVO
  Product Name                  2436CTO
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 10 08:37:50.407 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121012-10062-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16442.amd64fre.win8_gdr.121023-1503
System Uptime:[B]0 days 17:32:12.851[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13c4c )[/B]
BugCheck [B]133, {0, 281, 280, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000281, The DPC time count (in ticks).
Arg3: 0000000000000280, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]0x133_DPC_nt!_??_::FNODOBFM::_string_[/B]
CPUID:        "Intel(R) Core(TM) i7-3820QM CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: [B]2694[/B]
  BIOS Version                  G5ET61WW (2.03 )
  BIOS Release Date             09/13/2012
  Manufacturer                  LENOVO
  Product Name                  2436CTO
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Thu Dec 13 09:16:30.161 2012 (UTC - 5:00)**************************
[COLOR=RED][B]smihlp.sys                  Mon May 30 12:21:37 2011 (4DE3C411)[/B][/COLOR]
HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
risdxc64.sys                Wed Jul  4 00:39:23 2012 (4FF3C8FB)
iaStorA.sys                 Mon Jul  9 16:42:33 2012 (4FFB4239)
dump_iaStorA.sys            Mon Jul  9 16:42:33 2012 (4FFB4239)
e1c63x64.sys                Thu Jul 12 17:46:10 2012 (4FFF45A2)
usb3Hub.sys                 Fri Jul 20 08:04:32 2012 (50094950)
Apsx64.sys                  Sat Jul 21 03:30:07 2012 (500A5A7F)
iwdbus.sys                  Mon Jul 23 16:19:17 2012 (500DB1C5)
btwavdt.sys                 Wed Jul 25 17:46:28 2012 (50106934)
btwaudio.sys                Wed Jul 25 17:48:04 2012 (50106994)
btwrchid.sys                Wed Jul 25 17:49:13 2012 (501069D9)
bcbtums.sys                 Wed Jul 25 18:36:20 2012 (501074E4)
BthLEEnum.sys               Wed Jul 25 22:25:02 2012 (5010AA7E)
intelppm.sys                Wed Jul 25 22:26:48 2012 (5010AAE8)
XHCIPort.sys                Thu Jul 26 04:54:06 2012 (501105AE)
btwl2cap.sys                Thu Jul 26 11:14:41 2012 (50115EE1)
LnvHIDHW.sys                Mon Jul 30 03:11:29 2012 (501633A1)
RCUVCAVS.sys                Wed Aug  1 22:44:09 2012 (5019E979)
btwampfl.sys                Thu Aug  9 20:49:00 2012 (50245A7C)
ApsHM64.sys                 Fri Aug 10 22:24:57 2012 (5025C279)
ibmpmdrv.sys                Wed Aug 15 22:40:18 2012 (502C5D92)
SynTP.sys                   Thu Aug 16 16:09:43 2012 (502D5387)
Smb_driver_Intel.sys        Thu Aug 16 16:11:24 2012 (502D53EC)
RTKVHD64.sys                Tue Aug 21 06:32:01 2012 (503363A1)
igdkmd64.sys                Tue Aug 21 13:08:36 2012 (5033C094)
Tppwr64v.sys                Tue Sep  4 00:28:58 2012 (5045838A)
NETwew00.sys                Thu Sep 13 09:23:54 2012 (5051DE6A)
nvlddmkm.sys                Tue Oct  2 14:21:13 2012 (506B3099)
nvpciflt.sys                Tue Oct  2 14:21:40 2012 (506B30B4)
nvkflt.sys                  Tue Oct  2 14:21:49 2012 (506B30BD)
[/font]

usasma · Dec 14, 2012

I had a quick look at the dumps and nothing stands out to me.
Please start with these free diagnostics: Hardware Diagnostics

I'll post back this afternoon (after work) with more details.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

smihlp.sys Mon May 30 12:21:37 2011 (4DE3C411)
SMI helper driver - Likely part of the UPEK Protector Suite
http://www.carrona.org/drivers/driver.php?id=smihlp.sys

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Thu Dec 13 09:16:30.161 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121312-13000-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16442.amd64fre.win8_gdr.121023-1503
System Uptime:[B]0 days 21:37:51.936[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+24028 )[/B]
BugCheck [B]7A, {4, 0, fffffa800e8f8e80, 4b0000}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000007A]KERNEL_DATA_INPAGE_ERROR (7a)[/url]
Arguments: 
Arg1: 0000000000000004, lock type that was held (value 1,2,3, or PTE address)
Arg2: 0000000000000000, error status (normally i/o status code)
Arg3: fffffa800e8f8e80, current process (virtual address for lock type 3, or PTE)
Arg4: 00000000004b0000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
BUGCHECK_STR:  0x7a_0
PROCESS_NAME: [B]netsh.exe[/B]
FAILURE_BUCKET_ID: [B]0x7a_0_nt!_??_::FNODOBFM::_string_[/B]
CPUID:        "Intel(R) Core(TM) i7-3820QM CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: [B]2694[/B]
  BIOS Version                  G5ET61WW (2.03 )
  BIOS Release Date             09/13/2012
  Manufacturer                  LENOVO
  Product Name                  2436CTO
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 10 08:37:50.407 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121012-10062-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16442.amd64fre.win8_gdr.121023-1503
System Uptime:[B]0 days 17:32:12.851[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13c4c )[/B]
BugCheck [B]133, {0, 281, 280, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000281, The DPC time count (in ticks).
Arg3: 0000000000000280, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]0x133_DPC_nt!_??_::FNODOBFM::_string_[/B]
CPUID:        "Intel(R) Core(TM) i7-3820QM CPU @ 2.70GHz"
MaxSpeed:     2700
CurrentSpeed: [B]2694[/B]
  BIOS Version                  G5ET61WW (2.03 )
  BIOS Release Date             09/13/2012
  Manufacturer                  LENOVO
  Product Name                  2436CTO
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Thu Dec 13 09:16:30.161 2012 (UTC - 5:00)**************************
[COLOR=RED][B]smihlp.sys                  Mon May 30 12:21:37 2011 (4DE3C411)[/B][/COLOR]
HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
risdxc64.sys                Wed Jul  4 00:39:23 2012 (4FF3C8FB)
iaStorA.sys                 Mon Jul  9 16:42:33 2012 (4FFB4239)
dump_iaStorA.sys            Mon Jul  9 16:42:33 2012 (4FFB4239)
e1c63x64.sys                Thu Jul 12 17:46:10 2012 (4FFF45A2)
usb3Hub.sys                 Fri Jul 20 08:04:32 2012 (50094950)
Apsx64.sys                  Sat Jul 21 03:30:07 2012 (500A5A7F)
iwdbus.sys                  Mon Jul 23 16:19:17 2012 (500DB1C5)
btwavdt.sys                 Wed Jul 25 17:46:28 2012 (50106934)
btwaudio.sys                Wed Jul 25 17:48:04 2012 (50106994)
btwrchid.sys                Wed Jul 25 17:49:13 2012 (501069D9)
bcbtums.sys                 Wed Jul 25 18:36:20 2012 (501074E4)
BthLEEnum.sys               Wed Jul 25 22:25:02 2012 (5010AA7E)
intelppm.sys                Wed Jul 25 22:26:48 2012 (5010AAE8)
XHCIPort.sys                Thu Jul 26 04:54:06 2012 (501105AE)
btwl2cap.sys                Thu Jul 26 11:14:41 2012 (50115EE1)
LnvHIDHW.sys                Mon Jul 30 03:11:29 2012 (501633A1)
RCUVCAVS.sys                Wed Aug  1 22:44:09 2012 (5019E979)
btwampfl.sys                Thu Aug  9 20:49:00 2012 (50245A7C)
ApsHM64.sys                 Fri Aug 10 22:24:57 2012 (5025C279)
ibmpmdrv.sys                Wed Aug 15 22:40:18 2012 (502C5D92)
SynTP.sys                   Thu Aug 16 16:09:43 2012 (502D5387)
Smb_driver_Intel.sys        Thu Aug 16 16:11:24 2012 (502D53EC)
RTKVHD64.sys                Tue Aug 21 06:32:01 2012 (503363A1)
igdkmd64.sys                Tue Aug 21 13:08:36 2012 (5033C094)
Tppwr64v.sys                Tue Sep  4 00:28:58 2012 (5045838A)
NETwew00.sys                Thu Sep 13 09:23:54 2012 (5051DE6A)
nvlddmkm.sys                Tue Oct  2 14:21:13 2012 (506B3099)
nvpciflt.sys                Tue Oct  2 14:21:40 2012 (506B30B4)
nvkflt.sys                  Tue Oct  2 14:21:49 2012 (506B30BD)
[/font]

usasma · Dec 14, 2012

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.
10 Nov 2012 - I'm seeing an upswing in SSD errors - but most appear due to older storage controller drivers. I strongly suggest NOT using storage controller drivers that don't date from 2012 (if none are available, don't connect an SSD to that controller)

Other than the above comments, there isn't much else in the reports to place the blame on anything specific.
I'd suggest replacing the Intel Storage Drivers.
If the BSOD's continue, try Driver Verifier according to these instructions: Driver Verifier Settings
Beyond that, keep running the hardware diagnostics that I mentioned earlier.

Good luck!

BSOD Kernel_Data_Inpage_Error

badkenny

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One