Bsod system_thread_exception_not_handled

[Glaros]

(while i was writing here another BSOD appeared)

computer is "old" (2009), after many BSOD at windows xp and windows 7 ultimate x64 I installed windows 7 ultimate x86 a week ago. I was prepared for BSOD and after my personal research I uninstalled the display driver, windows installed and installed by myself the original from ati site. all were fine (5-6 days now) since today.
i had utorrent open downloading and when I returned i saw the minidump files open and everything closed.then after some minutes while i was writing here and everything was closed except firefox another BSOD!

OS: Windows 7 ultimate x64
CPU: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz 3.17GHz
RAM: 4.00 GB (3.00 GB usable)* *first time I see that, last days I could use all 4GB! (?!)*
GPU: ASUS EAH5850 1GB DDR5

BlueScreenView says:
Caused by driver atikmdag.sys
atikmpag.sys
dxgkrnl.sys
NETIO.SYS
ntkrnlpa.exe
tcpip.sys

I have my minidumps attached for you
btw why I can't use all 4GB RAM ? I could some days ago

 

[Glaros]

I could use all 4GB because I had windows ultimate x64 right ? silly me.. nevermind with that!

Looking forward to your search
George

 

[Glaros]

anyone guys ? :/

 

[yowanvista]

BSODs caused by your display driver, the problem lies in your Graphics card or RAM, it is hardware related
http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
If the RAM is ok then the cause is the HD5850, a RMA would be necessary

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {85188310, 90529d68, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+5d68 )


VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 85188310, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 90529d68, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+5d68
90529d68 8bff            mov     edi,edi

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8eaefba4 906bac26 00000116 85188310 90529d68 nt!KeBugCheckEx+0x1e
8eaefbc8 906bba45 90529d68 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
8eaefbec 906eb92c 00000000 00000000 8eaefcb0 dxgkrnl!TdrIsRecoveryRequired+0xb8
8eaefc64 90712c1d fffffcfb 0003a744 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8eaefc90 906f2993 871ca458 8eaefcb0 00000102 dxgmms1!VidSchWaitForCompletionEvent+0x16f
8eaefd28 907173c9 00000000 82a793c1 871ca458 dxgmms1!VidSchiScheduleCommandToRun+0x14d
8eaefd3c 90717485 871ca458 00000000 87290410 dxgmms1!VidSchiRun_PriorityTable+0xf
8eaefd50 82c4b9df 871ca458 a0f4fb25 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8eaefd90 82afd219 90717406 871ca458 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+5d68
90529d68 8bff            mov     edi,edi

SYMBOL_NAME:  atikmpag+5d68

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dae3541

FAILURE_BUCKET_ID:  0x116_IMAGE_atikmpag.sys

BUCKET_ID:  0x116_IMAGE_atikmpag.sys

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

 

[Glaros]

thanks yowanvista for your reply. I will run Memtest86+ now.
I got another BSOD from my last visit here, I uploaded the minidump file.
brb with the results from Memtest

 

[Glaros]

Hello again yowanvista.
Memtest was running for 16 hours yesterday as i fell asleep
After 16 hours of testing and 14 passes found 1 error at 9th pass at the 3rd test I believe.
So what should I do next ? Test each stick of RAM separately ?

 

[wish]

Hello again yowanvista.
Memtest was running for 16 hours yesterday as i fell asleep
After 16 hours of testing and 14 passes found 1 error at 9th pass at the 3rd test I believe.
So what should I do next ? Test each stick of RAM separately ?

Yes test each stick individually.
Also test each slot with a known good stick to find out whether there is any bad mobo slot.

 

[Glaros]

Yes test each stick individually.
Also test each slot with a known good stick to find out whether there is any bad mobo slot.

Hello again!
I am back with wierds news. My mb has 4 slots, 2 blue, 2 pink.. I checked both of my RAM at first slot(blue) and after 27 and 19 passes nothing showed up, no error. I was like damn.. motherboard must be the problem but at the third slot(second blue) memtest hasnt shown an error either after 17 passes now..
How is that possible ? anyone experienced enough here with a theory ?
what should I do next ?!

 

[wish]

Hello again!
I am back with wierds news. My mb has 4 slots, 2 blue, 2 pink.. I checked both of my RAM at first slot(blue) and after 27 and 19 passes nothing showed up, no error. I was like damn.. motherboard must be the problem but at the third slot(second blue) memtest hasnt shown an error either after 17 passes now..
How is that possible ? anyone experienced enough here with a theory ?
what should I do next ?!

Did you have another BSOD since then?
Would be better to follow this instruction and collect more files:
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[Glaros]

hello again.
I have only 1 stick of RAM connected since I don't spend so time with the computer nowadays and today I returned home to see that another BSOD had appeared.
i have attached the minidump file can you please check it again ?
its so annoying trying to find whats happening and can't find the actual problem :S

 

[Glaros]

another 2 BSOD, can anyone please check the files ?

 

[Glaros]

anyone ? please

 

[Glaros]

and another one

 

[wish]

Hello Glaros, I apologize for late reply

For troubleshooting the problem, please uninstall AVG then replace it with MSE.
Virus, Spyware & Malware Protection | Microsoft Security Essentials

Perform System File Cheker:
Right click cmd.exe → run as administrator then type sfc /scannow

Update your NIC driver:

Rt86win7.sys Thu Feb 26 01:04:22 2009 → [URL="http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=7&PFid=10&Level=3&Conn=2"]Realtek Networking Driver[/URL]

Also it would be good to install Windows 7 SP 1.
Learn how to install Windows 7 Service Pack 1 (SP1)

LOG

Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0x82a53000 PsLoadedModuleList = 0x82b9b810
Debug session time: Thu Jul 28 16:36:10.409 2011 (GMT-8)
System Uptime: 0 days 11:33:43.954
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {7, 2, 8, 7}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Xdpc_Signal+22 )

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

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

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: 00000007, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000007, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82bbb718
Unable to read MiSystemVaType memory at 82b9b160
 00000007 

CURRENT_IRQL:  2

FAULTING_IP: 
+66b6952f0091d840
00000007 ??              ???

PROCESS_NAME:  System

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  82b79bbc -- (.trap 0xffffffff82b79bbc)
ErrCode = 00000010
eax=00000001 ebx=85b7a028 ecx=00000001 edx=00000000 esi=8dd38b32 edi=85b7a720
eip=00000007 esp=82b79c30 ebp=85b7a720 iopl=0         nv up ei ng nz ac po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010292
00000007 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 00000007 to 82a997fb

FAILED_INSTRUCTION_ADDRESS: 
+66b6952f0091d840
00000007 ??              ???

STACK_TEXT:  
82b79bbc 00000007 badb0d00 00000000 00000002 nt!KiTrap0E+0x2cf
WARNING: Frame IP not in any known module. Following frames may be wrong.
82b79c2c 82b79c48 8dd38b8e 85b7a028 85b7a720 0x7
82b79c30 8dd38b8e 85b7a028 85b7a720 00000000 nt!KiDoubleFaultStack+0x2c48
82b79c48 8dd38792 85b7a028 85b7a720 00000000 USBPORT!USBPORT_Xdpc_Signal+0x22
82b79c78 82abb4f5 85b7ac74 85b7a028 00000000 USBPORT!USBPORT_IsrDpc+0x1d3
82b79cd4 82abb358 82b7cd20 82b86280 00000000 nt!KiExecuteAllDpcs+0xf9
82b79d20 82abb178 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82b79d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_Xdpc_Signal+22
8dd38b8e ff75fc          push    dword ptr [ebp-4]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  USBPORT!USBPORT_Xdpc_Signal+22

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc871

FAILURE_BUCKET_ID:  0xD1_CODE_AV_BAD_IP_USBPORT!USBPORT_Xdpc_Signal+22

BUCKET_ID:  0xD1_CODE_AV_BAD_IP_USBPORT!USBPORT_Xdpc_Signal+22

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

 

[Glaros]

hello again wish!
I am currently doing all the things you told me.
btw I dont use the realtek device, I use one U.S.Robotics should I disable it ?
and the service pack for my 32bit version is windows6.1-KB976932-X86.exe 537.0 MB right ?

 

[Glaros]

hello again wish, I did everything you suggested but sadly another BSOD today. can you check if we missed anything ?

 

[wish]

Hi Glaros,
Your latest dump file point to atikmdag.sys that using improper addresses.
So I would suggest you to reinstall your Graphic Drivers.
Use Driver Sweeper to remove current VGA driver, then download and install a fresh copy.
Phyxion.net - Driver Sweeper
AMD.com | Support & Downloads

Then let me know the result.

LOG

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x82a4e000 PsLoadedModuleList = 0x82b974d0
Debug session time: Wed Aug 10 14:32:16.241 2011 (GMT-8)
System Uptime: 0 days 0:04:21.786
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {3d60b04, 2, 1, 8e4d5dbc}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmdag.sys ( atikmdag+2badbc )

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

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

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: 03d60b04, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8e4d5dbc, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82bb7848
Unable to read MiSystemVaType memory at 82b96e20
 03d60b04 

CURRENT_IRQL:  2

FAULTING_IP: 
atikmdag+2badbc
8e4d5dbc c1e603          shl     esi,3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  8c6ab16c -- (.trap 0xffffffff8c6ab16c)
ErrCode = 00000002
eax=00000001 ebx=86a7c0a4 ecx=86a7c000 edx=00000001 esi=00000001 edi=8c6ab234
eip=8e4d5dbc esp=8c6ab1e0 ebp=8c6ab1e8 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00250202
atikmdag+0x2badbc:
8e4d5dbc c1e603          shl     esi,3
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8e4d5dbc to 82a8f5cb

STACK_TEXT:  
8c6ab16c 8e4d5dbc badb0d00 00000001 00000003 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
8c6ab1e8 8e4d6003 86a7c0c8 86a7c001 8c6ab2d8 atikmdag+0x2badbc
8c6ab208 8e4caee8 86a7c0a4 868bc2c0 86a7c010 atikmdag+0x2bb003
8c6ab21c 8e4cc2e9 8c6ab234 868fd580 868bc2c0 atikmdag+0x2afee8
8c6ab2c4 8e4e993e 016ab2d8 8c6aba48 8c6aba04 atikmdag+0x2b12e9
8c6ab324 8e4e96dd 8c6ab950 868fd7a0 00000018 atikmdag+0x2ce93e
8c6ab9c0 8e22a973 8d70c1fc 86d688d8 8c6aba60 atikmdag+0x2ce6dd
8c6aba28 8d6cf5e8 859dfc00 8c6aba48 82a1c6ee atikmdag+0xf973
8c6aba94 8d70c0db 859dfc00 8c6abaf0 86d6f8d8 atikmpag+0x55e8
8c6ababc 8d70bf9b 8c6abaf0 8c6abad8 8d7c20d5 dxgkrnl!DXGADAPTER::DdiSubmitCommand+0x49
8c6abac8 8d7c20d5 86d6c000 8c6abaf0 8c6abb64 dxgkrnl!DXGADAPTER_DdiSubmitCommand+0x10
8c6abad8 8d7cb4ea 8c6abaf0 86d703f0 86d6f000 dxgmms1!DXGADAPTER::DdiSubmitCommand+0x11
8c6abb64 8d7f2529 0000000b 868c0310 86d703f0 dxgmms1!VidSchiSendToExecutionQueue+0x7d6
8c6abbdc 8d7f2e99 86d55788 00000001 868c0310 dxgmms1!VidSchiSendToExecutionQueueWithWait+0x115
8c6abd18 8d7f3141 008c0310 868bb008 8c6abd3c dxgmms1!VidSchiSubmitRenderCommand+0x809
8c6abd28 8d7f33de 868c0310 82a8550e 86d55788 dxgmms1!VidSchiSubmitQueueCommand+0x61
8c6abd3c 8d7f3485 86d55788 00000000 86d53c48 dxgmms1!VidSchiRun_PriorityTable+0x24
8c6abd50 82c56f64 86d55788 a4e8065a 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8c6abd90 82aff219 8d7f3406 86d55788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+2badbc
8e4d5dbc c1e603          shl     esi,3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  atikmdag+2badbc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ddc6b3c

FAILURE_BUCKET_ID:  0xD1_atikmdag+2badbc

BUCKET_ID:  0xD1_atikmdag+2badbc

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

 

[Glaros]

I replaced the display drivers after I removed everything with drive sweeper. meanwhile I had another BSOD but I think I figured out the problem, I think its the drivers from my U.S. robotics adapter and since I failed to find online new drivers I went to device manager and windows downloaded automatically.

thanks again

 

[wish]

Hello,
Your latest dump point to Network Adapter Driver.
I would suggest you to update its driver or disable the Network Device for testing purpose.
Then see how things go.

Log

Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x82a1b000 PsLoadedModuleList = 0x82b644f0
Debug session time: Tue Aug 16 04:47:33.035 2011 (GMT-8)
System Uptime: 0 days 0:07:33.580
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 1, 8ee9a3e9}

Unable to load image \SystemRoot\system32\DRIVERS\bcmwl6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bcmwl6.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl6.sys
Probably caused by : bcmwl6.sys ( bcmwl6+733e9 )

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

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

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: 00000028, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8ee9a3e9, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82b84848
Unable to read MiSystemVaType memory at 82b63e40
 00000028 

CURRENT_IRQL:  2

FAULTING_IP: 
bcmwl6+733e9
8ee9a3e9 83672800        and     dword ptr [edi+28h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  82b4276c -- (.trap 0xffffffff82b4276c)
ErrCode = 00000002
eax=86dcff1d ebx=85c94e00 ecx=85d60098 edx=00000000 esi=86dcff1d edi=00000000
eip=8ee9a3e9 esp=82b427e0 ebp=82b427e8 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
bcmwl6+0x733e9:
8ee9a3e9 83672800        and     dword ptr [edi+28h],0 ds:0023:00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8ee9a3e9 to 82a5c5db

STACK_TEXT:  
82b4276c 8ee9a3e9 badb0d00 00000000 00000000 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
82b427e8 8ee74d55 867a7800 86dcff1d 867a7800 bcmwl6+0x733e9
82b427fc 8ee78666 867a7800 8c953000 86dcff00 bcmwl6+0x4dd55
82b42814 88cce5bf 867a7800 86dcff00 00000000 bcmwl6+0x51666
82b4282c 8c94baf3 86853420 86dcff00 00000000 ndis!NdisFReturnNetBufferLists+0x4c
82b4284c 8c94bb87 85c94e00 86dcff00 00000001 vwififlt!FilterReturnNetBufferListsCommon+0x67
82b42870 88cce5bf 85c94448 86dcff00 00000000 vwififlt!FilterReturnNetBufferLists+0x55
82b42888 9353df0c 86ef97e8 86dcff00 00000000 ndis!NdisFReturnNetBufferLists+0x4c
82b428a0 9353b67a 876394f0 86bce008 86dcff00 nwifi!NetTrcGetNetBufferListCorrelationGuid+0x264
82b428c0 9353e695 86bce008 876394f0 00000001 nwifi!Dot11RecvCompletion+0x2a
82b428d4 9355b886 86bce008 876394f0 00000000 nwifi!MP6ReturnNBL+0x1b
82b42900 9353d40c 00000001 82b42920 00000001 nwifi!ExtSTAReceivePacket+0x1c2
82b42950 9353e40e 86bce008 935681a0 85c94e50 nwifi!WPP_SF_qdd+0x358
82b42974 88cce56a 85833c08 876394f0 00000000 nwifi!Pt6Receive+0x14a
82b42990 88cce504 86853420 86dcff00 00000000 ndis!ndisFilterIndicateReceiveNetBufferLists+0x46
82b429ac 8c94bc85 86853420 86dcff00 00000000 ndis!NdisFIndicateReceiveNetBufferLists+0x2f
82b429d8 88cf2553 85c94454 86dcff00 00000000 vwififlt!FilterReceiveNetBufferLists+0xcf
82b42a00 88c9dc78 85a530e0 86dcff00 00000000 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x62
82b42a28 8ee78a2f 85a530e0 86dcff00 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x52
82b42aa8 8ee7bbf3 00000001 8693b000 00000000 bcmwl6+0x51a2f
82b42acc 8ee34dfb 000000c2 8693b000 86a3dfac bcmwl6+0x54bf3
82b42b64 8ee46a8e 856e4000 0000000c 86a3dfac bcmwl6+0xddfb
82b42ba8 8ee4753b 856e4000 86418098 86a3d8a4 bcmwl6+0x1fa8e
82b42bd8 8ee486ed ffffffff 82b42c40 867a7800 bcmwl6+0x2053b
82b42bf4 8ee7b984 00008000 00000000 00000000 bcmwl6+0x216ed
82b42c14 88cf289a 867a79c0 00000000 82b42c40 bcmwl6+0x54984
82b42c50 88c9da0f 868506d4 008506c0 00000000 ndis!ndisMiniportDpc+0xe2
82b42c78 82a931b5 868506d4 868506c0 00000000 ndis!ndisInterruptDpc+0xaf
82b42cd4 82a93018 82b45d20 82b4f380 00000000 nt!KiExecuteAllDpcs+0xf9
82b42d20 82a92e38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82b42d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
bcmwl6+733e9
8ee9a3e9 83672800        and     dword ptr [edi+28h],0

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  bcmwl6+733e9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bcmwl6

IMAGE_NAME:  bcmwl6.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49cc24c8

FAILURE_BUCKET_ID:  0xD1_bcmwl6+733e9

BUCKET_ID:  0xD1_bcmwl6+733e9

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

 

[Glaros]

hi again,
sadly another BSOD caused by my graphic card it seems