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

[BSODvictim829]

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.

 

[BSODvictim829]

(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

 

[axe0]

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.

 

[BSODvictim829]

Hello axe0, thank you .

I ran chkdsk and the built in windows memory diagonistic. (Il test each stick individually if that helps)
SSD firmware is up to date.

Thanks for the reply

 

[axe0]

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.

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

 

[BSODvictim829]

I have updated all USB3 chipset drivers&firmware, took me ages sorry for late reply.
However I can not for the life off me find the

" anodlwfx.sys Fri Mar 6 11:10:08 2009 (49B0F680)
ALPHA Networks Filter Driver
Driver Reference Table - anodlwfx.sys "

Im not even sure "明泰科技 Alpha Networks Inc." (alphanetworks Com) hosts these files anymore as I couldnt find driver files of any type on that site
I don't know what this driver is related to either

I have set up memtest86+ and I will run it when I go to bed.

Id also like to add that the last 2 times I turned on my computer I booted straight to safe mode and let it run for a couple of minutes and curiously had no freeze/bsod.

 

[chumbo]

Hi,
Imagine that, my first post here and I open up this forum section and the VERY first thread at the top of the BSOD section (i.e. this one)...describes EXACTLY the same problem I have as well!!
So you now know you're not alone...and nor am I!

Will be following this closely!
Cheers,
Chumbo

 

[axe0]

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.

 

[BSODvictim829]

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?:huh.

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 :busted:
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.

 

[BSODvictim829]

Hi,
Imagine that, my first post here and I open up this forum section and the VERY first thread at the top of the BSOD section (i.e. this one)...describes EXACTLY the same problem I have as well!!
So you now know you're not alone...and nor am I!

Will be following this closely!
Cheers,
Chumbo

Welcome to the thread
Hope you find a solution aswell, please post if you find anything that worked for you.

 

[axe0]

Please make sure the drivers of this USB network adapter are up to date or remove it while troubleshooting.
USB network adapters are known for causing problems when it comes to network BSODs.

Navn	[00000007] D-Link DWA-140 RangeBooster N USB Adapter(rev.B2)
Korttype	Ikke tilgjengelig
Produkttype	D-Link DWA-140 RangeBooster N USB Adapter(rev.B2)
Installert	Ja
ID for PNP-enhet	Ikke tilgjengelig
Sist tilbakestilt	17.05.2016 15:49
Indeks	7
Tjenestenavn	netr28ux
IP-adresse	Ikke tilgjengelig
IP-nettverk	Ikke tilgjengelig
Standard IP-gateway	Ikke tilgjengelig
DHCP-aktivert	Ja
DHCP-server	Ikke tilgjengelig
DHCP-leie utløper	Ikke tilgjengelig
DHCP-leie inngått	Ikke tilgjengelig
MAC-adresse	Ikke tilgjengelig

 

[BSODvictim829]

As I said I no longer use this "D-Link DWA-140" I recently bought a Pce card to replace it. Iv done my best to remove all the software that came with it, could you possibly offer some assistance with this?
And yes, Iv been quite displeased with that adapter for the time I had it.

Memtest86+ showed no error after 5 passes.

 

[axe0]

MemTest86+ needs at least 8 completed passes finished.

In control panel go to device manager, expand 'Network Adapter', right click the device and choose 'uninstall', that should get rid of it.

 

[BSODvictim829]

The adapter does not show up there, I "uninstalled" it when I changed but clearly there are remains. Id love to get rid off it all, any suggestions?

 

[axe0]

Please make a screenshot of device manager with network adapters expanded & 'show hidden devices' checked/enabled.

 

[chumbo]

So, let me describe my problem in more detail. As I said, it's very similar to the original poster's symptoms but I can add a few additional details to help diagnose...

There where the similarity is I think striking because rather unique, is that the problem only happens within +-10-15 min of booting. So after several initial crashes it almost always will finally go on working without a hitch for the rest of the day!? Which could be 10-12 hours working normally (this therefore makes me think it's not an overheating problem).
The problem has recently gotten worse, and now I can never even boot once without it crashing at least once within that time frame.

Either or all of the following symptoms could occur in one session: freeze completely, reboot on it's own or a BSOD (either while on or on the reboot). At it's worst, I think it took at least 4 or 5 crashes to get it running ok.
Yesterday and today have been good with only the one obligatory startup crash which has been the instant reboot. Although I do remember that the early symptoms were more a complete freeze forcing me to do the reboot myself.

One other interesting fact I should mention is, when I once ran the Windows Memory Diagnostics that runs before Windows boot, I ran it with the extended options as it had previously passed 2 runs of the normal test, and it froze then too! At least I think it did. There is a message displayed saying that during testing the PC might appear to be frozen, but I couldn't invoke either of the two available commands (Exit and Options) so I assume it really was frozen.
And that leads me to believe - correct me if I'm wrong! - that maybe it's hardware related since it happened BEFORE the OS was loaded! Am I right?

I just find the symptoms hard to understand...if it is a hardware failure, why does it only fail on startup?! Doesn't make sense to me.

Despite having it configured for create dump files, it almost never does. And I can't restore either because I discovered that although my system was configured to create Restore points, for some reason the space allocated to that was 0%! (Maybe because Windows dynamically allocates space for Restore according to available HD space? And since I've often found myself with almost only a few Mbs left...maybe then Windows didn't re-increase the space after I made some available?)

Here are two photos I did of 2 BSOD I got (there were others, with different messages).

So...any thoughts?

 

[axe0]

Hi chumbo,

In this thread I'm focusing on the OP, I understand that you are having similar problems but if I help 2 users at the same time it might give problems like me giving suggestions for you while it is meant for the OP.

Please read BSOD Posting Instructions & How to upload files & create a new thread to get the attention that is required for your problems.

 

[chumbo]

Ok, I understand. I'll do that!

 

[BSODvictim829]

Heres the picture with show hidden devices enabled

 

[axe0]

Thank you, it looks fine to me.
For now we can ignore it

Lets see if we can try a thing with the driver anodlwfx.sys, I guess it belongs to ASUS so I would like you to remove the ASUS software and reinstall it.
I suggest that you use Revo Uninstaller to remove everything of ASUS, but please be careful with it and carefully check what it finds, the things Revo Uninstaller finds might come from the registry in which case you need to verify that it really is from ASUS though that can easy be done by carefully going through what Revo Uninstaller has found.