i5 4460 - GT730 Windows 11 kaldırır mı?

Anlaşılmacak bir şey yok hocam NVIDIA'dan indiriyorsanız başka bir site üzerinden indirin NVIDIA da hata alıyordum bende.

Başka sitelerden indirmek biraz güven ister ve bulmak cidden zor ve driver kurmak neden bu kadar zor bir iş...

Olmaz diye düşünüyorum.

Deneyebilirsin. 388.00 sürümü de var.

368.22 kuruluyor hocam eğer mavi ekran yersem silip 388 denerim herhangirbir hatadada yazarım hocam.
 
Anlaşılmacak bir şey yok hocam NVIDIA'dan indiriyorsanız başka bir site üzerinden indirin NVIDIA'da hata alıyordum bende.
Nvidia'nın sürücülerinde hata olacağını pek sanmıyorum. Arkadaş eski sürücüyü denesin bakalım.
 
NVIDIA'nın sürücülerinde hata olacağını pek sanmıyorum. Arkadaş eski sürücüyü denesin bakalım.

391'den sonra bu biraz garip geldi normal mi :D

NVIDIA'nın sürücülerinde hata olacağını pek sanmıyorum. Arkadaş eski sürücüyü denesin bakalım.

Dedim driver bu şu an deneyeceğim kurulmazsa sıkıntı olur mu?
 

Dosya Ekleri

  • resim_2024-10-26_224837261.png
    resim_2024-10-26_224837261.png
    227,9 KB · Görüntüleme: 24
  • resim_2024-10-26_224909348.png
    resim_2024-10-26_224909348.png
    22,9 KB · Görüntüleme: 23
391'den sonra bu biraz garip geldi normal mi :D



Dedim driver bu şu an deneyeceğim kurulmazsa sıkıntı olur mu?
Bu zaten daha sonraki driver. En günceli 391.35. Bunu indirmesen de bir şey olmaz diye tahmin ediyorum.
 
Bu zaten daha sonraki driver. En günceli 391.35. bunu indirmesen de bir şey olmaz diye tahmin ediyorum.

Zaten yüklenmiyor hocam şu an 368 kurulu eğer mavi ekran verirse silip 388 indireceğim oda mavi ekran yerse yazarım hocam.

Bu zaten daha sonraki driver. En günceli 391.35. bunu indirmesen de bir şey olmaz diye tahmin ediyorum.

Hocam yazdıktan sonra mavi ekran yedim :D DDU ile silip 388 deniyorum sizin attığınız.
 
Hocam yazdıktan sonra mavi ekran yedim :D DDU ile silip 388 deniyorum sizin attığınız.
Anlaşıldı. Muhtemelen sürücüden kaynaklanmıyor. minidump atabilir misin? Kartın kendisinde sorun olabilir.

@Marix Hocam doğru yönlendirdiğimi düşünüyorum. Sizce kartın kendisinde sorun olma ihtimali nedir? Ben ekran kartından kaynaklandığını düşünüyorum.
Kod:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.047 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

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


Loading Dump File [C:\Users\Hüseyin\AppData\Local\Temp\Rar$DIa8472.3291.rartemp\102624-6625-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 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff805`4f000000 PsLoadedModuleList = 0xfffff805`4fc2a7c0
Debug session time: Sat Oct 26 21:54:46.686 2024 (UTC + 3:00)
System Uptime: 0 days 2:02:57.358
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols

Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`4f3fe310 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffffe07`5e2b5890=0000000000000119
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffe075e2b5960
Arg4: ffffc68daee7d670

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

*** WARNING: Unable to verify timestamp for dxgmms2.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2015

    Key  : Analysis.Elapsed.mSec
    Value: 13308

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x119

    Key  : Bugcheck.Code.TargetModel
    Value: 0x119

    Key  : Failure.Bucket
    Value: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!unknown_function

    Key  : Failure.Hash
    Value: {a94318af-dd13-4d43-2ae8-8f2dd0117694}

    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: fffffe075e2b5960

BUGCHECK_P4: ffffc68daee7d670

FILE_IN_CAB:  102624-6625-01.dmp

FAULTING_THREAD:  ffffc68daedf0280

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
fffffe07`5e2b5888 fffff805`5b3c3ad0     : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffe07`5e2b5960 : nt!KeBugCheckEx
fffffe07`5e2b5890 fffff805`6c2c95e9     : ffffc68d`aee7a000 00000000`c000000d ffffc68d`aee5b620 ffffc68d`aee7a000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffe07`5e2b58d0 ffffc68d`aee7a000     : 00000000`c000000d ffffc68d`aee5b620 ffffc68d`aee7a000 00000000`00000000 : dxgmms2+0x95e9
fffffe07`5e2b58d8 00000000`c000000d     : ffffc68d`aee5b620 ffffc68d`aee7a000 00000000`00000000 00000000`00000000 : 0xffffc68d`aee7a000
fffffe07`5e2b58e0 ffffc68d`aee5b620     : ffffc68d`aee7a000 00000000`00000000 00000000`00000000 ffffc68d`aee7d670 : 0xc000000d
fffffe07`5e2b58e8 ffffc68d`aee7a000     : 00000000`00000000 00000000`00000000 ffffc68d`aee7d670 00000000`00000000 : 0xffffc68d`aee5b620
fffffe07`5e2b58f0 00000000`00000000     : 00000000`00000000 ffffc68d`aee7d670 00000000`00000000 fffff805`6c2ce5f0 : 0xffffc68d`aee7a000


SYMBOL_NAME:  dxgmms2+95e9

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

STACK_COMMAND:  .process /r /p 0xffffc68da4e7c040; .thread 0xffffc68daedf0280 ; kb

BUCKET_ID_FUNC_OFFSET:  95e9

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a94318af-dd13-4d43-2ae8-8f2dd0117694}

Followup:     MachineOwner
---------
 
Anlaşıldı. Muhtemelen sürücüden kaynaklanmıyor. minidump atabilir misin? Kartın kendisinde sorun olabilir.

@Marix Hocam doğru yönlendirdiğimi düşünüyorum. Sizce kartın kendisinde sorun olma ihtimali nedir? Ben ekran kartından kaynaklandığını düşünüyorum.
Kod:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.047 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

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


Loading Dump File [C:\Users\Hüseyin\AppData\Local\Temp\Rar$DIa8472.3291.rartemp\102624-6625-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 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff805`4f000000 PsLoadedModuleList = 0xfffff805`4fc2a7c0
Debug session time: Sat Oct 26 21:54:46.686 2024 (UTC + 3:00)
System Uptime: 0 days 2:02:57.358
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols

Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`4f3fe310 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffffe07`5e2b5890=0000000000000119
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffe075e2b5960
Arg4: ffffc68daee7d670

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

*** WARNING: Unable to verify timestamp for dxgmms2.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2015

    Key  : Analysis.Elapsed.mSec
    Value: 13308

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x119

    Key  : Bugcheck.Code.TargetModel
    Value: 0x119

    Key  : Failure.Bucket
    Value: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!unknown_function

    Key  : Failure.Hash
    Value: {a94318af-dd13-4d43-2ae8-8f2dd0117694}

    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: fffffe075e2b5960

BUGCHECK_P4: ffffc68daee7d670

FILE_IN_CAB:  102624-6625-01.dmp

FAULTING_THREAD:  ffffc68daedf0280

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffffe07`5e2b5888 fffff805`5b3c3ad0     : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffe07`5e2b5960 : nt!KeBugCheckEx
fffffe07`5e2b5890 fffff805`6c2c95e9     : ffffc68d`aee7a000 00000000`c000000d ffffc68d`aee5b620 ffffc68d`aee7a000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffe07`5e2b58d0 ffffc68d`aee7a000     : 00000000`c000000d ffffc68d`aee5b620 ffffc68d`aee7a000 00000000`00000000 : dxgmms2+0x95e9
fffffe07`5e2b58d8 00000000`c000000d     : ffffc68d`aee5b620 ffffc68d`aee7a000 00000000`00000000 00000000`00000000 : 0xffffc68d`aee7a000
fffffe07`5e2b58e0 ffffc68d`aee5b620     : ffffc68d`aee7a000 00000000`00000000 00000000`00000000 ffffc68d`aee7d670 : 0xc000000d
fffffe07`5e2b58e8 ffffc68d`aee7a000     : 00000000`00000000 00000000`00000000 ffffc68d`aee7d670 00000000`00000000 : 0xffffc68d`aee5b620
fffffe07`5e2b58f0 00000000`00000000     : 00000000`00000000 ffffc68d`aee7d670 00000000`00000000 fffff805`6c2ce5f0 : 0xffffc68d`aee7a000


SYMBOL_NAME:  dxgmms2+95e9

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

STACK_COMMAND:  .process /r /p 0xffffc68da4e7c040; .thread 0xffffc68daedf0280 ; kb

BUCKET_ID_FUNC_OFFSET:  95e9

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a94318af-dd13-4d43-2ae8-8f2dd0117694}

Followup:     MachineOwner
---------
mimdump hemen atıyorum umarım donanımsal değildir mimdump: mavi ekran gt730.rar
bide hocam 388 denimmi ?
 

Dosya Ekleri

  • resim_2024-10-26_230456800.png
    resim_2024-10-26_230456800.png
    85,7 KB · Görüntüleme: 23

Technopat Haberler

Geri
Yukarı