winXP cannot start audio device, code 10

[Guest Bob I]

Look for ntbtlog.txt in the windows folder.

 

Cornelis Koger wrote:

> Machine: MSI K9VGM-V with AMD Athlon 64x2, 2,6 Ghz.

> O/S: WinXP-pro SP2

>

> This machine had the nasty habit to shutdown the power supply when the CPU

> temp neared 60C/150F. It caused all sorts of temporary files to be corrupted

> and cross linked, which were subsequently removed/truncated at the next

> boot.

> After one such occasion the on-board Realtek hi-def audio went mute.

>

> Enable/disable, remove and re-install does not help. All the drivers are

> there, but the hardware manager says "code 10" this device cannot start.

>

> Last known good config is no option, nor are roll back to previous drivers

> or system restore points.

> I solved the temperature problem by installing a giant Asus heatsink, but

> that doesn't bring the audio back.

>

> Now I want to see what goes wrong when XP loads the drivers, so I enabled

> boot logging at start-up. I expected a file called boot.log or bootlog.txt

> in the root, but I cannot find any such file, not in the root, not in the

> windows folders.

> Does anybody know where it should be located and what should be the file

> name?

>

>

[Guest Cornelis Koger]

winXP cannot start audio device, code 10

 

Machine: MSI K9VGM-V with AMD Athlon 64x2, 2,6 Ghz.

O/S: WinXP-pro SP2

 

This machine had the nasty habit to shutdown the power supply when the CPU

temp neared 60C/150F. It caused all sorts of temporary files to be corrupted

and cross linked, which were subsequently removed/truncated at the next

boot.

After one such occasion the on-board Realtek hi-def audio went mute.

 

Enable/disable, remove and re-install does not help. All the drivers are

there, but the hardware manager says "code 10" this device cannot start.

 

Last known good config is no option, nor are roll back to previous drivers

or system restore points.

I solved the temperature problem by installing a giant Asus heatsink, but

that doesn't bring the audio back.

 

Now I want to see what goes wrong when XP loads the drivers, so I enabled

boot logging at start-up. I expected a file called boot.log or bootlog.txt

in the root, but I cannot find any such file, not in the root, not in the

windows folders.

Does anybody know where it should be located and what should be the file

name?

[Guest Cornelis Koger]

Re: winXP cannot start audio device, code 10

 

Thanks, found the log, but it wasn't much help. Most of the 140k lists

drivers that were NOT loaded, probably because the system was waiting for

some process to complete.

The bootlog from win98 was much more detailed and showed load init,

enumeration, init complete etc.

Maybe reinstalling winXP is the only solution to get the sound back.

 

"Bob I" <birelan@yahoo.com> wrote in message

news:O8AfyNmGJHA.4760@TK2MSFTNGP05.phx.gbl...

>

> Look for ntbtlog.txt in the windows folder.

>

> Cornelis Koger wrote:

>

>> Machine: MSI K9VGM-V with AMD Athlon 64x2, 2,6 Ghz.

>> O/S: WinXP-pro SP2

>>

>> This machine had the nasty habit to shutdown the power supply when the

>> CPU temp neared 60C/150F. It caused all sorts of temporary files to be

>> corrupted and cross linked, which were subsequently removed/truncated at

>> the next boot.

>> After one such occasion the on-board Realtek hi-def audio went mute.

>>

>> Enable/disable, remove and re-install does not help. All the drivers are

>> there, but the hardware manager says "code 10" this device cannot start.

>>

>> Last known good config is no option, nor are roll back to previous

>> drivers or system restore points.

>> I solved the temperature problem by installing a giant Asus heatsink, but

>> that doesn't bring the audio back.

>>

>> Now I want to see what goes wrong when XP loads the drivers, so I enabled

>> boot logging at start-up. I expected a file called boot.log or

>> bootlog.txt in the root, but I cannot find any such file, not in the

>> root, not in the windows folders.

>> Does anybody know where it should be located and what should be the file

>> name?

>