Forum Home
Press F1
 
Thread ID: 141769 2016-02-20 21:53:00 BSOD when shutting laptop lid on battery dpDesignz (15919) Press F1
Post ID Timestamp Content User
1416314 2016-02-21 01:17:00 Download crystal diskinfo and run it, ( or any other software) that checks for Failing sectors on the HDD.

The start of the Bugcheck Analysis says its the problem ( highlighted below) as well as further down the report as well ( highlighted)

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: ffffc000ae1f8768, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000003744c8c0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8019a255824, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.63.amd64fre.th2_release.160104-1513

SYSTEM_MANUFACTURER: TOSHIBA

SYSTEM_PRODUCT_NAME: Satellite U840W

SYSTEM_SKU: PSU5XA

SYSTEM_VERSION: PSU5XA-001006

BIOS_VENDOR: Insyde Corp.

BIOS_VERSION: 6.30

BIOS_DATE: 09/21/2012

BASEBOARD_MANUFACTURER: Type2 - Board Vendor Name1

BASEBOARD_PRODUCT: Type2 - Board Product Name1

BASEBOARD_VERSION: Type2 - Board Version

DUMP_TYPE: 2

BUGCHECK_P1: ffffc000ae1f8768

BUGCHECK_P2: ffffffffc000000e

BUGCHECK_P3: 3744c8c0

BUGCHECK_P4: fffff8019a255824

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

CPU_COUNT: 4

CPU_MHZ: 6a0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 1B'00000000 (cache) 1B'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: LOUNGE

ANALYSIS_SESSION_TIME: 02-21-2016 14:11:43.0382

ANALYSIS_VERSION: 1 0. 0. 10586.567 amd64fre

TRAP_FRAME: ffffd0012940fd50 -- (.trap 0xffffd0012940fd50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000024a7e rbx=0000000000000000 rcx=ffffd0012940ff80
rdx=0000280070e458a4 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800f9358fc0 rsp=ffffd0012940fee8 rbp=0000000000015824
r8=0000000000000002 r9=0000000000000000 r10=0000000000015826
r11=ffffd0012940ff80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!memcpy+0x40:
fffff800`f9358fc0 8a040a mov al,byte ptr [rdx+rcx] ds:fffff801`9a255824=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800f9388f55 to fffff800f934d770

STACK_TEXT:
ffffd001`2940f9c8 fffff800`f9388f55 : 00000000`0000007a ffffc000`ae1f8768 ffffffff`c000000e 00000000`3744c8c0 : nt!KeBugCheckEx
ffffd001`2940f9d0 fffff800`f92b2b48 : 00000000`00000002 ffffd001`2940fb98 ffffc000`ae1f8768 ffffe001`a05b69d0 : nt! ?? ::FNODOBFM::`string'+0x2ce55
ffffd001`2940fb00 fffff800`f924437f : 00000000`c0033333 fffff800`f95078f0 ffffd001`2940fd50 00000000`ffffffff : nt!MiIssueHardFault+0x1a8
ffffd001`2940fbe0 fffff800`f93569bc : 00000000`00003803 ffffd001`294102f0 ffffd001`29410358 ffffc000`b2daba90 : nt!MmAccessFault+0x82f
ffffd001`2940fd50 fffff800`f9358fc0 : fffff800`f96cfec1 ffffd001`2940003b 00000000`00000001 00000000`00000001 : nt!KiPageFault+0x13c
ffffd001`2940fee8 fffff800`f96cfec1 : ffffd001`2940003b 00000000`00000001 00000000`00000001 fffff800`f97035c9 : nt!memcpy+0x40
ffffd001`2940fef0 fffff800`f96cfdbf : ffffd001`29410010 00000000`0000003b ffffd001`29410052 ffffd001`2941000d : nt!SdbpReadMappedData+0x31
ffffd001`2940ff40 fffff800`f96d4dbc : ffffd001`2941000e 00000000`0000003b ffffd001`29410000 ffffd001`2941000b : nt!SdbGetTagFromTagID+0x1b
ffffd001`2940ff70 fffff800`f96d480d : ffffd001`294101c0 00000000`0000003b ffffd001`2941004a ffffd001`29410009 : nt!SdbGetFirstChild+0x18
ffffd001`2940ffa0 fffff800`f95c76c7 : ffffd001`294101c0 ffffd001`294100d0 00000000`00015824 00000000`00000001 : nt!SdbFindFirstTag+0x29
ffffd001`2940ffd0 fffff800`f95c73b2 : ffffc000`bdd28be0 ffffc000`b4342350 ffffc000`bdd28be0 ffffc000`bdd28be0 : nt!SdbpFindFirstIndexedWildCardTag+0x163
ffffd001`29410180 fffff800`f96fc620 : 00000000`00000000 ffffc000`00000000 ffffd001`29410290 ffffc000`bdd28be0 : nt!SdbGetDatabaseMatchEx+0xae
ffffd001`29410220 fffff800`f96fc2e1 : 00000000`c0000225 ffffc000`bdd28be0 ffffc000`b4342350 00000000`00000000 : nt!KsepDbCacheReadDevice+0x90
ffffd001`294102c0 fffff800`f96fc16c : fffff801`99d987b0 ffffd001`29410380 00000000`00000000 00000000`00000206 : nt!KseQueryDeviceData+0xdd
ffffd001`29410320 fffff801`99dd0760 : ffffc000`bdd28be0 00000000`00000000 ffffe001`9ff82000 ffffc000`00000000 : nt!KseQueryDeviceFlags+0x88
ffffd001`294103b0 fffff801`99d3fc4b : ffffe001`9ff82000 ffffe001`9eb7e3e0 00000000`00000000 00000000`00000000 : bthport!BthQueryRadioCompatFlags+0xa0
ffffd001`294103f0 fffff801`99d1a9e5 : ffffe001`a1937600 ffffd001`29410721 00000000`00000000 ffffe001`a1937600 : bthport!HCI_CriticalCallback+0x92b
ffffd001`29410660 fffff801`99dba7ff : ffffe001`9ff82000 ffffe001`9ff82000 00000000`0000000e 00000000`00000000 : bthport!HCI_DoCmdCompletion+0x4fd
ffffd001`29410780 fffff801`99dc19eb : ffffe001`9ff40470 ffffd001`29410900 ffffe001`9ff82000 fffff801`99d9c5f0 : bthport!HCI_ProcessEvent+0xab
ffffd001`294107c0 fffff801`99d53185 : ffffe001`9ff40470 ffffe001`9ff82000 ffffe001`9ff404c8 ffffe001`00000000 : bthport!HCI_ProcessBip+0x63
ffffd001`29410800 fffff800`f9214125 : 00000005`bd9bbfff ffffe001`9ff83800 fffff801`99d52ae0 ffffe001`9eac7260 : bthport!HCI_ThreadFunction+0x6a5
ffffd001`29410c10 fffff800`f9352916 : ffffd001`2c480180 ffffe001`9ff83800 fffff800`f92140e4 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffd001`29410c60 00000000`00000000 : ffffd001`29411000 ffffd001`2940b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 547db67264e34ab12137fe53bc206cbaadb38be5

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f86e8e60fc79a258766f206e01d1a0fb123c68c6

THREAD_SHA1_HASH_MOD: e033f22f772995a07d49da7ec2df52c28abf9bed

FOLLOWUP_IP:
bthport!BthQueryRadioCompatFlags+a0
fffff801`99dd0760 ba42544443 mov edx,43445442h

FAULT_INSTR_CODE: 445442ba

SYMBOL_STACK_INDEX: f

SYMBOL_NAME: bthport!BthQueryRadioCompatFlags+a0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bthport

IMAGE_NAME: bthport.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 568b1fdf

IMAGE_VERSION: 1 0. 0. 10586.63

BUCKET_ID_FUNC_OFFSET: a0

FAILURE_BUCKET_ID: 0x7a_c000000e_bthport!BthQueryRadioCompatFlags

BUCKET_ID: 0x7a_c000000e_bthport!BthQueryRadioCompatFlags

PRIMARY_PROBLEM_CLASS: 0x7a_c000000e_bthport!BthQueryRadioCompatFlags

TARGET_TIME: 2016-01-20T04:28:05.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-01-05 14:28:56

BUILDDATESTAMP_STR: 160104-1513

BUILDLAB_STR: th2_release

BUILDOSVER_STR: 1 0. 0. 10586.63.amd64fre.th2_release.160104-1513

ANALYSIS_SESSION_ELAPSED_TIME: 32a4

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x7a_c000000e_bthport!bthqueryradiocompatflags

FAILURE_ID_HASH: {81dda3d1-3f5a-96e8-4b3a-3d0120205945}

Followup: MachineOwner
--------- 		wainuitech (129)
1416315 2016-02-21 05:09:00 If NOD is installed it should have disabled it

That's what I would have thought, but it hasn't :/ Any idea how to do this manually? 		dpDesignz (15919)
1416316 2016-02-21 05:10:00 @wainuitech spent the avo removing unrequired software, updating drivers, and running windows update. Just installing Crystal Disk Info. What do I need to be looking out for? dpDesignz (15919)
1416317 2016-02-21 07:35:00 When you run crystal disk info, it takes a few seconds to run but it shows the condition of the HDD. Any bad sectors will show as either Caution or BAD.

Theres 3 results.

Good = Blue
Yellow = Caution -- Drives starting to give problems /Fail
Red = Bad --- Copy off any data - Replace the Drive NOW before it dies.

Many drives if they have Caution will give problems, some may work like this for years, others wont.

If you notice the report, it says " Typically caused by a bad block in the paging file or disk controller error" This can mean if there's any failed sectors they may be in the section the drive uses when sleeping, and causing the BSOD - Think of it as a section like a jigsaw puzzle with pieces missing.


re the installing -- never used the install Version, the portable is all that s needed. crystalmark.info
6975

The drives on this PC are fine
6976

Heres a result, the second drive shows as Caution, its a temporary storage drive that's been like it for a few years now, the good drive has the Red square ( Reports as Good, the Arrow points to the second drive with reallocated sectors, if there's failed sectors the yellow dot is nearer the bottom in uncorrectable sector count.

6977 		wainuitech (129)
1 2