Windows 7: Recurring BSOD, need help

EduardoYayo · 20 Sep 2010

Hello everyone, I just registered here so i can get some help with this very annoying problem. You see, i have been getting bsods very frequently (2 every day). I have found that when i check out the report in Blue Screen View, ntoskrnl.exe is ALWAYS there, sometimes accompanied by other system files. I really need help, but all i can provide is this one dump file. Reason being i performed a reinstall of Windows 7 Ultimate and i performed a disk clean, and i cleaned all of my .dmp files thinking i wouldn't need them since i thought the problem would be fixed. Well, I was wrong. I even performed an sfc /scannow to check for corrupt files, some were found and fixed. But apparently that was not enough. I have no clue what the solution to this is, and help very much appreciated. Thank you!

Capt.Jack Sparrow · 20 Sep 2010

Hello and Welcome !

Seems like athr.sys i.e. Atheros Wireless LAN Driver as caused the System to crash. Please go to their website or Laptop manufactures website and install the latest version of Driver. Check this website ATHEROS drivers for Microsoft Windows

Follow this guide for Driver Cleanup https://captaindebugger.wordpress.com/drivers/

Bugcheck:

Code:

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 40010022, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8726c254, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 81d7a700
Unable to read MiSystemVaType memory at 81d5a0c0
 40010022 

CURRENT_IRQL:  2

FAULTING_IP: 
ndis!ndisIndicateStatusInternal+59f
8726c254 ad              lods    dword ptr [esi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  81d394f8 -- (.trap 0xffffffff81d394f8)
ErrCode = 00000000
eax=87250000 ebx=8463d0e0 ecx=00000028 edx=81d397e4 esi=40010022 edi=8463d0e0
eip=8726c254 esp=81d3956c ebp=81d39680 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
ndis!ndisIndicateStatusInternal+0x59f:
8726c254 ad              lods    dword ptr [esi]      ds:0023:40010022=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8726c254 to 81c53b7b

STACK_TEXT:  
81d394f8 8726c254 badb0d00 81d397e4 00000003 nt!KiTrap0E+0x2cf
81d39680 8721f4f2 8463d0e0 81d397e4 00000002 ndis!ndisIndicateStatusInternal+0x59f
81d396e0 877e320c 009f37f0 81d397e4 81d3974c ndis!NdisFIndicateStatus+0x43b
81d396f0 8721f48a 845b6e08 81d397e4 81d397e4 wfplwf!FilterStatus+0x14
81d3974c 87332776 00d0c350 81d397e4 81d399d8 ndis!NdisFIndicateStatus+0x3d3
81d39764 8721f48a 84d10f68 81d397e4 851caca8 pacer!PcFilterStatus+0x70
81d397c0 a14d35db 001caca8 81d397e4 85109b18 ndis!NdisFIndicateStatus+0x3d3
81d3982c a14b52bb 851d2010 40030008 81d399d8 nwifi!ExtSTAIHVSpecificIndication+0x49f
81d3984c a14baaef 851c9698 40030008 81d399d8 nwifi!Dot11ForwardStatusIndication+0x49
81d39870 8721f48a 851c9698 81d3996c 84a2ae50 nwifi!Pt6Status+0x151
81d398cc 877ed2b2 00d0f1a0 81d3996c 81c708c0 ndis!NdisFIndicateStatus+0x3d3
81d398e8 8726d765 84a2a448 81d3996c 81d22d82 vwififlt!FilterStatus+0x6c
81d39940 8be7fc0a 8463d002 81d3996c 0023c6b8 ndis!NdisMIndicateStatusEx+0x4f6
WARNING: Stack unwind information not available. Following frames may be wrong.
81d39954 8bea2bc7 845b7020 81d3996c 00000000 athr+0x4c0a
81d399bc 8be9f981 845b7020 40030008 00000000 athr+0x27bc7
81d399f4 8bea136f 845b7020 8530cb50 00000002 athr+0x24981
81d39a90 8bea1645 845b7020 00000001 81d39aac athr+0x2636f
81d39aa0 8be9dfec 845b7020 81d39aec 8be9e1bf athr+0x26645
81d39aac 8be9e1bf 845b7020 00000000 81d22d82 athr+0x22fec
81d39aec 8bebaaf2 00000000 845b7020 00000000 athr+0x231bf
81d39b08 87214774 00000000 845b7210 00000000 athr+0x3faf2
81d39b38 81c72497 84497d48 00497d10 5fa8b4b6 ndis!ndisMTimerObjectDpc+0xbc
81d39b7c 81c7243b 81d3cd20 81d39ca8 00000002 nt!KiProcessTimerDpcTable+0x50
81d39c68 81c722f8 81d3cd20 81d39ca8 00000000 nt!KiProcessExpiredTimerList+0x101
81d39cdc 81c7068e 00024b18 8525f030 81d46240 nt!KiTimerExpiration+0x25c
81d39d20 81c704b8 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
81d39d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndis
    8726c20c-8726c215  10 bytes - ndis!ndisIndicateStatusInternal+557
    [ 89 8d 10 ff ff ff 8b 8b:08 0a 2c 00 00 22 69 95 ]
    8726c217-8726c3b3  413 bytes - ndis!ndisIndicateStatusInternal+562 (+0x0b)
    [ 00 89 8d 14 ff ff ff 8b:24 37 ad 48 40 00 24 37 ]
423 errors : !ndis (8726c20c-8726c3b3)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

Hope this helps,
Captain

EduardoYayo · 20 Sep 2010

Hello, Captain (loved those movies), thank you so very much for your help! It WAS that driver that was outdated. I just downloaded the new updated version and bam, no more crashes. Sorry for the sort of late reply and i hope you come back to check back on this thread to see you just saved me lots of frustration and research! Again, THANK YOU!!!

richc46 · 20 Sep 2010

No worries, the good Captain will be notified that there was a reply and he will see that you are grateful, like so many of us are.

EduardoYayo · 20 Sep 2010

haha yes yes, very helpful. And your sig helped me too! Now i know you can give good rep! Thanks to you two for helping newbies like me

Capt.Jack Sparrow · 20 Sep 2010

Your Most Welcome Mate ! Glad that you got it fix.

Thanks for reporting back, which most of them fail to do so.

- Captain

richc46 · 20 Sep 2010

Capt. I get about 20% reporting back and 90% of those are the problems.

Capt.Jack Sparrow · 20 Sep 2010

Quote: Originally Posted by richc46

Capt. I get about 20% reporting back and 90% of those are the problems.

It's sad that people won't respond if they get it fixed. Atleast there are few of them who value our suggestions that care to come back and report.

Windows 7: Recurring BSOD, need help

Recurring BSOD, need help problems?