BSOD When Shutting Down, BAD_POOL_HEADER

This Is So Strange. No BSOD Happened To Me Before.
This Is My First BSOD

I Was In My PC. I Shutdown The PC Before Sleep.
And Guess What? It Appeared When The PC Shutdown.
I Know My Family Had A BSOD Once With This PC.
Found Out That Time HDD Was Corrupt.

And This Time ( I Used NirSoft´s Blue Screen View ) I Used sfc /scannow
And It Found Some Corrupt Files. But It Must Be Driver Issues. Hers The BSOD Display:

BAD_POOL_HEADER
0x00000019
Caused By Driver: ntoskrnl.exe

Strangely I Shutdown The PC, RIGHT After Avast! Free Anti-Virus Was Installed.
Im Gonna Later Edit This Post To See The sfc /scannow log.

EDIT: Past Time My Family Had A BSOD, I Ran a chkdsk check.
It Was Taking Too Long . So I Forced Shutdown.
I Reinstalled Windows 7 After That. I Formatted My Partitons, Deleted Them.
And Created New. Don´t Know If This Time Its HDD Corruption.

ANOTHER EDIT: Windows 7 Acess Denies Me When I Try To View Dump Files
Or CBS Logs. And I Am An Adminstrator. I Only Managed To View DMP Via Blue Screen View.
I Cannot Also View The sfc /scannow log.

Hello Darkus, and welcome to Seven Forums.

Please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions, and post back with the needed information. One of our BSOD experts should be by later when able to further help. :)

Download and install Drivers for Atheros AR9285 and Windows 7.

Follow Driver Install - Device Manager to install the driver.

Let us know the results.
-----------------------------------------------

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {22, fffffa80044f9000, 0, 0}

*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+11da )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000022, 
Arg2: fffffa80044f9000
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x19_22

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d13100
GetUlongFromAddress: unable to read from fffff80002d131c0
 fffffa80044f9000 Nonpaged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80002a6f4ce to fffff80002adbbc0

STACK_TEXT:  
fffff880`09cd0838 fffff800`02a6f4ce : 00000000`00000019 00000000`00000022 fffffa80`044f9000 00000000`00000000 : nt!KeBugCheckEx
fffff880`09cd0840 fffff800`02c0f54a : 00000000`00000000 fffff880`09cd0990 fffff880`09cd0910 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x72e6
fffff880`09cd08d0 fffff880`01470195 : fffffa80`03c95b30 fffffa80`0447f000 00000000`00000000 fffffa80`00000000 : nt!ExFreePoolWithTag+0x46a
fffff880`09cd0980 fffff880`06a411da : fffffa80`044f9000 fffff880`06a6f3d1 00000000`00000000 fffffa80`053e01a0 : ndis!NdisFreeMemory+0x15
fffff880`09cd09b0 fffffa80`044f9000 : fffff880`06a6f3d1 00000000`00000000 fffffa80`053e01a0 fffffa80`044f9000 : athrx+0x11da
fffff880`09cd09b8 fffff880`06a6f3d1 : 00000000`00000000 fffffa80`053e01a0 fffffa80`044f9000 fffffa80`03c95b30 : 0xfffffa80`044f9000
fffff880`09cd09c0 00000000`00000000 : fffffa80`053e01a0 fffffa80`044f9000 fffffa80`03c95b30 00000000`00000000 : athrx+0x2f3d1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrx+11da
fffff880`06a411da ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  athrx+11da

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrx

IMAGE_NAME:  athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a2ea4b9

FAILURE_BUCKET_ID:  X64_0x19_22_athrx+11da

BUCKET_ID:  X64_0x19_22_athrx+11da

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x19_22_athrx+11da

FAILURE_ID_HASH:  {b1ff1005-046b-2210-ff7f-2d93fe9a731c}

Followup: MachineOwner
---------

0: kd> lmvm athrx
start             end                 module name
fffff880`06a40000 fffff880`06b98000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Tue Jun 09 23:36:49 2009 (4A2EA4B9)
    CheckSum:         0015FE99
    ImageSize:        00158000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

DarkusFoxyn said:

But I Do Not Think The Wireless Driver Caused It.

Troubleshooting is based on facts, on on thinking. If you want to pay importance to thinking over fact, it is your choice. :)