Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD MULTIPLE crashes, mostly problem athr.sys ( athr + 428a5 ) HELP

16 Sep 2015   #1
abu2k15

windows 7 home premium 32bit
 
 
BSOD MULTIPLE crashes, mostly problem athr.sys ( athr + 428a5 ) HELP

hi guys i have experienced BSOD, i dont know much about how it happend but i have
this file to help u guys review it thank you.


My System SpecsSystem Spec
.
30 Sep 2015   #2
Laith

Windows 10 Professional x64
 
 

Hey there! You haven't enabled dumps, please do.
Dump Files - Configure Windows to Create on BSOD

Also snap a picture of the BSOD when it occurs.
My System SpecsSystem Spec
30 Sep 2015   #3
derekimo

Microsoft Community Contributor Award Recipient

 
 

Those are Windbg outputs from Minidumps,

Code:
Loading Dump File [C:\Windows\Minidump\091515-23197-01.dmp]
Code:
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\091515-23197-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18939.x86fre.win7sp1_gdr.150722-0600
Machine Name:
Kernel base = 0x8383d000 PsLoadedModuleList = 0x83988e30
Debug session time: Tue Sep 15 23:47:20.869 2015 (UTC + 1:00)
System Uptime: 0 days 0:05:12.773
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....

************* Symbol Loading Error Summary **************
Module name            Error
ntkrnlpa               The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
Unable to load image \SystemRoot\system32\DRIVERS\athr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {30, 2, 0, 8f2a38a5}

*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : athr.sys ( athr+428a5 )

Followup: MachineOwner
---------
Run the tool,

Blue Screen of Death (BSOD) Posting Instructions
My System SpecsSystem Spec
.

30 Sep 2015   #4
Laith

Windows 10 Professional x64
 
 

Oh, then it means that the Atheros Extensible Wireless LAN driver is acting up, update it.
My System SpecsSystem Spec
01 Oct 2015   #5
abu2k15

windows 7 home premium 32bit
 
 

yh i updated it but that didnt help, for me what worked was changing my network connection from our home 1 to my nieghbors. it turns out whenever i use my house one i get bsod but when using his one its alll good LOL
My System SpecsSystem Spec
01 Oct 2015   #6
Laith

Windows 10 Professional x64
 
 

That means it might be a problem with your router, this isn't the appropriate section for networking but if you want to fix it you can always post a thread in the networking topic.
My System SpecsSystem Spec
Reply

 BSOD MULTIPLE crashes, mostly problem athr.sys ( athr + 428a5 ) HELP




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD ,error 0x000000D1, athr.sys
i m frequently getting a blue screen of dead with error 0x000000D1, i tried registry cleaner as well as i formatted my system once but still the same problem appears frequently, i m using windows 7 ultimate 32 bit on my notebook compaq presario cq42 ................pls help me out from this Thnaks
BSOD Help and Support
BSOD, Random Reboot, ATHR.SYS
Over the last 2 days, I get the BSOD with an error message during the crash dump identifying "ATHR.SYS" as a problem. It began yesterday with my PC shutting down and not rebooting itself. Today, the PC shuts down and attempts to reboot itself, sometimes successfully and sometimes turning off an...
BSOD Help and Support
Frequent BSOD's (athr.sys) during normal usage.
Alright, so here's the lowdown: This started yesterday, and before this began my laptop ran normally and I like to game a lot. I use my laptop mainly for playing League of Legends, and the occasional web browsing. I have been running my laptop nonstop for the past couple of weeks or so, as a...
BSOD Help and Support
BSOD athr.sys - happening constantly
HELP!! I keep getting this error. I did a Google search and found several threads about it, some in this forum. I updated the drivers as others were told, and it has not helped. I am leaving to go to Chicago today for work and I really need my laptop functioning for the next 3 days. I hope that...
BSOD Help and Support
BSOD - While Turning on WiFi - athr.sys
Dear Sir/Madam. I'm running Windows 7 Ultimate SP1 X86bit on my HP Pavilion DV5 1235EE laptop. Today i tried to turn on/Enable my Wireless on my laptop. It's a touch button on my HP DV5 1235EE laptop which turns to 'Blue' when enabled and 'organge' when disabled. This button is used to...
BSOD Help and Support
BSOD at start-up (athr.sys)
Hi there, I'm running Windows 7 Ultimate (32 bit) and have started experiencing frequent BSODs, often during start-ups, but also after proper start-ups, at seemingly random times while the computer is being used. I've managed to catch the file name "athr.sys" in most of the BSODs, although I do...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 14:57.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App