If Ccleaner was reinstalled please modify the settings as in post #12.
Your welcome.
I glad its sorted out.
Type: Posts; User: zbook
If Ccleaner was reinstalled please modify the settings as in post #12.
Your welcome.
I glad its sorted out.
With replacement of the operating system please check the settings in the startup and recovery system failure to make sure that automatic restart is un-checked.
This way you will be know whether...
LOL.
It's complicated stuff.
See if the local store can swap the CPU > test the computer
This is the WHEA 0x124 error:
Error : GTLBL1_ERR (Proc 5 Bank 2)
Error : GTLBL1_ERR (Proc 4 Bank 2)
Common Platform Error Record @...
There were 5 BSOD mini dump files debugged that displayed 0x124 WHEA
One of the two BSOD memory dump files was able to be debugged.
Update:
e1d65x64.sys
Intel Pro/1000 Network Adapter driver...
Okay.
Looking at CPU versus motherboard for cause of WHEA 0x124.
The BSOD debugging displayed WHEA 0x124
Severity : Fatal
Error : GTLBL1_ERR (Proc 5 Bank 2)
Status : 0xb200000000010019
Open a support ticket with Intel.
Contact Intel...
Use the computer normally and under stress.
Monitor temperatures, display artifacts, freezings, etc.
See what happens with WHEA 0x124 and Nvidia.
The CPU was not replaced or swapped. The...
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...
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)...
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...
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...
When swapping GPU there can be 2 tests:
1) Testing a new GPU card in the problematic computer
2) Testing the problematic card in another computer
Which test(s) did they do and what were the...
It was a memory dump zip.
Please post a new beta log collector zip for troubleshooting.
What problems did they find with the GPU?
Did they perform any tests on the CPU?
Did they swap any hardware during the testing?
Run the beta log collector and post a new zip into the thread.
log...
The WHEA 0x124 uncorrectable hardware error displayed in post #2:
Severity : FatalError : GTLBL1_ERR (Proc 4 Bank 2)
TLB error on processor 4 bank 2
TLB = Translation Lookaside...
Please update the Macrium backup image.
Backup all files to another drive or to the cloud.
Find a flash drive that you can format ( > or = 8 GB )
Create a bootable windows 10 iso:
Download...
In reviewing the thread I have some questions:
How old is the computer?
What parts are still under warranty?
When was the GPU replaced?
What were the prior problems that you had before...
When you open the Gigabyte website is there detailed information available for the drivers?
When you open the Intel website is there detailed information available for the drivers?
What drivers...
With the driver uncertainty consider the following:
1) Download the Intel driver update utility:
IntelĀ® Driver & Support Assistant
2) Uninstall the first misbehaving driver (Ethernet LAN)
3) Run...
All of the drivers are already installed and replacement drivers can be installed only if the other drivers are uninstalled.
It cannot have two drivers installed at the same time.
It will not let...
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...
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...
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...
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?...