BSOD EN JEU | NEED HELP

Fermé
Yoyoboul Messages postés 2 Date d'inscription mercredi 21 novembre 2018 Statut Membre Dernière intervention 7 janvier 2019 - 7 janv. 2019 à 04:27
yoom81 Messages postés 3 Date d'inscription dimanche 6 janvier 2019 Statut Membre Dernière intervention 7 janvier 2019 - 7 janv. 2019 à 05:26
Bonjour, ma config est la suivante : Ryzen 5 2600, B350 Gaming PRO, GTX 1070, G skill 2x4 Go 2400MHz. Mon problème : j'ai des BSOD après quelques minutes de jeu sur fortnite : le programme who crashed indique juste :
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Mon 07/01/2019 03:03:42 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+0x7EA9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80705AB8875, 0xFFFFD004588DD0B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\010719-38890-01.dmp

Donc j'ai ouvert avec WINDB et j'ai ça :

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80705ab8875, Address of the instruction which caused the bugcheck
Arg3: ffffd004588dd0b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

KEY_VALUES_STRING: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7A39

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2.J0

BIOS_DATE: 11/06/2018

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: B350M GAMING PRO (MS-7A39)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 1

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80705ab8875

BUGCHECK_P3: ffffd004588dd0b0

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction 0x%p emploie l'adresse m moire 0x%p. L' tat de la m moire ne peut pas tre %s.

FAULTING_IP:
nt!EtwpReleaseProviderTraitsReference+11
fffff807`05ab8875 48875968 xchg rbx,qword ptr [rcx+68h]

CONTEXT: ffffd004588dd0b0 -- (.cxr 0xffffd004588dd0b0)
rax=0000000000000100 rbx=0000000000000000 rcx=99af1ea1d05b0000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80705ab8875 rsp=ffffd004588ddaa8 rbp=ffffd004588ddb50
r8=ffffbe054e0ec240 r9=0000000000000030 r10=00000001000000a3
r11=0000000000000000 r12=00000000009f8000 r13=00000000083cfda0
r14=00000000084cfa54 r15=0000000076f53640
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!EtwpReleaseProviderTraitsReference+0x11:
fffff807`05ab8875 48875968 xchg rbx,qword ptr [rcx+68h] ds:002b:99af1ea1`d05b0068=????????????????
Resetting default scope

CPU_COUNT: c

CPU_MHZ: f0a

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXPNP: 1 (!blackboxpnp)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: Discord.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-807GCD7

ANALYSIS_SESSION_TIME: 01-07-2019 03:27:06.0800

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

LAST_CONTROL_TRANSFER: from ffffd004588ddb50 to fffff80705ab8875

STACK_TEXT:
ffffd004`588ddaa8 ffffd004`588ddb50 : 00000000`084cfa54 00000000`00000000 00000000`00000060 00000000`00000040 : nt!EtwpReleaseProviderTraitsReference+0x11
ffffd004`588ddad8 00000000`084cfa54 : 00000000`00000000 00000000`00000060 00000000`00000040 fffff807`055cbd45 : 0xffffd004`588ddb50
ffffd004`588ddae0 00000000`00000000 : 00000000`00000060 00000000`00000040 fffff807`055cbd45 ffffbe05`4d488080 : 0x84cfa54

THREAD_SHA1_HASH_MOD_FUNC: bb057953032ae7e004a5c3daeef4665bff80d22b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ef5ab556c210e636b4aad7ad5d57ea04ee38b81a

THREAD_SHA1_HASH_MOD: 76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

FOLLOWUP_IP:
nt!EtwpReleaseProviderTraitsReference+11
fffff807`05ab8875 48875968 xchg rbx,qword ptr [rcx+68h]

FAULT_INSTR_CODE: 68598748

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!EtwpReleaseProviderTraitsReference+11

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xffffd004588dd0b0 ; kb

BUCKET_ID_FUNC_OFFSET: 11

FAILURE_BUCKET_ID: 0x3B_nt!EtwpReleaseProviderTraitsReference

BUCKET_ID: 0x3B_nt!EtwpReleaseProviderTraitsReference

PRIMARY_PROBLEM_CLASS: 0x3B_nt!EtwpReleaseProviderTraitsReference

TARGET_TIME: 2019-01-07T02:03:42.000Z

OSBUILD: 17763

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 5db

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_nt!etwpreleaseprovidertraitsreference

FAILURE_ID_HASH: {12c9e3ae-2f01-cef5-57a5-507cef26078a}

J'ai vu que ca pouvait avoir un rapport avec la mémoire virtuelle mais je ne sais pas quoi faire, si quelqu'un à une solution, je suis preneur, mercii :)
A voir également:

1 réponse

yoom81 Messages postés 3 Date d'inscription dimanche 6 janvier 2019 Statut Membre Dernière intervention 7 janvier 2019
7 janv. 2019 à 05:26
salut,
j'ai posté hier aussi pour un probleme de crash, pareil que toi whocrashed ne m'indique rien .
dés que je peut je vais acheter de la pate thermique et netoyer le pc completement . tu peut faire aussi ça, c'est peut etre une solution .
0