bsod freezing playing gta v bf1 error 0x124 and 0x3B

there you are the attachment

1) Testing a new GPU card in the problematic computer
as they claimed...that the gpu 100% the problematic drive...and now there will be no issues
but it is really funny...they test maybe for 5 minutes or so...
i did not expect that it will crash this fast
i told my mother that i don't think the problem will end from changing the gpu...because i believe it is one from two...cpu or mobo
they even replaced a better gpu from the old one...1080 gtx rog strix

There were no mini dumps collected by the beta log collector.
The memory dump debugging displayed Nvidia GPU drivers as the cause of the latest BSOD.
Tue Mar 20 11:18:08.582 2018 (UTC - 5:00)
The bugcheck was WHEA 0x124


The Nvidia driver was a recurrent misbehaving driver prior to the GPU replacement.
The WHEA 0x 124 fatal error was recurrent: GTLBL1_ERR (Proc 5 Bank 2)


The Nvidia driver can be replaced again (3rd) in the thread.
This would be the first replacement for this GPU card.

1) Turn off Windows updates of non-Microsoft drivers
Enable or Disable Driver Updates in Windows Update in Windows 10 Windows 10 Tutorials
2) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
3) re-install the Nvidia GPU driver from the Nvidia website (use a different drive version than in the recent BSOD)
4) make sure that you check the clean install box and if available install the physx driver.
Display Driver Uninstaller Download version 17.0.8.2 (or a newer version if available)
Display Driver Uninstaller: How to use - Windows 7 Help Forums
NVIDIA
Download Display Driver Uninstaller - MajorGeeks


nvlddmkm.sys (23.21.13.8843

Code:

nvlddmkm.sys Thu Mar 15 17:30:24 2018 (5AAAF400)

Code:

BugCheck 124, {0, ffffe407be740028, b2000000, 10019}Page 40707d not present in the dump file. Type ".hh dbgerr004" for detailsProbably caused by : GenuineIntelFollowup: MachineOwner---------5: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe407be740028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000010019, Low order 32-bits of the MCi_STATUS value.

Code:

Common Platform Error Record @ ffffe407be740028-------------------------------------------------------------------------------Record Id     : 01d3c065396ce312Severity      : Fatal (1)Length        : 928Creator       : MicrosoftNotify Type   : Machine Check ExceptionTimestamp     : 3/20/2018 16:18:08 (UTC)Flags         : 0x00000000===============================================================================Section 0     : Processor Generic-------------------------------------------------------------------------------Descriptor    @ ffffe407be7400a8Section       @ ffffe407be740180Offset        : 344Length        : 192Flags         : 0x00000001 PrimarySeverity      : FatalProc. Type    : x86/x64Instr. Set    : x64Error Type    : TLB errorFlags         : 0x00Level         : 1CPU Version   : 0x00000000000406f1Processor ID  : 0x0000000000000005===============================================================================Section 1     : x86/x64 Processor Specific-------------------------------------------------------------------------------Descriptor    @ ffffe407be7400f0Section       @ ffffe407be740240Offset        : 536Length        : 128Flags         : 0x00000000Severity      : FatalLocal APIC Id : 0x0000000000000005CPU Id        : f1 06 04 00 00 08 10 05 - bf fb fe 7f ff fb eb bf                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00Proc. Info 0  @ ffffe407be740240===============================================================================Section 2     : x86/x64 MCA-------------------------------------------------------------------------------Descriptor    @ ffffe407be740138Section       @ ffffe407be7402c0Offset        : 664Length        : 264Flags         : 0x00000000Severity      : FatalError         : GTLBL1_ERR (Proc 5 Bank 2)  Status      : 0xb200000000010019

Code:

Event[10352]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2018-03-20T16:20:34.269  Event ID: 18  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: DESKTOP-LFAU6I0  Description: A fatal hardware error has occurred.Reported by component: Processor CoreError Source: Machine Check ExceptionError Type: Translation Lookaside Buffer ErrorProcessor APIC ID: 4The details view of this entry contains further information.

Code:

Name    NVIDIA GeForce GTX 1080PNP Device ID    PCI\VEN_10DE&DEV_1B80&SUBSYS_85AA1043&REV_A1\4&FC7F53B&0&0018Adapter Type    GeForce GTX 1080, NVIDIA compatibleAdapter Description    NVIDIA GeForce GTX 1080Adapter RAM    (1,048,576) bytesInstalled Drivers    C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d65b7647eff8c45\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d65b7647eff8c45\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d65b7647eff8c45\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d65b7647eff8c45\nvldumdx.dllDriver Version    23.21.13.8843INF File    oem33.inf (Section136 section)Colour Planes    Not AvailableColour Table Entries    4294967296Resolution    2560 x 1440 x 165 hertzBits/Pixel    32Memory Address    0xDE000000-0xDF0FFFFFMemory Address    0xC0000000-0xD1FFFFFFMemory Address    0xD0000000-0xD1FFFFFFI/O Port    0x0000E000-0x0000EFFFIRQ Channel    IRQ 16I/O Port    0x000003B0-0x000003BBI/O Port    0x000003C0-0x000003DFMemory Address    0xA0000-0xBFFFFDriver    c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_2d65b7647eff8c45\nvlddmkm.sys (23.21.13.8843, 16.23 MB (17,020,720 bytes), 19/03/2018 12:57)

i did...so maybe there is no problem and i should test it with games now?

Please test to see if there is a spontaneous BSOD.
The goal is to get a stable computer without freezes and BSOD.

It would be surprising if it were just the driver.

1) Open Whocrashed > above analyze click on test > crash dump test > type: ACCEPT
2) Click analyze
3) Post the Whocrashed results into the thread using a one drive or drop box share link
4) Run the beta log collector after the test crash and post a new zip into the thread

hi..here it is the one drive link and the bet log collector attachment
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
crash test with whocrashed

The ESET software drivers were misbehaving in the latest dump.
Also the Nvida GPU drivers were involved in the crash.

23.21.13.9124
nvlddmkm.sys Thu Mar 15 17:30:24 2018 (5AAAF400)

1) Uninstall ESET using the applicable uninstall tool
2) Turn on Windows defender
3) Wait 1 -2 weeks to reinstall ESET (the longer the better)
Then when ESET is reinstalled if there is a BSOD > uninstall ESET.
If there is no BSOD then continue using the AV product.

Code:

Name    NVIDIA GeForce GTX 1080PNP Device ID    PCI\VEN_10DE&DEV_1B80&SUBSYS_85AA1043&REV_A1\4&FC7F53B&0&0018Adapter Type    GeForce GTX 1080, NVIDIA compatibleAdapter Description    NVIDIA GeForce GTX 1080Adapter RAM    (1,048,576) bytesInstalled Drivers    C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_95d88c9d04436846\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_95d88c9d04436846\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_95d88c9d04436846\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_95d88c9d04436846\nvldumdx.dllDriver Version    23.21.13.9124INF File    oem3.inf (Section118 section)Colour Planes    Not AvailableColour Table Entries    4294967296Resolution    2560 x 1440 x 165 hertzBits/Pixel    32Memory Address    0xDE000000-0xDF0FFFFFMemory Address    0xC0000000-0xD1FFFFFFMemory Address    0xD0000000-0xD1FFFFFFI/O Port    0x0000E000-0x0000EFFFIRQ Channel    IRQ 16I/O Port    0x000003B0-0x000003BBI/O Port    0x000003C0-0x000003DFMemory Address    0xA0000-0xBFFFFDriver    c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_95d88c9d04436846\nvlddmkm.sys (23.21.13.9124, 16.71 MB (17,526,688 bytes), 21/03/2018 0:20)

Code:

Event[11236]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2018-03-21T18:20:42.942  Event ID: 19  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: DESKTOP-LFAU6I0  Description: A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Internal parity errorProcessor APIC ID: 10The details view of this entry contains further information.

zbook said:

The ESET software drivers were misbehaving in the latest dump.
Also the Nvida GPU drivers were involved in the crash.

23.21.13.9124
nvlddmkm.sys Thu Mar 15 17:30:24 2018 (5AAAF400)

1) Uninstall ESET using the applicable uninstall tool
2) Turn on Windows defender
3) Wait 1 -2 weeks to reinstall ESET (the longer the better)
Then when ESET is reinstalled if there is a BSOD > uninstall ESET.
If there is no BSOD then continue using the AV product.

Code:

Name    NVIDIA GeForce GTX 1080PNP Device ID    PCI\VEN_10DE&DEV_1B80&SUBSYS_85AA1043&REV_A1\4&FC7F53B&0&0018Adapter Type    GeForce GTX 1080, NVIDIA compatibleAdapter Description    NVIDIA GeForce GTX 1080Adapter RAM    (1,048,576) bytesInstalled Drivers    C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_95d88c9d04436846\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_95d88c9d04436846\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_95d88c9d04436846\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_95d88c9d04436846\nvldumdx.dllDriver Version    23.21.13.9124INF File    oem3.inf (Section118 section)Colour Planes    Not AvailableColour Table Entries    4294967296Resolution    2560 x 1440 x 165 hertzBits/Pixel    32Memory Address    0xDE000000-0xDF0FFFFFMemory Address    0xC0000000-0xD1FFFFFFMemory Address    0xD0000000-0xD1FFFFFFI/O Port    0x0000E000-0x0000EFFFIRQ Channel    IRQ 16I/O Port    0x000003B0-0x000003BBI/O Port    0x000003C0-0x000003DFMemory Address    0xA0000-0xBFFFFDriver    c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_95d88c9d04436846\nvlddmkm.sys (23.21.13.9124, 16.71 MB (17,526,688 bytes), 21/03/2018 0:20)

Code:

Event[11236]:  Log Name: System  Source: Microsoft-Windows-WHEA-Logger  Date: 2018-03-21T18:20:42.942  Event ID: 19  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-19  User Name: NT AUTHORITY\LOCAL SERVICE  Computer: DESKTOP-LFAU6I0  Description: A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Internal parity errorProcessor APIC ID: 10The details view of this entry contains further information.

ok...but what about nvidia gpu drivers...i uninstalled it and reinstalled it 4 times...what's his problem with my graphic card

When there is a crash there is a cause and there are bystanders.
For the Nvidia we already know that there is a problem.
The GPU has been replaced twice.
The next step is to observe for spontaneous crashes and see which bugchecks appear.

sadly it's rare to get bsod...should i stress it with a lots of downloading?
but what is Nvidia's problem...as you said this is the third GPU
thank you anyway man