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

zbook said:

The latest version of the Windows operating system can become corrupted.
In a similar fashion the latest version of a driver can become corrupted.
For windows operating system corruption you may run scannow, restorehealth, perform an in place upgrade repair, or clean install.
For problems with drivers the drivers are updated. This may require an uninstall and a reinstall (for example this is regularly done with Nvidia and AMD GPU drivers.

For the motherboard there are multiple revisions. Please check the Gigabyte website to see the proper link for the motherboard.
Is this the correct or incorrect Gigabyte motherboard for the computer: GA-X99-UD4 (rev. 1.0) | Motherboard - GIGABYTE Global


Intel® Driver & Support Assistant
Drivers & Software

which one you recommend to run For windows operating system corruption

There was no windows operating system corruption reported.
Windows can be up to date and have corruption.
Drivers can be up to date and have corruption.
When you attempted to update the driver it posted a message that the driver was up to date.
So with an up to date driver you may have thought that it meant the driver was Okay because it was up to date.
The driver is up to date but it is a misbehaving up to date driver.
So the message that it is up to date did not tell you whether the driver is or is not working properly.
In a similar fashion an up to date Windows version and build does not tell you whether the operating system is corrupt.
So the BSOD produced dump files. The dump files were debugged. They have displayed multiple misbehaving drivers.

When there are problems with multiple hardware drivers there can be a problem with the motherboard. There is no definitive test for the motherboard. It is done by process of elimination and then swap or replace. At this time you will have replaced these drivers:

iocbios2.sys
gdrv.sys
iaStorA.sys
nvlddmkm.sys
e1d65x64.sys


When a driver is replaced and then windows is installed it will have default non-windows drivers.
The computer can function.
Then the best drivers are downloaded and installed from the computer or motherboard manufacturer's website.
Then the optimal performance is available.


Sometimes the drivers misbehave.
Then the misbehaving drivers are updated.
This may involve uninstalling and reinstalling the drivers.


The first misbehaving driver was the ESET driver.
This was troubleshooted or fixed by uninstalling the software.
Windows defender was then turned on.


In posts 29 - 31 iocbios2.sys was identified as a misbehaving driver.
Please review the steps that were used in fixing this driver.
Had you used the steps in the Microsoft link?
Was this driver fixed?


In post #36 gdrv.sys was identified as a misbehaving driver.
This was troubleshooted or fixed by uninstalling the software.

zbook said:

There was no windows operating system corruption reported.
Windows can be up to date and have corruption.
Drivers can be up to date and have corruption.
When you attempted to update the driver it posted a message that the driver was up to date.
So with an up to date driver you may have thought that it meant the driver was Okay because it was up to date.
The driver is up to date but it is a misbehaving up to date driver.
So the message that it is up to date did not tell you whether the driver is or is not working properly.
In a similar fashion an up to date Windows version and build does not tell you whether the operating system is corrupt.
So the BSOD produced dump files. The dump files were debugged. They have displayed multiple misbehaving drivers.

When there are problems with multiple hardware drivers there can be a problem with the motherboard. There is no definitive test for the motherboard. It is done by process of elimination and then swap or replace. At this time you will have replaced these drivers:

iocbios2.sys
gdrv.sys
iaStorA.sys
nvlddmkm.sys
e1d65x64.sys


When a driver is replaced and then windows is installed it will have default non-windows drivers.
The computer can function.
Then the best drivers are downloaded and installed from the computer or motherboard manufacturer's website.
Then the optimal performance is available.


Sometimes the drivers misbehave.
Then the misbehaving drivers are updated.
This may involve uninstalling and reinstalling the drivers.


The first misbehaving driver was the ESET driver.
This was troubleshooted or fixed by uninstalling the software.
Windows defender was then turned on.


In posts 29 - 31 iocbios2.sys was identified as a misbehaving driver.
Please review the steps that were used in fixing this driver.
Had you used the steps in the Microsoft link?
Was this driver fixed?


In post #36 gdrv.sys was identified as a misbehaving driver.
This was troubleshooted or fixed by uninstalling the software.

sorry to late

Intel(R) Extreme Tuning Utility Performance Tuning Driver...i just uninstalled it from control panel
and yes the last bsod was 0x124 that i posted
but now i don't know which is the exact drivers that i should reinstall from device manager..i googled it and search on youtube but i did not catch the right link yet

It is unclear what was and what was not done.
For each misbehaving driver identified in the thread please indicate the steps that you made.
Which drivers were fixed?
Which drivers were not fixed?
If a driver was fixed how it was fixed.

zbook said:

It is unclear what was and what was not done.
For each misbehaving driver identified in the thread please indicate the steps that you made.
Which drivers were fixed?
Which drivers were not fixed?
If a driver was fixed how it was fixed.

as i said my friend uninstalling the Intel(R) Extreme Tuning Utility Performance Tuning Driver has fixed iocbios2.sys
and uninstalling APP Center Gigabyte has fixed gdrv.sys
and i uninstalled eseT
the nvlddmkm.sys related..i uninstalled the graphics driver through ddu with safe mode and reinstalled it from nvidia website
the other 2 that related to chipset driver and network adapter did not fix i think because i don't know which the exact drivers on device manager should i uninstall

so e1d65x64.sys and IaStorA.sys did't fixed

For confirmation that you have the proper driver perform these steps:
Open device manager > expand the rows of interest > right click on the row > left click properties > left click on the driver tab > left click on driver details > the driver will be displayed > compare to the name of the misbehaving driver

For the Intel chip set drivers: Support for Intel® Chipset Software Installation Utility

If you were not able to replace the chip set drivers and after replacing the GPU and Ethernet drivers > turn windows driver verifier on and see if there are any other misbehaving drivers.

If there are BSOD please run the beta log collector > post a zip into the thread.

This is the information again on the misbehaving Intel Ethernet adapter:
e1d65x64.sys Mon Sep 25 07:45:31 2017 (59C8FA6B)

It displays: name, device ID, driver, etc.
So you will identify the matching driver on the Gigabyte or the Intel website for the replacement driver and identify the driver in device manger.

Please follow the instructions in this link:
Updating a driver. - Microsoft Community



Name [00000001] Intel(R) Ethernet Connection (2) I218-V
Adapter Type Ethernet 802.3
Product Type Intel(R) Ethernet Connection (2) I218-V
Installed Yes
PNP Device ID PCI\VEN_8086&DEV_15A1&SUBSYS_E0001458&REV_05\3&11583659&0&C8
Last Reset 10/03/2018 1:13
Index 1
Service Name e1dexpress
IP Address 10.0.0.18, fe80::e1d5:dd01:8f9e:22f, fd21:696e:7f91:0:7960:8532:67c1:f7fb, fd21:696e:7f91:0:e1d5:dd01:8f9e:22f
IP Subnet 255.255.255.0, 64, 128, 64
Default IP Gateway 10.0.0.138
DHCP Enabled Yes
DHCP Server 10.0.0.138
DHCP Lease Expires 01/01/1970 1:31
DHCP Lease Obtained 01/01/1970 0:31
MAC Address ‪1C:1B:0D:6E:55:7B‬
Memory Address 0xDF100000-0xDF11FFFF
Memory Address 0xDF139000-0xDF139FFF
IRQ Channel IRQ 4294967292
Driver c:\windows\system32\drivers\e1d65x64.sys (12.17.8.7, 542.57 KB (555,592 bytes), 02/03/2018 19:06)

Code:

Name    [00000001] Intel(R) Ethernet Connection (2) I218-V
Adapter Type    Ethernet 802.3
Product Type    Intel(R) Ethernet Connection (2) I218-V
Installed    Yes
PNP Device ID    PCI\VEN_8086&DEV_15A1&SUBSYS_E0001458&REV_05\3&11583659&0&C8
Last Reset    10/03/2018 1:13
Index    1
Service Name    e1dexpress
IP Address    10.0.0.18, fe80::e1d5:dd01:8f9e:22f, fd21:696e:7f91:0:7960:8532:67c1:f7fb, fd21:696e:7f91:0:e1d5:dd01:8f9e:22f
IP Subnet    255.255.255.0, 64, 128, 64
Default IP Gateway    10.0.0.138
DHCP Enabled    Yes
DHCP Server    10.0.0.138
DHCP Lease Expires    01/01/1970 1:31
DHCP Lease Obtained    01/01/1970 0:31
MAC Address    ‪1C:1B:0D:6E:55:7B‬
Memory Address    0xDF100000-0xDF11FFFF
Memory Address    0xDF139000-0xDF139FFF
IRQ Channel    IRQ 4294967292
Driver    c:\windows\system32\drivers\e1d65x64.sys (12.17.8.7, 542.57 KB (555,592 bytes), 02/03/2018 19:06)

e1dexpress Intel(R) PRO/1000 PCI Express Network Connection Driver D c:\windows\system32\drivers\e1d65x64.sys Kernel Driver Yes Manual Running OK Normal No Yes

Code:

e1dexpress    Intel(R) PRO/1000 PCI Express Network Connection Driver D    c:\windows\system32\drivers\e1d65x64.sys    Kernel Driver    Yes    Manual    Running    OK    Normal    No    Yes

For the Intel chip set drivers I looked on the Intel website to see if they offered a method to fix chip set drivers that was different from the Microsoft link method.

If you are able to follow there steps please update the Intel chip set drivers.
If you are not able to follow their steps please wait to see if an Intel chip set driver reappears in the BSOD dump files.

Either A or B:

A) Device Manager.
Select View > Devices by Type.
Expand System Devices.
Double-click the Intel chipset device from the list.
Select the Driver tab.
Click Update Driver.


B) On Intel Download Center search for:
Intel Chipset Device Software (INF Update Utility) or
Intel Server Chipset Driver
Download Intel® Server Chipset Driver for Windows*
Follow the installation instructions.

This source was used as the reference for a different problem but with a similar fix:
Intel® Chipset Device Software Update Through Microsoft Windows*...


Please update the thread with the progress for updating the 2 misbehaving Intel drivers ( Ethernet and chip set)

For any BSOD please post a new beta log collector zip into the thread:
log collector v2-beta08.zip

hi again
so just to be sure what i'm doing
Attachment 180498 am i updating the driver or uninstalling it and replace it with the one from gigabyte website like this

one...

Attachment 180501

updating will not work i think because i have the latest driver

and i found istora code in device manager there it is

Attachment 180502

so i uninstall it and install the ones on gigabyte website Attachment 180503

but i already have intel management engine interface like shown Attachment 180504

and look at this Attachment 180505 and this Attachment 180506 there is no driver installed..is it normal

thank you for your help