BSOD error 1000008e, 1000007e

Code:

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


Loading Dump File [E:\BSODDmpFiles\P911T\Windows_NT6_BSOD_jcgriff2\020912-16941-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x83605000 PsLoadedModuleList = 0x8374e4d0
Debug session time: Thu Feb  9 09:40:57.600 2012 (GMT-7)
System Uptime: 0 days 0:08:31.207
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 836a730a, 8f14bba4, 8f14b780}

Probably caused by : ntkrpamp.exe ( nt!ExpScanSystemLookasideList+106 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 836a730a, The address that the exception occurred at
Arg3: 8f14bba4, Exception Record Address
Arg4: 8f14b780, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExpScanSystemLookasideList+106
836a730a 8b5110          mov     edx,dword ptr [ecx+10h]

EXCEPTION_RECORD:  8f14bba4 -- (.exr 0xffffffff8f14bba4)
ExceptionAddress: 836a730a (nt!ExpScanSystemLookasideList+0x00000106)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 016ea660
Attempt to read from address 016ea660

CONTEXT:  8f14b780 -- (.cxr 0xffffffff8f14b780)
eax=807c66f8 ebx=00000004 ecx=016ea650 edx=00000096 esi=00000001 edi=807c6120
eip=836a730a esp=8f14bc6c ebp=8f14bc88 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!ExpScanSystemLookasideList+0x106:
836a730a 8b5110          mov     edx,dword ptr [ecx+10h] ds:0023:016ea660=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  016ea660

READ_ADDRESS: GetPointerFromAddress: unable to read from 8376e848
Unable to read MiSystemVaType memory at 8374de20
 016ea660 

FOLLOWUP_IP: 
nt!ExpScanSystemLookasideList+106
836a730a 8b5110          mov     edx,dword ptr [ecx+10h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 8367ded8 to 836a730a

STACK_TEXT:  
8f14bc88 8367ded8 00000000 8652fd48 00000000 nt!ExpScanSystemLookasideList+0x106
8f14bd50 8380dfda 00000000 a1f8857e 00000000 nt!KeBalanceSetManager+0x178
8f14bd90 836b61f9 8367dd60 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExpScanSystemLookasideList+106

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ea76eb4

STACK_COMMAND:  .cxr 0xffffffff8f14b780 ; kb

FAILURE_BUCKET_ID:  0x7E_nt!ExpScanSystemLookasideList+106

BUCKET_ID:  0x7E_nt!ExpScanSystemLookasideList+106

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

Possible causes are Memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases. Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

• If you are overclocking any hardware, please stop.
  
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
  
  
  
• Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
  
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. Run Driver Verifier
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.

Looks like the drive should be clean now. See how it runs and then proceed to the next step if necessary, as you said. :)

You're welcome. Glad it is running stable since disk errors were fixed.

Analyzed in https://www.sevenforums.com/crashes-d...ml#post1816218, and we should try to stick to that thread from now on.