Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD with SCSIPORT.SYS

01 Jun 2011   #1
gweglarz

Windows 7 64 Professional
 
 
BSOD with SCSIPORT.SYS

I am geting bsods with a scsiport.sys error. I have a Sil3124 card in the machine and sometimes I have to boot with the external cases turned off or it stops after the BIOS screen. As soon as I turn them on after the system boots, BSOD.

The cases are Lacie Biggest S2S and I use that software to configure the RAID boxes, instaed of using the SIL 3124 BIOS. I recently took 5x500GB drives and spanned them to RAID 0. I can configure the drive in the VDS for the 2320GB. I have 5 1TB drives in the other Lacie box. I used the Laice software to have them configured (through the Lacie software) as Raid 10 with a hot spare. (It used to work with RAID 10)

I recently changed it to RAID 0 for 4560GB. I created the drive as GUID and it did work, but intermitently reboote3d.

I have an Alienware Auora 6 core I7 980x
OEM Windows 7 Ultimate installed.
18GB of new RAM.


I have only had the system since January and just had the MOBO swapped out today (it failed last week)


I am trying to see if the problem is with SIL 3124 and the drivers, or some problem with the Windows drivers. This also happened in another computer with the same OS where I swapped out the card and drives into the test machine. This machine also has an internal SIL 3132.


Here is my zip file.


Thanks,

Geoffrey


My System SpecsSystem Spec
.
01 Jun 2011   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by gweglarz View Post
I am geting bsods with a scsiport.sys error. I have a Sil3124 card in the machine and sometimes I have to boot with the external cases turned off or it stops after the BIOS screen. As soon as I turn them on after the system boots, BSOD.

The cases are Lacie Biggest S2S and I use that software to configure the RAID boxes, instaed of using the SIL 3124 BIOS. I recently took 5x500GB drives and spanned them to RAID 0. I can configure the drive in the VDS for the 2320GB. I have 5 1TB drives in the other Lacie box. I used the Laice software to have them configured (through the Lacie software) as Raid 10 with a hot spare. (It used to work with RAID 10)

I recently changed it to RAID 0 for 4560GB. I created the drive as GUID and it did work, but intermitently reboote3d.

I have an Alienware Auora 6 core I7 980x
OEM Windows 7 Ultimate installed.
18GB of new RAM.


I have only had the system since January and just had the MOBO swapped out today (it failed last week)


I am trying to see if the problem is with SIL 3124 and the drivers, or some problem with the Windows drivers. This also happened in another computer with the same OS where I swapped out the card and drives into the test machine. This machine also has an internal SIL 3132.


Here is my zip file.


Thanks,

Geoffrey
Not SCSIPORT at all PCTCORE64.sys. I would remove it

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\060111-48063-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03404000 PsLoadedModuleList = 0xfffff800`03649e90
Debug session time: Wed Jun  1 16:44:59.119 2011 (GMT-4)
System Uptime: 0 days 0:06:10.523
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
.......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880014e2591, fffff88003d31898, fffff88003d310f0}

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

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880014e2591, The address that the exception occurred at
Arg3: fffff88003d31898, Exception Record Address
Arg4: fffff88003d310f0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
SCSIPORT!memmove+1d1
fffff880`014e2591 668b040a        mov     ax,word ptr [rdx+rcx]

EXCEPTION_RECORD:  fffff88003d31898 -- (.exr 0xfffff88003d31898)
ExceptionAddress: fffff880014e2591 (SCSIPORT!memmove+0x00000000000001d1)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003d310f0 -- (.cxr 0xfffff88003d310f0)
rax=000000000000766f rbx=000000000000766f rcx=fffffa80166306d8
rdx=6e6f6ef45311e1f6 rsi=fffffa8016629000 rdi=00000000000076da
rip=fffff880014e2591 rsp=fffff88003d31ad8 rbp=fffff88003d31bb0
 r8=000000000000766f  r9=0000000000000000 r10=0200002002050000
r11=fffffa801662906b r12=fffffa801662906b r13=000000000000766f
r14=0000000000000000 r15=fffffa800f0f91a0
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
SCSIPORT!memmove+0x1d1:
fffff880`014e2591 668b040a        mov     ax,word ptr [rdx+rcx] ds:002b:6e6f6974`6974e8ce=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b50e8
 ffffffffffffffff 

FOLLOWUP_IP: 
PCTCore64+11c31
fffff880`015afc31 ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880014f4250 to fffff880014e2591

STACK_TEXT:  
fffff880`03d31ad8 fffff880`014f4250 : 00000000`00000000 fffffa80`125c6000 fffffa80`0e8f0668 00000000`00000000 : SCSIPORT!memmove+0x1d1
fffff880`03d31ae0 fffff880`014f3fd3 : fffff6fb`7ea00598 fffff6fd`400b3148 00000000`0f0f91a0 00000000`00000000 : SCSIPORT!SpBuildDeviceDescriptor+0x228
fffff880`03d31b80 fffff880`014dcb37 : fffffa80`000076da fffffa80`0e8f0550 fffffa80`0f0f91a0 fffffa80`0f0f9050 : SCSIPORT!ScsiPortQueryPropertyPdo+0xd7
fffff880`03d31bb0 fffff880`015afc31 : fffffa80`0f272040 fffffa80`0f2721a0 fffff880`015c0148 fffffa80`0f272190 : SCSIPORT!ScsiPortPdoDeviceControl+0x1bb
fffff880`03d31be0 fffffa80`0f272040 : fffffa80`0f2721a0 fffff880`015c0148 fffffa80`0f272190 fffffa80`16621000 : PCTCore64+0x11c31
fffff880`03d31be8 fffffa80`0f2721a0 : fffff880`015c0148 fffffa80`0f272190 fffffa80`16621000 00000000`00000000 : 0xfffffa80`0f272040
fffff880`03d31bf0 fffff880`015c0148 : fffffa80`0f272190 fffffa80`16621000 00000000`00000000 fffffa80`0f272040 : 0xfffffa80`0f2721a0
fffff880`03d31bf8 fffffa80`0f272190 : fffffa80`16621000 00000000`00000000 fffffa80`0f272040 fffff880`015a5c35 : PCTCore64+0x22148
fffff880`03d31c00 fffffa80`16621000 : 00000000`00000000 fffffa80`0f272040 fffff880`015a5c35 00000000`00000000 : 0xfffffa80`0f272190
fffff880`03d31c08 00000000`00000000 : fffffa80`0f272040 fffff880`015a5c35 00000000`00000000 fffffa80`0e8f0550 : 0xfffffa80`16621000


SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  PCTCore64+11c31

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PCTCore64

IMAGE_NAME:  PCTCore64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cfff70b

STACK_COMMAND:  .cxr 0xfffff88003d310f0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_PCTCore64+11c31

BUCKET_ID:  X64_0x7E_PCTCore64+11c31

Followup: MachineOwner
---------
My System SpecsSystem Spec
02 Jun 2011   #3
gweglarz

Windows 7 64 Professional
 
 

That may be a problem, and I'll remove it, but that doesn't seem to explain why the system will BSOD after I turn on the external drive. The system runs fine as long as the drive case with the RAID 0 2300GB setup is off. As soon as I turn it on, the system will BSOD with the SCSISTOR error in the BSOD.
My System SpecsSystem Spec
.

02 Jun 2011   #4
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by gweglarz View Post
That may be a problem, and I'll remove it, but that doesn't seem to explain why the system will BSOD after I turn on the external drive. The system runs fine as long as the drive case with the RAID 0 2300GB setup is off. As soon as I turn it on, the system will BSOD with the SCSISTOR error in the BSOD.
Can only read the DMP with more of them a trend may develop
My System SpecsSystem Spec
Reply

 BSOD with SCSIPORT.SYS




Thread Tools




Similar help and support threads
Thread Forum
Driver_Power_State_Failure (scsiport.sys) after Sleep
Hello there, just ran into this BSOD. Looked into the minidump and the files that caused the crash are ntoskrnl.exe+81e7a and scsiport.sys+1f9b4. I don't get it. I don't have any SCSI devices. :sarc: How can I find out which device is responsible for this? minidump ist in the attachment.
BSOD Help and Support
SCSIPORT.SYS Bluescreen?
Earlier this morning I got the BSOD. Nirsoft BSV points to SCSIPORT.SYS. I haven't been able to find any relevant help from googling. Can anyone help with reading the attached BSOD files? I just did a clean install a couple of days ago. Thanks, Ed
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 13:02.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App