Re: Code 39 - Missing processor driver/mono sound



Perform the fix as described in the KB and then post back with any left over issue(s) that comes up. Reboot after doing the fix.

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"plastic" <plastic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:49C39AF1-A9D9-4A27-B1EE-4C9547F0E8C8@xxxxxxxxxxxxxxxx
Ok thankyou, but after reading the fix I couldn't see how it relates to a
missing processor driver, it's just talking about CD drives. Will performing
the fix anyway be fine?

"Peter Foldes" wrote:

Read the below and follow the fix. It should get you back on track

http://support.microsoft.com/default.aspx?scid=kb;en-us;314060

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"plastic" <plastic@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:3CF2726A-4C8F-4AFC-9293-C17037F96D99@xxxxxxxxxxxxxxxx
I have an ASUS A7N8X-E Deluxe mobo, and recently I installed 2 new SATA hard
drives (Seagate 80gb barracuda - OS/ seagate 160gb barracuda - Data).

I installed Win XP pro, upgraded to SP2 + updates etc. and the whole system
was working just fine, but after about 20 reboots or so I was experiencing
problems with boot-up. Suspecting I had some bad RAM, I took it into a
technician who confirmed that the RAM was faulty, and it was replaced.

However my initial problem was not fixed - this being: When I booted the PC
up after the power had been off for a while, it invariable took forever to
load up, and usually ran Checkdisk (deleting a few things along the way). I
have disconnected my Data drive, suspecting that this may be faulty, and so
far the PC has booted fine.
The technician explained to me over the phone that he suspected this disk
was causing the trouble.

One strange thing that has happened since having the PC back from the
technician though is that in Device Manager, my AMD Athlon XP 2600+ processor
is showing up with the exclamation mark warning, and a Code 39 "Windows
cannot load the device driver for this hardware. The driver may be corrupted
or missing. (Code 39)" error message. When I go to update the driver, it
says it has the most recent version. I've tried visiting the AMD website to
find an update but can't navigate the site very well. Also, in addition to
this, I am only getting mono sound output (and a lot of hard disk activity
'noise' through the speakers). Is there an easy way for me to troubleshoot
this problem? I suspect it's just a matter of rolling back some drivers or
something simple. I have also tried re-installing the mobo drivers from the
CD it came with.

Any help would be greatly appreciated, thanks.

.



Relevant Pages

  • Re: Beginning dump of physical memory
    ... When I reboot the error is goes away only to ... G> appear again next time when booting up. ... Usually in the BSOD there is information what driver failed with what exception. ... OTOH if it is one of the system components then running windows installation in repair mode can fix the problem. ...
    (microsoft.public.dotnet.general)
  • Re: 8.10 and the GeForce 6100 NVIDIA
    ... up in the poor X windows possible with the Ubuntu "nv" driver. ... Alas it didn't fix anything I could see. ... Had to use Ctrl-Alt-F1 to get to a place I can reboot, ...
    (Ubuntu)
  • 8.10 and the GeForce 6100 NVIDIA
    ... up in the poor X windows possible with the Ubuntu "nv" driver. ... Alas it didn't fix anything I could see. ... Had to use Ctrl-Alt-F1 to get to a place I can reboot, ...
    (Ubuntu)
  • Re: Mouse Problems
    ... getting the latest driver for your mouse. ... It certainly couldn't hurt ... The only way to get the mouse to work is to reboot. ... o how to fix the problem? ...
    (microsoft.public.windowsxp.hardware)
  • Linux 2.6.9-rc2
    ... ALSA update, and tons of small fixes pretty much ... work on trying to fix up the drivers as we go along, but they can be a bit ... Update unlink testing code in the usbtest driver ...
    (Linux-Kernel)

Loading