求助,IRQL_NOT_LESS_OR_EQUAL导致蓝屏
看了下TMP文件内容如下,请大神们帮我分析下是由于什么导致的?(两次蓝屏文件)
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\072318-9453-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 17134 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`96a10000 PsLoadedModuleList = 0xfffff803`96dca1f0
Debug session time: Mon Jul 23 11:21:39.800 2018 (UTC + 8:00)
System Uptime: 1 days 1:08:48.971
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {8, 2, 0, fffff80396a6fd8e}
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
Followup: MachineOwner
---------
*** Memory manager detected 138461 instance(s) of page corruption, target is likely to have memory corruption.
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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80396a6fd8e, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
0000000000000008
CURRENT_IRQL: 2
FAULTING_IP:
nt!ExDeleteResourceLite+8e
fffff803`96a6fd8e 48395a08 cmp qword ptr [rdx+8],rbx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: crossproxy.exe
BAD_PAGES_DETECTED: 21cdd
LAST_CONTROL_TRANSFER: from fffff80396bb8f69 to fffff80396ba8430
STACK_TEXT:
fffff58b`c4f66688 fffff803`96bb8f69 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff58b`c4f66690 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
STACK_COMMAND: kb
SYMBOL_NAME: PAGE_NOT_ZERO
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: PAGE_NOT_ZERO
Followup: MachineOwner
---------
*** Memory manager detected 138461 instance(s) of page corruption, target is likely to have memory corruption.
================================================================================================================================================================================================
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\072518-8703-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 17134 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff802`cb015000 PsLoadedModuleList = 0xfffff802`cb3cf1f0
Debug session time: Wed Jul 25 08:48:43.720 2018 (UTC + 8:00)
System Uptime: 1 days 15:13:44.704
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {8, 2, 0, fffff802cb074d8e}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
*** Memory manager detected 107008 instance(s) of page corruption, target is likely to have memory corruption.
0: kd> !analyze _v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {8, 2, 0, fffff802cb074d8e}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
*** Memory manager detected 107008 instance(s) of page corruption, target is likely to have memory corruption.
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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff802cb074d8e, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
0000000000000008
CURRENT_IRQL: 2
FAULTING_IP:
nt!ExDeleteResourceLite+8e
fffff802`cb074d8e 48395a08 cmp qword ptr [rdx+8],rbx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0xA
PROCESS_NAME: TASLogin.exe
BAD_PAGES_DETECTED: 1a200
LAST_CONTROL_TRANSFER: from fffff802cb1bdf69 to fffff802cb1ad430
STACK_TEXT:
fffff589`a329e688 fffff802`cb1bdf69 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff589`a329e690 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
141 errors : !nt (fffff802cb07408a-fffff802cb1addff)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
Followup: memory_corruption
---------
*** Memory manager detected 107008 instance(s) of page corruption, target is likely to have memory corruption.
0: kd> lmvm memory_corruption
start end module name
0: kd> !process
PROCESS ffff8e0c6c574580
SessionId: none Cid: 4f08 Peb: 00386000 ParentCid: 1014
DirBase: 277600002 ObjectTable: ffffd10792efc500 HandleCount: <Data Not Accessible>
Image: TASLogin.exe
VadRoot ffff8e0c697a5e30 Vads 1 Clone 0 Private 4621. Modified 8157. Locked 0.
DeviceMap ffffd10782a65670
Token ffffd1078bac6780
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
ElapsedTime 00:00:00.000
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 0
QuotaPoolUsage[NonPagedPool] 0
Working Set Sizes (now,min,max) (0, 0, 0) (0KB, 0KB, 0KB)
PeakWorkingSetSize 0
VirtualSize 291 Mb
PeakVirtualSize 299 Mb
PageFaultCount 0
MemoryPrio