cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Kxer44
Fanfold Paper
Posts: 15
Registered: ‎11-20-2013
Location: Finland
Views: 4,174
Message 1 of 12

Thinkpad S440 systematic crashes after upgrade to Win 8.1

Hi,

 

After installing Windows 8.1 I've had big problems with my brand new Thinkpad S440. The laptop has generated systematic bluescreens, mostly related to the Intel Wireless-N 7260 WiFi module. Disabling it in the Device Manager helped a little bit, but I also get other Bluescreens related to e.g.. to "usbxhci.sys" and other modules. After the BSoD the laptop always goes into a reboot-loop at the Lenovo logo during the boot-up with the only solution do do a hard shut down (keeping the power-button pressed for 5 sec). 

 

Yesterday I tried doing a fresh install, but it did not help at all. A few minutes after installing Win 8.1 from scratch the laptop generated a bluescreen.

 

I have updated all drivers to the latest version, and also tried to solve it by installing an earlier version of e.g. the WiFi driver. Neither one has helped

 

Below is a list of the minidumps generated during BSoD's I've had during the last 12 hours since installing a fresh copy of Windows 8.1. 

 

Please, what can I do about this situation? I would not like to return the machine since I like the hardware, but in the current state my Thinkpad S440 is useless. I have not found a way going back to Windows 8.0, since the recovery partition on the HDD apparently was destroyed (according to an Microsoft engineer) during my first trial to update to Win 8.1. (the first update ended in a Black Screen of Death). Microsoft was only willing supply me with a Win 8.1 product key (since a clean install was the only way to recover from the Black Screen of Death back then), which, of course, doesn't work for installing Win 8.0.

 

 

System Information (local)



computer name: LENOVO
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: 20AY001DMS, LENOVO
CPU: GenuineIntel Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8284897280 total




Crash Dump Analysis



Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

 

On Wed 11/20/2013 1:12:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-4734-01.dmp
This was probably caused by the following module: storport.sys (storport+0x1400)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80000740400, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 11/20/2013 1:12:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: storport.sys (storport!memset+0xC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80000740400, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 

 

 


On Wed 11/20/2013 10:03:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-9437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802A67DE929, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 11/20/2013 10:03:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: storport.sys (storport!StorPortExtendedFunction+0xEBB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802A67DE929, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 11/20/2013 6:23:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-4750-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002C71AFE)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF80002C71AFE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 11/19/2013 10:50:16 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-4375-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C5DAFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 11/19/2013 8:50:19 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111913-4921-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002EFDB12)
Bugcheck code: 0xD1 (0x38, 0x2, 0x0, 0xFFFFF80002EFDB12)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 11/19/2013 8:02:46 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111913-5640-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002C76B12)
Bugcheck code: 0xD1 (0x1038, 0x2, 0x0, 0xFFFFF80002C76B12)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 11/19/2013 7:38:32 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111913-7296-01.dmp
This was probably caused by the following module: netwbw02.sys (0xFFFFF800021A763A)
Bugcheck code: 0xD1 (0xFFFFE00069F99A4D, 0x2, 0x0, 0xFFFFF800021A763A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netwbw02.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netwbw02.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL


Vince69
Bit Torrent
Posts: 1,213
Registered: ‎12-24-2010
Location: Perth, Australia
Views: 4,151
Message 2 of 12

Re: Thinkpad S440 systematic crashes after upgrade to Win 8.1

Hi Kxer44,

 

It's mainly a driver isuue as you noticed. Unfortunately I don't think much can be done about it for now. You will have to wait for Lenovo to release drivers compatible with windows 8.1.

 

You will need to order a set of recovering discs from Lenovo and reinstall windows 8: http://support.lenovo.com/en_US/product-and-parts/detail.page?&LegacyDocID=MIGR-4M7HWZ

 

Vince.

__________________________________________________________________________________

Knowledge is of two kinds. We know a subject ourselves, or we know where we can find information on it.


ThinkPad T510 4313-CTO Windows 8 x64 - Intel Core i7-620M - NVIDIA NVS 3100M - 8GB RAM - 240GB SSD- Intel Centrino Ultimate-N 6300 - Gobi 2000.
ThinkPad Helix 3697-CTO Windows 8.1 x64 - Intel Core i7-3667U - Intel HD Graphics 4000 - 8GB RAM- 256GB SSD - Intel Centrino Advanced-N 6205 - Ericsson C5621gw

Kxer44
Fanfold Paper
Posts: 15
Registered: ‎11-20-2013
Location: Finland
Views: 4,131
Message 3 of 12

Re: Thinkpad S440 systematic crashes after upgrade to Win 8.1

Vince, thanks for the quick reply.

 

I can't be the only one having these issues since it's happening straight away with a clean install of Win 8.1? Anyone else having these issues on the S440 and been able to solve them without downgrading to Win 8.0? 

 

I think it's shameful that I first pay $1950 for this laptop which is marketed as a Win 8.1 machine, only to find out that it's unable to even run 8.1, and my only option would be to spend another $50 and 5 days (!) to get a recover media, which basically could be distributed over the internet as an option without any problems!

 

 

Is there any info on an existing solution or when these problems will be fixed on Win 8.1?

Kxer44
Fanfold Paper
Posts: 15
Registered: ‎11-20-2013
Location: Finland
Views: 4,113
Message 4 of 12

Re: Thinkpad S440 systematic crashes after upgrade to Win 8.1

Is there something I can disable in the Device Manager to stop USBXHCI.sys from crashing?

 

 

 On Wed 11/20/2013 8:57:07 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-11421-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002CF2AFB) 
Bugcheck code: 0xD1 (0xFFFFE008048F5240, 0x2, 0x0, 0xFFFFF80002CF2AFB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Wed 11/20/2013 8:57:07 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB) 
Bugcheck code: 0xD1 (0xFFFFE008048F5240, 0x2, 0x0, 0xFFFFF80002CF2AFB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Wed 11/20/2013 8:52:19 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-5265-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002F3EAFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Wed 11/20/2013 8:47:44 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-11218-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002C97AFE) 
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF80002C97AFE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Wed 11/20/2013 8:29:32 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-5218-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002CE9B20) 
Bugcheck code: 0xD1 (0x2261DC, 0x2, 0x0, 0xFFFFF80002CE9B20)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Wed 11/20/2013 8:20:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-11140-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002D44AFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Wed 11/20/2013 8:08:45 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-5000-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E9DAFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Wed 11/20/2013 7:46:12 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-11093-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C90AFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Wed 11/20/2013 6:53:10 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-4937-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002CBAB20) 
Bugcheck code: 0xD1 (0x225EEC, 0x2, 0x0, 0xFFFFF80002CBAB20)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Wed 11/20/2013 6:21:37 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-10140-01.dmp
This was probably caused by the following module: storport.sys (storport+0x1400) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800006BF400, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 

Vince69
Bit Torrent
Posts: 1,213
Registered: ‎12-24-2010
Location: Perth, Australia
Views: 4,089
Message 5 of 12

Re: Thinkpad S440 systematic crashes after upgrade to Win 8.1

USBXHCI.sys is the USB 3.0 driver, so remove the devices connected to the USB 3.0 port and use the USB 2.0 port instead.

 

Vince.

__________________________________________________________________________________

Knowledge is of two kinds. We know a subject ourselves, or we know where we can find information on it.


ThinkPad T510 4313-CTO Windows 8 x64 - Intel Core i7-620M - NVIDIA NVS 3100M - 8GB RAM - 240GB SSD- Intel Centrino Ultimate-N 6300 - Gobi 2000.
ThinkPad Helix 3697-CTO Windows 8.1 x64 - Intel Core i7-3667U - Intel HD Graphics 4000 - 8GB RAM- 256GB SSD - Intel Centrino Advanced-N 6205 - Ericsson C5621gw

Kxer44
Fanfold Paper
Posts: 15
Registered: ‎11-20-2013
Location: Finland
Views: 4,086
Message 6 of 12

Re: Thinkpad S440 systematic crashes after upgrade to Win 8.1

Interestingly enough I haven't had any USB device connected at all, but I did have the OneLink dock connected (for external screen). I really hope this will be solved by going back to Win 8.0 (which still can't be a long term solution).
Kxer44
Fanfold Paper
Posts: 15
Registered: ‎11-20-2013
Location: Finland
Views: 4,037
Message 7 of 12

Re: Thinkpad S440 systematic crashes after upgrade to Win 8.1

UPDATE: DOWNGRADING TO WIN 8.0 DID NOT SOLVE THE PROBLEM

 

I did a downgrade to Win 8.0 with a fresh install, but the problem remains. Straight after having the fresh copy of Win 8.0 the computer started crashing with a KERNEL_SECURITY_CHECK_FAILURE. Reading up a little on it on the internet it seemed that it might be caused by having old drivers or devices without drivers attached. Having a long list of internal uninstalled devices in the device manager I downloaded ThinkVantage System Update and updated all drivers to the latest version and installed all Windows Updates, only to notice that the same BSoD errors are back, whith the only exception that KERNEL_SECURITY_CHECK_FAILURE continues to appear and is the most common one.

 


I hoped downgrading back to Win 8.0 would help, but it didn't. Is there anything else I can try?

 

 

On Sat 23.11.2013 11:41:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112313-5250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF880009C4CA0, 0xFFFFF880009C4BF8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 23.11.2013 11:41:20 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: btmhsf.sys (btmhsf+0x3387)
Bugcheck code: 0x139 (0x3, 0xFFFFF880009C4CA0, 0xFFFFF880009C4BF8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\btmhsf.sys
product: Intel PROSet\Wireless Bluetooth
company: Motorola Solutions, Inc.
description: Bluetooth HighSpeed Filter Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: btmhsf.sys (Bluetooth HighSpeed Filter Driver, Motorola Solutions, Inc.).
Google query: Motorola Solutions, Inc. KERNEL_SECURITY_CHECK_FAILURE



On Sat 23.11.2013 11:37:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112313-5171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF880009C4CA0, 0xFFFFF880009C4BF8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 23.11.2013 11:30:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112313-5468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF880009C4CA0, 0xFFFFF880009C4BF8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 23.11.2013 11:11:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112313-6765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF880009C4CA0, 0xFFFFF880009C4BF8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 23.11.2013 11:04:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112313-6703-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF88005ECEF7C)
Bugcheck code: 0xD1 (0xFFFFFA880DB553C0, 0x2, 0x0, 0xFFFFF88005ECEF7C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 23.11.2013 11:01:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112313-6593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF880009C4CA0, 0xFFFFF880009C4BF8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 23.11.2013 11:00:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112313-6562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF880009C4CA0, 0xFFFFF880009C4BF8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 23.11.2013 10:53:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112313-6453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF880009C4CA0, 0xFFFFF880009C4BF8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 23.11.2013 10:52:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112313-7031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF880009C4CA0, 0xFFFFF880009C4BF8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Lenovo Employee howardhugy1
Lenovo Employee
Posts: 15
Registered: ‎11-25-2012
Location: SH,CN
Views: 3,952
Message 8 of 12

Re: Thinkpad S440 systematic crashes after upgrade to Win 8.1

what about the result of removing the docking.
Kxer44
Fanfold Paper
Posts: 15
Registered: ‎11-20-2013
Location: Finland
Views: 3,948
Message 9 of 12

Re: Thinkpad S440 systematic crashes after upgrade to Win 8.1

You mean not having it attached to the OneLink dock? In these cases the DRIVER_IRQL_NOT_LESS_OR_EQUAL caused by usbxhci.sys did not appear.

Currently I have the system back on the pre-installed Windows 8.0 OEM version without any updates, after Lenovo Support replaced the motherboard. It now allows me to have it connected to the dock with no BSoD's (at least so far, sub 24h's since getting it back), but straight after updating the system through Windows Update I started getting the KERNEL_SECURITY_CHECK_FAILURE crashes, so had to restore it back to original OEM version, without any updates, through system restore.
Lenovo Employee howardhugy1
Lenovo Employee
Posts: 15
Registered: ‎11-25-2012
Location: SH,CN
Views: 3,930
Message 10 of 12

Re: Thinkpad S440 systematic crashes after upgrade to Win 8.1

ker44,  I read the BSOD related to Kernel_Security... you mentioned in another topic---WIFI problem;

now, lenovo has got reported of this WIFI problem, and already been on analyzing, please wait for update, thank you.

Check out current deals!


Shop current deals

Top Kudoed Authors