BSOD Every Time I Game (atikmdag.sys)

Hello hungrymaven I will leave you with zbook as I am sure he can carry on from here

Just as by the by though I had no idea that you were using a driver finder software and just as a personal thing I never use add on software that will check for drivers except for one and then only in desperation, Windows 7 and it is removed immediately after use. I also include any software that promises an increase in performance of a machine puts the registry right etc etc because they often well more than often instil more problems than when you didn't have them on board. Plus I think that the OS is so much more involved in the drivers than 7 ever was and I am not that familiar with 10 yet to make comment I can only pick the glaringly obvious right now.
Anyway I shall let you get on with where you are up to good luck I'm sure the others can get it fixed for you.

Hey ICIT2LOL,

Thanks for the help nonetheless, it's truly appreciated!

Yeah, that was a dumb mistake - I am new to the whole driver thing... was a Mac user for most of my life, and to be completely fair, this driver thing (and BSOD's in general) is a pain the arse. Thought the software would help, guess it didn't

I also wasn't aware that Windows kept drivers up to date. Now I know :)

There's just so much software, even quite a bit recommended here on the forums, it's sometimes hard to tell which one is "legit" and which one will cause more harm than good.

Thanks again (and for the good luck wishes).

Hey Guys,

Got a new BSOD. This time it seems to be related to the tcpip.sys

Minidump attached.

Should I be clearing/backing up and removing the minidump files perchance?\

EDIT: I'm legit thinking of reinstalling windows, etc, etc. I just think it will be a pain in the ASS. How hard/easy is it to do a fresh install?

Thanks

Attachment 153198

hungrymaven,

The latest crash was caused by e1d65x64.sys, your Intel Ethernet driver.

Code:

00 ffffc200`ee37ca08 fffff801`75e020df nt!KeBugCheckEx
01 ffffc200`ee37ca10 fffff801`75d7fb46 nt!KiFatalFilter+0x1f
02 ffffc200`ee37ca50 fffff801`75d5d45f nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
03 ffffc200`ee37ca90 fffff801`75d79a5d nt!_C_specific_handler+0x9f
04 ffffc200`ee37cb00 fffff801`75c33234 nt!RtlpExecuteHandlerForException+0xd
05 ffffc200`ee37cb30 fffff801`75c31fd6 nt!RtlDispatchException+0x404
06 ffffc200`ee37d220 fffff801`75d7e98e nt!KiDispatchException+0x1f6
07 ffffc200`ee37d8d0 fffff801`75d7c43d nt!KiExceptionDispatch+0xce
08 ffffc200`ee37dab0 fffff80b`567efbe6 nt!KiInvalidOpcodeFault+0xfd
09 ffffc200`ee37dc40 fffff80b`567ef094 tcpip!TlShimOptionalReauthorizeConnection+0x2d6
0a ffffc200`ee37de40 fffff80b`567ecf6a tcpip!ProcessALEForTransportPacket+0x284
0b ffffc200`ee37e120 fffff80b`567eba9d tcpip!WfpProcessInTransportStackIndication+0xafa
0c ffffc200`ee37e580 fffff80b`5680890a tcpip!InetInspectReceiveDatagram+0x27d
0d ffffc200`ee37e6c0 fffff80b`56808427 tcpip!UdpBeginMessageIndication+0x7a
0e ffffc200`ee37e960 fffff80b`568078a6 tcpip!UdpDeliverDatagrams+0x177
0f ffffc200`ee37eb60 fffff80b`567f959e tcpip!UdpReceiveDatagrams+0x386
10 ffffc200`ee37ef20 fffff80b`567f8607 tcpip!IpFlcReceivePreValidatedPackets+0x82e
11 ffffc200`ee37f130 fffff801`75c1d20b tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x107
12 ffffc200`ee37f260 fffff80b`567c9c06 nt!KeExpandKernelStackAndCalloutInternal+0x8b
13 ffffc200`ee37f2b0 fffff80b`565c2da7 tcpip!FlReceiveNetBufferListChain+0xb6
14 ffffc200`ee37f330 fffff80b`565c2a9f ndis!ndisMIndicateNetBufferListsToOpen+0x117
15 ffffc200`ee37f3f0 fffff80b`565c3317 ndis!ndisMTopReceiveNetBufferLists+0x22f
16 ffffc200`ee37f4f0 fffff80b`565c267d ndis!ndisCallReceiveHandler+0x47
17 ffffc200`ee37f540 fffff80b`5bef7407 ndis!NdisMIndicateReceiveNetBufferLists+0x70d
18 ffffc200`ee37f730 00000000`00000000 e1d65x64+0x17407

The latest driver that was tested by Gigabyte for your motherboard can be found here.

Consider a clean install so that you have drivers only directly from the component manufactures.

Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take many hours so plan to run it overnight.
Memtest86+ version 5.01 is not run by time but by passes.
There are significant false negatives if testing has fewer than 8 passes.
A false negative is a pass when there is malfunctioning RAM.
There is 16 GB RAM on 2 DIMM
Testing both RAM modules at the same time enables testing multichannel capability.
Memtest86+ version 5.01 takes approximately 1 -2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM for 8 or more passes.
Memtest86+ - Advanced Memory Diagnostic Tool
When Memtest86+ has completed 8 or more runs use a camera or smart phone camera to take a picture and post an image into the thread.
Microsoft Community
MemTest86+ - Test RAM

Spectrum said:

hungrymaven,

The latest crash was caused by e1d65x64.sys, your Intel Ethernet driver.
The latest driver that was tested by Gigabyte for your motherboard can be found here.

Thank you, I'll install it now.

EDIT: Just tried installing it and got the error in the attached screenshot.

Should I really uninstall the newer version and install the older version?

Attachment 153349

ICIT2LOL said:

Yes as a general rule they do my friend but personally still like to do things "manually" from manufacturers sites at times - the machine I am on right now is a prime example of 10 taking over all but the prime drivers it needs but again I would prefer to do it myself a bit like putting the right brand and type of fuel in my car.

OK, fair enough

How does one know when the manual drivers need to be installed? I'm fairly new to the world of drivers, bsods, reinstalling windows, etc.

zbook said:

Consider a clean install so that you have drivers only directly from the component manufactures.
Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
MemTest86+ - Test RAM

Hey zbook,

Do you recommend doing the clean install before, or after the memtest?

I've done the memtest before, and I have the USB ready, but I wasn't aware it needed 8 runs - only did 2.

Thanks for the instructions!

The memtest86+ version 5.01 can be run before or after the clean install.

Please run a minimum of 8 continuous passes and the more the better.

It sometimes takes passes in the 20's to display malfunctioning RAM /DIMM /Motherboard.

When the testing has completed please use a camera or smart phone camera to take a picture and post an image into the thread.

For the clean install please backup all of your files and bookmarks and follow the steps in this link:

Clean Install Windows 10 Windows 10 Installation Upgrade Tutorials

Sorry for the delay - my work room was being "renovated" and I had to move my computer out and put it in a corner for over a week.

This problem has been fixed - so far over 5-6 hours of intense gaming over the last 3 days: Shadow of Mordor, Overwatch, CS:GO and no BSODs.

I did not do a memtest, nor did I do a clean install.

I simply moved the ram sticks from slots 1 & 2, to 3 & 4 (according to the manual, found here: GA-Z270XP-SLI (rev. 1.0) | Motherboard - GIGABYTE
)

This was done on the recommendation of a friend, and since the computer was not attached, it seemed like a quick test.

Besides this, I have also moved both monitors to be attached to the graphics card as opposed to the second monitor being attached to the motherboard (intel graphics).

I'm glad this problem has been fixed without the need for a clean install.

Thanks a ton for all your help guys! :)