IDE drives showing in device manager as SCSI drives
I've been trying to track a stability issue that has been developing over the past few weeks and has been getting increasingly worse. I'm getting a lot of input lag in games and even on the desktop, this is mostly things like the screen freezing in game while the mouse continues moving or ghost keyboard inputs/ignored keyboard inputs. Sometimes on the desktop I'll see the pointer freeze or the keyboard response slow down so that text appears a good second or more after hitting the key for the corresponding letter.
Looking through my events log I spotted some errors relating to my storage controllers so I looked in my device manager and found that I have the latest Microsoft Storage Spaces Controller and drilling into the Details I found in the class it says that I have a SCSIAdapter installed, I can't figure out why that's the case though. I don't have and JMicron or Marvell IDE controllers installed, as far as I know and to the best of my knowledge I am running my drives via the Intel drive controllers on the motherboard. I have tried installing the Intel Chipset drivers and Intel RAID drivers to see if I can persuade the mobo to show my drives as IDE, but it hasn't changed anything in the storage controllers section and my SSD and HHD are also showing as SCSI drives in the Properties for these drives using device manager.
The only other persistent error that's showing is for nvwgf2vmx.dll which is part of the nVidia drivers, but having tested a few games until they crash that particular dll didn't show in the error logs, but I did upgrade the drivers to the latest WHQL version from the nVidia website today. The only thing that I can see is that I am getting storage errors at around the same time as the game I am playing crashes. I have tested with BF4, Far Cry 3 and Just Cause 2. All games are crashing though I didn't notice input lag on JC2.
Any ideas on what I should try? Is it likely that the SCSI/IDE issue is at the root of my errors?
Re: IDE drives showing in device manager as SCSI drives
This thread has had 90+ views but nobody has been able to offer an opinion.
It looks like I am going to need to re-install Windows, which is not really an issue. What I need to know is how can I make sure that my new installation will install correctly using IDE drivers instead of SCSI?
Also, is it likely that the issues I have seen are what's causing my stability issues? My PC did run without issue for quite some after I last installed Windows as a fresh install, so I don't know if that's the cause or if there's some other problem behind the stability issues I've been facing.
Re: IDE drives showing in device manager as SCSI drives
I've never used storage spaces, but as its effectively a virtual disk solution that may be why you're seeing the disk as a scsi device.
Re: IDE drives showing in device manager as SCSI drives
Where exactly are you seeing it say SCSI?
I am wondering if this is a red herring.
Stuttering makes me want to check CPU temps, NIC drivers and BIOS.
Re: IDE drives showing in device manager as SCSI drives
Quote:
Originally Posted by
shaithis
Where exactly are you seeing it say SCSI?
I am wondering if this is a red herring.
Stuttering makes me want to check CPU temps, NIC drivers and BIOS.
In device manager, disk drive, then right clicking any of my drives to get into properties and selecting the details tab. Under details when I go through the drop down menu for Property the Device instance path shows my drives as:
Quote:
SCSI\DISK&VEN_CRUCIAL_&PROD_CRUCIAL_CT1024M5\4&15828421&0&010000
I'll investigate temperatures when I can get back to my PC, typically my CPU package temps at idle tend to sit at around 37 to 42 degrees C, not sure what my loaded temps are at the moment, but fairly confident that they weren't exceeding 65 degree when I last checked them under load.
I take it from the red herring remark that you feel that the SCSI/IDE issue is not the culprit behind my stability issues, if not there then what would you check first?
Re: IDE drives showing in device manager as SCSI drives
I'm pretty certain thats how windows shows all sata drives, both mine show the same.
Re: IDE drives showing in device manager as SCSI drives
Ok. In that case it must be something else.
Checked temps, and after 15 minutes of benchmark software running on my PC the temps went up to 60 degrees overall with core 1 getting to 61 degrees.
Re: IDE drives showing in device manager as SCSI drives
Ok, I think we can completely rule out SCSI as an issue, my other PC has it's SSD and HDDs configured as SCSI too.
Also while browsing YouTube just now I got the following error:
Quote:
SYSTEM_SERVICE_EXCEPTION
Which led to a forced restart, before restarting it saved some sort of log file but I don't know where it saved it to. So I guess now I need to find out what to do next. This what I found in my event viewer under Critical errors in the last hour:
Quote:
- System
- Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41
Version 3
Level 1
Task 63
Opcode 0
Keywords 0x8000000000000002
- TimeCreated
[ SystemTime] 2015-05-06T21:38:11.590338100Z
EventRecordID 15377
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8
Channel System
Computer DemonsKeyboard
- Security
[ UserID] S-1-5-18
- EventData
BugcheckCode 59
BugcheckParameter1 0xc0000005
BugcheckParameter2 0xfffff802ea651580
BugcheckParameter3 0xffffd00024464740
BugcheckParameter4 0x0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
**edit** I have got a fairly large Memory dump that was created, but I have no idea how to use it.
Plus I also found this under Warnings in my Event Viewer for the last hour:
Quote:
The driver \Driver\WudfRd failed to load for the device SWD\SensorsAndLocationEnum\LPSensorSWDevice.
It would be awesome if someone with special powers (like admin/mod powers as opposed to godly/inhuman superpowers) could move this thread to a more appropriate location on the boards.
Thanks.
But this is getting quite exciting as at least one possibility has been ruled out, I just need to rule out a stack more until I find the one that fixes my issue.