Comment #3 on issue 5826 by [email protected]: BSOD on vista triggered by
Chrome
http://code.google.com/p/chromium/issues/detail?id=5826
I haven't received a minidump from the original poster, but Hernán (from
comment 1 above) sent me his.
Hernán, thank you for the minidump.
This blue screen doesn't look Chrome-specific to me. The process crashing
is avgnsx.exe (AVG Internet Security) with a call stack
that leads into Sacm2A.sys causing a blue screen. A Google search for this
driver revealed that it is a Scientific-Atlanta USB
cable modem driver, and looking at the callstack it seems the drivers for
it haven't been updated since mid-year 2004:
8f600000 8f603800 Sacm2A T (no symbols)
Loaded symbol image file: Sacm2A.sys
Image path: \SystemRoot\system32\DRIVERS\Sacm2A.sys
Image name: Sacm2A.sys
Timestamp: Thu Jun 10 05:42:36 2004 (40C8573C)
CheckSum: 0000EFC0
ImageSize: 00003800
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
My recommendation to you would be to update the drivers if you are using
the modem and uninstall the drivers if you are not. If
it still crashes after updating the drivers I would provide a new minidump
to Scientific-Atlanta.
For posterity, here is the analysis from the minidump.
Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Kernel base = 0x81c4c000 PsLoadedModuleList = 0x81d63c70
Debug session time: Thu Mar 5 03:40:31.859 2009 (GMT-8)
System Uptime: 0 days 0:09:23.694
BugCheck D1, {6, 2, 0, 828a40e4}
Unable to load image \SystemRoot\system32\DRIVERS\Sacm2A.sys, Win32 error
0n2
*** WARNING: Unable to verify timestamp for Sacm2A.sys
*** ERROR: Module load completed but symbols could not be loaded for
Sacm2A.sys
*** WARNING: Unable to verify timestamp for VMNetSrv.sys
*** ERROR: Module load completed but symbols could not be loaded for
VMNetSrv.sys
*** WARNING: Unable to verify timestamp for avgtdix.sys
*** ERROR: Module load completed but symbols could not be loaded for
avgtdix.sys
Probably caused by : Sacm2A.sys ( Sacm2A+cd8 )
Followup: MachineOwner
---------
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: 00000006, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 828a40e4, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 81d83868
Unable to read MiSystemVaType memory at 81d63420
00000006
CURRENT_IRQL: 2
FAULTING_IP:
ndis!NdisQueryBuffer+11
828a40e4 f6460605 test byte ptr [esi+6],5
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: avgnsx.exe
TRAP_FRAME: b6ba5184 -- (.trap 0xffffffffb6ba5184)
ErrCode = 00000000
eax=00000000 ebx=b6ba5250 ecx=b6ba5220 edx=000009c0 esi=00000000
edi=b6ba5220
eip=828a40e4 esp=b6ba51f8 ebp=b6ba5200 iopl=0 nv up ei ng nz na po
nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010282
ndis!NdisQueryBuffer+0x11:
828a40e4 f6460605 test byte ptr [esi+6],5
ds:0023:00000006=??
Resetting default scope
LAST_CONTROL_TRANSFER: from 828a40e4 to 81ca6d24
STACK_TEXT:
b6ba5184 828a40e4 badb0d00 000009c0 86e40102 nt!KiTrap0E+0x2ac
b6ba5200 8f600cd8 00000000 b6ba5220 b6ba5240 ndis!NdisQueryBuffer+0x11
WARNING: Stack unwind information not available. Following frames may be
wrong.
b6ba5224 8f600c46 86e40008 84eb6d58 000002ba Sacm2A+0xcd8
b6ba5264 8f600b2d 00000002 86e3e0e8 84eb6d58 Sacm2A+0xc46
b6ba527c 829458e1 86e40008 b6ba52fc 00000000 Sacm2A+0xb2d
b6ba52a4 82943cb3 b6ba5300 b6ba52fc 00000001
ndis!ndisMSendPacketsXToMiniport+0x141
b6ba52dc 82945792 86e4ec50 b6ba52fc 00000001 ndis!ndisMSendPackets+0x1b4
b6ba52f0 82b8a55e 86e4ec50 84eb6d58 84d7c468 ndis!ndisMSend+0x13
b6ba5330 82945883 86e4bb2c 84d7c468 00000082 VMNetSrv+0x355e
b6ba535c 82945707 b6ba537c b6ba537c 00000000
ndis!ndisMSendPacketsXToMiniport+0xe3
b6ba53c4 82877585 865470e8 853ca500 00000000
ndis!ndisMSendNetBufferListsToPackets+0x84
b6ba53e4 828775a8 853ca500 853ca500 00000000
ndis!ndisFilterSendNetBufferLists+0x8b
b6ba53fc 8f6864ab 86e51008 853ca500 00000000
ndis!NdisFSendNetBufferLists+0x18
b6ba5478 82877638 86e52008 853ca500 00000000
pacer!PcFilterSendNetBufferLists+0x233
b6ba5494 8294264a 853ca500 853ca500 00000000 ndis!ndisSendNBLToFilter+0x87
b6ba54b8 82a661ae 86cd8c50 853ca500 00000000
ndis!NdisSendNetBufferLists+0x4f
b6ba5500 82a65d8c 86e51a78 00000000 00000000 tcpip!FlSendPackets+0x399
b6ba5540 82a6599b 82acac68 00000000 00000000 tcpip!IppFragmentPackets+0x201
b6ba5578 82a6778b 82acac68 b6ba5694 616c7049
tcpip!IppDispatchSendPacketHelper+0x252
b6ba5618 82a66bff 00ba5694 b6ba57d8 851bd008
tcpip!IppPacketizeDatagrams+0x8fd
b6ba5778 82a5fcab 00000000 00000007 82acac68
tcpip!IppSendDatagramsCommon+0x5f9
b6ba5798 82a54c01 8563c2a0 b6ba57b0 8563c2a0 tcpip!IpNlpSendDatagrams+0x4b
b6ba5820 82a4631d 8563c2a0 b6ba5914 84f55578 tcpip!IppSlowSendDatagram+0x31
b6ba587c 82a47b20 8563c2a0 00000001 b6ba5914
tcpip!IpNlpFastSendDatagram+0x47f
b6ba5970 82a4c18d 00000000 00000000 b6ba59a4 tcpip!TcpTcbSend+0x4aa
b6ba5980 82a4c03d 851f8008 872d30f8 00000000
tcpip!TcpEnqueueTcbSendOlmNotifySendComplete+0x13f
b6ba59a4 82a4c269 001f8008 b6ba5a00 00000000 tcpip!TcpEnqueueTcbSend+0x27d
b6ba59bc 8f3a9ad9 851f8008 b6ba5a00 8516b8b8 tcpip!TcpTlConnectionSend+0x1e
b6ba5a1c 8f3aea77 001e1160 8516b8b8 8516b970 tdx!TdxSendConnection+0x1d7
b6ba5a38 81d07fd3 86a97440 8516b8b8 8516b8b8
tdx!TdxTdiDispatchInternalDeviceControl+0x115
b6ba5a50 8f3bb259 8542c6f8 86abe8f0 b6ba5a70 nt!IofCallDriver+0x63
b6ba5a60 8f3bb5aa 86abe8f0 8516b8b8 b6ba5a88 avgtdix+0x2259
b6ba5a70 81d07fd3 86abe8f0 8516b8b8 8516bfa0 avgtdix+0x25aa
b6ba5a88 8f62b405 39dbccb3 b6ba5b54 00000001 nt!IofCallDriver+0x63
b6ba5aec 8f61b52b 854347f8 b6ba5b44 00000284 afd!AfdFastConnectionSend+0x28c
b6ba5c58 81e989be 8514b801 00000001 02effbc0
afd!AfdFastIoDeviceControl+0x512
b6ba5d00 81e82a8d 86aaf900 00000534 00000000 nt!IopXxxControlFile+0x2cf
b6ba5d34 81ca3a1a 00000524 00000534 00000000 nt!NtDeviceIoControlFile+0x2a
b6ba5d34 77219a94 00000524 00000534 00000000 nt!KiFastCallEntry+0x12a
02effc14 00000000 00000000 00000000 00000000 0x77219a94
STACK_COMMAND: kb
FOLLOWUP_IP:
Sacm2A+cd8
8f600cd8 ?? ???
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Sacm2A
IMAGE_NAME: Sacm2A.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 40c8573c
SYMBOL_NAME: Sacm2A+cd8
FAILURE_BUCKET_ID: 0xD1_Sacm2A+cd8
BUCKET_ID: 0xD1_Sacm2A+cd8
Followup: MachineOwner
---------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
