Laptopun içini açtıktan sonra mavi ekran vermeye başladı

Minidump dosyasini paylasir misiniz?

MamiDigital dedi:

Fanı tamir etmek için laptopun içini açtım. Tamir ettim, geri kapattım ve laptopu açtıktan sonra mavi ekran vermeye başladı.

Genişletmek için tıkla...

Küçültmek için tıkla...

RAM'lerde sorun var muhtemelen.

Uyuyan Sincap dedi:

RAM'lerde sorun var muhtemelen.

Genişletmek için tıkla...

Küçültmek için tıkla...

RAM'lerle oynadiysa tabii...

Uyuyan Sincap dedi:

RAM'lerde sorun var muhtemelen.

Genişletmek için tıkla...

Küçültmek için tıkla...

Muhtemelen laptopun içini açarken kazara statik elektrik yüklemesine sebep olarak bazı bileşenleri bozdu yada geçici etki yarattı. Topraklamak lazım. Fişten çekip, bataryayı söküp bekletmek lazım.

MamiDigital dedi:

@tornatezgahi @adios

Yandex

Her şey bulunur

disk.yandex.com.tr

Genişletmek için tıkla...

Küçültmek için tıkla...

Minidump'lari inceledim, attiginiz dosyalarin cogu calismiyor, sadece ikisini calistirabildim. Ciktilari:
[CODE title="Minidump ciktisi"]*******************************************************************************

• *
• Bugcheck Analysis *
• *

*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80650b20227, The address that the exception occurred at
Arg3: fffffc09a9c46e88, Exception Record Address
Arg4: fffffc09a9c466c0, Context Record Address

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


KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullClassPtr

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 687

Key : Analysis.Elapsed.mSec
Value: 11225

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 10

Key : Analysis.Init.CPU.mSec
Value: 46

Key : Analysis.Init.Elapsed.mSec
Value: 2386

Key : Analysis.Memory.CommitPeak.Mb
Value: 91

Key : Bugcheck.Code.LegacyAPI
Value: 0x1000007e

Key : Bugcheck.Code.TargetModel
Value: 0x1000007e

Key : Failure.Bucket
Value: AV_nvlddmkm!unknown_function

Key : Failure.Hash
Value: {7eea5677-f68d-2154-717e-887e07e55cd3}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80650b20227

BUGCHECK_P3: fffffc09a9c46e88

BUGCHECK_P4: fffffc09a9c466c0

FILE_IN_CAB: 070424-36171-01.dmp

EXCEPTION_RECORD: fffffc09a9c46e88 -- (.exr 0xfffffc09a9c46e88)
ExceptionAddress: fffff80650b20227 (nvlddmkm+0x0000000000610227)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000058
Attempt to read from address 0000000000000058

CONTEXT: fffffc09a9c466c0 -- (.cxr 0xfffffc09a9c466c0)
rax=0000000000000000 rbx=ffff9c891b2aa000 rcx=0000000000000001
rdx=fffffc09a9c470d8 rsi=ffff9c891b2e4f68 rdi=0000000000000000
rip=fffff80650b20227 rsp=fffffc09a9c470c0 rbp=ffff9c891b2c4000
r8=0000000000000020 r9=0000000000000000 r10=0000000000000001
r11=0000000000000001 r12=ffff9c891b2b2000 r13=ffff9c891b2aa000
r14=0000000000000000 r15=ffff9c891b34dc98
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nvlddmkm+0x610227:
fffff806`50b20227 48837f5800 cmp qword ptr [rdi+58h],0 ds:002b:00000000`00000058=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff8062c8fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
0000000000000058

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000058

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
fffffc09`a9c470c0 ffff9c89`1b2aa000 : 00000000`00000000 ffff9c89`1b34dc98 00000000`00000020 00000000`00000000 : nvlddmkm+0x610227
fffffc09`a9c470c8 00000000`00000000 : ffff9c89`1b34dc98 00000000`00000020 00000000`00000000 ffff9c89`156465a0 : 0xffff9c89`1b2aa000


SYMBOL_NAME: nvlddmkm+610227

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr 0xfffffc09a9c466c0 ; kb

BUCKET_ID_FUNC_OFFSET: 610227

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup: MachineOwner
---------[/CODE]
Bu hata driverdan kaynaklanmakta. Driverinizin guncel oldugundan emin olun.
[CODE title="Minidump ciktisi 2"]*******************************************************************************

• *
• Bugcheck Analysis *
• *

*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffff8789ed79a860
Arg4: ffffdf0e8e377ad0

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 218

Key : Analysis.Elapsed.mSec
Value: 4200

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 108

Key : Analysis.Init.Elapsed.mSec
Value: 1955

Key : Analysis.Memory.CommitPeak.Mb
Value: 93

Key : Bugcheck.Code.LegacyAPI
Value: 0x119

Key : Bugcheck.Code.TargetModel
Value: 0x119

Key : Failure.Bucket
Value: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

Key : Failure.Hash
Value: {9a11bf9c-270e-962e-7a82-3efdab93c10e}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffff8789ed79a860

BUGCHECK_P4: ffffdf0e8e377ad0

FILE_IN_CAB: 070424-44578-01.dmp

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8789`ed79a788 fffff805`35b73ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff8789`ed79a860 : nt!KeBugCheckEx
ffff8789`ed79a790 fffff805`5f289629 : ffffdf0e`8e374000 00000000`c000000d ffff8789`ed79a899 00000000`00000009 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff8789`ed79a7d0 fffff805`5f3069cd : ffffdf0e`00000000 ffffdf0e`8e377ad0 ffffdf0e`8e34b000 ffffdf0e`8f86b550 : dxgmms2!VidSchiSendToExecutionQueue+0xa99
ffff8789`ed79a900 fffff805`5f30f5ba : ffffdf0e`8f86b550 ffffdf0e`8e34b000 00000000`00000000 ffffdf0e`8e34e8f0 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffff8789`ed79aa80 fffff805`5f30f42a : ffffdf0e`8e34b400 fffff805`5f30f360 ffffdf0e`8e34b000 ffff8b80`a3fe8100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffff8789`ed79aad0 fffff805`2974eb35 : ffffdf0e`8e342540 fffff805`00000001 ffffdf0e`8e34b000 000fa4ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff8789`ed79ab10 fffff805`29806af8 : ffff8b80`a3fe8180 ffffdf0e`8e342540 fffff805`2974eae0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8789`ed79ab60 00000000`00000000 : ffff8789`ed79b000 ffff8789`ed794000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+a99

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.4597

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: a99

FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}

Followup: MachineOwner
---------
[/CODE]
Bu hatanin sebebi genellikle ekran karti driver kaynakli, ancak arastirdigima gore donanimda da bozulma oldugunda bu hatayi veriyormus.

MamiDigital dedi:

Ne kadar beklemesi lazım.

Genişletmek için tıkla...

Küçültmek için tıkla...

5-10 Dakika. Bu esnada tozlarıda almak için hava basıncı uygulanabilir.