Analyze minidump

Hi all.

First off, i don’t know if i’m on the right place for ask my question, your site is really technical for me, i’m really lost on that many informations.

I’ve got an BSOD on Vista and Windows 7 only, due to my USB wireless adaptator driver sis163u.sys.

I’m running Windows 7 RC actually, i’m really happy with it for now, except this BSOD.I think he doesn’t appear on Windows 7, but …

Here are the analyze of th minidump, on Windows 7.I can try to analyze the Vista minidump if you preffer.

Someone can do a patch or something like that ?

I’m really bored by this problem, i’ve no problem on XP so far I remember, but for some reason, I need Vista.

Here is the analyze:

BugCheck D1, {4f, 2, 0, 91e1b66a}

*** ERROR: Module load completed but symbols could not be loaded for sis163u.sys
Probably caused by : sis163u.sys ( sis163u+1766a )

Followup: MachineOwner

1: 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: 0000004f, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 91e1b66a, address which referenced memory

Debugging Details:

READ_ADDRESS: GetPointerFromAddress: unable to read from 82970718
Unable to read MiSystemVaType memory at 82950160
0000004f

CURRENT_IRQL: 2

FAULTING_IP:
sis163u+1766a
91e1b66a 8b434f mov eax,dword ptr [ebx+4Fh]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: 8aca7c4c – (.trap 0xffffffff8aca7c4c)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=861844c8 edx=00000000 esi=8658700c edi=860ad000
eip=91e1b66a esp=8aca7cc0 ebp=8aca7cd4 iopl=0 nv up ei ng nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010296
sis163u+0x1766a:
91e1b66a 8b434f mov eax,dword ptr [ebx+4Fh] ds:0023:0000004f=???
Resetting default scope

LAST_CONTROL_TRANSFER: from 91e1b66a to 828437bb

STACK_TEXT:
8aca7c4c 91e1b66a badb0d00 00000000 91e1b09e nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
8aca7cd4 91e1b9d9 00000000 0058700c 8658700c sis163u+0x1766a
8aca7cec 91e27346 860ad000 8658700c 8658700c sis163u+0x179d9
8aca7d0c 91e0593d 000ad000 0000060c 40000100 sis163u+0x23346
8aca7d2c 91e067b4 0000007b 00000000 00000000 sis163u+0x193d
8aca7d50 82a02bc3 86184000 b0ce781e 00000000 sis163u+0x27b4
8aca7d90 828c5e29 91e064c4 86184000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

STACK_COMMAND: kb

FOLLOWUP_IP:
sis163u+1766a
91e1b66a 8b434f mov eax,dword ptr [ebx+4Fh]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: sis163u+1766a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: sis163u

IMAGE_NAME: sis163u.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45b83d3e

FAILURE_BUCKET_ID: 0xD1_sis163u+1766a

BUCKET_ID: 0xD1_sis163u+1766a

Followup: MachineOwner

Many thanks in advance, I hope I’m on the good place for ask my question, if i’m not, i’m really sorry.

Best regards.

PS: sorry for my bad english.

xxxxx@orange.fr wrote:

First off, i don’t know if i’m on the right place for ask my question, your site is really technical for me, i’m really lost on that many informations.

I’ve got an BSOD on Vista and Windows 7 only, due to my USB wireless adaptator driver sis163u.sys.

I’m running Windows 7 RC actually, i’m really happy with it for now, except this BSOD.I think he doesn’t appear on Windows 7, but …

Here are the analyze of th minidump, on Windows 7.I can try to analyze the Vista minidump if you preffer.

Someone can do a patch or something like that ?

There’s nothing we can do about this. You will have to go to the
vendor. It’s their problem. Are you allowing the system to send the
dump information to Microsoft each time it happens? You should
definitely make a habit of that. Each bug report gets forwarded on to
the vendor, so if you annoy them enough, maybe they will finally address
the problem.

There are lots of reports of this BSOD on the web. Make sure you have
the latest driver from sis.com. The last released version was 05/21/2007.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Thanks for your answer.

I send the dump to microsoft each time it happen, but no fix at this time.

I will try to contact sis, but i’m not sure they will help me.

I’ve the latest version of the driver, but no way to fix the BSOD, i’m really bored by that.

In any case, thanks for your help.

Best regards.

Sorry for the double post, I don’t find any link for contact sis on their site.So, I try to contact the manufacturer of my USB controller, i’m afraid there is no chance to fix my prob.

Thanks again.

Best regards.