阅读924 返回首页    go 微软 go windows


Win10笔记本电脑开机不正常,IRQL

问题详情:

        Dell Inspiron 5545笔记本,系统为Windows10专业版。每次开机的时候黑屏,不显示任何东西,过一段时间(半分钟左右)后电脑就会自动重启,重启之后一切正常。进入系统之后在C:\Windows\Minidump文件夹中能找到dump文件。文件中显示电脑出现的错误为IRQL_NOT_LESS_OR_EQUAL,看描述像是电脑驱动的问题,但是搞不清楚具体是哪里出了问题。

        该问题只在第一次开电脑的时候出现,自动重启之后,以及之后手动重启都正常,关机后再开机时又会像之前一样自动重启,如此往复。

        查了挺多资料不太理解问题原因以及解决方案,求内行人解答。

dump文件内容:

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

Loading Dump File [C:\Windows\Minidump\120816-10843-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
Machine Name:
Kernel base = 0xfffff803`40e78000 PsLoadedModuleList = 0xfffff803`4117d060
Debug session time: Thu Dec  8 18:10:40.354 2016 (UTC + 8:00)
System Uptime: 0 days 4:30:46.372
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffad0c00000306, 2, 0, fffff80340ed8468}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

2: kd> -+
       ^ Syntax error in '-+'
2: 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: ffffad0c00000306, 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: fffff80340ed8468, address which referenced memory

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  14393.447.amd64fre.rs1_release_inmarket.161102-0100

SYSTEM_MANUFACTURER:  Dell Inc.

SYSTEM_PRODUCT_NAME:  Inspiron 5545

SYSTEM_SKU:  Inspiron 5545

SYSTEM_VERSION:  A04

BIOS_VENDOR:  Dell Inc.

BIOS_VERSION:  A04

BIOS_DATE:  08/18/2016

BASEBOARD_MANUFACTURER:  Dell Inc.

BASEBOARD_PRODUCT:  016HP6

BASEBOARD_VERSION:  A00

DUMP_TYPE:  2

BUGCHECK_P1: ffffad0c00000306

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80340ed8468

READ_ADDRESS: fffff8034121f338: Unable to get MiVisibleState
 ffffad0c00000306 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!IopCompleteRequest+b28
fffff803`40ed8468 488b09          mov     rcx,qword ptr [rcx]

CPU_COUNT: 4

CPU_MHZ: 705

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 30

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  AV

PROCESS_NAME:  System

ANALYSIS_SESSION_HOST:  BOHOUZHANG

ANALYSIS_SESSION_TIME:  12-08-2016 18:14:20.0855

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

IRP_ADDRESS: ffffffffffffff88

TRAP_FRAME:  ffff97805a577560 -- (.trap 0xffff97805a577560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffad0c00000306 rbx=0000000000000000 rcx=ffffad0c00000306
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80340ed8468 rsp=ffff97805a5776f0 rbp=ffff97805a577830
 r8=0000000000000002  r9=fffff80340e78000 r10=ffff9780579c0ca0
r11=ffff8783b1ae78c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe nc
nt!IopCompleteRequest+0xb28:
fffff803`40ed8468 488b09          mov     rcx,qword ptr [rcx] ds:ffffad0c`00000306=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80340fcd629 to fffff80340fc2510

STACK_TEXT:  
ffff9780`5a577418 fffff803`40fcd629 : 00000000`0000000a ffffad0c`00000306 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff9780`5a577420 fffff803`40fcbc07 : 00000000`00000000 fffff803`40f164c4 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff9780`5a577560 fffff803`40ed8468 : ffff8783`b1ae78c0 00000000`00000000 00000000`00000000 fffff803`00000008 : nt!KiPageFault+0x247
ffff9780`5a5776f0 fffff803`40f07a44 : 00000000`00000000 fffff803`410c434b ffff8783`ae239100 00000000`00000000 : nt!IopCompleteRequest+0xb28
ffff9780`5a5777e0 fffff803`40f078e1 : 00000000`00000000 ffffad0c`850058d0 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x134
ffff9780`5a577870 fffff803`40f357af : ffff8783`b2fa1f30 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KiCheckForKernelApcDelivery+0x21
ffff9780`5a5778a0 fffff803`40f32806 : ffff8783`b2fa1f30 00000000`00000005 00000000`00000001 00000000`0000000e : nt!KiLeaveGuardedRegionUnsafe+0x2f
ffff9780`5a5778d0 fffff803`40e90a54 : ffff8783`b32e0040 fffff803`40f3b4e0 00000000`00000000 00000000`00000005 : nt!MmWaitForCacheManagerPrefetch+0x6a
ffff9780`5a577900 fffff803`40f3b72b : fffff803`00000000 00000000`00000000 fffff803`41198f20 fffff803`41198f10 : nt!CcPerformReadAhead+0x2d4
ffff9780`5a577aa0 fffff803`40f0efd9 : fffff803`41235100 ffff8783`b32e0040 ffff8783`ae276a60 fffff80f`70e04380 : nt!CcWorkerThread+0x24b
ffff9780`5a577b80 fffff803`40e7a729 : 00000000`00000000 00000000`00000080 ffff8783`ae2753c0 ffff8783`b32e0040 : nt!ExpWorkerThread+0xe9
ffff9780`5a577c10 fffff803`40fc79d6 : ffff9780`57d40180 ffff8783`b32e0040 fffff803`40e7a6e8 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffff9780`5a577c60 00000000`00000000 : ffff9780`5a578000 ffff9780`5a572000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80340ecd25a-fffff80340ecd25b  2 bytes - nt!MmSetAddressRangeModified+20a
[ 80 fa:00 ee ]
    fffff80340f16d8d-fffff80340f16d8e  2 bytes - nt!MiRemoveLockedPageChargeAndDecRef+8d (+0x49b33)
[ 80 f6:00 fd ]
    fffff803410c4387-fffff803410c4389  3 bytes - nt!ExFreePoolWithTag+387
[ 40 fb f6:80 7e fd ]
7 errors : !nt (fffff80340ecd25a-fffff803410c4389)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE

TARGET_TIME:  2016-12-08T10:10:40.000Z

OSBUILD:  14393

OSSERVICEPACK:  447

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-11-02 18:17:03

BUILDDATESTAMP_STR:  161102-0100

BUILDLAB_STR:  rs1_release_inmarket

BUILDOSVER_STR:  10.0.14393.447.amd64fre.rs1_release_inmarket.161102-0100

ANALYSIS_SESSION_ELAPSED_TIME: 2942

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup:     memory_corruption
---------




您好,

上传的几次日志都表明是atikmdag.sys导致的,

atikmdag.sys一般是由于ATI或者NVIDIA显卡驱动与当前的系统不兼容导致的。

对应一下当前的的显卡驱动版本,查看品牌机或者显卡的官网是否有最新的显卡驱动下载安装,建议在官方网站下载驱动不要通过第三方的软件更新驱动,



最后更新:2017-06-25 14:01:57

  上一篇:go 禁用iwindows10应用商店
  下一篇:go 1、如何取消桌面窗口拖动时分屏虚线框(如图)2、如何关闭cortana自启动进程(WIN