Selamlar, Intel ekran kartı sürücünüzü DDU ile kaldırıp aşağıdaki sürücüyü kurmayı deneyin. DDU kullanım rehberi aşağıda yer almaktadır.
Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
www.technopat.net
[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff88000006ba0, The address that the exception occurred at
Arg3: fffff880033c6398, Exception Record Address
Arg4: fffff880033c5c00, Context Record Address
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for mountmgr.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: Wdf01000!_FX_DRIVER_GLOBALS ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: Wdf01000!_WDF_DRIVER_GLOBALS ***
*** ***
*************************************************************************
GetUlongPtrFromAddress: unable to read from fffff800036ab300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3046
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 3552
Key : Analysis.Init.CPU.mSec
Value: 1280
Key : Analysis.Init.Elapsed.mSec
Value: 12885
Key : Analysis.Memory.CommitPeak.Mb
Value: 61
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2019-02-20T18:00:00Z
Key : WER.OS.Version
Value: 7.1.7601.24384
FILE_IN_CAB: 021022-17066-01.dmp
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc000001d
BUGCHECK_P2: fffff88000006ba0
BUGCHECK_P3: fffff880033c6398
BUGCHECK_P4: fffff880033c5c00
EXCEPTION_RECORD: fffff880033c6398 -- (.exr 0xfffff880033c6398)
ExceptionAddress: fffff88000006ba0
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff880033c5c00 -- (.cxr 0xfffff880033c5c00)
rax=0000000000000000 rbx=fffffa800a096ac0 rcx=fffffa8007a50fc0
rdx=0000057ff5e59e58 rsi=fffffa800af9fe30 rdi=0000000000000000
rip=fffff88000006ba0 rsp=fffff880033c65d8 rbp=0000057ff5f697e8
r8=fffff78000000008 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=fffff8800456b3c8 r13=fffffa800a1c4688
r14=fffffa800a1a3200 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
fffff880`00006ba0 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
EXCEPTION_CODE_STR: c000001d
EXCEPTION_STR: 0xc000001d
FAILED_INSTRUCTION_ADDRESS:
+0
fffff880`00006ba0 ?? ???
STACK_TEXT:
fffff880`033c65d8 fffff880`04572693 : fffffa80`0a1a61a0 fffffa80`0a096ac0 0000057f`f5f697e8 00000000`00000000 : 0xfffff880`00006ba0
fffff880`033c65e0 fffff880`04572435 : fffffa80`0af9fd70 0000057f`f5060288 0000057f`f5060288 fffffa80`0a1c44e0 : cdrom!DeviceCleanupProtectedLocks+0x163
fffff880`033c66b0 fffff880`00ec685a : fffffa80`0a1a3190 0000057f`f5060288 fffffa80`0a1c44e0 fffff800`034afbd3 : cdrom!DeviceEvtFileClose+0x79
fffff880`033c6710 fffff880`00ec672e : fffff880`033c6800 00000000`00000000 fffffa80`0af9fd70 00000000`00000000 : Wdf01000+0x1185a
fffff880`033c6790 fffff880`00eb979a : 00000000`00000006 00000000`00000000 fffffa80`0a1c44e0 00000000`00000000 : Wdf01000+0x1172e
fffff880`033c67f0 fffff880`00eb9866 : fffffa80`0a1c44e0 00000000`00000001 fffffa80`0a1cde10 fffffa80`0a1cde10 : Wdf01000+0x479a
fffff880`033c6830 fffff800`0370076e : fffffa80`0b0b9a30 00000000`00000001 fffffa80`0a1c44e0 00000000`00000000 : Wdf01000+0x4866
fffff880`033c6870 fffff800`0344d5e4 : 00000000`00000000 00000000`00000000 fffffa80`06d32640 fffff800`0346e534 : nt!IopDeleteFile+0x11e
fffff880`033c6900 fffff880`00e916aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`033c6960 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mountmgr+0x126aa
SYMBOL_NAME: cdrom!DeviceCleanupProtectedLocks+163
MODULE_NAME: cdrom
IMAGE_NAME: cdrom.sys
IMAGE_VERSION: 6.1.7601.17514
STACK_COMMAND: .cxr 0xfffff880033c5c00 ; kb
FAILURE_BUCKET_ID: 0x7E_BAD_IP_cdrom!DeviceCleanupProtectedLocks+163
OS_VERSION: 7.1.7601.24384
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {905a6d78-e276-ea77-e556-049218bf7612}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a00d0ed6b0, The pool entry we were looking for within the page.
Arg3: fffff8a00d0ed730, The next pool entry.
Arg4: 000000000d080307, (reserved)
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
GetUlongPtrFromAddress: unable to read from fffff800036f3300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3718
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 18968
Key : Analysis.Init.CPU.mSec
Value: 1109
Key : Analysis.Init.Elapsed.mSec
Value: 6919
Key : Analysis.Memory.CommitPeak.Mb
Value: 62
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2019-02-20T18:00:00Z
Key : WER.OS.Version
Value: 7.1.7601.24384
FILE_IN_CAB: 012122-17284-01.dmp
BUGCHECK_CODE: 19
BUGCHECK_P1: 20
BUGCHECK_P2: fffff8a00d0ed6b0
BUGCHECK_P3: fffff8a00d0ed730
BUGCHECK_P4: d080307
POOL_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800036f32f0
GetUlongPtrFromAddress: unable to read from fffff800036f34a8
fffff8a00d0ed6b0 Paged pool
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: javaw.exe
STACK_TEXT:
fffff880`0ad797c8 fffff800`03631aea : 00000000`00000019 00000000`00000020 fffff8a0`0d0ed6b0 fffff8a0`0d0ed730 : nt!KeBugCheckEx
fffff880`0ad797d0 fffff880`0ff282fd : fffff8a0`0c0ceea0 00000000`00000000 fffff8a0`4b677844 00000000`00000799 : nt!ExFreePoolWithTag+0x18aa
fffff880`0ad79880 fffff8a0`0c0ceea0 : 00000000`00000000 fffff8a0`4b677844 00000000`00000799 00000000`00000001 : dxgkrnl+0x382fd
fffff880`0ad79888 00000000`00000000 : fffff8a0`4b677844 00000000`00000799 00000000`00000001 fffff8a0`0c0ceea0 : 0xfffff8a0`0c0ceea0
SYMBOL_NAME: dxgkrnl+382fd
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x19_20_dxgkrnl+382fd
OS_VERSION: 7.1.7601.24384
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {1eccba0e-0eb6-ef79-5e5e-1ed6e8f9480a}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880031de180, The PRCB address of the hung processor.
Arg4: 0000000000000003, The index of the hung processor.
Debugging Details:
------------------
GetUlongPtrFromAddress: unable to read from fffff800036ea300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4343
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 34846
Key : Analysis.Init.CPU.mSec
Value: 1077
Key : Analysis.Init.Elapsed.mSec
Value: 2324
Key : Analysis.Memory.CommitPeak.Mb
Value: 65
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2019-02-20T18:00:00Z
Key : WER.OS.Version
Value: 7.1.7601.24384
FILE_IN_CAB: 011922-23462-01.dmp
BUGCHECK_CODE: 101
BUGCHECK_P1: 31
BUGCHECK_P2: 0
BUGCHECK_P3: fffff880031de180
BUGCHECK_P4: 3
FAULTING_PROCESSOR: 3
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff800`00b9c8e8 fffff800`034f81ee : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`031de180 : nt!KeBugCheckEx
fffff800`00b9c8f0 fffff800`034c8f27 : 00000000`00000000 fffff800`00000003 00000000`00026160 fffffa80`09ed4d30 : nt! ?? ::FNODOBFM::`string'+0x4c6e
fffff800`00b9c980 fffff800`0340f8e9 : fffff800`03434360 fffff800`00b9cb30 fffff800`03434360 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00b9ca80 fffff800`034e1aef : fffff800`03631180 fffff800`00b9cb01 fffff800`03634b60 00000000`00000003 : hal!HalpHpetClockInterrupt+0x8d
fffff800`00b9cab0 fffff800`034e40f2 : fffff800`03631180 fffff800`036411c0 00000000`00000002 fffff880`00000002 : nt!KiInterruptDispatchNoLock+0xaf
fffff800`00b9cc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x32
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4c6e
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 6.1.7601.24384
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_IDLE_THREAD_nt!_??_::FNODOBFM::_string_+4c6e
OS_VERSION: 7.1.7601.24384
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {1c993d21-7ff2-42e9-69a6-dc57f2982d52}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff8000362a120, Address of the instruction which caused the BugCheck
Arg3: fffff8800be92bc0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
GetUlongPtrFromAddress: unable to read from fffff800036ee300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3593
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 9573
Key : Analysis.Init.CPU.mSec
Value: 999
Key : Analysis.Init.Elapsed.mSec
Value: 2026
Key : Analysis.Memory.CommitPeak.Mb
Value: 62
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2019-02-20T18:00:00Z
Key : WER.OS.Version
Value: 7.1.7601.24384
FILE_IN_CAB: 011922-22557-01.dmp
BUGCHECK_CODE: 3b
BUGCHECK_P1: c0000005
BUGCHECK_P2: fffff8000362a120
BUGCHECK_P3: fffff8800be92bc0
BUGCHECK_P4: 0
CONTEXT: fffff8800be92bc0 -- (.cxr 0xfffff8800be92bc0)
rax=fffff8a00d8ca780 rbx=0000000000000004 rcx=fffffa8006c90570
rdx=fa8029e63d3004c0 rsi=fffff8a00da55000 rdi=fffff8a00cdbc8d0
rip=fffff8000362a120 rsp=fffff8800be93590 rbp=0000000000000001
r8=fa8029e63d3004c0 r9=fffff8a00d00b9a0 r10=0000000000000000
r11=0000000000000000 r12=fffffa8006c90140 r13=0000000000000000
r14=0000000000000020 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!ExDeferredFreePool+0x100:
fffff800`0362a120 4c8b02 mov r8,qword ptr [rdx] ds:002b:fa8029e6`3d3004c0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: javaw.exe
STACK_TEXT:
fffff880`0be93590 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0x100
SYMBOL_NAME: nt!ExDeferredFreePool+100
IMAGE_NAME: Pool_Corruption
IMAGE_VERSION: 6.1.7601.24384
MODULE_NAME: Pool_Corruption
STACK_COMMAND: .cxr 0xfffff8800be92bc0 ; kb
FAILURE_BUCKET_ID: 0x3B_c0000005_nt!ExDeferredFreePool+100
OS_VERSION: 7.1.7601.24384
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {883c13f4-464a-8412-f98b-6542d18da495}
Followup: Pool_corruption
---------[/CODE]