Crunchez vos adresses URL
|
Rejoignez notre discord
|
Hébergez vos photos
Affichage des résultats 1 à 5 sur 5

Discussion: Bleu creen Windows

  1. #1
    Bonjour à tous,
    PC :
    Spoiler Alert!
    NVIDIA GeForce RTX 3070 - 8GB Ray Tracing Technology (VR Ready)

    Carte mère : ASRock Z490 Phantom Gaming 4 -- 2 PCIe 3.0 x16, 3 PCIe 3.0 x1,

    Alim : 650W Be Quiet! Straight Power 11 80+ Gold
    Processeur : Intel® Core™ i7-10700K Processor (8x 3.80 GHz /16MB L3 Cache)
    RAM : 16GB DDR4/3200MHz RGB Memory(G.SKILL ,Corsair, T-Force)


    Depuis son achat, il fait régulièrement des blues screen of death avec à chaque fois des erreurs différents. J'ai mis à jour tout ce que je pouvais (carte graphique, drivers de ma souris, de mon clavier) mais rien n'y fait. Du coup j'ai regardé les derniers minidump.

    Le dernier en date :
    Spoiler Alert!

    ************************************************** ****************************** *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    REFERENCE_BY_POINTER (18)
    Arguments:
    Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
    Arg2: ffff9489ef27ab40, Object whose reference count is being lowered
    Arg3: 0000000000000001, Reserved
    Arg4: 0000000000000001, Reserved
    The reference count of an object is illegal for the current state of the object.
    Each time a driver uses a pointer to an object the driver calls a kernel routine
    to increment the reference count of the object. When the driver is done with the
    pointer the driver calls another kernel routine to decrement the reference count.
    Drivers must match calls to the increment and decrement routines. This BugCheck
    can occur because an object's reference count goes to zero while there are still
    open handles to the object, in which case the fourth parameter indicates the number
    of opened handles. It may also occur when the object's reference count drops below zero
    whether or not there are open handles to the object, and in that case the fourth parameter
    contains the actual value of the pointer references count.

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 3000

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 6383

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

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

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

    Key : WER.OS.Branch
    Value: vb_release

    Key : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key : WER.OS.Version
    Value: 10.0.19041.1


    BUGCHECK_CODE: 18

    BUGCHECK_P1: 0

    BUGCHECK_P2: ffff9489ef27ab40

    BUGCHECK_P3: 1

    BUGCHECK_P4: 1

    BLACKBOXBSD: 1 (
    !blackboxbsd)


    BLACKBOXNTFS: 1 (
    !blackboxntfs)


    BLACKBOXPNP: 1 (
    !blackboxpnp)


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: chrome.exe

    STACK_TEXT:
    ffff938f`21d25a18 fffff800`0a216e66 : 00000000`00000018 00000000`00000000 ffff9489`ef27ab40 00000000`00000001 : nt!KeBugCheckEx
    ffff938f`21d25a20 fffff800`0a00827e : 00000000`00000000 00000000`00000000 00000000`00000001 ffff9489`ef27ab40 : nt!ObfDereferenceObjectWithTag+0x20ebd6
    ffff938f`21d25a60 fffff800`0a4e003a : 00000000`00000000 ffff938f`21d25b80 ffff938f`00000102 ffffd08c`569e31c0 : nt!HalPutDmaAdapter+0xe
    ffff938f`21d25a90 fffff800`0a2086b8 : ffffd08c`50761080 00000000`00000001 ffff938f`00000000 ffffd08c`00000000 : nt!NtSetEvent+0xda
    ffff938f`21d25b00 00007ffe`8228cfe4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
    000000a8`f1ffdf38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`8228cfe4


    SYMBOL_NAME: nt!ObfDereferenceObjectWithTag+20ebd6

    MODULE_NAME:
    nt

    IMAGE_NAME: ntkrnlmp.exe

    IMAGE_VERSION: 10.0.19041.964

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 20ebd6

    FAILURE_BUCKET_ID: 0x18_CORRUPT_REF_COUNT_nt!ObfDereferenceObjectWith Tag

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {fa6b3516-71cb-1e92-b987-b8bebd3458ac}

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


    Et la seule chose que je comprends, c'est que chrome merde. C'est également le cas de l'avant dernier minidump.

    Mais, le minidump du 24 avril (j'ai eu 5 crash depuis cette date avec une utilisation quotidienne) me dit également :

    Spoiler Alert!
    KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQ L (192)A lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or
    above.
    Arguments:
    Arg1: ffffb78f3aacd0c0, The address of the thread.
    Arg2: ffffb78f4b497310, The lock address.
    Arg3: 0000000000000000, The IRQL at which the lock was acquired.
    Arg4: 0000000000000000, Reserved.

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

    *** WARNING: Unable to verify checksum for win32kbase.sys

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 3624

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 11715

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

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

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

    Key : WER.OS.Branch
    Value: vb_release

    Key : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key : WER.OS.Version
    Value: 10.0.19041.1


    BUGCHECK_CODE: 192

    BUGCHECK_P1: ffffb78f3aacd0c0

    BUGCHECK_P2: ffffb78f4b497310

    BUGCHECK_P3: 0

    BUGCHECK_P4: 0

    BLACKBOXBSD: 1 (
    !blackboxbsd)


    BLACKBOXNTFS: 1 (
    !blackboxntfs)


    BLACKBOXPNP: 1 (
    !blackboxpnp)


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: steam.exe

    STACK_TEXT:
    ffffee87`5933a888 fffff807`6ca134f5 : 00000000`00000192 ffffb78f`3aacd0c0 ffffb78f`4b497310 00000000`00000000 : nt!KeBugCheckEx
    ffffee87`5933a890 fffff807`6cbfd2bb : 00000000`8000e00c ffffee87`5933ab80 00000000`00010000 ffffb78f`00000000 : nt!KeAbPreAcquire+0x1b3275
    ffffee87`5933a8e0 fffff807`6cbfcbf6 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x6ab
    ffffee87`5933aa20 fffff807`6ca077b8 : 00000000`0a93fda0 00000000`77b94660 00000000`0aa3f138 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
    ffffee87`5933aa90 00000000`77b91cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
    00000000`0a93ee58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b91cfc


    CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kbase
    ffffb35ab4631480-ffffb35ab4631493 20 bytes - win32kbase!xxxCreateThreadInfo+954
    [ 02 00 00 eb 08 4c 8b ac:48 8b 02 49 3b 00 77 09 ]
    ffffb35ab4631496-ffffb35ab46314a1 12 bytes - win32kbase!xxxCreateThreadInfo+96a (+0x16)
    [ 4c 8b f8 48 85 c0 75 0a:c3 cc cc cc cc cc cc cc ]
    ffffb35ab46314a3-ffffb35ab46314ad 11 bytes - win32kbase!xxxCreateThreadInfo+977 (+0x0d)
    [ e9 19 08 00 00 4c 89 bf:4c 8b d1 45 88 01 85 d2 ]
    ffffb35ab46314af-ffffb35ab46314dc 46 bytes - win32kbase!xxxCreateThreadInfo+983 (+0x0c)
    [ 0f 10 00 0f 11 84 24 e0:00 00 83 ea 01 74 7c 83 ]
    ffffb35ab46314de - win32kbase!xxxCreateThreadInfo+9b2 (+0x2f)
    [ 00:8d ]
    ffffb35ab46314e0-ffffb35ab46314f8 25 bytes - win32kbase!xxxCreateThreadInfo+9b4 (+0x02)
    [ 8b 05 02 f8 21 00 48 39:10 49 8d 14 0a 48 85 d2 ]
    ffffb35ab46314fa-ffffb35ab4631506 13 bytes - win32kbase!xxxCreateThreadInfo+9ce (+0x1a)
    [ eb 21 48 8b 87 a0 01 00:cc 83 fa 01 0f 85 14 2f ]
    ffffb35ab4631509-ffffb35ab463150e 6 bytes - win32kbase!xxxCreateThreadInfo+9dd (+0x0f)
    [ 41 89 8f ac 01 00:8d 4a 5b eb d3 b8 ]
    ffffb35ab4631510-ffffb35ab4631514 5 bytes - win32kbase!xxxCreateThreadInfo+9e4 (+0x07)
    [ 48 8b 87 a0 01:10 00 00 b9 64 ]
    ffffb35ab4631517-ffffb35ab463151a 4 bytes - win32kbase!xxxCreateThreadInfo+9eb (+0x07)
    [ 8b 80 74 03:00 eb c7 b8 ]
    ffffb35ab463151c-ffffb35ab4631521 6 bytes - win32kbase!xxxCreateThreadInfo+9f0 (+0x05)
    [ 00 41 89 87 b0 01:01 00 00 b9 60 00 ]
    ffffb35ab4631524-ffffb35ab4631528 5 bytes - win32kbase!xxxCreateThreadInfo+9f8 (+0x08)
    [ 8b 87 e0 01 00:eb bb b8 00 04 ]
    ffffb35ab463152a-ffffb35ab4631538 15 bytes - win32kbase!xxxCreateThreadInfo+9fe (+0x06)
    [ a8 0c 0f 85 d8 02 00 00:00 b9 54 00 00 00 eb af ]
    ffffb35ab463153a-ffffb35ab463153e 5 bytes - win32kbase!xxxCreateThreadInfo+a0e (+0x10)
    [ 0f 84 ca 02 00:00 00 eb a3 b8 ]
    ffffb35ab4631540-ffffb35ab4631545 6 bytes - win32kbase!xxxCreateThreadInfo+a14 (+0x06)
    [ 48 8b 05 c1 69 22:02 00 00 b9 68 00 ]
    ffffb35ab4631547-ffffb35ab463154b 5 bytes - win32kbase!xxxCreateThreadInfo+a1b (+0x07)
    [ 48 85 c0 74 0a:00 eb 97 cc cc ]
    ffffb35ab4631552-ffffb35ab4631572 33 bytes - win32kbase!xxxCreateThreadInfo+a26 (+0x0b)
    [ 8b f0 eb 03 41 8b f4 85:5c 24 18 48 89 74 24 20 ]
    ffffb35ab4631574-ffffb35ab4631577 4 bytes - win32kbase!xxxCreateThreadInfo+a48 (+0x22)
    [ 49 8d 55 28:00 48 33 c4 ]
    ffffb35ab4631579-ffffb35ab463157f 7 bytes - win32kbase!xxxCreateThreadInfo+a4d (+0x05)
    [ 8d 4c 24 48 48 89 4c:89 45 27 44 8b fa 89 ]
    ffffb35ab463cba0-ffffb35ab463cbf5 86 bytes - win32kbase!DC::bCompute+1f0 (+0xb627)
    [ 21 00 49 8b 7a 10 0f b7:48 83 ec 28 48 8b ca e8 ]
    ffffb35ab463cbf7-ffffb35ab463cbfe 8 bytes - win32kbase!DC::bCompute+247 (+0x57)
    [ 0f b6 c8 48 03 c9 48 8b:83 e8 01 0f 84 b2 ad 0a ]
    ffffb35ab463cc00-ffffb35ab463cc9f 160 bytes - win32kbase!DC::bCompute+250 (+0x09)
    [ 48 8b 04 d0 48 8b 4c c8:41 83 e8 01 0f 84 73 ad ]
    ffffb35ab463f480-ffffb35ab463f485 6 bytes - win32kbase!AllocateObject+60 (+0x2880)
    [ 0f 84 72 67 0b 00:48 83 ec 28 8b ca ]
    ffffb35ab463f48c-ffffb35ab463f4a6 27 bytes - win32kbase!AllocateObject+6c (+0x0c)
    [ 85 c0 0f 88 6e 67 0b 00:6d 61 e8 b1 e2 04 00 48 ]
    ffffb35ab463f4ad-ffffb35ab463f4d5 41 bytes - win32kbase!AllocateObject+8d (+0x21)
    [ 48 8b d8 48 85 db 0f 84:ec 30 44 8b c9 33 db 48 ]
    ffffb35ab463f4d7-ffffb35ab463f4e6 16 bytes - win32kbase!AllocateObject+b7 (+0x2a)
    [ 66 89 43 0e 48 8b c3 48:85 db 0f 88 aa 00 00 00 ]
    ffffb35ab463f4ea-ffffb35ab463f4fb 18 bytes - win32kbase!AllocateObject+ca (+0x13)
    [ 74 24 40 48 83 c4 20 5f:05 41 8e 23 00 48 3b 08 ]
    ffffb35ab463f4fd-ffffb35ab463f4fe 2 bytes - win32kbase!AllocateObject+dd (+0x13)
    [ 89 43:8d 4a ]
    ffffb35ab463f500-ffffb35ab463f57f 128 bytes - win32kbase!AllocateObject+e0 (+0x03)
    [ eb c8 c1 e2 18 8b cf 81:48 3b ca 72 0c 48 8b 05 ]
    721 errors : !win32kbase (ffffb35ab4631480-ffffb35ab463f57f)

    MODULE_NAME:
    memory_corruption

    IMAGE_NAME: memory_corruption

    MEMORY_CORRUPTOR: LARGE

    STACK_COMMAND: .thread ; .cxr ; kb

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
    Followup: memory_corruption


    Mais du coup, je ne sais pas du tout quoi faire à partir de là (et je ne comprends absolument à rien à l'analyse). Et le mot corruption ça fait peur.

  2. #2
    Un petit whocrashed pour voir.

    Et un memtest pour la RAM.
    La Zone symbolise l'étrangeté, lieu abandonné et sinistre, mais fascinant pour ce qu'il suppose d'inhumanité. (Frédérique ROUSSEL, Libération 3/06/2010)

  3. #3
    t'a 3 types de barretes differentes ? (tu marques Corsair, Gskill et Tforce)
    elles sont toujours a le meme frequence/CAS j'espere ? sinon boujour l'instabilité système qui doit jongler avec ca en permanence
    Dernière modification par Chico008 ; 09/05/2021 à 10h28.

  4. #4
    Alors petit crash ce matin, donc voilà pour whocrashed :

    On Sun 09/05/2021 13:40:46 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\050921-7750-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6CF0)
    Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8043D923039)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 09/05/2021 13:40:46 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8229)
    Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8043D923039)
    Error: IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Fri 07/05/2021 08:10:56 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\050721-5328-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6CF0)
    Bugcheck code: 0x18 (0x0, 0xFFFF9489EF27AB40, 0x1, 0x1)
    Error: REFERENCE_BY_POINTER
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 06/05/2021 08:38:58 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\050621-21296-01.dmp
    This was probably caused by the following module: fltmgr.sys (0xFFFFF80455030D80)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80455030D80, 0xFFFFFD09CD78DC60, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\drivers\fltmgr.sys
    product: Système d’exploitation Microsoft® Windows®
    company: Microsoft Corporation
    description: Gestionnaire de filtres de système de fichiers Microsoft
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



    On Wed 05/05/2021 12:15:45 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\050521-20984-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
    Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8011758A9F7)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Fri 30/04/2021 17:30:06 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\043021-13593-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
    Bugcheck code: 0xA (0x30, 0xD, 0x0, 0xFFFFF8076F528125)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    Alors, non j'ai deux barrettes de 8 Go RAM de la marque VIPER. Juste j'avais mis ma facture pour savoir exactement ce que j'avais acheté sans vérifier outre mesure.

    Pour le whocrashed, donc il semble que c'est principalement "ntoskrnl.exe". Internet ne m'aide pas trop...

  5. #5
    En fait mon bios n était pas à jour. On verra si ça résoudre le soucis.

    Et sinon avec un nouveau crash, whocrashed m'a pointé des drivers NVIDIA. Du coup, j'ai essayé de réinstaller des drivers en mode clean (directement depuis le site). A voir si ça marche, si ça ne marche pas, je désintallarais la carte graphique pour la réinstaller.
    Dernière modification par Molina ; 10/05/2021 à 11h19.

Règles de messages

  • Vous ne pouvez pas créer de nouvelles discussions
  • Vous ne pouvez pas envoyer des réponses
  • Vous ne pouvez pas envoyer des pièces jointes
  • Vous ne pouvez pas modifier vos messages
  •