5etleto

Здравейте. След заспиване на компа ми, при събуждане излиза син екран. Моля Ви за помощ. ............................ ******************************************************************************* * * * 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: fffff8a00b225410, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff880032acade, address which referenced memory Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034af100 GetUlongFromAddress: unable to read from fffff800034af1c8 fffff8a00b225410 Paged pool CURRENT_IRQL: 2 FAULTING_IP: klflt+1ade fffff880`032acade 48890a mov qword ptr [rdx],rcx CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: avp.exe TRAP_FRAME: fffff88006c0cf40 -- (.trap 0xfffff88006c0cf40) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800d9a33e0 rdx=fffff8a00b225410 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880032acade rsp=fffff88006c0d0d8 rbp=fffff88006c0d1b0 r8=fffffa800d9a3370 r9=00000000000000fd r10=0000000000000000 r11=fffff880032b5e20 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc klflt+0x1ade: fffff880`032acade 48890a mov qword ptr [rdx],rcx ds:fffff8a0`0b225410=0000000000000000 Resetting default scope LAST_CONTROL_TRANSFER: from fffff800032719e9 to fffff80003272440 STACK_TEXT: fffff880`06c0cdf8 fffff800`032719e9 : 00000000`0000000a fffff8a0`0b225410 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`06c0ce00 fffff800`03270660 : 00000000`00000000 00000980`00000000 0000007f`fffffff8 fffffa80`10c94802 : nt!KiBugCheckDispatch+0x69 fffff880`06c0cf40 fffff880`032acade : fffff880`032acbeb fffffa80`0d9a3370 fffffa80`10c94802 00000000`00000000 : nt!KiPageFault+0x260 fffff880`06c0d0d8 fffff880`032acbeb : fffffa80`0d9a3370 fffffa80`10c94802 00000000`00000000 fffff880`00e070cf : klflt+0x1ade fffff880`06c0d0e0 fffffa80`0d9a3370 : fffffa80`10c94802 00000000`00000000 fffff880`00e070cf 00000000`00000000 : klflt+0x1beb fffff880`06c0d0e8 fffffa80`10c94802 : 00000000`00000000 fffff880`00e070cf 00000000`00000000 fffff880`032b9e28 : 0xfffffa80`0d9a3370 fffff880`06c0d0f0 00000000`00000000 : fffff880`00e070cf 00000000`00000000 fffff880`032b9e28 00000000`00000000 : 0xfffffa80`10c94802 STACK_COMMAND: kb FOLLOWUP_IP: klflt+1ade fffff880`032acade 48890a mov qword ptr [rdx],rcx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: klflt+1ade FOLLOWUP_NAME: MachineOwner MODULE_NAME: klflt IMAGE_NAME: klflt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 52949624 FAILURE_BUCKET_ID: X64_0xD1_klflt+1ade BUCKET_ID: X64_0xD1_klflt+1ade Followup: MachineOwner --------- This free analysis is provided by OSR Open Systems Resources, Inc. Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window) Crash Code Links View the MSDN page for DRIVER_IRQL_NOT_LESS_OR_EQUAL Search Google for DRIVER_IRQL_NOT_LESS_OR_EQUAL Hide DivInformation About Address 0xfffff8a00b225410 Supplied dump is a mini-dump. Memory analysis commands unavailable. ................................. И това: .................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time (usually 10 minutes). Arguments: Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem. Arg2: 0000000000000258, Timeout in seconds. Arg3: fffffa800d782660, The thread currently holding on to the Pnp lock. Arg4: fffff80000b9a3d0, nt!TRIAGE_9F_PNP on Win7 Debugging Details: ------------------ Implicit thread is now fffffa80`0d782660 TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 DRVPOWERSTATE_SUBCODE: 4 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff800032db762 to fffff800032d8cca STACK_TEXT: fffff880`037ee0c0 fffff800`032db762 : fffffa80`0d782720 fffffa80`0d782660 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a fffff880`037ee200 fffff800`032ddf8f : fffffa80`0f10da20 fffff880`037ee418 fffff8a0`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2 fffff880`037ee290 fffff880`01d6fc0e : 00000000`00000000 00000000`00000000 fffff8a0`00e94f00 00000000`c0000500 : nt!KeWaitForSingleObject+0x19f fffff880`037ee330 fffff880`01d692cf : fffffa80`11523190 00000000`00000002 00000000`00000000 fffff880`01d2d101 : ndis! ?? ::LNCPHCLB::`string'+0x4f4b fffff880`037ee3c0 fffff880`01d4f552 : fffffa80`00000000 00000000`00000000 fffffa80`0d831c00 fffffa80`1144e060 : ndis!ndisPnPNotifyAllTransports+0x18f fffff880`037ee530 fffff880`01d4f520 : fffffa80`0d8389d0 fffffa80`113621a0 fffffa80`0d831c80 fffff880`037ee620 : ndis!NdisFNetPnPEvent+0xd2 fffff880`037ee570 fffff880`01d4f520 : fffffa80`0d831c80 fffffa80`113621a0 fffffa80`1054c520 fffff880`037ee620 : ndis!NdisFNetPnPEvent+0xa0 fffff880`037ee5b0 fffff880`01d1b508 : fffffa80`1054c520 00000000`00000000 fffffa80`113621a0 00000000`00000002 : ndis!NdisFNetPnPEvent+0xa0 fffff880`037ee5f0 fffff880`01d86d2a : 00000000`00000000 fffffa80`0d873c60 00000000`00000000 fffffa80`113621a0 : ndis! ndisDevicePnPEventNotifyFiltersAndAllTransports+0x128 fffff880`037ee6f0 fffff800`0353ee01 : fffffa80`0d98bbd0 fffffa80`11362050 fffff880`037ee848 fffffa80`1144e060 : ndis!ndisPnPDispatch+0x80b fffff880`037ee790 fffff800`036bd021 : fffffa80`1144e060 00000000`00000000 fffffa80`0da5ad90 fffff880`037ee828 : nt!IopSynchronousCall+0xe1 fffff880`037ee800 fffff800`036bb848 : fffffa80`1148f640 fffffa80`1144e060 00000000`0000030a 00000000`00000308 : nt!IopRemoveDevice+0x101 fffff880`037ee8c0 fffff800`036bcb67 : fffffa80`0da5ad90 00000000`00000000 00000000`00000003 00000000`00000086 : nt!PnpSurpriseRemoveLockedDeviceNode+0x128 fffff880`037ee900 fffff800`036bcc80 : 00000000`00000000 fffff8a0`033dcd00 fffff8a0`0e840410 fffff880`037eea58 : nt!PnpDeleteLockedDeviceNode+0x37 fffff880`037ee930 fffff800`0375a54f : 00000000`00000002 00000000`00000000 fffffa80`111ac010 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0 fffff880`037ee9a0 fffff800`0375b10c : fffff880`037eeb78 fffffa80`0dcd6000 fffffa80`0d782600 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0x6cf fffff880`037eeae0 fffff800`036442f6 : 00000000`00000000 fffffa80`0dcd60a0 fffff8a0`033c8b30 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c fffff880`037eeb10 fffff800`032e0839 : fffff800`0353dc68 fffff8a0`033dcde0 fffff800`034802d8 fffff800`034802d8 : nt! ?? ::NNGAKEGL::`string'+0x46e5b fffff880`037eeb70 fffff800`0357229a : 00000000`00000000 fffffa80`0d782660 00000000`00000080 fffffa80`0d76e720 : nt!ExpWorkerThread+0x111 fffff880`037eec00 fffff800`032c86e6 : fffff880`03572180 fffffa80`0d782660 fffff880`0357cfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`037eec40 00000000`00000000 : fffff880`037ef000 fffff880`037e9000 fffff880`037ee410 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: ndis! ?? ::LNCPHCLB::`string'+4f4b fffff880`01d6fc0e 8b5e28 mov ebx,dword ptr [rsi+28h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: ndis! ?? ::LNCPHCLB::`string'+4f4b FOLLOWUP_NAME: MachineOwner MODULE_NAME: ndis IMAGE_NAME: ndis.sys DEBUG_FLR_IMAGE_TIMESTAMP: 561c7ad7 FAILURE_BUCKET_ID: X64_0x9F_4_ndis!_??_::LNCPHCLB::_string_+4f4b BUCKET_ID: X64_0x9F_4_ndis!_??_::LNCPHCLB::_string_+4f4b Followup: MachineOwner ..... Това е системата ми Предварително благодаря.

Благодаря ти Night_Raven , драйверите ги имам, но не ги инсталирах защото и аз прочетох за Intel Management Interface Engine че е малко "опасен" за обикновен потребител и за това писах тук за съвет. Още веднъж голямо благодаря

Привет на всички. В device manager имам две жълти триъгълничетча с удивителни: Ethernet Controller и PCI Simple Communications Controller, няма инсталирани драйвери код 28. Трябва ли да инсталирам дрйвери, след като системата си работи и без тях? Интернета ми е мобилен USB modem stick, а домашната ми мрежа е с USB WiFi adapter.