BSOD/freeze 1-10m after startup or not at all until next reboot

Hello, as the title says Im having problems with freezes/BSOD shortly after I turn on my computer every day. Takes about 30m to get past always.

The problem can occur during any activity whether Im not doing anything on my computer, or have not even logged into my windows user. After a couple of restarts it will however make it past 10m without errors and not experience any problems until it's turned off again.

During these restarts it will occationally attempt to boot, turn itself off and then on again. It will occationally take longer (couple of seconds) to load the OS.

Sometimes the screen+sound will just freeze and never respond and I have to cut the power but occationally Im lucky enough to find a minidump file.
Ran harddrive checks and memory (not 1 by 1). Temperatures are low according to software.

Hope I have been detailed enough, file is attached below and Iv filled out most computer specs.

(Posting the specs here if it helps)
Computer type - PC/Desktop OS -Windows 7 64 bit
CPU - Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz, 2927mhz 4 cores
MB - Gigabyte P55-USB3
RAM - 2x2 (old) + 2x4 (newer)
GPU -Geforce GTX 750 Ti
Hard Drives - Samsung SSD 850 EVO 250gb(OS+apps) & Seagate 1TB HDD ST1000DM003-1ER162
PSU - Corsair TX 650W PSU (quite old)
ASUS PCE-AC56 AC1300 network card (installed 2~weeks prior to start of problems)
Monitor - Benq xl2411z

Hi BSODvictim829,

Welcome to the 7forums :)

What tests did you run on your HDD & RAM?

Please make sure the SSD firmware is up to date.

I noticed this WER, even though it is from nearly a month ago it happened a few times and as such I'd like you to run MemTest86+.
Besides of the probable cause of hardware, according to the dump, is the dump not of much use. The 0x7F shows a double fault, meaning the CPU was handling a fault when another fault came in, 0x7F minidumps with double faults are pretty much useless.

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

Code:

26.04.2016 15:52	Windows Error Reporting	Feil-bucket BAD_DUMPFILE, type 0
Hendelsesnavn: LiveKernelEvent
Svar: http://wer.microsoft.com/responses/resredir.aspx?sid=79&Bucket=BAD_DUMPFILE&ID=3b9e808e-921c-4cff-a3f0-963db9e65a5f
Cab-ID: 0

Problemsignatur:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Vedlagte filer:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20160404-2224.dmp
C:\Windows\Temp\WER-5201042-0.sysdata.xml
C:\Windows\Temp\WER5DE9.tmp.WERInternalMetadata.xml

Disse filene kan være tilgjengelige her:


Analysesymbol: BAD_DUMPFILE
Leter etter løsning en gang til: 1
Rapport-ID: 3836e920-faa3-11e5-a1c8-1c6f65940c65
Rapportstatus: 0

Furthermore, please update following drivers
anodlwfx.sys Fri Mar 6 11:10:08 2009 (49B0F680)
ALPHA Networks Filter Driver
Driver Reference Table - anodlwfx.sys

nusb3hub.sys Mon Oct 26 15:19:44 2009 (4AE5B000)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions) Try OEM first
Driver Reference Table - nusb3hub.sys

nusb3xhc.sys Mon Oct 26 15:19:48 2009 (4AE5B004)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions) Try OEM first
Driver Reference Table - nusb3xhc.sys

It appears that there are many others having the same problem with anodlwfx.sys.
I recommend that you create a restore point before you start with below suggestion! This is in case something goes wrong for whatever reason so we can get you back online.

Please go in Windows explorer to C:\Windows\system32\DRIVERS\ and search for the driver.
Once you have found it rename it to anodlwfx.bak and reboot your system.

I read some old threads about anodlwfx.sys and many people say it's related to D-link adapters, up until recently I was using such an adapter but I uninstalled all the software upon changing (or did I?).

I tried moving the file earlier but then I could not get an internet connection (could connect to network but with "limited acess"). Since I no longer use the adapter isnt there some way to let me connect online with my current ASUS PCE-AC56 card?

Il try the .bak fix now lets hope I come back
EDIT: .bak fix yielded the same result as i experienced earlier. For some reason the asus ulitities program can't identify my network card with anodlwfx.sys missing either, tried to reinstall drivers but didnt help.