System drive reverted to PIO-After adding new HD

surg

Junior Member
Oct 9, 2010
15
0
0
Hey guys,

I have a Gigabyte- GA-ep45-ds3r motherboard which has 6 sata ports. Up until now i have had 5 sata drives installed without much problem however, yesterday i installed a brand new Seagate 1TB as my 6th drive which went into (sata-4) socket and now my System drive is stuck in PIO transfer mode.

The weird thing is, when i check the respective IDE channel in device manager it says Device 0 is running PIO and Device 1 is running UDMA-5.


Using Nero info tool my drive configuration looks like this:

Primary IDE channel: Master- sony dvd-rom - DMA : on
Slave- Sony dvd-rom DMA : on

Secondary IDE channel:

Primary IDE channel:Master - Seagate - DMA: off
Slave - Western digital - DMA: on

Secondary IDE channel:Master - Seagate - DMA: on
Slave - Seagate - DMA: on


Primary IDE channel: Master - Seagate - DMA: on

Secondary IDE channel:Master - Seagate - DMA: on

Primary IDE channel: Master - UM4733J XXXXXX < don't know what this is.


Since i don't have much options in the bios apart from running in AHCI mode which gives me BSOD, i have my Sata set to Native IDE which has always worked.

I get the feeling and logic tells me the system drive diden't like me adding the new drive, although the new drive is functioning flawlessly, i don't get it.

Please help, i can't even play games with my system drive in PIO. :'(
 

sub.mesa

Senior member
Feb 16, 2010
611
0
0
Check SMART data on both HDDs and check for UDMA CRC Error Count. If the data value (raw value) of this property is NOT ZERO, then you have cabling problems, which cause Windows to revert to PIO.

So check SMART data and if it indeed is non-zero, replace the cables. Note that poor quality power adapters may also cause such issues.
 

tommo123

Platinum Member
Sep 25, 2005
2,617
48
91
this used to happen to me in the long long ago time

never had probs with errors as far as my day to day experience went but there were probs somewhere. changing cables didnt help. i just ended up uninstalling the controller, reboot, windows reinstalls it and i'm back on DMA again.
 

surg

Junior Member
Oct 9, 2010
15
0
0
Check SMART data on both HDDs and check for UDMA CRC Error Count. If the data value (raw value) of this property is NOT ZERO, then you have cabling problems, which cause Windows to revert to PIO.

So check SMART data and if it indeed is non-zero, replace the cables. Note that poor quality power adapters may also cause such issues.

Hey sub.mesa,

I have SMART technology enabled in the bios, but have no idea how to access the data, i'll have a closer look tomorrow when i'm fresh.

Btw, when i was searching for SMART data i found system errors in Computer management-event viewer, they are as follows:

Warning - Disk
Error - atapi

There are multitudes of the same events, at any rate thank you for your reply hopefully i can sort it out when i wake up. ;)


this used to happen to me in the long long ago time

never had probs with errors as far as my day to day experience went but there were probs somewhere. changing cables didnt help. i just ended up uninstalling the controller, reboot, windows reinstalls it and i'm back on DMA again.

Hey Tommo,

This isen't the first time this has happened and that was the method i used before to get back onto UDMA mode, however that was a long time ago and i forgot what exactly i need to remove, i just don't want to loose all my data in the process.

But thanks for reminding me about it, to me it sounds very likely that its just the driver that needs resetting.
 

tweakboy

Diamond Member
Jan 3, 2010
9,517
2
81
www.hammiestudios.com
This is a rough one. What I would try is uninstalling motherboard drivers,, Intel chipset drivers or nVidia whichever one your using.

Then reinstall the mobo drivers and I hope that solves this issue.

Also after uninstalling the mobo drivers before you reboot go to Device Manager and remove all the IDE stuff you see and your hard drives, "dont worry they will get detected and come back after boot.

Soo then after booting then install mobo drivers and reboot hope this fixes you up. Let us know.
 
Last edited:

surg

Junior Member
Oct 9, 2010
15
0
0
Hey guys,

Reporting back with findings.

I went with Tommo's method and uninstalled the problematic IDE controller but it diden't go as smooth as anticipated.

After a reboot my windows loading screen hung for a while and windows eventually started up, then before everything could render i got a BSOD error which i recorded the code for.

I then turned off my machine and fiddled around with the power adapter and re-seated the Sata cables. Started back up and all seems well and my system drive is now running UDMA. :awe:



This is a rough one. What I would try is uninstalling motherboard drivers,, Intel chipset drivers or nVidia whichever one your using.

Then reinstall the mobo drivers and I hope that solves this issue.

Also after uninstalling the mobo drivers before you reboot go to Device Manager and remove all the IDE stuff you see and your hard drives, "dont worry they will get detected and come back after boot.

Soo then after booting then install mobo drivers and reboot hope this fixes you up. Let us know.


Hey Tweakboy,


This motherboard has been nothing but trouble since i got it, actually took me 2 weeks to sort out driver problems and BIOS settings.

To this date my ram still won't run at rated speed no matter how i set it. At the time of purchase everyone who bought this model and variants were all on this forum by the hundreds with the same problems.

I dare not touch any of the motherboard drivers as it took so long to get it stable. Don't get me wrong it is a sensible idea and especially since my windows installation is over 3 years old.

This is the last time i buy a Gigabyte board, i only bought it because it was the only thing available at the time. Asus boards are the way to go in my opinion, will be getting one when i format so i don't have to deal with this horrible board again.


Thank you all very much for great advice and info, hope this doesen't happen again any time soon. ;)