Scsiport.sys errors

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I got a Kernel_data_inpage_error yesterday mentioning scsiport.sys and the
code 0x0000007A. The error stayed on the screen until I pressed enter. When
the system restarted, I got another error with code 0x0000007E. One of these
error messages told me to update my BIOS, which I have already done. When I
turned on my computer today, the screen said something about not being able
to read from the bootable drive. My SATA hard drive has this desrciption in
XP: WDC WD80 0JD -55JRC0 SCSI Disk Device. I even have a SCSI properties tab.
There are no SCSI symbols or connectors on the drive itself. It is using a
driver provided by Microsoft, as the drive came with no drivers of its own.
The SATA connectors on my motherboard are controlled by SiS RAID/SCSI
controller software. In the system log of Event Viewer, I have several
warnings in a row called disk, the description says: "An error was detected
on device \Device\Harddisk0\D during a paging operation. Event ID 51." I also
have sporadic errors about SiSRaid, the description reads: "The description
for Event ID ( 9 ) in Source ( SiSRaid ) cannot be found. The local computer
may not have the necessary registry information or message DLL files to
display messages from a remote computer. You may be able to use the
/AUXSOURCE= flag to retrieve this description; see Help and Support for
details. The following information is part of the event:
device\Scsi\SiSRaid1."

Thanks, lrh381b2
 
In windows,SCSI & RAID are sometimes the same,& actually they are in most
ways.Youre SATA hd is connected thru a RAID/SCSI controller,next time you
install xp,press the F6 option & install the drivers from a floppy for the
controller.
Download the drivers from SIS for the controller on the MB,you probably can
at this time,update the chipset drivers,& the controller drivers from SIS.
 
I'm not sure that the controller is the problem. The controller (SiS 180 RAID
Controller) recognizes the drive as ATA, not SCSI. Windows thinks the drive
is SCSI, I even have a "SCSI Properties" tab on the properties window when I
click on my HDD in Device Manager. That is probably because Windows gives
drivers to all hardware components before manufacturer drivers and software
can be installed.
 
I occasionaly get unmountable boot volume errors and a blank scren after
POST. I ran memtest without any problems. I have Vista Business installed in
VPC 2007 (beta) which has caused an 8 GB piece of my HDD to be fragmented,
disk defragmenter can't defrag it. I get errors inside Vista sometimes too.
Will a fragmented disk cause these problems? I think the problem is in my
cheap mobo, HDD, or HDD cable. The connection between the cable and the mobo
has some play in it.
 
Back
Top