BSOD and crash dump analysis.

[Achilleslastand]

Just got a blue screen 9 days after doing a mobo/cpu switch.
This is the error report.........


On Fri 9/18/2015 3:43:35 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: e1d62x64.sys (e1d62x64!DriverEntry+0x175DD)
Bugcheck code: 0xD1 (0x2E0, 0x2, 0x1, 0xFFFFF88004A1B081)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1d62x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e1d62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL


A local shop did the switch and said when they installed the new mobo/cpu windows booted right up, so no new install was needed.
I tried to google the driver but haven't had any luck.
Here are the specs.
Gigabyte Z97 UDH Black ..Mobo
i7-4790K
16 Gigs Ram@1600
1 Samsung 500 GB SSD
1 WD Black 1 TB HDD
MSI R290 Gpu
Windows 7-64

Updated from Asus M5A97/AMD FX-8350.

Any ideas or help would be greatly appreciated.

 

[cholley]

you didn't google very well then

 

[Achilleslastand]

you didn't google very well then

Really?
In the time it took you to be snide you could have posted the link the said driver update?

 

[Ketchup]

If they didn't connect it to the Internet, that makes sense I suppose.

Get the latest drivers from Gigabyte and see if the problem goes away. Before you do, take another look at the motherboard model and make sure you are getting the right drivers. You are missing a couple pieces of the model number in your post. However, it's the Intel NIC, so it is most likely this one:

http://www.gigabyte.com/products/product-page.aspx?pid=4960#dl

 

[Achilleslastand]

If they didn't connect it to the Internet, that makes sense I suppose.

Get the latest drivers from Gigabyte and see if the problem goes away. Before you do, take another look at the motherboard model and make sure you are getting the right drivers. You are missing a couple pieces of the model number in your post. However, it's the Intel NIC, so it is most likely this one:

http://www.gigabyte.com/products/product-page.aspx?pid=4960#dl

Well I assume they did connect it to the internet but even so after I got it home I was able to connect right away.
Since they didn't do a fresh install of windows could this be a driver conflict of some sort?
I ran the Intel auto driver updater and it said everything was updated.

Weird because it has ran w/o error for 9 days until I got the BSOD last night.

 

[Ketchup]

Well I assume they did connect it to the internet but even so after I got it home I was able to connect right away.
Since they didn't do a fresh install of windows could this be a driver conflict of some sort?
I ran the Intel auto driver updater and it said everything was updated.

Weird because it has ran w/o error for 9 days until I got the BSOD last night.

OK. The added info helps. You might want to see if the Gigabyte if drivers is any older/newer than the one you have. If so, replace it.

So did you change any driver/nic-related soft since you got it home?

That error really is typical of a driver problem. The only other possibility is a bad stick of RAM/ bad NIC. If a driver change doesn't help, you may need to wait for another memory dump file to see if it is pointing to the same file.

 

[Achilleslastand]

OK. The added info helps. You might want to see if the Gigabyte if drivers is any older/newer than the one you have. If so, replace it.

So did you change any driver/nic-related soft since you got it home?

That error really is typical of a driver problem. The only other possibility is a bad stick of RAM/ bad NIC. If a driver change doesn't help, you may need to wait for another memory dump file to see if it is pointing to the same file.

No none at all..........
I did notice last night that the Ethernet driver for my old mobo was still installed so I uninstalled it.
Also noticed when they reinstalled my Ram which is 4x4gb sticks they had 2 of the red colored ones in slots 1 and 2 and the other 2 black sticks in slots 3 and 4. I did move the Black sticks to 2 and 4 and the Red ones to 1 and 3, although the Ram is different color and bought at different times the model # as well as the timings are exactly the same so not sure if that made a difference at all.
Thanks!