DVD drive problem - DMA

Okay, first off, I did try everything I have knowledge of before I resorted to ask for help.

I recently built a new computer, everything works fine except for one thing, I can't enable Ultra DMA 4 on my DVD drive. (PIO transfer mode works fine.) When I enable it by having Windows uninstall and install my secondary IDE controller, explorer crashes and reverts to PIO. I checked the jumper setting on the DVD drive, it was set to master (It's the only DVD drive in this PC, and on the second IDE controller.)

There's nothing I can do, and burning/reading DVDs is really slow and makes everything lock up if I'm doing anything else ;_; Please help, and thanks for any replies.

My epeen (specs):
ASUS K8N-DL nForce 4 motherboard
Dual AMD Opteron 242
1GB ECC RAM
DVD drive - LITEON SHW-160P6S
GeForce 7300LE (If it matters...)

;_; Someone said to install my RAID drivers, I updated it with the one's on Nvidia's site even though I installed the nForce drivers, didn't work. ;_;

My computar/ properties/ device manager/hardware.

Browse down to whatever IDE channel its on and ENABLE DMA under the settings.

This only works if you use REAL MANLY BEARDED IDE CAYBULZ.
If youve got shitty ide cables you wont be able to support it.

Yeah, I know how to enable it. I guess the cables that came with the ASUS motherboard aren't manly enough. I happen to have another IDE cable. I'll try that.

OP here. Okay, so I used the IDE cable that came with my Rosewill IDE controller card. Same results as the other IDE cable.

Okay, that leaves it to 2 possible errors. It's either the controller or the drive. I'll just connect the DVD drive to my IDE controller card, and see what happens (First I need an extention cable) If that doesn't work, it's the drive, and I'll just buy another drive.

Thread over, I guess.

are those soem 80 conductor IDE cables or the shitty 40 conductor ones?

40 = ERRONEOUS.

Bios settings also may affect things

>>6

Not sure, they're probably the 80 conductor ones because they work fine with my hard drives.

If you have only one drive on the cable, but a cable with 3 connectors, did you used the far end?

Here is a quote from pcguide.com, it's a great page btw:
"it is not a good idea to connect a single drive to the middle connector on a ribbon cable, because the "stub" of left-over, unconnected cable causes signaling problems. With Ultra DMA this "stub" connection is not just "not recommended", it is illegal: a single device must be at the end of the cable. The other reason is that since these cables support cable select inherently, the position of each drive on the cable matters if cable select is being used. With these two needs combined, it just made sense to design the cable so that drive positioning was explicitly clear."

sauce: http://www.pcguide.com/ref/hdd/if/ide/conf_Cable80.htm

Oh yeah, they have a page on udma that you might find useful too:
http://www.pcguide.com/ref/hdd/if/ide/modes_UDMA.htm

by chance are you using DvDFab decryptor?

I recently had a prob. where dvdfab was changing my dvd drives from dma to PIO. I uninstalled dvdfab, then
My computer--Properties--Hadrware--device Manager--IDE ATA/ATAPI controller (then select the paralle ATA controller and instead of uninstall, just press DEL key) then reboot and let windows re-install IDE ATA/ATAPI controller.

>>10

No, I've never heard of it.

>>8

I just noticed, I had the damn cable backwards. I'm an idiot, I was in a rush building my PC that I overlooked that. I'm going to see if DMA works now.

No, it's just as before. DMA doesn't work. Reverted to PIO.

PIO sucks, install Linux and you won't have to worry about this.

Maybe try using/buying a new ide cable.

Have you looked into dmafix

http://72.14.253.104/search?q=cache:nyEXUHbOn6QJ:club.cdfreaks.com/showthread.php%3Ft%3D73257+dmafix&hl=en&gl=us&ct=clnk&cd=3

dmafix link
http://www.filesend.net/download.php?f=4211eaa7f1969676a2548b324df87191

Similar problems can happen with non-MS drivers for IDE controllers.

Chances are high that you would not be seeing this problem if you uninstalled those drivers and used the default Windows drivers.  Shit sux, but this is what a lot of Intel users had to do a few years ago when Intel Application Accelerator (just Intel's name for their UATA drivers) caused similar problems.  Try it and report back.

>>15

You mean my nForce drivers are doing this?

>>16 = OP post

OP here, I'm just going to connect my DVD burner to a USB. I should've done this before.

Christ. I did a lot of research on the topic. Seems that EVERYONE has DMA problems with their DVD recorder.

>>16
No, I mean your nForce drivers MIGHT be doing this, since it's been known to happen with other non-MS ATA controller drivers in Windows.

>>17
That's not going to help your speeds.

>>18
So do what they're doing:  CHECK YOUR FUCKING DRIVERS.

>>19

I checked them, they're Micosoft's drivers, actually. It says "Driver Provider: Microsoft" I tried "Roll Back Driver", it says the drivers were not changed. I check "Driver Details", looks like it's Windows.

And, USB will help my speeds, there's no bottleneck, because 12x doesn't go past 50MB/s.

>>20 And, USB will help my speeds, there's no bottleneck, because 12x doesn't go past 50MB/s.
FAIL.

>>21
http://www.osta.org/technology/dvdqa/dvdqa4.htm

Okay, so I connected 2 HDDs to the secondary IDE. They're having the PIO problem. That pretty much solves it, the IDE channel is the problem. (I won't troubleshoot this, because they're storage drives, not needing performance.) Thanks whoever tried to help me. I have my DVD drive connected via USB, and it works fine.

use linax faggots lol

DVD drive connected to USB, 0% CPU load, much faster, and I can play music without it interfering! (Compared to PIO.) This is megas awesome.

I am going to stop trolling for a few minutes. This only happens like once a week so listen up

You can really have some good times with your computer. You seriously should learn to fix it yourself. Nobody cares about how it runs but you. If you take it to some jackhole and tell him to fix it, it's not going to get done right. Even if you have a father/brother/boyfriend/whatever that you LIVE with who is a Lunix tard and fixes computers for a living, he can't fix it like you can. Even if you're mediocre at best dealing with hardware. Only you use it enough to make a true diagnosis of your computer's health.

Start troubleshooting. Rule everything you can out, then make an educated guess about the source. You know where all the components came from (or have at least a good guess). You know that hard disk failure is probably not the culprit because it's new. Did you install Windows from scratch on it, or did you use some utility to move it from your old disk (like MaxBlast/dd/etc.)? Can you consistantly get your disk to register in the BIOS? Can you make it consistantly fail? If either is true, you found the cause. Try replacing the IDE cable. If that fixes it, you found the cause. Try removing one stick of RAM and see if the problem happens still. If so, take it out and try the other. If still, try one stick in the other DDR channel or another slot. If that still doesn't fix it, you ruled out a RAM error too. Remove all PCI cards but the graphics. Remove all other disk drives. If this doesn't fix it, you've ruled out the possibility of a power drought (not enough power from the power supply causes brownouts that show this kind of behaviour).

Try anything else reasonable you can think of. If all else fails, you have a bad IDE channel on the motherboard. In that case, you need a new motherboard.

>Start troubleshooting. Rule everything you can out, then make an educated guess about the source.

I know that, I did everything I can to find the problem. I tried different cables, hard drives, DVD-ROM drives, advanced BIOS settings, DMA memory addresses I've messed with, etc.

>You know where all the components came from (or have at least a good guess).

I built it myself.


>You know that hard disk failure is probably not the culprit because it's new. Did you install Windows from scratch on it, or did you use some utility to move it from your old disk (like MaxBlast/dd/etc.)?

Multiple fresh Windows installs. No hard drive utilities besides my BIOS were used.

>Can you consistantly get your disk to register in the BIOS? Can you make it consistantly fail? If either is true, you found the cause. Try replacing the IDE cable. If that fixes it, you found the cause.

BIOS recognizes it fine, even showed that DMA was enabled, it was just DMA in Windows.

>Try removing one stick of RAM and see if the problem happens still. If so, take it out and try the other. If still, try one stick in the other DDR channel or another slot. If that still doesn't fix it, you ruled out a RAM error too.

Not worth it, besides, I did memtest, said everything was fine.

>Remove all PCI cards but the graphics. Remove all other disk drives. If this doesn't fix it, you've ruled out the possibility of a power drought (not enough power from the power supply causes brownouts that show this kind of behaviour).

I had no PCI cards in when I tested it.

>Try anything else reasonable you can think of. If all else fails, you have a bad IDE channel on the motherboard. In that case, you need a new motherboard.

Bad IDE channel, causes CRC errors while in DMA transfer mode. Not a problem, since I'm using my storage hard drives in PIO mode, which don't need performance. I hardly notice a difference, too.

>>27
please tell me you didnt srsly reply to the copypasta.

>>27
>>28
i lol'd

>>28,29
>Start troubleshooting. Rule everything you can out, then make an educated guess about the source.

I know that, I did everything I can to find the problem. I tried different cables, hard drives, DVD-ROM drives, advanced BIOS settings, DMA memory addresses I've messed with, etc.

>You know where all the components came from (or have at least a good guess).

I built it myself.


>You know that hard disk failure is probably not the culprit because it's new. Did you install Windows from scratch on it, or did you use some utility to move it from your old disk (like MaxBlast/dd/etc.)?

Multiple fresh Windows installs. No hard drive utilities besides my BIOS were used.

>Can you consistantly get your disk to register in the BIOS? Can you make it consistantly fail? If either is true, you found the cause. Try replacing the IDE cable. If that fixes it, you found the cause.

BIOS recognizes it fine, even showed that DMA was enabled, it was just DMA in Windows.

>Try removing one stick of RAM and see if the problem happens still. If so, take it out and try the other. If still, try one stick in the other DDR channel or another slot. If that still doesn't fix it, you ruled out a RAM error too.

Not worth it, besides, I did memtest, said everything was fine.

>Remove all PCI cards but the graphics. Remove all other disk drives. If this doesn't fix it, you've ruled out the possibility of a power drought (not enough power from the power supply causes brownouts that show this kind of behaviour).

I had no PCI cards in when I tested it.

>Try anything else reasonable you can think of. If all else fails, you have a bad IDE channel on the motherboard. In that case, you need a new motherboard.

Bad IDE channel, causes CRC errors while in DMA transfer mode. Not a problem, since I'm using my storage hard drives in PIO mode, which don't need performance. I hardly notice a difference, too.

>>28

How am I supposed to know it was copypasta? It sounded series. :<

Serious*

>>31
Of course it sounds serious, that's why we copy it!

>>33

:<

I AM ROTFLOL @ THIS LEGENDARY THREAD. thank you anonymous for wonderful times.