i3 540 ve GTX 1050 Sistem Mavi Ekran Sorunu

djdarkslav

Decapat
Katılım
26 Ocak 2019
Mesajlar
5
4+4 8 GB RAM, GTX 1050 ve i3 540 var. Bilgisayar mavi ekran veriyor, sebebi nedir?
 
Tarihe göre sırala Puana göre sırala
439640 dedi:
Senin i3 milattan kalma. Ondan veriyor.
Genişletmek için tıkla...

Ne güzel atmışsınız öyle... Sorunun kaynağı ekran kartıyla RAM. Dump okumadan bir şeyler söylemek çok kolay değil mi...

Bu arada geçen yıldan kalam bir konuyu hortlatmış bulunmaktasınız.

[CODE title="Dökümler"]
Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Enes3078\AppData\Local\Temp\7zO0F3BC948\012619-16036-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0300a000 PsLoadedModuleList = 0xfffff800`0324e670
Debug session time: Sat Jan 26 15:07:36.306 2019 (UTC + 3:00)
System Uptime: 0 days 0:04:06.789
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`03088fc0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`094c0150=000000000000003b
2: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff80003080ec5, Address of the instruction which caused the bugcheck
Arg3: fffff880094c0a10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2608

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 6565

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

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

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

Key : WER.OS.Branch
Value: win7sp1_gdr

Key : WER.OS.Timestamp
Value: 2012-08-30T03:33:00Z

Key : WER.OS.Version
Value: 7.1.7601.17944


BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80003080ec5

BUGCHECK_P3: fffff880094c0a10

BUGCHECK_P4: 0

CONTEXT: fffff880094c0a10 -- (.cxr 0xfffff880094c0a10)
rax=000000001c520003 rbx=0000000000000000 rcx=fffffa8006b415b0
rdx=fa8000820d400001 rsi=ffffffffffffffff rdi=0000000000000036
rip=fffff80003080ec5 rsp=fffff880094c13f0 rbp=fffff880094c1440
r8=fa8000820d400000 r9=0000000005556020 r10=fffffa8006b415b0
r11=0000007ffffffff8 r12=fffff6fcc00dc4b0 r13=0000000000000000
r14=0000000000001000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!ExpInterlockedPopEntrySListFault16:
fffff800`03080ec5 498b08 mov rcx,qword ptr [r8] ds:002b:fa800082`0d400000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: OriginSetup.ex

STACK_TEXT:
fffff880`094c13f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16


SYMBOL_NAME: nt!ExpInterlockedPopEntrySListFault16+0

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 6.1.7601.17944

STACK_COMMAND: .cxr 0xfffff880094c0a10 ; kb

FAILURE_BUCKET_ID: 0x3B_c0000005_nt!ExpInterlockedPopEntrySListFault16+0

OS_VERSION: 7.1.7601.17944

BUILDLAB_STR: win7sp1_gdr

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

FAILURE_ID_HASH: {7c071dcb-e023-550b-4ce4-4e6ed91b9026}

Followup: MachineOwner
---------


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


Loading Dump File [C:\Users\Enes3078\AppData\Local\Temp\7zO0F33FD48\012419-30732-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0301c000 PsLoadedModuleList = 0xfffff800`03260670
Debug session time: Thu Jan 24 19:57:52.976 2019 (UTC + 3:00)
System Uptime: 0 days 3:16:04.146
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`0309afc0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff880`08355950=000000000000001a
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000003452, The subtype of the bugcheck.
Arg2: 00000000927d6000
Arg3: fffff700015b4480
Arg4: fff00000a3d778f6

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2921

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 23301

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

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

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

Key : WER.OS.Branch
Value: win7sp1_gdr

Key : WER.OS.Timestamp
Value: 2012-08-30T03:33:00Z

Key : WER.OS.Version
Value: 7.1.7601.17944


BUGCHECK_CODE: 1a

BUGCHECK_P1: 3452

BUGCHECK_P2: 927d6000

BUGCHECK_P3: fffff700015b4480

BUGCHECK_P4: fff00000a3d778f6

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: FIFA19.exe

STACK_TEXT:
fffff880`08355948 fffff800`03106c33 : 00000000`0000001a 00000000`00003452 00000000`927d6000 fffff700`015b4480 : nt!KeBugCheckEx
fffff880`08355950 fffff800`0306bc9e : fffffa80`06660060 fffffa80`00000001 fffff8a0`00080104 fffff880`000121ae : nt! ?? ::FNODOBFM::`string'+0x35133
fffff880`08356200 fffff800`0336c65a : fffff8a0`0acfb840 fffff880`08356540 00000000`00000000 fffffa80`08768b50 : nt!MmCleanProcessAddressSpace+0x96
fffff880`08356250 fffff800`0334fb7d : 00000000`c0000005 00000000`00000001 000007ff`fffde000 fffffa80`06f40b50 : nt!PspExitThread+0x56a
fffff880`08356350 fffff800`0308db3a : fffff880`08350000 fffff800`0309e08f fffff880`009ee180 fffffa80`06792060 : nt!PsExitSpecialApc+0x1d
fffff880`08356380 fffff800`0308de80 : 00000000`0012f9a8 fffff880`08356400 fffff800`0334faf0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`08356400 fffff800`0309a2f7 : fffffa80`08768b50 00000000`00000000 00000000`00000020 ffffffff`cc690083 : nt!KiInitiateUserApc+0x70
fffff880`08356540 00000000`77661206 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0012f820 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77661206


SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+35133

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 6.1.7601.17944

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x1a_3452_nt!_??_::FNODOBFM::_string_+35133

OS_VERSION: 7.1.7601.17944

BUILDLAB_STR: win7sp1_gdr

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

FAILURE_ID_HASH: {75b29266-f5a2-e998-9ba5-e896abbbd656}

Followup: MachineOwner
---------


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


Loading Dump File [C:\Users\Enes3078\AppData\Local\Temp\7zO0F3B9148\011919-14664-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03012000 PsLoadedModuleList = 0xfffff800`03256670
Debug session time: Sat Jan 19 17:44:59.111 2019 (UTC + 3:00)
System Uptime: 0 days 0:04:05.266
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`03090fc0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`08b2a820=000000000000003b
1: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff9600014f4e1, Address of the instruction which caused the bugcheck
Arg3: fffff88008b2b0e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2906

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 7755

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

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

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

Key : WER.OS.Branch
Value: win7sp1_gdr

Key : WER.OS.Timestamp
Value: 2012-08-30T03:33:00Z

Key : WER.OS.Version
Value: 7.1.7601.17944


BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff9600014f4e1

BUGCHECK_P3: fffff88008b2b0e0

BUGCHECK_P4: 0

CONTEXT: fffff88008b2b0e0 -- (.cxr 0xfffff88008b2b0e0)
rax=0000000000000000 rbx=fffff900c0156b60 rcx=fffff900c0156ea0
rdx=fffff900c0815920 rsi=fffff900c0156ea0 rdi=02008ffffff900c0
rip=fffff9600014f4e1 rsp=fffff88008b2bac0 rbp=000000000000000a
r8=000000000000000a r9=0000000000000000 r10=fffff96000135d8c
r11=fffff80003090228 r12=0000000000000000 r13=000000000000000a
r14=0000000000000001 r15=0000000141964240
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
win32k!InternalBuildHwndList+0x39:
fffff960`0014f4e1 488b07 mov rax,qword ptr [rdi] ds:002b:02008fff`fff900c0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: PES2019.exe

STACK_TEXT:
fffff880`08b2bac0 fffff960`0014f3aa : 00000000`00000000 fffff900`c0815920 00000000`00000000 fffff880`08b2bd60 : win32k!InternalBuildHwndList+0x39
fffff880`08b2baf0 fffff960`00135f29 : 00000000`00000000 fffff880`08b2bca0 00000000`00000000 fffff880`08b2bd60 : win32k!BuildHwndList+0x76
fffff880`08b2bb20 fffff800`03090253 : fffffa80`05627060 00000000`00000000 00000000`026df758 fffff880`08b2bbc8 : win32k!NtUserBuildHwndList+0x19d
fffff880`08b2bbb0 00000000`77125c7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`026df738 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77125c7a


SYMBOL_NAME: win32k!InternalBuildHwndList+39

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

IMAGE_VERSION: 6.1.7601.17904

STACK_COMMAND: .cxr 0xfffff88008b2b0e0 ; kb

FAILURE_BUCKET_ID: 0x3B_c0000005_win32k!InternalBuildHwndList+39

OS_VERSION: 7.1.7601.17944

BUILDLAB_STR: win7sp1_gdr

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

FAILURE_ID_HASH: {a6b2998f-281d-946b-3be3-a74e51360599}

Followup: MachineOwner
---------


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


Loading Dump File [C:\Users\Enes3078\AppData\Local\Temp\7zO0F3EA2CB\011919-17472-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03068000 PsLoadedModuleList = 0xfffff800`032ac670
Debug session time: Sat Jan 19 17:23:15.744 2019 (UTC + 3:00)
System Uptime: 0 days 3:46:12.274
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`030e6fc0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff880`07df7ac0=0000000000000050
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: 00000000f2e5d000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: 000000006ae72cce, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000008, (reserved)

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


Could not read faulting driver name

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3030

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 7533

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

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

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

Key : WER.OS.Branch
Value: win7sp1_gdr

Key : WER.OS.Timestamp
Value: 2012-08-30T03:33:00Z

Key : WER.OS.Version
Value: 7.1.7601.17944


BUGCHECK_CODE: 50

BUGCHECK_P1: f2e5d000

BUGCHECK_P2: 0

BUGCHECK_P3: 6ae72cce

BUGCHECK_P4: 8

READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800033162e0
GetUlongPtrFromAddress: unable to read from fffff80003316490
00000000f2e5d000

MM_INTERNAL_CODE: 8

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csgo.exe

STACK_TEXT:
fffff880`07df7ab8 fffff800`0307712b : 00000000`00000050 00000000`f2e5d000 00000000`00000000 fffff880`07df7c20 : nt!KeBugCheckEx
fffff880`07df7ac0 fffff800`030e50ee : 00000000`00000000 00000000`f2e5d000 fffff880`07df7b01 00000000`f2e5d000 : nt! ?? ::FNODOBFM::`string'+0x45915
fffff880`07df7c20 00000000`6ae72cce : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`20e8fcd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6ae72cce


SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+45915

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 6.1.7601.17944

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x50_nt!_??_::FNODOBFM::_string_+45915

OS_VERSION: 7.1.7601.17944

BUILDLAB_STR: win7sp1_gdr

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

FAILURE_ID_HASH: {133c8565-226b-893a-ac87-5c2e73bdf839}

Followup: MachineOwner
---------


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


Loading Dump File [C:\Users\Enes3078\AppData\Local\Temp\7zO0F32B5CB\011919-17784-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0305d000 PsLoadedModuleList = 0xfffff800`032a1670
Debug session time: Sat Jan 19 10:16:28.284 2019 (UTC + 3:00)
System Uptime: 0 days 0:15:08.814
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`030dbfc0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`06424c30=000000000000001a
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff680001b92d8
Arg3: d9700001af6fe86f
Arg4: fffff680001b9255

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2593

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9770

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

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

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

Key : WER.OS.Branch
Value: win7sp1_gdr

Key : WER.OS.Timestamp
Value: 2012-08-30T03:33:00Z

Key : WER.OS.Version
Value: 7.1.7601.17944


BUGCHECK_CODE: 1a

BUGCHECK_P1: 403

BUGCHECK_P2: fffff680001b92d8

BUGCHECK_P3: d9700001af6fe86f

BUGCHECK_P4: fffff680001b9255

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csgo.exe

STACK_TEXT:
fffff880`06424c28 fffff800`0307f8e6 : 00000000`0000001a 00000000`00000403 fffff680`001b92d8 d9700001`af6fe86f : nt!KeBugCheckEx
fffff880`06424c30 fffff800`0310d1b7 : 00000000`00000000 fffff680`001b9478 fffffa80`05dfe630 fffff880`000dca70 : nt! ?? ::FNODOBFM::`string'+0x320ec
fffff880`06424de0 fffff800`030c881f : fffffa80`00000000 00000000`3728ffff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`06424fa0 fffff800`030db253 : ffffffff`ffffffff fffff8a0`0aa6a1d8 fffff8a0`0aa6a200 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`064250a0 fffff800`030d7810 : fffff880`043374b2 fffff8a0`0beb1780 fffffa80`05dfe630 fffffa80`05dabf00 : nt!KiSystemServiceCopyEnd+0x13
fffff880`06425238 fffff880`043374b2 : fffff8a0`0beb1780 fffffa80`05dfe630 fffffa80`05dabf00 fffff8a0`0aa6a1d0 : nt!KiServiceLinkage
fffff880`06425240 fffff880`04322b5a : 00000000`00000000 fffff8a0`0aa9b910 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`06425270 fffff880`0431d523 : fffffa80`08bd2c50 00000000`00000001 fffff8a0`0beb1780 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x112
fffff880`06425320 fffff880`04303ecc : fffff880`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`064253f0 fffff880`04245ccc : 00000000`00000000 fffff8a0`01bd3000 fffff8a0`01bd3000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`06425420 fffff880`0424565f : fffff8a0`01bd3000 fffff8a0`01bd4300 fffff8a0`00000000 00000000`00000799 : dxgkrnl!DXGDEVICE:estroyAllocations+0x248
fffff880`06425510 fffff880`0427374f : 00000000`00000000 fffff8a0`0a696ec0 fffff8a0`0acde980 fffff880`06425930 : dxgkrnl!DXGDEVICE:rocessTerminationList+0xa3
fffff880`06425560 fffff880`04272e7b : fffff8a0`0acde980 fffff8a0`0acde980 fffff880`064258c0 fffff880`064258f0 : dxgkrnl!DXGCONTEXT:resent+0x2cb
fffff880`06425880 fffff960`001e03a8 : fffffa80`06083750 00000000`fff09000 00000000`000007dc fffff8a0`01bd3000 : dxgkrnl!DxgkPresent+0x543
fffff880`06425bf0 fffff800`030db253 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!NtGdiDdDDIPresent+0x18
fffff880`06425c20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


SYMBOL_NAME: dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

IMAGE_VERSION: 6.1.7601.17514

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x1a_403_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

OS_VERSION: 7.1.7601.17944

BUILDLAB_STR: win7sp1_gdr

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

FAILURE_ID_HASH: {e094ff83-1733-7258-62b1-90818d070c98}

Followup: MachineOwner
---------

[/CODE]
 
Artı 0 Eksi
ram 2400mhz olmalı 1200 olmamlı parçadan sıkıntı baktır tamirciye sen
 
Artı 0 Eksi
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

  • Soru
i3 540 Sistem ''Recovery'' Mavi Ekran Hatası
Mesaj
0
Görüntüleme
1.166
GreenWhisper92
  • Soru
i3 4130 ve GTX 1050 sistemde mavi ekran ve ısınma
2
Mesaj
18
Görüntüleme
1.233
Recep Baltaş
  • Soru
i3 540 Sistemde mavi ekran hatası
Mesaj
2
Görüntüleme
356
Quantum9
S
  • Soru
Ryzen 5 1600 ve GTX 1050 Ti sistem mavi ekran sorunu
Mesaj
3
Görüntüleme
535
GerginGörünüşlüAdam
B
  • Soru
GT710 - i3 540 sistemde mavi ekran hatası
Mesaj
1
Görüntüleme
187
feelsbadman
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…