0 / 0 / 0
Регистрация: 15.05.2019
Сообщений: 1
|
|
1 | |
DRIVER_IRQL_NOT_LESS_OR_EQUAL15.05.2019, 16:05. Показов 648. Ответов 1
Метки нет (Все метки)
Подскажите на что ругается комп, поставили новую материнку проц, а он начал такое выдавать...
Кликните здесь для просмотра всего текста
icrosoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\051419-16255-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*%systemroot%\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.24408.amd64fre.win7sp1_ldr_escrow.190320-1700 Machine Name: Kernel base = 0xfffff800`0345a000 PsLoadedModuleList = 0xfffff800`03693c90 Debug session time: Tue May 14 17:07:48.814 2019 (UTC + 3:00) System Uptime: 0 days 6:04:51.548 Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {202, 2, 8, 202} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+448 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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 kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000202, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: 0000000000000202, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036f7100 0000000000000202 CURRENT_IRQL: 2 FAULTING_IP: +6236643566656138 00000000`00000202 ?? ??? PROCESS_NAME: System CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: fffff80000b9c260 -- (.trap 0xfffff80000b9c260) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffff8000343cd60 rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000 rip=0000000000000202 rsp=fffff80000b9c3f8 rbp=0000000000000002 r8=fffff8000343cd60 r9=00000000c2435528 r10=0000000000000000 r11=0000000000000002 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up di ng nz na po nc 00000000`00000202 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800034fbf69 to fffff800034edba0 FAILED_INSTRUCTION_ADDRESS: +6236643566656138 00000000`00000202 ?? ??? STACK_TEXT: fffff800`00b9c118 fffff800`034fbf69 : 00000000`0000000a 00000000`00000202 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx fffff800`00b9c120 fffff800`034f9d88 : 00000000`00000008 00000000`00000202 00000000`00000000 fffff800`0349a59d : nt!KiBugCheckDispatch+0x69 fffff800`00b9c260 00000000`00000202 : fffff800`0349a59d fffff800`0363e180 fffffa80`07126060 fffff800`00000002 : nt!KiPageFault+0x448 fffff800`00b9c3f8 fffff800`0349a59d : fffff800`0363e180 fffffa80`07126060 fffff800`00000002 00000000`0000000f : 0x202 fffff800`00b9c400 fffff800`0348ba07 : fffffa80`07126120 fffffa80`07126168 fffffa80`07126168 00000000`00000000 : nt!KiDeferredReadyThread+0x2fd fffff800`00b9c480 fffff800`0348ad3e : 00000032`f8613161 fffff800`00b9cb18 00000000`0015699f fffff800`03642168 : nt!KiProcessExpiredTimerList+0x1b7 fffff800`00b9caf0 fffff800`0348ab27 : 00000013`78f4dfc1 fffffa80`0015699f fffffa80`0add6470 00000000`0000009f : nt!KiTimerExpiration+0x1be fffff800`00b9cb90 fffff800`034f111a : fffff800`0363e180 fffff800`0364e1c0 00000000`00000002 fffff880`00000002 : nt!KiRetireDpcList+0x277 fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiPageFault+448 fffff800`034f9d88 440f20c0 mov rax,cr8 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiPageFault+448 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5c92eb27 FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+448 BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+448 Followup: MachineOwner
0
|
15.05.2019, 16:05 | |
Ответы с готовыми решениями:
1
DRIVER_IRQL_NOT_LESS_OR_EQUAL DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD. driver_irql_not_less_or_equal 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL |
4243 / 1742 / 248
Регистрация: 01.05.2013
Сообщений: 7,786
|
|
18.05.2019, 00:31 | 2 |
0
|
18.05.2019, 00:31 | |
18.05.2019, 00:31 | |
Помогаю со студенческими работами здесь
2
0x000000001 Driver_IRQL_NOT_LESS_OR_EQUAL BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL (Windows 8.1) DRIVER_IRQL_NOT_LESS_OR_EQUAL (bridge.sys) Driver_irql_not_less_or_equal - netio.sys Искать еще темы с ответами Или воспользуйтесь поиском по форуму: |