BSOD Once every 2 weeks, usually happens within 1 hour of turning on

HI Guys

So i have been getting a BSOD every 2 weeks or so, and it only ever happens when the computer has recently been turned on, never happened after an hour or so of it being turned on.

Recently I have been getting more frequent Blue Screens, which aren't shown in the zip file as once or twice it hung whilst creating the dump file on the BSOD.

I have googled the issues and most are saying bad ram, but i have run the inbuilt windows memory test along side the memtest and not a single error has been found.

Things I have done:
Samsung SSD firmware is up to date
Bios up to date
Tried a GTX 1080 and RX 580 and get BSOD
MEMTEST has been done, I am leaving it on tonight for 12 passes just to be doubly sure.
I also took the RAM out and checked for any physical damage and its fine, its only a few months old.
No OC's on ram or cpu.

Attachment 137780

Hello :)

I see that in the crash dump from 1st June the Intel driver for the network adapter is highlighted:

Code:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
BugCheck 1000007E, {ffffffffc0000005, fffff8095f17765c, ffff8d006f9e4598, ffff8d006f9e3dd0}
Probably caused by : e1i63x64.sys ( e1i63x64+1765c )

Driver Timestamp:        Fri Mar 04 21:46:29 2016 (56DA0235)

See if you can find an updated driver on the Intel site

Also it is important to run the Memtest86+ test for as many passes as you can so your plan is spot on! Post a photo of the result.

philc43 said:

Hello :)

I see that in the crash dump from 1st June the Intel driver for the network adapter is highlighted:

Code:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
BugCheck 1000007E, {ffffffffc0000005, fffff8095f17765c, ffff8d006f9e4598, ffff8d006f9e3dd0}
Probably caused by : e1i63x64.sys ( e1i63x64+1765c )

Driver Timestamp:        Fri Mar 04 21:46:29 2016 (56DA0235)

See if you can find an updated driver on the Intel site

Also it is important to run the Memtest86+ test for as many passes as you can so your plan is spot on! Post a photo of the result.

Updated the driver and ran the memtest with 0 errors, I guess ill just wait to see if another one happens.

Using Microsoft (R) Windows Debugger Version 10.0.15063.137 AMD64 there were multiple bsod that could not be processed as they displayed: GetContextState failed, 0x8007001E

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff8095f17765c, ffff8d006f9e4598, ffff8d006f9e3dd0}Probably caused by : e1i63x64.sys ( e1i63x64+1765c )

e1i63x64.sysIntel(R) Gigabit Adapter NDIS 6.x driverhttps://downloadcenter.intel.com/

Code:

BugCheck 3B, {c0000005, fffff11d31a31b84, ffffc100746e60f0, 0}Probably caused by : win32k.sys ( win32k!NtUserKillTimer+0 )

Code:

Probably caused by : memory_corruption

Code:

The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_&Prod_USB_DISK_2.0&Rev_PMAP#C70058E7EC1DDF43&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Code:

Windows failed fast startup with error status 0xC00000D4.

Code:

Crash dump initialization failed!

In addition to uninstalling and reinstalling the Intel driver and testing memory with memtest86+ version 5.01 please turn off Windows fast startup.

Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

The Pros and Cons of Windows 10 Mode

So my motherboard just killed itself whilst playing Dota 2, the bios led started to flash between main and backup and on a restart it had completely corrupted both bios's yay.. thank god there is a backup bios to stop that happening.... and as they provide a backup bios there is no USB method of restoring the bios.

So motherboard going to be RMA'd, but i had not bluescreened since doing the intel and fast boot option so thats a +.

For the minidumps these drivers were identified by date with the debugging

6/1/2017 and 5/17/2017: e1i63x64.sys
Intel(R) Gigabit Adapter NDIS 6.x driver
Drivers & Software

4/24/2017: nvlddmkm.sys
nVidia Video drivers
NVIDIA
Get from OEM for laptops

4/17/2017: AuthenticAMD
OEM (primarily for laptops) or
Download Drivers


The later two happened about 7 weeks ago so they were not troubleshooted at this time.

There were multiple memory bsod. We will troubleshoot pending the results of the Memtest86+ with 8 or more runs.