HP Laptop Pavilion g6
Windows 8.1
dxdiag screens:
Crashes whenever booting and coming back from sleep with this error
already ran multiple disk checks with both windows and seatools and memory diagnostics with no errors anywhere
also tried running driver verifier for a while and didnt find anything.
Windows 8.1
dxdiag screens:
Crashes whenever booting and coming back from sleep with this error
already ran multiple disk checks with both windows and seatools and memory diagnostics with no errors anywhere
also tried running driver verifier for a while and didnt find anything.
Code:
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17736.amd64fre.winblue_r9.150322-1500
Machine Name:
Kernel base = 0xfffff802`4f201000 PsLoadedModuleList = 0xfffff802`4f4da850
Debug session time: Wed Jul 8 12:00:24.671 2015 (UTC + 2:00)
System Uptime: 1 days 0:26:47.112
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6e000f07e48, ffffffffc000000e, 14bbcf880, ffffc001e0fc9040}
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
************* Symbol Loading Error Summary **************
Module name Error
atapi The system cannot find the file specified : srv*c:\windows\symbol_cache*http://msdl.microsoft.com/download/symbols
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1881b )
Followup: MachineOwner
---------
3: 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: fffff6e000f07e48, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000014bbcf880, current process (virtual address for lock type 3, or PTE)
Arg4: ffffc001e0fc9040, 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
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
TRAP_FRAME: ffffd001be7f89b0 -- (.trap 0xffffd001be7f89b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000d rbx=0000000000000000 rcx=ffffd001be7f8b60
rdx=ffffc001e0fc9000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8024f6cbe27 rsp=ffffd001be7f8b40 rbp=0000000000000001
r8=00000000ffffffff r9=fffff8024f201000 r10=ffffd001ba9c1560
r11=ffffc001e3167010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!MiFreeRelocations+0x37:
fffff802`4f6cbe27 488b4f40 mov rcx,qword ptr [rdi+40h] ds:00000000`00000040=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8024f37a9db to fffff8024f351ca0
STACK_TEXT:
ffffd001`be7f8678 fffff802`4f37a9db : 00000000`0000007a fffff6e0`00f07e48 ffffffff`c000000e 00000001`4bbcf880 : nt!KeBugCheckEx
ffffd001`be7f8680 fffff802`4f2679e0 : 00000000`00000002 ffffd001`be7f87a8 fffff802`4f55cdc0 ffffe000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1881b
ffffd001`be7f8770 fffff802`4f25468a : fffff802`4f55cdc0 ffffe000`d4334700 00000000`00000000 ffffe000`d7ab3be8 : nt!MiIssueHardFault+0x184
ffffd001`be7f87f0 fffff802`4f35bf2f : 00000000`00000000 ffffe000`d9019ea0 ffffe000`d6898300 ffffe000`d6898010 : nt!MmAccessFault+0x5ba
ffffd001`be7f89b0 fffff802`4f6cbe27 : 00000000`00000000 ffffe000`d9019ea0 00000000`00000001 ffffe000`d9019ca0 : nt!KiPageFault+0x12f
ffffd001`be7f8b40 fffff802`4f27109d : ffffe000`d9019ea0 00000000`00000000 ffffc001`e3167010 fffff802`4f25401f : nt!MiFreeRelocations+0x37
ffffd001`be7f8b80 fffff802`4f271028 : 00000000`000800a1 00000000`00000000 ffffe000`d9019ca0 00000000`00000001 : nt!MiDeleteControlArea+0x6d
ffffd001`be7f8bb0 fffff802`4f5aa071 : 00000000`00000000 ffffe000`d9019ca0 ffffe000`000800a1 00000000`0000000a : nt!MiDereferenceControlAreaProbe+0x10
ffffd001`be7f8be0 fffff802`4f31afb4 : fffff802`4f55c000 ffffd001`be7f8c90 ffffe000`d9019ca8 00000000`80000000 : nt!MiSegmentDelete+0xbd
ffffd001`be7f8c20 fffff802`4f339601 : 00000000`00000000 fffff802`4f4dadc0 ffffe000`d42838c0 510875ff`00000012 : nt!MiProcessDereferenceList+0x100
ffffd001`be7f8cb0 fffff802`4f30136c : ffffe000`d4334700 00000000`00000080 ffffe000`d4334700 00000000`00000000 : nt!MiDereferenceSegmentThread+0xd9
ffffd001`be7f8d40 fffff802`4f3582c6 : fffff802`4f504180 ffffe000`d4334700 fffff802`4f55da00 ec658dc0`330001da : nt!PspSystemThreadStartup+0x58
ffffd001`be7f8da0 00000000`00000000 : ffffd001`be7f9000 ffffd001`be7f3000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+1881b
fffff802`4f37a9db cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+1881b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 550f41a6
BUCKET_ID_FUNC_OFFSET: 1881b
FAILURE_BUCKET_ID: 0x7a_c000000e_nt!_??_::FNODOBFM::_string_
BUCKET_ID: 0x7a_c000000e_nt!_??_::FNODOBFM::_string_
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x7a_c000000e_nt!_??_::fnodobfm::_string_
FAILURE_ID_HASH: {5654bc57-9720-546c-de0e-76a002c66fe5}
Followup: MachineOwner
---------
3: kd> lmvm nt
start end module name
fffff802`4f201000 fffff802`4f995000 nt (pdb symbols) c:\windows\symbol_cache\ntkrnlmp.pdb\3BAEE2762F6442089EF8B926DDC8DBA61\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Sun Mar 22 23:26:46 2015 (550F41A6)
CheckSum: 0072FF0F
ImageSize: 00794000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4