- Thread Author
-
- #1
Hi,
I have recently had a run of BSODs all with different causes. They all seem to have the same readout for BugCheck (BugCheck 1E). It all seemed to start after I ran disk cleaner and disk defragmenter. I will upload all four minidumps. We have also had some network virus issues on another PC in the house. I cannot specify an exact cause, so I hope you can help me with this.
Thanks,
Rob.
I have recently had a run of BSODs all with different causes. They all seem to have the same readout for BugCheck (BugCheck 1E). It all seemed to start after I ran disk cleaner and disk defragmenter. I will upload all four minidumps. We have also had some network virus issues on another PC in the house. I cannot specify an exact cause, so I hope you can help me with this.
Thanks,
Rob.
Attachments
Solution
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+fa )
Followup: MachineOwner
out of the four dump file...
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+fa )
Followup: MachineOwner
out of the four dump file sent three were memory corruption and one, the above, blames wifi. I doubt you have a memory issue and is probably down to a driver namely the one below:
athrxusb.sys Mon Jan 29 12:57:10 2007: Atheros Wireless LAN USB device driver please update:
Link Removed
AppleCharger.sys Mon Jan 10 09:57:29 2011: GIGABYTE On/Off Charge driver this can cause bsod on some systems. Try uninstalling to test.
If after making the above changes you still get a bsod then please download the latest copy of memtest86 here:
http://www.memtest.org/
Although a little old this guide explains how best to use it:
http://www.techspot.com/community/topics/tutorial-how-to-use-memtest.62524/
Post any new dump files.
- Thread Author
-
- #3
Thanks for the fast reply. I updated my network driver, because I remembered that it installed old drivers over the new ones. I do have another dump file that you can have a look at. I believe it will say much the same as the ones before.
Thanks again.
Thanks again.
Attachments
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
Probably caused by : athrxusb.sys ( athrxusb+500d1 )
Followup: MachineOwner
---------
athrxusb.sys Mon Jan 29 12:57:10 2007