PDA

View Full Version : win xp x64 and dvdrw driver problem


danhua
05-03-2007, 03:56 PM
ok, we've just installed win xp x64 on one of our computers here at work. everything went well during the install process. they're were no hiccups or problems at all (amazingly).

now that we got the 64 bit os up and running, the internal dvd writer is not recognized. doesn't make sense though since it was the same drive we used to install the 64 bit os. we've even tried installing an external usb dvdrw drive, and still, no luck. seems like whatever generic/universal cd/dvd-rom driver that is installed is not working correctly. anyone here have this problem before?

here are the system specs:

asus k8n-sli socket 939 mobo
4gb ram
2 160gb seagate barracudas (raid 0)
sony dvd-r/rw model dw-q28a
nvidia quadro fx 1300 pci-e

any help is greatly appreciated. you guys here on the forum has been a great help to me in the past. i hope that you can help me with this issue as well.

danhua
05-04-2007, 06:09 PM
ok, i found the solution to this problem. it's basically a registry fix. no driver or firmware update will fix this problem. here's the fix for anyone else who may encounter this problem. it supposedly works for both 32 bit and 64 bit xp. you can search for error code 39 or 31 at the microsoft website.

Method 2: Manually delete the registry entries
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 (http://support.microsoft.com/kb/256986/) Description of the Microsoft Windows registry
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.Log on to Windows by using an account that has administrator rights and permissions. Then, follow these steps.
Step 1: Start Registry Editor
Click Start, click Run, type regedit, and then click OK. Registry Editor starts.
Step 2: Delete the UpperFilters registry entry
1. In Registry Editor, expand My Computer, and then expand HKEY_LOCAL_MACHINE.
2. Expand SYSTEM, and then expand CurrentControlSet.
3. Expand Control, and then expand Class.
4. Under Class, click {4D36E965-E325-11CE-BFC1-08002BE10318}.
5. In the right pane (topic area), click UpperFilters.

Note An UpperFilters.bak registry entry may also appear. To delete the UpperFilters registry entry, you must click UpperFilters and not UpperFilters.bak.
6. On the Edit menu, click Delete.
7. When you receive the following message, click Yes to confirm the deletion of the UpperFilters registry entry:
Are you sure you want to delete this value?
The UpperFilters registry entry is removed from the {4D36E965-E325-11CE-BFC1-08002BE10318} registry subkey.

Note Do not exit Registry Editor. You must have this program for the next step.
Step 3: Delete the LowerFilters registry entry
1. In Registry Editor, expand My Computer, and then expand HKEY_LOCAL_MACHINE.
2. Expand SYSTEM, and then expand CurrentControlSet.
3. Expand Control, and then expand Class.
4. Under Class, click {4D36E965-E325-11CE-BFC1-08002BE10318}.
5. In the right pane (topic area), click LowerFilters.

Note An LowerFilters.bak registry entry may also appear. To delete the LowerFilters registry entry, you must click LowerFilters and not LowerFilters.bak.
6. On the Edit menu, click Delete.
7. When you receive the following message, click Yes to confirm the deletion of the LowerFilters registry entry:
Are you sure you want to delete this value?
The LowerFilters registry entry is removed from the {4D36E965-E325-11CE-BFC1-08002BE10318} registry subkey.
8. Exit Registry Editor.

Step 4: Restart the computer

CGTalk Moderation
05-04-2007, 06:09 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.