[Shanaedawn]

Managed to get a screenshot of a typical occurance of the issue with the task manager open:

[Advertisements]

Just had a bluescreen after a freeze up. Followed these instructions to access the contents of the dump file. They don't mean anything to me, but I thought they might be useful:

Microsoft ® Windows Debugger Version 6.3.9600.17029 AMD64
Copyright © 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.microsof...ownload/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsof...ownload/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`0160e000 PsLoadedModuleList = 0xfffff802`018d82d0
Debug session time: Sun Jun 15 19:00:51.203 2014 (UTC - 7:00)
System Uptime: 0 days 2:38:00.951
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols

Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff802016b3baf}

*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by : iaStorA.sys ( iaStorA+6710a )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff802016b3baf, address which referenced memory

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


WRITE_ADDRESS: unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 0000000000000000

CURRENT_IRQL:  2

FAULTING_IP:
nt!KeAcquireInStackQueuedSpinLock+2f
fffff802`016b3baf 488711          xchg    rdx,qword ptr [rcx]

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

DPC_STACK_BASE:  FFFFD001C07FBFB0

TRAP_FRAME:  ffffd001c07f45e0 -- (.trap 0xffffd001c07f45e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffd001c07f47e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802016b3baf rsp=ffffd001c07f4778 rbp=ffffd001c07f4960
 r8=ffffd001c07f47e0  r9=ffffd001c07f4720 r10=fffff80201d9d501
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeAcquireInStackQueuedSpinLock+0x2f:
fffff802`016b3baf 488711          xchg    rdx,qword ptr [rcx] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8020176dae9 to fffff80201761fa0

STACK_TEXT:  
ffffd001`c07f4498 fffff802`0176dae9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd001`c07f44a0 fffff802`0176c33a : 00000000`00000001 ffffd001`c07f47e0 ffffe001`49ebc000 ffffd001`c07f45e0 : nt!KiBugCheckDispatch+0x69
ffffd001`c07f45e0 fffff802`016b3baf : fffff800`186ce10a 00000000`00000000 ffffe001`494f4798 00000000`00000002 : nt!KiPageFault+0x23a
ffffd001`c07f4778 fffff800`186ce10a : 00000000`00000000 ffffe001`494f4798 00000000`00000002 ffffe001`494f4618 : nt!KeAcquireInStackQueuedSpinLock+0x2f
ffffd001`c07f4780 fffff800`1866d45e : ffffe001`49ebc0a8 ffffe001`494f4010 ffffd001`c07f4820 fffff800`186ce134 : iaStorA+0x6710a
ffffd001`c07f47b0 fffff800`18671d81 : ffffe001`494f4010 ffffe001`4899f180 00000000`00000004 fffff800`186f7000 : iaStorA+0x645e
ffffd001`c07f4810 fffff802`016681e0 : ffffd001`c07e2f00 ffffd001`c07f4b10 ffffe001`495837d8 fffff800`186d8e05 : iaStorA+0xad81
ffffd001`c07f4860 fffff802`016673fb : 00000000`00000001 00000000`00000001 ffffd001`c07e0180 fffff802`017e0f45 : nt!KiExecuteAllDpcs+0x1b0
ffffd001`c07f49b0 fffff802`01765aea : ffffd001`c07e0180 ffffd001`c07e0180 ffffd001`c07ec2c0 ffffe001`49feb880 : nt!KiRetireDpcList+0xdb
ffffd001`c07f4c60 00000000`00000000 : ffffd001`c07f5000 ffffd001`c07ef000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP:
iaStorA+6710a
fffff800`186ce10a 488b5c2430      mov     rbx,qword ptr [rsp+30h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  iaStorA+6710a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStorA

IMAGE_NAME:  iaStorA.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51fb0de8

FAILURE_BUCKET_ID:  AV_iaStorA+6710a

BUCKET_ID:  AV_iaStorA+6710a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_iastora+6710a

FAILURE_ID_HASH:  {f733faf2-d2a8-1b11-9fa3-afbe5930de67}

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

Sorry for the wall of information from the last few days, I just figured anything could help. Thanks again for your efforts on this. :-)

[Shanaedawn]

Just had a bluescreen after a freeze up. Followed these instructions to access the contents of the dump file. They don't mean anything to me, but I thought they might be useful:

Microsoft ® Windows Debugger Version 6.3.9600.17029 AMD64
Copyright © 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.microsof...ownload/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsof...ownload/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`0160e000 PsLoadedModuleList = 0xfffff802`018d82d0
Debug session time: Sun Jun 15 19:00:51.203 2014 (UTC - 7:00)
System Uptime: 0 days 2:38:00.951
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols

Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff802016b3baf}

*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by : iaStorA.sys ( iaStorA+6710a )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff802016b3baf, address which referenced memory

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


WRITE_ADDRESS: unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 0000000000000000

CURRENT_IRQL:  2

FAULTING_IP:
nt!KeAcquireInStackQueuedSpinLock+2f
fffff802`016b3baf 488711          xchg    rdx,qword ptr [rcx]

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

DPC_STACK_BASE:  FFFFD001C07FBFB0

TRAP_FRAME:  ffffd001c07f45e0 -- (.trap 0xffffd001c07f45e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffd001c07f47e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802016b3baf rsp=ffffd001c07f4778 rbp=ffffd001c07f4960
 r8=ffffd001c07f47e0  r9=ffffd001c07f4720 r10=fffff80201d9d501
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeAcquireInStackQueuedSpinLock+0x2f:
fffff802`016b3baf 488711          xchg    rdx,qword ptr [rcx] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8020176dae9 to fffff80201761fa0

STACK_TEXT:  
ffffd001`c07f4498 fffff802`0176dae9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd001`c07f44a0 fffff802`0176c33a : 00000000`00000001 ffffd001`c07f47e0 ffffe001`49ebc000 ffffd001`c07f45e0 : nt!KiBugCheckDispatch+0x69
ffffd001`c07f45e0 fffff802`016b3baf : fffff800`186ce10a 00000000`00000000 ffffe001`494f4798 00000000`00000002 : nt!KiPageFault+0x23a
ffffd001`c07f4778 fffff800`186ce10a : 00000000`00000000 ffffe001`494f4798 00000000`00000002 ffffe001`494f4618 : nt!KeAcquireInStackQueuedSpinLock+0x2f
ffffd001`c07f4780 fffff800`1866d45e : ffffe001`49ebc0a8 ffffe001`494f4010 ffffd001`c07f4820 fffff800`186ce134 : iaStorA+0x6710a
ffffd001`c07f47b0 fffff800`18671d81 : ffffe001`494f4010 ffffe001`4899f180 00000000`00000004 fffff800`186f7000 : iaStorA+0x645e
ffffd001`c07f4810 fffff802`016681e0 : ffffd001`c07e2f00 ffffd001`c07f4b10 ffffe001`495837d8 fffff800`186d8e05 : iaStorA+0xad81
ffffd001`c07f4860 fffff802`016673fb : 00000000`00000001 00000000`00000001 ffffd001`c07e0180 fffff802`017e0f45 : nt!KiExecuteAllDpcs+0x1b0
ffffd001`c07f49b0 fffff802`01765aea : ffffd001`c07e0180 ffffd001`c07e0180 ffffd001`c07ec2c0 ffffe001`49feb880 : nt!KiRetireDpcList+0xdb
ffffd001`c07f4c60 00000000`00000000 : ffffd001`c07f5000 ffffd001`c07ef000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP:
iaStorA+6710a
fffff800`186ce10a 488b5c2430      mov     rbx,qword ptr [rsp+30h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  iaStorA+6710a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStorA

IMAGE_NAME:  iaStorA.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51fb0de8

FAILURE_BUCKET_ID:  AV_iaStorA+6710a

BUCKET_ID:  AV_iaStorA+6710a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_iastora+6710a

FAILURE_ID_HASH:  {f733faf2-d2a8-1b11-9fa3-afbe5930de67}

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

Sorry for the wall of information from the last few days, I just figured anything could help. Thanks again for your efforts on this. :-)

[Naathim]

Hi

 

Please try to update the driver using this tool from Intel.

 

Minidump points to the faulting disk controller.

[Shanaedawn]

The only update that the Intel driver finder thingy found was an update for the graphics card on the computer. When I try to install the recommended driver, it returns an error saying:

 

The driver being installed is not validated for this computer. Please obtain the appropriate driver from the computer manufacturer.

Setup will exit.

 

The Lenovo website returns no newer drivers for any hardware.

[Brennan C.]

New bluescreen this morning; here's the dump information, I think it's pretty much the same:

 

Microsoft ® Windows Debugger Version 6.3.9600.17029 AMD64

Copyright © 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.microsof...ownload/symbols

Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsof...ownload/symbols

Executable search path is: 

Windows 8 Kernel Version 9600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035

Machine Name:

Kernel base = 0xfffff802`3bc84000 PsLoadedModuleList = 0xfffff802`3bf4e2d0

Debug session time: Mon Jun 16 11:18:37.320 2014 (UTC - 7:00)

System Uptime: 0 days 2:59:13.068

Loading Kernel Symbols

..............

 

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.

 

.................................................

................................................................

.......................

Loading User Symbols

 

Loading unloaded module list

..............

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck A, {0, 2, 1, fffff8023bd29baf}

 

*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys

Probably caused by : iaStorA.sys ( iaStorA+6710a )

 

Followup: MachineOwner

---------

 

1: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

IRQL_NOT_LESS_OR_EQUAL (a)

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 a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 0000000000000000, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000001, bitfield :

bit 0 : value 0 = read operation, 1 = write operation

bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

Arg4: fffff8023bd29baf, address which referenced memory

 

Debugging Details:

------------------

 

 

WRITE_ADDRESS: unable to get nt!MmNonPagedPoolStart

unable to get nt!MmSizeOfNonPagedPoolInBytes

 0000000000000000 

 

CURRENT_IRQL:  2

 

FAULTING_IP: 

nt!KeAcquireInStackQueuedSpinLock+2f

fffff802`3bd29baf 488711          xchg    rdx,qword ptr [rcx]

 

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

 

BUGCHECK_STR:  AV

 

PROCESS_NAME:  System

 

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

 

DPC_STACK_BASE:  FFFFD00164BFBFB0

 

TRAP_FRAME:  ffffd00164bf45e0 -- (.trap 0xffffd00164bf45e0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000

rdx=ffffd00164bf47e0 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8023bd29baf rsp=ffffd00164bf4778 rbp=ffffd00164bf4960

 r8=ffffd00164bf47e0  r9=ffffd00164bf4720 r10=fffff8023bc1a501

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei pl zr na po nc

nt!KeAcquireInStackQueuedSpinLock+0x2f:

fffff802`3bd29baf 488711          xchg    rdx,qword ptr [rcx] ds:00000000`00000000=????????????????

Resetting default scope

 

LAST_CONTROL_TRANSFER:  from fffff8023bde3ae9 to fffff8023bdd7fa0

 

STACK_TEXT:  

ffffd001`64bf4498 fffff802`3bde3ae9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx

ffffd001`64bf44a0 fffff802`3bde233a : 00000000`00000001 ffffd001`64bf47e0 ffffe001`3f2d7000 ffffd001`64bf45e0 : nt!KiBugCheckDispatch+0x69

ffffd001`64bf45e0 fffff802`3bd29baf : fffff801`2d54010a 00000000`00000000 ffffe001`3e9b4798 00000000`00000002 : nt!KiPageFault+0x23a

ffffd001`64bf4778 fffff801`2d54010a : 00000000`00000000 ffffe001`3e9b4798 00000000`00000002 ffffe001`3e9b4618 : nt!KeAcquireInStackQueuedSpinLock+0x2f

ffffd001`64bf4780 fffff801`2d4df45e : ffffe001`3f2d70a8 ffff914b`1fae3f0f ffffd001`64dd8180 ffffd001`64be0180 : iaStorA+0x6710a

ffffd001`64bf47b0 fffff801`2d4e3d81 : ffffe001`3e9b4010 ffffe001`3dd9f180 fffffff6`00000000 00000001`ffffffff : iaStorA+0x645e

ffffd001`64bf4810 fffff802`3bcde1e0 : ffffd001`64be2f00 ffffd001`64bf4b20 ffffe001`3e9d7a98 fffff801`2d54ae05 : iaStorA+0xad81

ffffd001`64bf4860 fffff802`3bcdd3fb : ffffe001`42b8b240 00000000`00000001 ffffd001`64be0180 fffff802`3be50f45 : nt!KiExecuteAllDpcs+0x1b0

ffffd001`64bf49b0 fffff802`3bddbaea : ffffd001`64be0180 ffffd001`64be0180 ffffd001`64bec2c0 ffffe001`47dec880 : nt!KiRetireDpcList+0xdb

ffffd001`64bf4c60 00000000`00000000 : ffffd001`64bf5000 ffffd001`64bef000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

 

 

STACK_COMMAND:  kb

 

FOLLOWUP_IP: 

iaStorA+6710a

fffff801`2d54010a 488b5c2430      mov     rbx,qword ptr [rsp+30h]

 

SYMBOL_STACK_INDEX:  4

 

SYMBOL_NAME:  iaStorA+6710a

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: iaStorA

 

IMAGE_NAME:  iaStorA.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP:  51fb0de8

 

FAILURE_BUCKET_ID:  AV_iaStorA+6710a

 

BUCKET_ID:  AV_iaStorA+6710a

 

ANALYSIS_SOURCE:  KM

 

FAILURE_ID_HASH_STRING:  km:av_iastora+6710a

 

FAILURE_ID_HASH:  {f733faf2-d2a8-1b11-9fa3-afbe5930de67}

 

Followup: MachineOwner

---------

[Shanaedawn]

A new bluescreen this evening, with a different error message. All I did was restart the system from the Start menu (nothing open) due to issues with the iTunes updater, and then it gave me the BSoD. Here's the crash dump:

 

Microsoft ® Windows Debugger Version 6.3.9600.17029 AMD64
Copyright © 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.microsof...ownload/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsof...ownload/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`49c7f000 PsLoadedModuleList = 0xfffff802`49f492d0
Debug session time: Tue Jun 17 21:22:05.962 2014 (UTC - 7:00)
System Uptime: 1 days 10:03:02.709
Loading Kernel Symbols
...............................................................
..............................

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.....................Page 1a353b not present in the dump file. Type ".hh dbgerr004" for details
...Page 109821 not present in the dump file. Type ".hh dbgerr004" for details
..........
......................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff7`03979018).  Type ".hh dbgerr001" for details
Loading unloaded module list
....................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fb40000030, ffffffffc000000e, 1e4726880, fffff68000006000}

Page 1a353b not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1ecfd )

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

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

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

Page 1a353b not present in the dump file. Type ".hh dbgerr004" for 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:  GoogleCrashHan

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80249e021ad to fffff80249dd2fa0

STACK_TEXT:  
ffffd000`2318d418 fffff802`49e021ad : 00000000`0000007a fffff6fb`40000030 ffffffff`c000000e 00000001`e4726880 : nt!KeBugCheckEx
ffffd000`2318d420 fffff802`49d075f8 : 00000000`00000002 ffffd000`2318d588 ffffe000`e4bf2dd8 ffffd000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1ecfd
ffffd000`2318d510 fffff802`49ce65f5 : ffffe000`e63ad080 ffffe000`e4bf2dd8 00000000`c0033333 ffffc001`00000000 : nt!MiIssueHardFault+0x184
ffffd000`2318d5d0 fffff802`49cf8448 : 01000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x3d5
ffffd000`2318d710 fffff802`49d27cb8 : 00000000`00000000 fffff6fb`40000030 00000000`00000000 80000001`2b081863 : nt!MiMakeSystemAddressValid+0x154
ffffd000`2318d7a0 fffff802`49d26fb7 : ffffe000`e63ad080 ffffe000`e4bf2900 ffffe000`e4bf2de8 00000000`00000003 : nt!MiQueryAddressState+0xa78
ffffd000`2318d8a0 fffff802`4a08258b : 00000000`00000003 ffffd000`2318db80 00000080`bb98bf40 ffffd000`00000000 : nt!MiQueryAddressSpan+0xe3
ffffd000`2318d910 fffff802`4a082106 : 00000080`bb00bf00 ffffe000`e3482dd8 ffffe000`e63ad080 00000000`00000000 : nt!MmQueryVirtualMemory+0x47f
ffffd000`2318da40 fffff802`49dde7b3 : 00000000`00000000 00000080`bb98dd20 00000000`c00019ff 00000000`00000194 : nt!NtQueryVirtualMemory+0x22
ffffd000`2318da90 00007ffd`9ad1adba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000080`bb98beb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`9ad1adba


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+1ecfd
fffff802`49e021ad cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+1ecfd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  53388e13

BUCKET_ID_FUNC_OFFSET:  1ecfd

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
---------
 

[Naathim]

Hi
 
Most of my research points me to faulting drivers, either related to some security software or graphic card ones.
 
Download Slimdrivers to your desktop.

• Install the app and on completion run.
  During the installation make sure that additional checkbox for installing My PC Backup is unchecked. This is an unwanted software!
   
• On the first page select Start Scan:
  
  
   
• Once it has completed please tell me if any suitable drivers were found for updating.

Cheers,

Naat

 

 

 

[Shanaedawn]

SlimDrivers found the following 9 updates:

Intel HD Grapics 4000 - Current 9/15/13, available 3/28/14
Intel Display Audio - Current 8/28/13, available 2/19/14
Intel 7 Series/C216 Chipset Family USB ... - Current 6/20/06, available 7/29/13
Intel HM76 Express Chipset LPC Controller - 1E59 - Current 6/20/06, available 7/23/13
Intel Management Engine Interface - Current 7/1/13, available 11/25/13
Intel 7 Series/C216 Chipset Family PCI Express... - Current 6/20/06, available 7/23/13
3rd Gen Core processor DRAM Controller - 0154 - Current 6/20/06, available 7/23/13
Intel 7 Series/C216 Chipset Family PCI Express... - Current 6/20/06, available 7/23/13
Intel 7 Series/C216 Chipset Familiy USB ... - Current 6/20/06, available 7/29/13

 

Should I be attempting to install all of these? The full names of some aren't available, they get cut off in the window, but it seems like there might be some conflicts. I won't take any action until you get back to us. Thank you for your help. :-)

Edited by Shanaedawn, 18 June 2014 - 09:39 AM.

[Naathim]

Hi

Sorry for a delay, back to normal life after a couple of free days so I should be present normally now.

 

Went once more through your logfiles... Did you run CCleaner recently?

 

Try to update the drivers one at a time, work with it for a while (watch carefully machine's behavior), then using SlimDrivers scan again and update the next one etc.

 

Also remember to create System Restore Point before every update (SlimDrivers should do it, but in the case it wouldn't... better be safe than sorry).

 

Cheers,

Naat

[Brennan C.]

Yeah, we run CCleaner fairly regularly. Once every few days or so. Starting updating drivers with Intel HD Graphics 4000, because it's at the top of the list, although this is one that the Intel updater thingy said was out of date but when I downloaded the driver, it said it wasn't compatable with my system. Sure enough, once it tried to install the driver I got the same error message. I don't have the time before work to try another one, I'll move on to the next one on the list when I get home. 

[Brennan C.]

Tried the next driver on the list: Intel 7 Series/C216 Chipset Family USB Enhanced Host Controller. No change to performance, and installing that one removed all but one other update from the list, so I tried installing the last one that was left: Intel Management Interface Engine. No freezes on that one yet, although we have gotten errors in Firefox that we weren't previously getting:

Warning: Unresponsive script
A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: <<usually a URL to a YouTube video>>

I'll let you know if anything else happens.

[Naathim]

Hi.
 
The unresponsive script error isn't connected with any driver updates. It means that your browser is a little stall (most probably because of limited resources).
 
If you are using CCleaner fairly regularly, my best advice would be to stop it.

 

Read below my canned for this kind of software:
 
Registry Cleaner/Optimizer advice and warning!

Looks like there's this kind of software installed on your machine. I really doubt it will speed up your machine's performance, but it will surely increase the risk to damage it. Without even the basic Registry knowledge, this type of application may bring more harm than good. There were cases when such software left PC's unstable and unbootable. Below you can find Microsoft statement and some wise people talking about Registry Cleaners and this kind of Windows tweaking:
Microsoft policy for the use of registry cleaners
Mike Russinovich (Microsoft)
Miekiemoes (Malwarebytes)
Macboatmaster (G2G)
In your own interest should be staying away from this kind of applications. My best advice is that they should be removed/uninstalled.

 

Now... CCleaner could mess something up...

 

All of possible driver updates were installed?

[Brennan C.]

Hmm, I never knew that CCleaner could be so problematic; my techie friends and I have been using it for years. Is it just the registry fixer that's an issue, or should the cleanup feature be avoided as well?

 

The initial scan yielded 9 results; clicking on the graphics card download button reduced the number to 7 (somehow)(and the graphics card driver never installed, as noted previously). Downloading the next available driver removed all other entries from the list. 

[Naathim]

Being honest I prefer TFC by OldTimer to clean unneeded temp files.
 
For the reasons stated previously, I strongly suggest to stop cleaning the registry with CC. If you wish to stay with it, that's your call. Just bare in mind what those people said
 
If not the drivers, my best shot would be RAM. Windows 8 has got built-in memtest.

 

Go to Control panel and in the search box type memory;

 

Select the related option and it will ask whether to it now or on next boot:

- select now and it will reboot and then conduct the check

 

[Brennan C.]

Windows memory diagnostic reported no errors.