📎 AI Summary:
The thread discusses a recurring Windows blue screen issue experienced by the original poster, who has been troubleshooting by enabling dump files and updating drivers. A responder identifies the probable cause as a driver related to anodlwfx.sys, advises running system scans, updating BIOS, and replacing certain drivers, including Avast antivirus. The original poster reports implementing some recommendations, such as installing MSE and updating drivers, and plans to continue monitoring for further BSODs. The overall tone is collaborative, focusing on diagnosing and resolving the driver-related crash.
The thread discusses a recurring Windows blue screen issue experienced by the original poster, who has been troubleshooting by enabling dump files and updating drivers. A responder identifies the probable cause as a driver related to anodlwfx.sys, advises running system scans, updating BIOS, and replacing certain drivers, including Avast antivirus. The original poster reports implementing some recommendations, such as installing MSE and updating drivers, and plans to continue monitoring for further BSODs. The overall tone is collaborative, focusing on diagnosing and resolving the driver-related crash.
Solution
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,160
Hi Arodes,
Unfortunately no dump files were present in the zip file which probably means your system isn't configured to produce them. Dump files are created when the machine bsods and we use these to determine the cause of the blue screen.
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click and apply to exit the dialogs.
Once the machine bsod's again then run the app or check the main Windows folder for a folder marked 'Minidump'.
In the meantime I can tell you that 'anodlwfx.sys' relates to a ALPHA Networks Filter Driver and I'd try to update it if possible:
http://www.alphanetworks.com/
Unfortunately no dump files were present in the zip file which probably means your system isn't configured to produce them. Dump files are created when the machine bsods and we use these to determine the cause of the blue screen.
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click and apply to exit the dialogs.
Once the machine bsod's again then run the app or check the main Windows folder for a folder marked 'Minidump'.
In the meantime I can tell you that 'anodlwfx.sys' relates to a ALPHA Networks Filter Driver and I'd try to update it if possible:
http://www.alphanetworks.com/
So today I got the bluescreen again but when I tried to do what you listed above after I clicked ok and apply settings I get this message: It is probably not possible to register all details that can help you identify system errors because your current file is disabled or smaller than 1MB. (rough translation) As a result I'm still not able to find the dump file.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,160
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff88004de5069, 2, 0, fffff880044bf850}
*** WARNING: Unable to verify timestamp for anodlwfx.sys
*** ERROR: Module load completed but symbols could not be loaded for anodlwfx.sys
Probably caused by : anodlwfx.sys ( anodlwfx+2850 )
Followup: MachineOwnerthe above Bugcheck is usually driver related and is blaming anodlwfx.sys:
anodlwfx.sys Fri Mar 06 10:10:08 2009: ALPHA Networks Filter Driver.
This is a driver supplied by Microsoft and is part of the drivers which come with windows. There is a possibility that something else is causing this driver to crash and going through your system step by step will hopefully find and fix the culprit.
First let's see if your os is corrupt. Find command prompt in the start menu, right click on it and run as admin. Type:
sfc /scannow
Press enter and await results.
Looking over your system updates I notice you do have driver updates which I'll point out below and this:
BiosVersion = 0906
BiosReleaseDate = 03/26/2012
The latest Bios was released in 2013 and stands at 2105. I would consider updating the Bios but do make sure my information is correct before going ahead.
http://www.asus.com/Motherboards/P8Z77M/HelpDesk_Download/
aswRdr2.sys Fri Mar 20 11:44:46 2015: Avast AV, known on occasion to cause the odd issue. If the bsod continues consider replacing with MSE:
http://windows.microsoft.com/en-GB/windows/security-essentials-download
HECIx64.sys Mon Jul 02 23:14:58 2012: Intel Management Engine Interface
iaStor.sys Wed Nov 30 03:39:19 2011: Intel Storage drivers
iusb3hcs.sys Thu Jan 05 11:56:40 2012: Intel USB 3
Please run the Intel driver update utility:
Link Removed
Rt64win7.sys Tue Sep 27 15:50:33 2011: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet please update:
Link Removed
RTKVHD64.sys Tue Jan 03 10:51:09 2012: Realtek HiDef Audi driver please update:
Link Removed
Try updating the above and see how you go. Also do make sure Windows is fully updated too.
Post any new dump files
Ok I did the scan and my OS is not corrupt. I have replaced avast with MSE and downloaded all drivers you linked. I have not updated my Bios because I'm not sure how to do that. I will let you know if I get another BSOD.
Similar threads
- Article
- Article
- Article