Code:
-
Loading Dump File [F:\BSODDmpFiles\edeedbeebe\Windows_NT6_BSOD_jcgriff2\012412-29515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*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 = 0x82844000 PsLoadedModuleList = 0x8298d4d0
Debug session time: Tue Jan 24 14:11:01.044 2012 (GMT-7)
System Uptime: 0 days 0:07:21.699
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {8c62ec80, 2, 1, 828d1eda}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+258 )
Followup: MachineOwner
---------
0: 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: 8c62ec80, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 828d1eda, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829ad848
Unable to read MiSystemVaType memory at 8298ce20
8c62ec80
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiUnlinkPageFromLockedList+258
828d1eda 89441a04 mov dword ptr [edx+ebx+4],eax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: 8a743bb4 -- (.trap 0xffffffff8a743bb4)
ErrCode = 00000002
eax=ffffffff ebx=83a00000 ecx=ae06f629 edx=08c2ec7c esi=83ef6560 edi=8298ca94
eip=828d1eda esp=8a743c28 ebp=8a743c4c iopl=0 ov up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010a93
nt!MiUnlinkPageFromLockedList+0x258:
828d1eda 89441a04 mov dword ptr [edx+ebx+4],eax ds:0023:8c62ec80=cc8b4eea
Resetting default scope
LAST_CONTROL_TRANSFER: from 828d1eda to 828855fb
STACK_TEXT:
8a743bb4 828d1eda badb0d00 08c2ec7c 000001ff nt!KiTrap0E+0x2cf
8a743c4c 828b9600 00000000 84888430 868fb378 nt!MiUnlinkPageFromLockedList+0x258
8a743cec 828b9ab0 868fb378 00000000 84888430 nt!MiGatherMappedPages+0x777
8a743d50 82a4cfda 00000000 a1062977 00000000 nt!MiMappedPageWriter+0x13d
8a743d90 828f51f9 828b9973 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiUnlinkPageFromLockedList+258
828d1eda 89441a04 mov dword ptr [edx+ebx+4],eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiUnlinkPageFromLockedList+258
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4ea76eb4
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_nt!MiUnlinkPageFromLockedList+258
BUCKET_ID: 0xA_nt!MiUnlinkPageFromLockedList+258
Followup: MachineOwner
---------
-
Loading Dump File [F:\BSODDmpFiles\edeedbeebe\Windows_NT6_BSOD_jcgriff2\012312-12511-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16905.x86fre.win7_gdr.111025-1503
Machine Name:
Kernel base = 0x82853000 PsLoadedModuleList = 0x8299b810
Debug session time: Mon Jan 23 19:42:59.075 2012 (GMT-7)
System Uptime: 0 days 0:59:44.730
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {b80024, ff, 0, 828d8413}
Probably caused by : ntkrpamp.exe ( nt!PoIdle+17c )
Followup: MachineOwner
---------
0: 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: 00b80024, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000000, 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: 828d8413, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 829bb718
Unable to read MiSystemVaType memory at 8299b160
00b80024
CURRENT_IRQL: 2
FAULTING_IP:
nt!PoIdle+17c
828d8413 3b7004 cmp esi,dword ptr [eax+4]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: 82979c2c -- (.trap 0xffffffff82979c2c)
ErrCode = 00000000
eax=00b80020 ebx=000004ed ecx=00000000 edx=000184e5 esi=00000000 edi=8297cd20
eip=828d8413 esp=82979ca0 ebp=82979d20 iopl=0 nv up di pl nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010012
nt!PoIdle+0x17c:
828d8413 3b7004 cmp esi,dword ptr [eax+4] ds:0023:00b80024=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 828d8413 to 8289986b
STACK_TEXT:
82979c2c 828d8413 badb0d00 000184e5 8ea676e8 nt!KiTrap0E+0x2cf
82979d20 828bb14d 00000000 0000000e 00000000 nt!PoIdle+0x17c
82979d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!PoIdle+17c
828d8413 3b7004 cmp esi,dword ptr [eax+4]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!PoIdle+17c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ea76ed3
FAILURE_BUCKET_ID: 0xA_nt!PoIdle+17c
BUCKET_ID: 0xA_nt!PoIdle+17c
Followup: MachineOwner
---------
- Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Antivirus Software...
- Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Antivirus Software...
Thanks to Dave76 for help understanding possible causes.
What kind of memory diagnostic did you run? How long did it run?
We will start with the most likely, common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). 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 anything, please stop.
- Remove AVG at least for testing using its remover from AVG - Download tools and utilities and install AVG - Download tools and utilities in its place to run with Windows firewall.
- Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
- Update your Intel graphics driver:
Code:
igdkmd32 8ea28000 8ef25000 Wed May 06 12:13:40 2009 (4a01d354) 0048df97 igdkmd32.sys
Use the Intel® Driver Update Utility