My Nextbook PC tablet frequently crashes with the "blue screen of death" DRIVER_IRQL_NOT_LESS_OR_EQUAL tcpip.sys error. It does not consistently occur while running a particular program, Windows 8.1 is up to date, all drivers report they are functioning properly, and the only additional things I've installed are Steam, a Steam game, and a wireless bluetooth mouse. I've also seen this error once: KERNEL_DATA_INPAGE_ERROR. Here are all my dmp files: https://onedrive.live.com/redir?resid=56A1A63274D590CC!466&authkey=!AJ35Ui-W-tF2HeU&ithint=file%2czip. Please help!!

ZS

These were ALL Related to BTHport.sys Bluetooth Bus Driver.  I would remove the current driver and install the newest driver available

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Ken\Desktop\Minidump\020915-19109-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17328.x86fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0x81a69000 PsLoadedModuleList = 0x81c67498
Debug session time: Tue Feb 10 04:49:22.095 2015 (UTC - 4:00)
System Uptime: 5 days 5:12:45.808
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {18, 2, 0, 8f013878}

Probably caused by : bthport.sys ( bthport!WPP_RECORDER_SF_sss+f8 )

Followup: MachineOwner
---------

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000018, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8f013878, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 81c966f4
Unable to read MiSystemVaType memory at 81c66580
 00000018 

CURRENT_IRQL:  2

FAULTING_IP: 
bthport!WPP_RECORDER_SF_sss+f8
8f013878 8a01            mov     al,byte ptr [ecx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

TRAP_FRAME:  8ee52a64 -- (.trap 0xffffffff8ee52a64)
ErrCode = 00000000
eax=00000001 ebx=8f075f00 ecx=00000018 edx=00000019 esi=00000018 edi=8f0708dc
eip=8f013878 esp=8ee52ad8 ebp=8ee52af8 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
bthport!WPP_RECORDER_SF_sss+0xf8:
8f013878 8a01            mov     al,byte ptr [ecx]          ds:0023:00000018=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 81b7c0d3 to 81b679f0

STACK_TEXT:  
8ee529c0 81b7c0d3 0000000a 00000018 00000002 nt!KiBugCheck2
8ee529c0 8f013878 0000000a 00000018 00000002 nt!KiTrap0E+0x1cf
8ee52af8 8f022807 00000001 00000012 8f0720e8 bthport!WPP_RECORDER_SF_sss+0xf8
8ee52b20 8f026c86 8d084738 96703dd0 00000000 bthport!HCI_CxnSetStateLocked+0x61
8ee52b34 8f01ff6a 8d084738 00000000 96703dd0 bthport!Fn_EVENT_ModeChange+0x46
8ee52bb4 8f034c66 96703dd0 00000000 00000001 bthport!HCI_DoCmdCompletion+0x410
8ee52be0 8f080016 c000000d 896712f8 00000000 bthport!HCI_ProcessAsynchronousEvent+0xcc
8ee52bf4 8f084504 00000008 81ad7bf0 896712f8 bthport!HCI_ProcessEvent+0x42
8ee52c08 8f042a83 00000000 895ba300 84113cc0 bthport!HCI_ProcessBip+0x4c
8ee52d70 81b2a34e 8d0840d0 449500fd 00000000 bthport!HCI_ThreadFunction+0x1d3
8ee52db0 81b7d411 8f0428b0 8d0840d0 00000000 nt!PspSystemThreadStartup+0x58
8ee52dbc 00000000 00000000 00000001 01c13e28 nt!KiThreadStartup+0x15


STACK_COMMAND:  kb

FOLLOWUP_IP: 
bthport!WPP_RECORDER_SF_sss+f8
8f013878 8a01            mov     al,byte ptr [ecx]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  bthport!WPP_RECORDER_SF_sss+f8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bthport

IMAGE_NAME:  bthport.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53d0e346

IMAGE_VERSION:  6.3.9600.17238

BUCKET_ID_FUNC_OFFSET:  f8

FAILURE_BUCKET_ID:  AV_bthport!WPP_RECORDER_SF_sss

BUCKET_ID:  AV_bthport!WPP_RECORDER_SF_sss

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_bthport!wpp_recorder_sf_sss

FAILURE_ID_HASH:  {55986864-2ba6-3b5b-c65d-7837ad452922}

Followup: MachineOwner
---------

0: kd> lmvm bthport
start    end        module name
8f00e000 8f10d000   bthport    (pdb symbols)          e:\symbols\bthport.pdb\2F0DDD68EA714A00B20430AE29216DB31\bthport.pdb
    Loaded symbol image file: bthport.sys
    Mapped memory image file: e:\symbols\bthport.sys\53D0E346ff000\bthport.sys
    Image path: \SystemRoot\System32\Drivers\bthport.sys
    Image name: bthport.sys
    Timestamp:        Thu Jul 24 06:43:18 2014 (53D0E346)
    CheckSum:         000FEA9D
    ImageSize:        000FF000
    File version:     6.3.9600.17238
    Product version:  6.3.9600.17238
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft Windows Operating System
    InternalName:     bthport.sys
    OriginalFilename: bthport.sys
    ProductVersion:   6.3.9600.17238
    FileVersion:      6.3.9600.17238 (winblue_gdr.140723-2018)
    FileDescription:  Bluetooth Bus Driver
    LegalCopyright:    Microsoft Corporation. All rights reserved.

Okay, thanks.

Once I uninstall the current one, where can I find and download a new one??

Also, could you please explain why this error is happening? I assume it's something to do with my bluetooth mouse, right?

• Edited by ZipporahS 4 hours 4 minutes ago

ZS

Sorry.  On further examination it may be part of the OS.  If that is the case you should simply run a system file check to verify it. 

One other thing of note.  The most recent DMP file was from Feb 10, 2015 so it may not reflect your current problem

Please run a system file check (SFC)
All instructions are in our Wiki article below...
Should you have any questions please ask us.

System file check (SFC) Scan and Repair System Files

Okay, thanks.

Once I uninstall the current one, where can I find and download a new one??

Also, could you please explain why this error is happening? I assume it's something to do with my bluetooth mouse, right?

• Edited by ZipporahS Sunday, March 15, 2015 3:13 AM

Okay, thanks.

Once I uninstall the current one, where can I find and download a new one??

Also, could you please explain why this error is happening? I assume it's something to do with my bluetooth mouse, right?

• Edited by ZipporahS Sunday, March 15, 2015 3:13 AM

I ran the system check and it found "no integrity violations". Does this confirm a problem with the bthport.sys driver? If so, what steps do I need to take to uninstall the old one and install a new one?? Thanks!

ZS

With only one DMP file there is no way to confirm it or track the trend.  If you have other DMP files upload them.  It may have been something else that triggered the BT driver to fail

I don't know about these things so if there are any other dmp files I wouldn't know where else to look for them or why they wouldn't be where you said (I simply followed one of your articles to find them). The ones I uploaded are the red flagged errors, none of the yellow ones. Do you mean those?

Hi ZipporahS,

You can uninstall the device under Device Manager first. For the newest driver, you need go to the manufacturer website to download the driver.

Anyway, a new dump file is better to analyze the root cause as  ZigZag3143x said.

There is no "new" or more recent dump file. I uploaded ALL of them. Feb is the most recent because I couldn't use the tablet for a month. If there are dump files in a location besides C:\Windows\Minidump, please tell me how to find them and I'll upload them for you. If not, what other information would be useful for you to help me? Maybe the system error logs or something??

• Edited by ZipporahS 12 hours 37 minutes ago

There is no "new" or more recent dump file. I uploaded ALL of them. Feb is the most recent because I couldn't use the tablet for a month. If there are dump files in a location besides C:\Windows\Minidump, please tell me how to find them and I'll upload them for you. If not, what other information would be useful for you to help me? Maybe the system error logs or something??

• Edited by ZipporahS Thursday, March 19, 2015 6:43 PM

PLEASE respond!!!