blue screen/crash while using winupdate

Grev_michal

Gooday/evening all.

I hope you can help me with this, im not very clever with these things - however I did manage to run the debug tool to see the dmp file.

But the result dosent mean anything to me, hopefully one of you can decipher it and maybe pinpoint a solution.

In advance thank you for your time

Michal


Motherboard:
Asus A7N8X-E Deluxe

Bios version:
ASUS A7N8X-E Deluxe ACPI BIOS Rev 1013 (award phoenix)

Harddisken:
ST380013 AS SCSI Disk Device (Barracuda 7200.7 SATA 80013)

Driver version:
5.1.2535.0

SCSI- og RAID-controllere:
Silicon Image SiI 3112 SATARaid Controller

Driver Version 1.0.0.33


The dmp:

Microsoft Windows XP [version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Michal Greve Nielsen>cd c:\programmer\debugging tools
for windows

C:\Programmer\Debugging Tools for Windows>windbg -y symbolpath -i imagepath -z d
umpfilepath

C:\Programmer\Debugging Tools for Windows>kd -y srv*c:\symbols*http://msdl.micro
soft.com/download/symbols -i c:\windows\servicepackfiles\i386 -z c:\windows\mini
dump\mini052806-01.dmp

Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\minidump\mini052806-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: c:\windows\servicepackfiles\i386
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sun May 28 05:21:22.515 2006 (GMT+2)
System Uptime: 0 days 0:04:21.116
Loading Kernel Symbols
................................................................................
........................................
Loading User Symbols
Loading unloaded module list
........
Unable to load image si3112r.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for si3112r.sys
*** ERROR: Module load completed but symbols could not be loaded for si3112r.sys

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

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {2a, 6, 0, f7463afb}

Probably caused by : si3112r.sys ( si3112r+7afb )

Followup: MachineOwner

---

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: 0000002a, memory referenced
Arg2: 00000006, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f7463afb, address which referenced memory

Debugging Details:

---

READ_ADDRESS: 0000002a

CURRENT_IRQL: 6

FAULTING_IP:
si3112r+7afb
f7463afb 80792a00 cmp byte ptr [ecx+0x2a],0x0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f7468802 to f7463afb

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b8ac9720 f7468802 00000002 0000000a 00000000 si3112r+0x7afb
b8ac9774 f745e1c3 82eec004 f7b8c5fc b8ac99d8 si3112r+0xc802
b8ac97a0 f74458eb 82eec004 b8ac9900 b8ac99d8 si3112r+0x21c3
b8ac97c4 804da6ed 82f0ea30 00000002 82f0eae8 SCSIPORT!SpStartIoSynchronized+0x14
f
b8ac9804 806f13cc 82f0ea30 82066008 00000000 nt!KeSynchronizeExecution+0x17
b8ac9830 8052d065 82f0e6c0 82f0ea64 00000001 hal!HalAllocateAdapterChannel+0x126

b8ac9848 f744764d 82f0e6c0 82f0ea30 00000001 nt!IoAllocateAdapterChannel+0x2a
b8ac9880 804e3e9d 82f0ea30 82066008 82f0eae8 SCSIPORT!ScsiPortStartIo+0x23f
b8ac98a0 f7446d04 82f0ea30 82066008 00000000 nt!IoStartPacket+0xa1
b8ac98d4 f7445726 82f0ea30 0006609c b8ac99d8 SCSIPORT!ScsiPortFdoDispatch+0x270
b8ac98f0 f7448d50 82f0daf0 82066008 82f0daf0 SCSIPORT!SpDispatchRequest+0x68
b8ac990c f7444469 82f0da38 82066008 82f0f240 SCSIPORT!ScsiPortPdoScsi+0xec
b8ac9920 804e37f7 82f0da38 82066008 82066008 SCSIPORT!ScsiPortGlobalDispatch+0x1
d
b8ac9930 f74464e6 82f0eae8 b8ac99d8 82066008 nt!IopfCallDriver+0x31
b8ac9944 f7446bac 82f0ea30 82066008 82f0daf0 SCSIPORT!SpRerouteLegacyRequest+0x7
c
b8ac9970 f7444469 82f0ea30 8206609c 82f0f240 SCSIPORT!ScsiPortFdoDispatch+0x118
b8ac9984 804e37f7 82f0ea30 82066008 828ced38 SCSIPORT!ScsiPortGlobalDispatch+0x1
d
b8ac9994 f7450ca3 828ced38 828ceda8 82f0eae8 nt!IopfCallDriver+0x31
b8ac9a1c f7451073 82f0eae8 828ced38 82f0daf0 SCSIPORT!SpSendMiniPortIoctl+0x137
b8ac9a3c f7444469 82f0ea30 828ced38 82f0f240 SCSIPORT!ScsiPortFdoDeviceControl+0
x1f5
b8ac9a50 804e37f7 82f0ea30 828ced38 828ced38 SCSIPORT!ScsiPortGlobalDispatch+0x1
d
b8ac9a60 f7448bff 00000000 828ced38 828ced38 nt!IopfCallDriver+0x31
b8ac9a74 f7444469 82f0da38 828ced38 82f0f240 SCSIPORT!ScsiPortPdoDeviceControl+0
xc1
b8ac9a88 804e37f7 82f0da38 828ced38 828ced38 SCSIPORT!ScsiPortGlobalDispatch+0x1
d
b8ac9a98 f7591e05 00000000 8284fbac b8049c01 nt!IopfCallDriver+0x31
b8ac9ab8 f7596b76 82f0da38 828ced38 8284fb78 CLASSPNP!ClassSendIrpSynchronous+0x
3e
b8ac9ad4 f757faa0 00000000 82f0da38 8284fb78 CLASSPNP!ClassSendDeviceIoControlSy
nchronous+0x145
b8ac9b7c f759047f 82eeb9c0 828995d0 82899688 disk!DiskDeviceControl+0x46a
b8ac9b98 804e37f7 82eeb9c0 828995d0 828995d0 CLASSPNP!ClassDeviceControlDispatch
+0x48
b8ac9ba8 f77b9667 828996ac 82fc91e0 00000000 nt!IopfCallDriver+0x31
b8ac9bd4 804e37f7 82f66020 828995d0 828996d0 PartMgr!PmDeviceControl+0x8c
b8ac9be4 8059ceb5 82120b60 829a9f70 b8ac9c34 nt!IopfCallDriver+0x31
b8ac9bf4 8059ce63 829a9f70 828995d0 828996ac nt!RawReadWriteDeviceControl+0x60
b8ac9c34 804e37f7 829a9eb8 828995d0 806ee2d0 nt!RawDispatch+0x114
b8ac9c44 8056a101 828996ac 821167a8 828995d0 nt!IopfCallDriver+0x31
b8ac9c58 80579a8a 829a9eb8 828995d0 821167a8 nt!IopSynchronousServiceTail+0x60
b8ac9d00 8057bfa5 000002dc 00000000 00000000 nt!IopXxxControlFile+0x611
b8ac9d34 804de7ec 000002dc 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
b8ac9d34 7c90eb94 000002dc 00000000 00000000 nt!KiFastCallEntry+0xf8
00a1ee8c 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
si3112r+7afb
f7463afb 80792a00 cmp byte ptr [ecx+0x2a],0x0

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: si3112r+7afb

MODULE_NAME: si3112r

IMAGE_NAME: si3112r.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3ed7e3b9

FAILURE_BUCKET_ID: 0xD1_si3112r+7afb

BUCKET_ID: 0xD1_si3112r+7afb

Followup: MachineOwner

---

RichD

Hi,

I seem to be having exactly the same problem. I have the same motherboard and hard disk and I get the blue screen dump after Windows boots up. I am running Windows XP SP 2. If I boot into Safe mode it seems to work fine but I cant use normal mode. I have downloaded the latest nvidia nforce drivers but that does not seem to help.

Does anyone have any idea what could be causing this or how to solve it?

Thanks,

Rich

kryyst

The problem seems to be with a corrupted sata driver, or possibly the wrong one was installed. Unfortunately the only way I know of fixing it is to do a clean install with the right driver.

RichD

That was my first thought. Which is why I updated the nforce drivers (the sata driver comes bundelled with nforce). I have now downloaded the latest driver from Silicon Image and bios update. The thing I dont understand is why it should work in safe mode? Surely it uses the same driver? This leads me to believe it is possibly some sort of conflict with another driver which is active in normal mode but not in safe mode.

I have done a bit of reading and it seems that this is quite a common fault with Asus Mboards.

kryyst

Looks like you've read all the same articles I did