Windows 10: BSOD: My computer have been crashing about 11 times within 2 days... I'm not sure about the pattern

I -think I- have the same problem, and I can't seem to find a way around it.
That site you linked to with driver for the Qualcomm ethernet controller haven't got one for Windows 10. I have the newest installed for Windows 8.1 but no luck.

My computer have been crashing about 11 times within 2 days... I'm not sure about the pattern, but it seems to me that it's more prone to crashing when I download much data at the same time. E.g. downloading a game from Steam have crashed my computer several times already.

Attachment 32610

If you have any solution what so ever, please tell me *Smile

Cheers

:)

 

Driver Verifier BSOD diagnosis opinions?

Thank you very much for looking at this.

I followed the directions for uninstalling the drivers, and attempted to install new ones that I

downloaded from my motherboard maker, ASUS. Unfortunately, they don't provide audio drivers for anything past Win 7 64 bit, but even though I'm running Win 10, I tried them. The computer would still crash when I ran driver verifier at startup and I had
to use a restore point.

When I checked which drivers were installed, however, it seemed to still be reverting to the original ones that initially caused the problem. So, I did some research on my own and used the Windows Show or Hide Updates program to make sure VIA wasn't auto-updating,
but the issues persisted. So, as a last resort, I simply went to device manager and updated the audio drivers to Win 10 provided by Microsoft, but I'm still getting the driver verifier crash before the system starts. My computer is presently in this state.
As long as I don't use driver verifier, it doesn't crash at startup, but I bet it will after normal sustained use.

The new dump files are here from the trials above. I'm curious if they're all still pointing to the audio driver, and if so/not,
what other steps you might recommend?

 

Driver Verifier BSOD diagnosis opinions?

I used the link provided and selected the option that says the BSOD occurred while using my PC. The link suggests checking for updates and disconnecting hardware. My software is already up to date, and rather than disconnecting random hardware, I was under
the impression from that by uploading the dump files from the Driver Verifier program that from

this post, there might be some clues as to what specific driver is causing the crashes. Is that possible to determine?

 

hello, Swung. All of the dumpds I looked at were the same.

Code: Use !analyze -v to get detailed debugging information. BugCheck D1, {0, 2, 0, fffff801d5216cb3} *** WARNING: Unable to verify timestamp for L1C63x64.sys *** ERROR: Module load completed but symbols could not be loaded for L1C63x64.sys Probably caused by : L1C63x64.sys ( L1C63x64+6cb3 ) Followup: MachineOwner[/quote] Which is your Qualcomm Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.30). But, They also balme your Agnitum Firewall. The Firewall may be stopping your Ethernet Controller.

Code: ffffd000`2573c288 fffff801`d31c2800Unable to load image \SystemRoot\system32\DRIVERS\afw.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for afw.sys *** ERROR: Module load completed but symbols could not be loaded for afw.sys afw+0x2800[/quote] Code: Use !analyze -v to get detailed debugging information. BugCheck D1, {0, 2, 0, fffff801ddcd6cb3} *** WARNING: Unable to verify timestamp for L1C63x64.sys *** ERROR: Module load completed but symbols could not be loaded for L1C63x64.sys *** WARNING: Unable to verify timestamp for afwcore.sys *** ERROR: Module load completed but symbols could not be loaded for afwcore.sys Probably caused by : L1C63x64.sys ( L1C63x64+6cb3 ) Followup: MachineOwner[/quote] Try uninstalling the Agnitum program and use Windows Firewall and see how it does.

 

Wow, thank you so much *Biggrin It worked!
I removed Bullguard, which had the Agnitum Firewall and no more BSODs for me. Thank you! ^^

 

Great. I am glad to hear you have the machine running correctly. If you have any further problems, just let us know.